EJB communication fails after long pause

Solution Unverified - Updated -

Issue

  • In the context of an EJB communication, the following ERROR occurs on the server side after long pause of inactivity:
26.11.2014 13:59:24 Thread<170> org.jboss.as.naming.remote.RemoteNamingLogger failedToSendExceptionResponse
ERROR: JBAS011809: Failed to send exception response to client: 
org.jboss.remoting3.NotOpenException: Writes closed
    at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:108)
    at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:297)
    at org.jboss.naming.remote.protocol.v1.WriteUtil.write(WriteUtil.java:59)
    at org.jboss.naming.remote.protocol.v1.WriteUtil.writeExceptionResponse(WriteUtil.java:81)
    at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.sendIOException(RemoteNamingServerV1.java:97)
    at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:86)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)

followed by an application specific stacktrace in the server log.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 6.2
    • Remote EJB invocation

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.