Hello community,
i have persisted somes messages in the jms_messages database.
What i'm finding strange is that the messages are persisted in the DB only when
i stop and restart the testQueue in the JMX Console. Only if i do this
Messages are persisted and clients receive some answer back
(java.net.SocketTimeoutException: Read timed out .... ) only after a timeout.
This means Alex's assumptions where wright: If every think works well nothink
will happen. Message will be persist only in case of failure (Queue not
reachable).
In the jmx console browsing the testQueu the method listMessages() gives
following informations back:
[org.jboss.mq.SpyObjectMessage {
| Header {
| jmsDestination : QUEUE.testQueue
| jmsDeliveryMode : 2
| jmsExpiration : 0
| jmsPriority : 4
| jmsMessageID : ID:3-11486715531501
| jmsTimeStamp : 1148671553150
| jmsCorrelationID: null
| jmsReplyTo : QUEUE.JMS_TQ3
| jmsType : null
| jmsRedelivered : false
| jmsProperties : {_$partnerLinkId=3, _$operationName=sayHello}
| jmsPropReadWrite: false
| msgReadOnly : true
| producerClientId: ID:3
| }
| }, org.jboss.mq.SpyObjectMessage {
| Header {
| jmsDestination : QUEUE.testQueue
| jmsDeliveryMode : 2
| jmsExpiration : 0
| jmsPriority : 4
| jmsMessageID : ID:3-11486716083902
| jmsTimeStamp : 1148671608390
| jmsCorrelationID: null
| jmsReplyTo : QUEUE.JMS_TQ4
| jmsType : null
| jmsRedelivered : false
| jmsProperties : {_$partnerLinkId=3, _$operationName=sayHello}
| jmsPropReadWrite: false
| msgReadOnly : true
| producerClientId: ID:3
| }
| }, org.jboss.mq.SpyObjectMessage {
| Header {
| jmsDestination : QUEUE.testQueue
| jmsDeliveryMode : 2
| jmsExpiration : 0
| jmsPriority : 4
| jmsMessageID : ID:3-11486716315733
| jmsTimeStamp : 1148671631573
| jmsCorrelationID: null
| jmsReplyTo : QUEUE.JMS_TQ5
| jmsType : null
| jmsRedelivered : false
| jmsProperties : {_$partnerLinkId=3, _$operationName=sayHello}
| jmsPropReadWrite: false
| msgReadOnly : true
| producerClientId: ID:3
| }
| }]
|
The table jms_messages:
(MESSAGEID, DESTINATION, TXID, TXOP, MESSAGEBLOB) has values: (0,
QUEUE.testQueue, Null, A, BLOB),
(1, QUEUE.testQueue, Null, A, BLOB),
(2, QUEUE.testQueue, Null, A, BLOB).
In the JBPM BPEL 1.0_UserGuide it's says :
| The BPEL extension uses JMS to ensure orderly delivery of incoming messages
to the right
| process instances. Each partner link in a process definition is assigned a
queue. An inbound
| message activity (receive, pick or onMessage event) listens for messages on
the queue
| assigned to its partner link. When a SOAP message arrives at the port
component that
| represents that partner link, it is sent to the same queue. The selection
feature of JMS routes it
| to the right receiver.
|
| If i understand this well all process partners (clients) listen on the same
queue testQueue that's why we have for each persisted message the same
destination QUEUE.testQueue. But it seams to be that the server (May be process
instance) identifies the clients with the internalID jmsReplyTo :
QUEUE.JMS_TQ3, jmsReplyTo: QUEUE.JMS_TQ4, jmsReplyTo: QUEUE.JMS_TQ5 .
|
| My question hier is to know the function of the jmsReplyTo field. Is it
generated form the server to distinguish clients? All this informations are not
clear for me (How different clients are bound to the same queue and how the
process instance can identify the wright client ).
|
| I need your help to understand how the communication works according to
process instances. Any suggestion, document reference or any link will help.
|
|
| Thanks in advance
|
| Bertrand Njipwo
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947018#3947018
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947018
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
