Many "can't identify protocol" sockets in JBoss EAP

Solution Verified - Updated -

Issue

  • Got java.net.SocketException: Too many open files with lsof showing many "can't identify protocol" sockets
COMMAND  PID USER   FD   TYPE   DEVICE        SIZE     NODE   NAME
java    4031 iocc *615u  sock       0,5              99996497 can't identify protocol
java    4031 iocc *619u  sock       0,5              99996430 can't identify protocol
java    4031 iocc *620u  sock       0,5              99996910 can't identify protocol
java    4031 iocc *621u  sock       0,5              99996796 can't identify protocol
java    4031 iocc *622u  sock       0,5              99996690 can't identify protocol
java    4031 iocc *623u  sock       0,5              99996980 can't identify protocol
java    4031 iocc *625u  sock       0,5              99997060 can't identify protocol

These sockets sometimes disappear due to Full GC

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 4.x
    • 5.x
    • 6.x
    • 7.x
  • Java

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.