rtm333, I've performed the experiment you described.
While it's true that the client sends and invocation into the server every other two seconds (that's the ConnectionValidator, the remoting client uses it to detect failed connections), no new socket is created. The same physical TCP/IP connection is re-used, and the validator seems rather well behaved and working as intended.
I must mention though I am using Remoting 2.2.0.Alpha5, which includes a fair amount of changes in exactly this area, so the bug that you noticed probably has already been fixed.
I am going to close http://jira.jboss.org/jira/browse/JBMESSAGING-749 with "Cant' reproduce bug"
Try 1.0.1.SP4, it will be out soon, and if you see the same behavior again, please reopen the issue
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003190#4003190
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003190
i have an EJB that uses entityManager.
the entityManager is injected throw seam.
on my application every thing works fine,
the persistence.xml define the DS and the entityManager JNDI lookup,
the component is created by seam as defined in the components.xml.
in my EJB i have this:
| @In(create=true)
| private EntityManager entityManager;
|
when i write test for the ejb i get exception,
how can I make my test work?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003188#4003188
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003188