Bug 724277 (BRMS-222) - BRMS must be installed in production config - or jgroups must be installed into default config - to avoid non-fatal error written to log
Summary: BRMS must be installed in production config - or jgroups must be installed in...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-222
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Documentation
Version: 5.0.0 GA,5.0.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.1.0 GA
Assignee: Dana Mison
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-03 18:23 UTC by Len DiMaggio
Modified: 2010-11-23 13:35 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-23 13:35:15 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-222 0 Major Closed BRMS must be installed in production config - or jgroups must be installed into default config - to avoid non-fatal erro... 2012-11-16 14:27:46 UTC
Red Hat Issue Tracker JBPAPP-1717 0 Major Closed NoClassDefFoundError: org/jgroups/MembershipListener during deployment of seam example to default profile 2012-11-16 14:27:46 UTC

Description Len DiMaggio 2009-09-03 18:23:38 UTC 
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
Comment 1 Jaroslaw Kijanowski 2009-09-05 09:38:03 UTC 
Works fine when deploying to JBoss AS 4.2.3 into the default config, which doesn't contain jgroups.jar.
Comment 2 Jaroslaw Kijanowski 2009-10-07 16:57:38 UTC 
Link: Added: This issue related JBPAPP-1717
Comment 3 dereed 2010-04-21 20:30:16 UTC 
Link: Added: This issue is related to JBPAPP-2765
Comment 4 Tihomir Surdilovic 2010-09-10 19:58:41 UTC 
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.
Comment 5 Dana Mison 2010-10-27 03:06:31 UTC 
Release Notes Text: Added: test
Comment 6 Dana Mison 2010-10-27 03:13:19 UTC 
Release Notes Text: Removed: test
Comment 7 David Le Sage 2010-11-03 05:13:29 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Writer: Added: Darrin
Comment 8 Dana Mison 2010-11-12 04:04:57 UTC 
updated the known issue from 5.0.2 to include workaround
Comment 9 Dana Mison 2010-11-12 04:04:57 UTC 
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.
Comment 10 Petr Široký 2010-11-23 13:35:15 UTC 
Verified at http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html/5.1.0_Release_Notes/index.html
Note You need to log in before you can comment on or make changes to this bug.