users@glassfish.java.net

Re: Queueing jobs for processing in their own thread/transaction?

From: <glassfish_at_javadesktop.org>
Date: Tue, 10 Feb 2009 14:45:15 PST

Ok.

I know I have a queue and a topic working in JMS. We're constantly getting something like:

[#|2009-02-10T13:47:58.835-0800|INFO|sun-appserver9.1|javax.resourceadapter.mqjm
sra.outbound.connection|_ThreadID=20;_ThreadName=Timer-8;|MQJMSRA_MC1101: constr
uctor:Created mcId=114766:xacId=4133494539453853184:Using xacf config={imqDefaul
tUsername=guest, imqBrokerHostName=localhost, imqSetJMSXUserID=false, imqJMSExpi
ration=0, imqQueueBrowserRetrieveTimeout=60000, imqSSLProviderClassname=com.sun.
net.ssl.internal.ssl.Provider, imqConfiguredClientID=, imqSSLIsHostTrusted=false
, imqSetJMSXProducerTXID=false, imqJMSDeliveryMode=PERSISTENT, imqAddressListBeh
avior=RANDOM, imqEnableSharedClientID=false, imqAckOnProduce=, imqConnectionURL=
http://localhost/imq/tunnel, imqConnectionFlowLimit=1000, imqSetJMSXAppID=false,
 imqAddressListIterations=3, imqBrokerServicePort=0, imqSetJMSXRcvTimestamp=fals
e, imqReconnectInterval=5000, imqConnectionType=TCP, imqLoadMaxToServerSession=t
rue, imqSetJMSXConsumerTXID=false, imqAddressList=localhost:7676, imqOverrideJMS
DeliveryMode=false, imqPingInterval=30, imqDefaultPassword=guest, imqAckOnAcknow
ledge=, imqJMSPriority=4, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqOverrid
eJMSPriority=false, imqConsumerFlowLimit=1000, imqBrokerHostPort=7676, imqReconn
ectEnabled=true, imqConnectionFlowCount=100, imqReconnectAttempts=3, imqConnecti
onFlowLimitEnabled=false, imqAckTimeout=0, imqBrokerServiceName=, imqOverrideJMS
Expiration=false, imqConnectionHandler=com.sun.messaging.jmq.jmsclient.protocol.
tcp.TCPStreamHandler, imqDisableSetClientID=false, imqOverrideJMSHeadersToTempor
aryDestinations=false, imqConsumerFlowThreshold=50}|#]

spammed in our logs, but my understanding is that this is harmless.

I also don't drive it super hard, but it is reliable (it's mostly for event notifications). I, also, had to set it LOCAL. It flat out didn't work otherwise.

Besides allowing only a single MDB on the Queue, it's pretty much generic and default all the way through.

We're running: Sun Java System Application Server 9.1_02 (build b04-fcs)

Don't know if that's helpful at all...

I agree that the connector should "just work".
[Message sent by forum member 'whartung' (whartung)]

http://forums.java.net/jive/thread.jspa?messageID=331148