-
1. Re: JBoss Messenger upgrade to 1.4.2. GA - MDBs suddenly wan
jaikiran Feb 13, 2009 5:30 AM (in response to mhoennig)Please post more details including the configuration files that you use. Also please post the console logs. If the QueueStatusReceiver is configured through annotations, then post that code or else post the ejb-jar.xml and jboss.xml for that EJB.
-
2. Re: JBoss Messenger upgrade to 1.4.2. GA - MDBs suddenly wan
mhoennig Feb 13, 2009 7:13 AM (in response to mhoennig)I can hardly post all my JBoss configuration. The point is: It DID WORK with JBoss Messenger 1.4.0 and I just upgraded to 1.4.2. I have not changed my other config at all.
But anyway: Here my annotations (... is just a placeholder):
@MessageDriven(activationConfig=
{
@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination", propertyValue="queue/...Status"),
@ActivationConfigProperty(propertyName="acknowledgeMode", propertyValue="Auto-acknowledge")
} )
public class QueueStatusReceiver
implements javax.jms.MessageListener
Here the relevant part of boss-messaging.sar/destinations-service.xml:
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=...Status"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer
jboss.messaging:service=PostOffice
Which other of the vast amount of configs would you need? As I said, there is not a single word of MQ in any config file. Not a single! And yet, some JBoss part suddenly is asking for it.
Maybe one hint: I am using sslbisocket, but I also used it with 1.4.0 and it did work (just not with PostgreSQL 8.3 anymore - but that's a different problem). -
3. Re: JBoss Messenger upgrade to 1.4.2. GA - MDBs suddenly wan
mhoennig Feb 13, 2009 7:16 AM (in response to mhoennig)Also the log of startup is HUGE. Any hints what to look for in the log?
-
4. Re: JBoss Messenger upgrade to 1.4.2. GA - MDBs suddenly wan
jaikiran Feb 14, 2009 3:44 AM (in response to mhoennig)Its a WARN message. Is it affecting your application in any way? Also are there any ERROR or exceptions? Around 10 lines before that WARN message might give some hints.