[jboss-user] [JBoss Messaging] - Message selector and consuming messages

2009-04-13 Thread eontech
Hello Everyone, We have a requirement of two queues. One primary and other secondary i.e. if a message can be processed immediately, it is sent to primary queue else it is sent to secondary queue. Both queues are consumed by different MDBs and all transactions work in container transaction. Fo

[jboss-user] [JBoss Messaging] - Re: Sending Messages from EJB using container transaction

2009-04-08 Thread eontech
Thank you very much Frank for your response. We want to know if using java:JmsXA won't affect the performance or what would be the performance impact if we use this factory. Best Regards, Abhishek View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224242#4224242

[jboss-user] [JBoss Messaging] - Sending Messages from EJB using container transaction

2009-04-06 Thread eontech
Hello Everyone, We have a requirement to send thousands of messages using EJB in a day. Thus every time a need arises to send a message, we have a dedicated session bean which will post message to the queue as part of EJB (container) transaction. We are using JBoss EAP 4.3.0. Our question is w

[jboss-user] [JBossWS] - Problem in interpreting SOAP message on JBoss EAP 4.3.0

2008-11-18 Thread eontech
Hi All, We are using XFire to invoke webservices. We were using Jboss AS 4.0.5 earlier to deploy our webservices. This combination was working fine. Now we have upgraded to JBossEAP 4.3.0. When we generate webservice clients via XFire to test webservices deployed on EAP, the parameters passed ar

[jboss-user] [Installation, Configuration & DEPLOYMENT] - User Agent is NULL in Jboss EAP (JBoss 4.3.0.GA_CP011)

2008-09-23 Thread eontech
Whenever I start the EAP with default settings i.e. server is bound to localhot, the user-agent field in HTTP Request headers comes as null. If I start the EAP bounded to machine's IP address i.e. using -b option, it works well. On debugging I found that if we start the EAP with default options,