Home > Coherence, SOA > „No buffer space available” while starting SOA 11g managed server

„No buffer space available” while starting SOA 11g managed server

November 14, 2011 Leave a comment Go to comments

While starting a SOA managed server, you might notice the soa-infra application is not starting with the following stack trace thrown in the server’s log file:

Stack trace for message 149004[[
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1399)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)

Caused By: (Wrapped) java.net.SocketException: No buffer space available
at com.tangosol.coherence.component.net.socket.UdpSocket.initializeDatagramSocket(UdpSocket.CDB:28)
at com.tangosol.coherence.component.net.socket.UdpSocket.open(UdpSocket.CDB:11)

The SOA 11g on AIX context is something specific to an environment where I encountered the issue, but it can also happen on other UNIX platforms. Actually, it can happen on Weblogic Server only, not necessarily SOA, since the issue is related to Coherence. The cause of the problem is that the operating system does not accommodate the network buffer socket size that Coherence requires. In conclusion, to fix the issue you will need to set a OS parameter as root:

no -o sb_max=8388608

You might want to check with your system admin to make sure the new value is persistent through a system reboot or use an OS administrative tool such as smitty.

Tags: ,
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: