-
15. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jkreska Jun 7, 2012 9:41 AM (in response to jkreska)Well, that was the source from my stdalone client
The web client has the ejb ref cached and only does the getCity call
-
16. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jkreska Jun 7, 2012 9:52 AM (in response to jaikiran)jaikiran pai wrote:
Also please include org.jboss.ejb.client package to the TRACE level logs - I missed out that package in my previous reply.
-
client3.log.zip 4.2 KB
-
-
17. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jkreska Jun 11, 2012 9:00 AM (in response to jkreska)Any ideas?
-
18. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jaikiran Jun 11, 2012 11:48 AM (in response to jkreska)There's one other thread with a similar issue and I'm still investigating. I'll update these threads when I've something to report.
-
19. Re: 7.1.2.Final Is there a timeout for inbound connnections?
gwwallace Jun 15, 2012 12:23 AM (in response to jaikiran)Any more news ?
-
20. Re: 7.1.2.Final Is there a timeout for inbound connnections?
gwwallace Jun 20, 2012 4:26 PM (in response to gwwallace)Jaikiran - ping
-
21. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jaikiran Jun 21, 2012 1:52 AM (in response to gwwallace)I've discussed this with David and one possible way to overcome this is to set the KEEP_ALIVE option on the channel. You can do that by adding the following to your remoting connector in the standalone.xml/domain.xml if your client is a remote standalone client:
<subsystem xmlns="urn:jboss:domain:ejb3:1.3"> ... <remote connector-ref="remoting-connector" thread-pool-name="default"> <channel-creation-options> <option name="KEEP_ALIVE" value="true" type="xnio"/> </channel-creation-options> </remote> ...
If the client is an AS7 server itself, then that config should go in the jboss-ejb-client.xml:
<jboss-ejb-client xmlns="urn:jboss:ejb-client:1.0"> <client-context> <ejb-receivers> <remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection"> <channel-creation-options> <property name="org.xnio.Options.KEEP_ALIVE" value="true"/> </channel-creation-options> </remoting-ejb-receiver> ... <!-- If you have any cluster configurations, then include that property there too --> <clusters> <cluster name="ejb" ....> <channel-creation-options> <property name="org.xnio.Options.KEEP_ALIVE" value="true"/> </channel-creation-options> </cluster> </clusters> ....
-
22. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jkreska Jun 21, 2012 7:49 AM (in response to jaikiran)jaikiran pai wrote:
I've discussed this with David and one possible way to overcome this is to set the KEEP_ALIVE option on the channel. You can do that by adding the following to your remoting connector in the standalone.xml/domain.xml if your client is a remote standalone client:
<subsystem xmlns="urn:jboss:domain:ejb3:1.3"> ... <remote connector-ref="remoting-connector" thread-pool-name="default"> <channel-creation-options> <option name="KEEP_ALIVE" value="true" type="xnio"/> </channel-creation-options> </remote> ...
If the client is an AS7 server itself, then that config should go in the jboss-ejb-client.xml:
<jboss-ejb-client xmlns="urn:jboss:ejb-client:1.0"> <client-context> <ejb-receivers> <remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection"> <channel-creation-options> <property name="org.xnio.Options.KEEP_ALIVE" value="true"/> </channel-creation-options> </remoting-ejb-receiver> ... <!-- If you have any cluster configurations, then include that property there too --> <clusters> <cluster name="ejb" ....> <channel-creation-options> <property name="org.xnio.Options.KEEP_ALIVE" value="true"/> </channel-creation-options> </cluster> </clusters> ....
I added the KEEP_ALIVE option to the remoting-connector and it did not help my standalone client.
-
23. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jaikiran Jul 5, 2012 9:16 AM (in response to jkreska)I haven't been able to reproduce this. Please file a JIRA with all the relevant details including the configurations you used and also any Resin related details. If possible please also attach the client and the EJB deployment.
-
24. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jkreska Jul 9, 2012 1:50 PM (in response to jaikiran)jaikiran pai wrote:
I haven't been able to reproduce this. Please file a JIRA with all the relevant details including the configurations you used and also any Resin related details. If possible please also attach the client and the EJB deployment.
- resin_conf_webapp.zip - resin config file, bin dir and webapp (I used resin 4.0.7 and hit this url http://jb7-5.alpha:7810/jb7/index.html?cityCode=DFW)
- cluster-server.zip - cluster server config files
- relay-server.zip - relay server config files (webapp connects here)
- JBoss7Clustering-RelayServer.zip - IDEA project and ant make files to buld #2 and #3
Let me know if you need anything else
-
relay-server.zip 780.4 KB
-
cluster-server.zip 1.9 MB
-
resin_conf_webapp.zip 7.2 MB
-
25. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jaikiran Jul 9, 2012 10:54 AM (in response to jkreska)Quick question - How long do I have to wait for that timeout to happen to reproduce this?
-
26. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jkreska Jul 9, 2012 10:58 AM (in response to jaikiran)No time at all. It happens as soon as you hit the webpage.
-
27. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jkreska Jul 9, 2012 1:51 PM (in response to jkreska)jkreska wrote:
jaikiran pai wrote:
I haven't been able to reproduce this. Please file a JIRA with all the relevant details including the configurations you used and also any Resin related details. If possible please also attach the client and the EJB deployment.
- resin_conf_webapp.zip - resin config file, bin dir and webapp (I used resin 4.0.7 and hit this url http://jb7-5.alpha:7810/jb7/index.html?cityCode=DFW)
- cluster-server.zip - cluster server config files
- relay-server.zip - relay server config files (webapp connects here)
- JBoss7Clustering-RelayServer.zip - IDEA project and ant make files to buld #2 and #3
Let me know if you need anything else
I attached the wrong webapp, just updated the post to include the correct one.
-
28. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jkreska Jul 9, 2012 2:41 PM (in response to jkreska)I noticed the following messages in the webapp log, didn't notice them before
2012-07-09 14:38:00,149 DEBUG [IndexAction] In action 2012-07-09 14:38:00,150 TRACE [remote] Requesting service open of type jboss.ejb on Connection handler for Remoting conn ection 3534e8e8 to null 2012-07-09 14:38:00,150 TRACE [remote] Refused outbound channel open on Connection handler for Remoting connection 3534e 8e8 to null because close request was sent 2012-07-09 14:38:05,150 INFO [remoting] EJBCLIENT000014: Version handshake not completed for receiver context EJBReceiv erContext{clientContext=org.jboss.ejb.client.EJBClientContext@8c6272f, receiver=Remoting connection EJB receiver [connec tion=Remoting connection <79623fc9>,channel=jboss.ejb,nodename=jb7-8]}. Closing receiver context 2012-07-09 14:38:05,151 WARN [RequestProcessor] Unhandled Exception thrown: class java.lang.IllegalStateException [12-07-09 14:38:05.152] {http://*:7810-2} javax.servlet.ServletException: java.lang.IllegalStateException: EJBCLIENT0000 25: No EJB receiver available for handling [appName:relaymodule, moduleName:farecompare-relaymodule-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@2f41cd06 at org.apache.struts.action.RequestProcessor.processException(RequestPro cessor.java:523) at org.apache.struts.action.RequestProcessor.processActionPerform(Reques tProcessor.java:421) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.ja va:224) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:119 4) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:119) ....
Caused by: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:relaymodule, moduleName:farecompare-relaymodule-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@2f41cd06 at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:588) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116) at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) at $Proxy39.getNameForCityCode(Unknown Source) at com.farecompare.website.jb7.actions.IndexAction.execute(IndexAction.j -
29. Re: 7.1.2.Final Is there a timeout for inbound connnections?
jkreska Jul 9, 2012 2:55 PM (in response to jaikiran)jaikiran pai wrote:
Quick question - How long do I have to wait for that timeout to happen to reproduce this?
It appears to be random. It is now taking a minute or more for connection to drop and that is while reloading the page every 10-15 seconds