Kbase P162745: Errors 8109, 8100 and 8101 when starting additional WebSpeed broker on the Solaris 10 Container Virt
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/30/2010 |
|
Status: Unverified
SYMPTOM(s):
Errors 8109, 8100 and 8101 when starting additional WebSpeed broker on the Solaris 10 Container Virtual Server
Errors 8109, 8100 and 8101 when starting additional AppServer broker on the Solaris 10 Container Virtual Server
The WebSpeed broker log shows the following errors:
Server exec error : Not enough space (8109)
Server exec error : <IOException_string> <IOExceptionMsg_string> (8109)
ERROR: cannot start server. (8100)
Started server thread: <threadName>. (8101)
FACT(s) (Environment):
There are 5 virtual containers and 1 global container
The containers are set to be dynamic so it grows and shrinks as other containers uses more or less resources
The error comes when additional brokers are started on demand
If one running broker is stopped on one container, a new broker can be started on a different container without any errors
Increasing the java heap size resolves the issue
UNIX
Solaris 10
OpenEdge 10.1C
OpenEdge 10.2x
Sun Solaris SPARC
CAUSE:
The exact cause is unknown at the time of this writing
FIX:
The workaround is to increase the java heap size for each broker on the $DLC/properties/AdminServerPlugins.properties file as follows and restart all the processes again:
[PluginPolicy.Progress.AdminServer]
jvmargs=-Xms32m -Xmx1024m
[Plugin.WebSpeed]
jvmargs=-Xms16m -Xmx254m
[Plugin.NameServer]
jvmargs=-Xms16m -Xmx254m