| Summary: | BRMS must be installed in production config - or jgroups must be installed into default config - to avoid non-fatal error written to log | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | Documentation | Assignee: | Dana Mison <dmison> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0 GA, 5.0.1 | ||
| Target Milestone: | --- | ||
| Target Release: | 5.1.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/BRMS-222 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-11-23 13:35:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Works fine when deploying to JBoss AS 4.2.3 into the default config, which doesn't contain jgroups.jar. Link: Added: This issue related JBPAPP-1717 Link: Added: This issue is related to JBPAPP-2765 We need to document that when deploying brms into the default configuration, to avoid this warning user should copy the jgroups.jar from server/production/lib to server/default/lib. Release Notes Text: Added: test Release Notes Text: Removed: test Release Notes Docs Status: Added: Not Yet Documented Writer: Added: Darrin updated the known issue from 5.0.2 to include workaround Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Added: The JBoss Enterprise BRMS Platform logs several errors if it is deployed to the default server profile of JBoss Enterprise Application Platform. This is because the jgroups.jar JAR file is not deployed to the default server profile. This does not have any functional impact but the error messages can be avoided by deploying the jgroups.jar JAR file from the production server profile. To do this, copy the file jgroups.jar from the JAVA_HOME/server/production/lib directory to the JAVA_HOME/server/default/lib directory. |
Affects: Documentation (Ref Guide, User Guide, etc.) Date of First Response: 2009-09-05 05:38:03 securitylevel_name: Public If BRMS 5.0 or 5.0.1 is installed into an EAP server profile (the default profile) that does not include jgroups.jar, this exception is written to the server log: java.lang.NoClassDefFoundError: org/jgroups/MembershipListener at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) There does not seem to any functional impact on BRMS. This is not a regression in 5.0.1