Hide Forgot
Date of First Response: 2007-11-20 05:54:16 project_key: SOA These instances of jboss-messaging.jar are included in the standalone and AS IR6 SOA-P builds: [ldimaggi@ldimaggi default]$ find /opt/IR6/ -name jboss-messaging.jar -ls 823394 1060 -rw-r--r-- 1 ldimaggi ldimaggi 1076255 Oct 25 20:35 /opt/IR6/jboss-soa-p.4.2.0/server/production/lib/jboss-messaging.jar 822829 1060 -rw-r--r-- 1 ldimaggi ldimaggi 1076255 Oct 25 20:34 /opt/IR6/jboss-soa-p.4.2.0/server/default/lib/jboss-messaging.jar 822504 1060 -rw-r--r-- 1 ldimaggi ldimaggi 1076255 Oct 25 20:35 /opt/IR6/jboss-soa-p.4.2.0/server/all/lib/jboss-messaging.jar 4849731 1044 -rw-r--r-- 1 ldimaggi ldimaggi 1057500 Nov 16 15:31 /opt/IR6/jboss-soa-p-standalone.4.2.0/server/default/lib/jboss-messaging.jar The VERSION file for both versions of jboss-messaging.jar contains the same information: jboss.messaging.jmsVersion=1.1 jboss.messaging.jmsMajorVersion=1 jboss.messaging.jmsMinorVersion=1 jboss.messaging.jmsProviderName=JBoss Messaging jboss.messaging.providerVersion=1.4.0.GA jboss.messaging.providerMajorVersion=1 jboss.messaging.providerMinorVersion=4 jboss.messaging.providerIncrementingVersion=18 I noticed this problem because the error messages displayed at startup were different: [ldimaggi@ldimaggi tmp]$ grep -i sucker /opt/IR6/jboss-soa-p.4.2.0/server/all/log/server.log 2007-11-19 16:17:54,434 WARN [org.jboss.jms.server.security.SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the userguide for instructions on how to do this. [ldimaggi@ldimaggi tmp]$ grep -i sucker /opt/IR6/jboss-soa-p-standalone.4.2.0/server/default/log/server.log 2007-11-19 16:27:35,219 WARN [org.jboss.jms.server.security.SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! ** This is an old message - resolved here: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
Is this not an EAP issue since we should be getting JBM from there now.
Link: Added: This issue is incorporated by SOA-161
updated jar now in build jboss.messaging.providerIncrementingVersion=19
Verified fixed in IR8 [ldimaggi@ldimaggi IR8]$ find /opt/IR8 -name jboss-messaging.jar -ls 65615 1084 -rw-r--r-- 1 ldimaggi ldimaggi 1098393 Nov 29 18:36 /opt/IR8/jboss-soa-p.4.2.0/jboss-as/server/production/lib/jboss-messaging.jar 884967 1084 -rw-r--r-- 1 ldimaggi ldimaggi 1098393 Nov 29 18:37 /opt/IR8/jboss-soa-p.4.2.0/jboss-as/server/default/lib/jboss-messaging.jar 5668926 1084 -rw-r--r-- 1 ldimaggi ldimaggi 1098393 Nov 29 18:37 /opt/IR8/jboss-soa-p.4.2.0/jboss-as/server/all/lib/jboss-messaging.jar 9182640 1084 -rw-r--r-- 1 ldimaggi ldimaggi 1098393 Dec 5 17:28 /opt/IR8/jboss-soa-p-standalone.4.2.0/server/default/lib/jboss-messaging.jar