2:09 a.m.
I've been working on migrating from JBossMQ to JBossMessaging with JBoss AS 4.2.2.GA.
I'm using JBossMessaging 1.4.0.SP3.
Our JBoss AS is completely configured through Maven. We put the JBoss AS as a zip artifact
in a local repository; extract it from there using the maven-depenency-plugin and do some
assembling to get the correct libraries in the correct locations with the
maven-assembly-plugin. Configuration is done through maven filtering the JBoss XML
configuration files. All this worked perfectly before I started the migration to
JBossMessaging from JBossMQ.
Seeing as so much has been customized about our JBoss AS, I went about this manually
rather than using the script.
Unfortunately when actually launching our application in the AS, JMS starts complaining
about the fact that it cannot authenticate the user null. I'm assuming I somewhere
forgot to mention what user it's supposed to be defaulting to? However, such a
"default" user had not been configured for JBossMQ either, as far as I know.
| * The exception: http://www.lhunath.lyndir.com/stuff/jboss.log
| * Trace messages on org.jboss.jms & org.jboss.ejb.plugins.jms:
http://www.lhunath.lyndir.com/stuff/trace.log
|
Here's an overview of what exactly I did to replace JBossMQ by JBossMessaging:
| * I removed the jbossmq.jar from server/default/lib.
| * I moved jms-ds.xml and jms-ra.rar from server/default/deploy/jms into
server/default/deploy and removed the server/default/deploy/jms directory.
| * In server/default/conf/standardjboss.xml I toggled CreateJBossMQDestination to
false .
| * In server/default/conf/login-config.xml I commented the JBossMQ application-policy
and added one for JBossMessaging: http://www.lhunath.lyndir.com/stuff/login-config.xml
| * In server/default/conf/jboss-service.xml I removed
jboss.mq:service=DestinationManager
| * Removed server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
and replaced it with the mysql-persistence-service.xml from the examples directory.
Modifications made to the mysql-persistence-service.xml include changing of DefaultDS to
the DS we use and removed all POPULATE.TABLES.X instances except for the guest ones. See
http://www.lhunath.lyndir.com/stuff/mysql-persistence-service.xml.
|
Any files not mentioned are kept at their defaults.
Additionally, the SAR that configures our MDBs has the following done to
META-INF/jboss-service.xml:
| * Added the following to the top of the file:
| <loader-repository>jboss.messaging:loader=ScopedLoaderRepository
| |
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
| | </loader-repository>
| * Diff of our queue configuration:
| | - <mbean code="org.jboss.mq.server.jmx.Queue"
| | - name="safeonline:service=Queue,name=outgoing-email">
| | - <attribute
name="JNDIName">queue/outgoing-email</attribute>
| | - <depends
optional-attribute-name="DestinationManager">
| | - jboss.mq:service=DestinationManager
| | - </depends>
| | + <mbean code="org.jboss.jms.server.destination.QueueService"
| | + name="safeonline:service=Queue,name=outgoing-email"
| | + xmbean-dd = "xmdesc/Queue-xmbean.xml">
| | + <attribute
name="JNDIName">queue/outgoing-email</attribute>
| | + <depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| | + <depends>jboss.messaging:service=PostOffice</depends>
| | </mbean>
| | - <mbean code="org.jboss.mq.server.jmx.Queue"
| | - name="safeonline:service=Queue,name=auditBackend">
| | - <attribute
name="JNDIName">queue/auditBackend</attribute>
| | - <depends
optional-attribute-name="DestinationManager">
| | - jboss.mq:service=DestinationManager
| | - </depends>
| | + <mbean code="org.jboss.jms.server.destination.QueueService"
| | + name="safeonline:service=Queue,name=auditBackend"
| | + xmbean-dd = "xmdesc/Queue-xmbean.xml">
| | + <attribute
name="JNDIName">queue/auditBackend</attribute>
| | + <depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| | + <depends>jboss.messaging:service=PostOffice</depends>
| | </mbean>
| |
|
| Do request any further information required to diagnose the problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143059#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...