EJB-s "disappear" after some use

[zhivagodr]

Hi,

On JBOSS AS 7.1.1 served from Windows Server 2008 from a VM, we have the following problem. After several hours of usage the EJB-s can't be reached from the clients. 

This is the error on the clients. On the server side no error in standalone.log. Please help, where to look, how to find the root of this problem.

This is the log the client produce:

2016-09-26 12:17:10,901 WARN  [javawsApplicationMain] remoting.ConfigBasedEJBClientContextSelector (ConfigBasedEJBClientContextSelector.java:138) - Could not register a EJB receiver for connection to hubpelnt01:4447

java.lang.RuntimeException: Operation failed with status WAITING

    at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:93)

    at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:126)

    at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.<init>(ConfigBasedEJBClientContextSelector.java:83)

    at com.chemistry.enotebook.servicelocator.ServiceLocator.getInitialContext(ServiceLocator.java:93)

    at com.chemistry.enotebook.servicelocator.ServiceLocator.locateEJB3(ServiceLocator.java:67)

    at com.chemistry.enotebook.session.delegate.SessionTokenDelegate.<init>(SessionTokenDelegate.java:38)

    at com.chemistry.enotebook.experiment.utils.CeNSystemProperties.getProperty(CeNSystemProperties.java:235)

    at com.chemistry.enotebook.experiment.utils.CeNSystemProperties.getCeNSystemProperty(CeNSystemProperties.java:104)

    at com.chemistry.enotebook.client.controller.MasterController.checkSystemStatus(MasterController.java:558)

    at com.chemistry.enotebook.client.controller.MasterController.startApp(MasterController.java:261)

    at com.chemistry.enotebook.client.controller.MasterController.main(MasterController.java:455)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

    at java.lang.reflect.Method.invoke(Unknown Source)

    at com.sun.javaws.Launcher.executeApplication(Unknown Source)

    at com.sun.javaws.Launcher.executeMainClass(Unknown Source)

    at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)

    at com.sun.javaws.Launcher.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)

2016-09-26 12:17:11,010 INFO  [javawsApplicationMain] ejb.client (EJBClient.java:42) - JBoss EJB Client version 1.0.12.Final

2016-09-26 12:17:16,082 ERROR [javawsApplicationMain] utils.CeNSystemProperties (CeNSystemProperties.java:106) - Failed to retrieve server property: /Notebook_Properties/Status

com.chemistry.enotebook.experiment.utils.SystemPropertyException: Failed to retrieve global properties

    at com.chemistry.enotebook.experiment.utils.CeNSystemProperties.getProperty(CeNSystemProperties.java:267)

    at com.chemistry.enotebook.experiment.utils.CeNSystemProperties.getCeNSystemProperty(CeNSystemProperties.java:104)

    at com.chemistry.enotebook.client.controller.MasterController.checkSystemStatus(MasterController.java:558)

    at com.chemistry.enotebook.client.controller.MasterController.startApp(MasterController.java:261)

    at com.chemistry.enotebook.client.controller.MasterController.main(MasterController.java:455)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

    at java.lang.reflect.Method.invoke(Unknown Source)

    at com.sun.javaws.Launcher.executeApplication(Unknown Source)

    at com.sun.javaws.Launcher.executeMainClass(Unknown Source)

    at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)

    at com.sun.javaws.Launcher.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)

Caused by: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:enotebook_server, moduleName:CeNSessionServiceEJB, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@4ca53e

    at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:638)

    at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)

    at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)

    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 com.sun.proxy.$Proxy0.getSystemProperties(Unknown Source)

    at com.chemistry.enotebook.session.delegate.SessionTokenDelegate.getSystemProperties(SessionTokenDelegate.java:94)

    at com.chemistry.enotebook.experiment.utils.CeNSystemProperties.getProperty(CeNSystemProperties.java:236)

    ... 13 more

Thanks,

Istvan

[doh]

Root Cause

The error message "Operation failed with status WAITING" means that the client was unable to connect to the host/port and timed out. This is caused by having the wrong host/port configuration in the client's jboss-ejb-client.properties or by a network issue such as firewall, network connectivity, mis-configured DNS entry, or invalid /etc/hosts entry.

Resolution

Configure the jboss-ejb-client.properties remote.connection.default.host & remote.connection.default.port to point to the correct host and port that the server is running on and assure that the client can access the host and port and that there is not a firewall or network issue. Update to the latest Oracle JDK 7 and check release notes for networking bugs.

Standalone EJB client fails to connect with RuntimeException: Operation failed with status WAITING in JBoss EAP6 - Red H…

[zhivagodr]

Thanks for the reply.

Well, the config (host, port) of the client is good. The clients work for a while, but after some time something happens and the server stops serving the EJB-s. If I restart the server, the clients start working again. I can't find any relevant info in the server.log.

I tracked the issue to one client PC today. When the client app starts on that PC, it pops up a java error message, but the window so tiny only the title showed. The symptoms of the server starts after this moment. I switched on java console on the PC, to see what happens, but with the console switched on, no any error shows up on the console, and the client starts and works flawlessly. So I'm puzzled. The most worrying is that a client somehow can block the server. It would be better to prevent this to happen again, but I have no clue how. Will update the java on that PC first, of course.

Thanks,

Istvan