Socket on server side remains “ESTABLISHED” even connected EJB client is not online .

Solution Verified - Updated -

Issue

  • One application uses the JBoss EJB-Client to call stateless session beans on a remote JBoss application server . An established TCP Socket can be seen on the remoting port of the Jboss server to each connected client workstation. If client terminates abnormal or if there is any network issue then also the socket on server side remains ESTABLISHED which causes errors like SocketException: too many open files. Is there any work around for closing the socket if connected EJB client is not online .
  • How to close socket on server side if connected EJB client is not online ?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x.x

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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