I have executed your examples... and I realized you have several debug options set.
so, few questions for you:
I - Have you used debugging during your tests?
II - Also.. have you seen this sort of message on server?
"16:09:52,005 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client 3j011-dg4k19-fc3uylzr-1-fc3uymin-4, jmsClientID=b-7omyu3cf-1-rzlyu3cf-91k4gd-110j3. It is possible the client has exited without closing its connection(s) or the network has failed. All connection resources corresponding to that client process will now be removed."
III - If you start another client, Long-live-queue-consumer, would you see messages arriving?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125313#4125313
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125313
We're getting an identical error when an application deployed on JBoss422 tries to get a remote interface to an ejb that's deployed on JBoss404. I suspect that there has been a change in the org.jboss.ejb3.remoting.BaseRemoteProxy. We have an isolated class loader as default on our JBoss servers and if we put the jboss-ejb3-client.jar that is deployed on JBoss404 into the ear that is deployed on JBoss422 we no longer get the error.
However, now we can't access 422 specific classes and get "JBossProxy not visible from the classloader" errors when trying to access the objects on the 422 server.
It would seem that if you want to move from JBoss404 to 422, you will need to update ALL of the servers at the same time because of these incompatibilities.
There doesn't seem to be any problem with using remote queues however.
If anyone out there can tell me I'm wrong I'd be most pleased to know because for now I'm going to have to revert those servers running on 422 back to 404 until we can upgrade all at once.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125296#4125296
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125296
In our project we are also using Richfaces and Trinidad together. I encountered exactly the same problem. I created a jira issue for that:
Well, until now I have found no solution to the problem and just live with the error message in the log.. but you are right, that is not an applicable solution.
Even worse since the Richfaces version prior 3.1.3 show the error *every* time the page is loading, not only the first. And I have to use Richfaces 3.1.2 because later versions have a still unsolved memory leak with the dropdown menue in Firefox.
Well, all in all Richfaces work together with Trinidad however, there are small but nasty issues when using them together... one thing for example is the different approach of partial page rendering.. And the use of Trinidad tables (tr:table is much better than Richfaces tables imho and this is the main reason why we are using Trinidad) with Richfaces a4jsf controls can also be a bit tricky sometimes...
Please let me know if you find a solution... or encounter other problems.. maybe I could help..
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125292#4125292
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125292