Closed glassfishrobot closed 15 years ago
@glassfishrobot Commented ksak said: The routing of a particular rar to the MDB container is handled by the connector code so we need the connector team to investigate this further.
@glassfishrobot Commented ksak said: Also changing to P2.
@glassfishrobot Commented @h2002044 said: Created an attachment (id=3531) analysis
@glassfishrobot Commented @h2002044 said: I was able to setup active-mq with GlassFish, deploy the .rar, create admin-objects, connector-resource, pools and send/receive messages. Attached the (analysis.tar.gz) GlassFish server.log, active-mq.log, ejb-jar.xml, sun-ejb-jar.xml.
GlassFish server.log will show the messages as :
"[#|2009-10-15T22:37:25.018+0530|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=18;_ThreadName=p: thread-pool-1; w: 5;| MessageBean:: onMessage :: Got message!!!ActiveMQTextMessage
{commandId = 6, responseRequired = true, messageId = ID:matrix-42819-1255626443998-0:0:1:1:1, originalDestination = null, originalTransactionId = null, producerId = ID:matrix-42819-1255626443998-0:0:1:1, destination = queue://Send, transactionId = null, expiration = 0, timestamp = 1255626444705, arrival = 0, brokerInTime = 1255626444708, brokerOutTime = 1255626444710, correlationId = null, replyTo = null, persistent = true, type = null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = null, content = null, marshalledProperties = null, dataStructure = null, redeliveryCounter = 0, size = 0, properties = null, readOnlyProperties = true, readOnlyBody = true, droppable = false, text = foo #1}
|#] "
active-mq logs will also show appropriate information.
@glassfishrobot Commented File: analysis.tar.gz Attached By: @h2002044
@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-7432
@glassfishrobot Commented Reported by bjb
@glassfishrobot Commented Marked as incomplete on Thursday, October 15th 2009, 3:18:27 am
A MDB listening fpr message on a physical ActiveMQ queue is never triggered when message arrive on the queue.
1- Setup a ActiveMQ (5.2) server (just download and start activemq.sh) 2- Create the queue in activemq "test.queue" 3- Deploy the ActiveMQ RAR in GF 4- Create in GF the admin objects for the ActiveMQ items 5- Create a MDB nammed TestMDB with annotation @MessageDriven(mappedName = "jms/TestQueue") and display the message in a log 6- Deploy a sun specific descriptor like :
7- Build and deploy the EAR : you get no error message at all ! 8- Go in the ActiveMQ admin and create a message
Nothing will happen No consumer is shown ... you can undeploy/redeploy no message.
Either there is a mistake/misunderstanding from us or we have a serious issue there in GF.
FYI, we have tried to solve this blocking issue during almost a week with different strategy but all of them leads to dead-ends.
Rgs, JB
Environment
Operating System: All Platform: Linux
Affected Versions
[9.1peur2]