Have you considered breaking up your EJB into two EJBs joined via a JMS queue?
Basically have the first EJB generate the messages for the web service, and as
it generates say 100 web service requests, it tosses those requests onto a
queue instead of making those requests itself. Then have
Hey mclu,
sorry, but I have no solution. I raised the Transaction Timeout for the EJB
Method sending the messages and
accept that sometimes the method will be aborted because of a timeout. In order
to avoid the rollback of the successfuly sended messages I use an EJB Method to
send one single
Have you solved it?
I have a similar issue but I don't want to increase the timeout for the 97%
mainstream handling like you
Greets
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4233281#4233281
Reply to the post :
