1) thinks in JMS for decouple APPs.
2) SLSB not support @Remove. Remove is a SFSB event.
Thank you for your reply.
I have found a solution for decouple my App with the SLSB, but i want a way to kill that SLSB that is consuming 100% of CPU. Is there a way to signal the JBoss to kill that instance that is not functioning well ?
Because i am dependent of external SLSB which are on my JBoss, i need a way to kill those that are not responding for a large period of time.
My tests used the TransactionManager to reduce the transaction timeout, but that did not result. The timeout has passed and the resources were not freed.
Now i am trying to found a way of having the SLSB reference a put it a NULL in order to kill it, but that is not working as well.....
I am becoming without solutions to solve this problem....
I am having similar problem with SLSB calls that takes too much time and memory resources that renders the entire server useless. Other than good programming and testing (alas!), any way to deal with such problem, in production system?
Did you find solution to your problem? If so, can you share please? O/w, any workarounds?