Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beanmill freezes on selection of "delete filtered Events" if events are received. #5

Open
og0815 opened this issue Jan 5, 2015 · 12 comments

Comments

@og0815
Copy link

og0815 commented Jan 5, 2015

A Bug that exists for a long time. Beanmill freezes if you have a producer of many log infomation (e.g. hibernate in debug mode), continually receiving these events, selecting a node and change the level to something higher (e.g. info or warning) and than select delete filtered Events.

@mscholl
Copy link
Member

mscholl commented Jan 7, 2015

Unfortunately you're right :) This is actually a known issue and is caused by the underlying lumbermill framework. We already had a look into it but could not come up with a fast solution. It seems rather complicated due to some design decision made there... Unfortunately we did not have the time to really dive in yet, however, patches are welcome :)

@mscholl
Copy link
Member

mscholl commented Jan 7, 2015

BTW the best method so far (if you receive heavy load of messages) is to temporarily stop logging. Some messages may then be missing though. If "delete filtered events" is activated before the logging starts this issue should not occur, too.

@og0815
Copy link
Author

og0815 commented Jan 8, 2015

Hi, I would like to help, but already stuck at the clean/install. Either I cannot reach your repositories or some old artefacts are not found. Try to build it on a clean machine and you might see it.
Also I would recommend a profile for a nbm configuration without the keystore.

@mscholl
Copy link
Member

mscholl commented Jan 8, 2015

Could you post the error that you get?

@mscholl
Copy link
Member

mscholl commented Jan 8, 2015

I assume that the error that you get is ssl related: the repo that we use is currently "secured" by a self-signed certificate that mvn won't accept unless you use mvn v3.0.4. We didn't have the spare money to invest in a official certificate that is also accepted by the JVM out of the box. So I suggest that you use mvn v3.0.4 to build as adding the certificate to the keystore is ... not as smooth as it should be.

@og0815
Copy link
Author

og0815 commented Jan 9, 2015

Debian Jessie, Oracle jdk 1.8.0_u25, maven 3.0.5

[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project de.cismet:beanmill:2.7-SNAPSHOT (/home/oliver.guenther/Development/test/beanmill/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not transfer artifact de.cismet:cismet-parent:pom:2.0 from/to cismet-repo (https://repo.cismet.de/repo): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target and 'parent.relativePath' points at wrong local POM @ line 5, column 13 -> [Help 2]

Debian Wheeze, Oracle jdk 1.8.0_u25, maven 3.0.4

[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project de.cismet:beanmill:2.7-SNAPSHOT (/root/beanmill/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not transfer artifact de.cismet:cismet-parent:pom:2.0 from/to cismet-repo (https://repo.cismet.de/repo): peer not authenticated and 'parent.relativePath' points at wrong local POM @ line 5, column 13 -> [Help 2]

Aren't Certificates form https://www.startssl.com enought ?

@mscholl
Copy link
Member

mscholl commented Jan 9, 2015

Unfortunately not, the startssl certificates are fine for browsers, however, not for the JVM. The issue seems to be ssl related though, I'll have to create a maschine that actually runs jdk8 to test as I yesterday only had a maschine with jdk7. I'll come back to you as soon as I know more :)

@og0815
Copy link
Author

og0815 commented Jan 9, 2015

Debian Jessie,
Apache Maven 3.0.5
Maven home: /usr/share/maven
Java version: 1.7.0_72, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-oracle/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "3.16.0-4-amd64", arch: "amd64", family: "unix"

[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project de.cismet:beanmill:2.7-SNAPSHOT (/home/oliver.guenther/Development/test/beanmill/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not transfer artifact de.cismet:cismet-parent:pom:2.0 from/to cismet-repo (https://repo.cismet.de/repo): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target and 'parent.relativePath' points at wrong local POM @ line 5, column 13 -> [Help 2]

Debian Wheeze
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.7.0_72, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.2.0-4-amd64", arch: "amd64", family: "unix"

[INFO] Scanning for projects...
Downloading: https://repo.cismet.de/repo/de/cismet/cismet-parent/2.0/cismet-parent-2.0.pom
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project de.cismet:beanmill:2.7-SNAPSHOT (/root/beanmill/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not transfer artifact de.cismet:cismet-parent:pom:2.0 from/to cismet-repo (https://repo.cismet.de/repo): peer not authenticated and 'parent.relativePath' points at wrong local POM @ line 5, column 13 -> [Help 2]

No change.

@mscholl
Copy link
Member

mscholl commented Jan 9, 2015

are you sure that you use mvn 3.0.4? this seems pretty odd, in the meantime I tried on fresh win7/jdk8/mvn3.0.4 and on fresh deb7.7/jdk8/mvn3.0.4. Both is fine.

@og0815
Copy link
Author

og0815 commented Jan 12, 2015

May be the debian package. I think it simpler to just close the issue for now.

@mscholl
Copy link
Member

mscholl commented Jan 15, 2015

Hm, don't know what you mean with debian package... And I'm really curious what is the issue here as the goal is to have any project buildable for anyone anytime (with mvn 3.0.4 currently)

@p-a-s-c-a-l
Copy link
Member

Suggestion: If this bug cannot be fixed, the "delete filtered Events" selection box should be disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants