Bertrand, >From the description in the JBoss AS guide, section 6.2, the message cache >holds messages in memory until space usage passes defined limits. At that >time, the cache starts persisting messages. I guess this explains the behavior >you are experiencing.
Regarding the use of queues, here is how it works: An inbound message activity (receive, pick or onMessage event) listens for messages on the queue assigned to its partner link. When a SOAP envelope arrives at the endpoint associated with the partner link, the port component we configured in Web services deployment descriptor performs the steps below. Determine which operation, among those listed in the WSDL port type, is being requested. Retrieve the WSDL message that describes the operation input and the BPEL property aliases associated to that message. Extract the part values from the SOAP envelope and put them in the body of a JMS message. Calculate the correlation property values from the part values and set them as property values into the JMS message. Send the JMS message to the queue assigned to the partner link. The JMS implementation delivers the message to a listening activity whose selector matches the message properties. Hope this helps. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3948242#3948242 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3948242 ------------------------------------------------------- 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
