Hi Folks,
I am trying to invoke the same method on the same EJB object from multiple concurrent clients. But JBoss seems to not like it .. I get the following exception on the client side ...
Connection refused to host: <<ip address of the Jboss Server host>>; nested exception is:
java.net.ConnectException: Connection refused: no further information
Any clues on why this might happen or is it just that JBoss is not scalable enough ????
And also I haven't had much success using Transactions in JBoss with Concurrent Clients. Everytime I try I get deadLock exceptions and XA_NOTA and XA_PROTA error codes ..(no clue what the heck they mean though ...). I have tried TX_REQUIRED, TX_REQUIRES_NEW, TX_MANDATORY .. with concurrent clients ... I have modified the jboss.jcml file with different combinations of max/min connections and timeout values ..but nothing seems to work ..I found out that others had similar problems ..but nobody seems to have a clear idea of whats going on here ... But TX_NEVER works though ..which means that the JBoss TxManager is not handling concurrency well ... Is this a known issue and has been noted as a bug which will be fixed in future releases ????
I have been using JBoss2.4.1
Thanks
-Prashanth
