Problem Note 57029: SAS® Web Application Server instances might fail to start and return the error "Timeout for Application Server startup has reached before port opened"
 |  |  |  |
In a multi-tier configuration, servers might fail to start and return the following output in the log if one of the tiers is a Solaris operating system:
[appserverTarget] 2015-10-22 06:47:09,408 [main] INFO
com.sas.appserver.vfabrictcsvr.Server - Timeout reached before port opened.
(rdcesx09053.race.sas.com:8080)
[appserverTarget] 2015-10-22 06:47:09,408 [main] INFO
com.sas.appserver.vfabrictcsvr.Server - getFailedApps() >>>
[appserverTarget] 2015-10-22 06:47:14,417 [main] INFO
com.sas.appserver.vfabrictcsvr.Server - getFailedApps() >>>
[appserverTarget] 2015-10-22 06:47:14,417 [main] INFO
com.sas.appserver.vfabrictcsvr.Server - testServer() - Throwing
AppServerException
[appserverTarget] 2015-10-22 06:47:14,417 [main] INFO
com.sas.appserver.vfabrictcsvr.Server - testServer() <<<
[appserverTarget] 2015-10-22 06:47:14,511 [main] INFO
com.sas.sdw.SDWExceptionHandler - handle() >>>
[appserverTarget] 2015-10-22 06:47:14,511 [main] INFO
com.sas.sdw.SDWExceptionHandler - handleSDWException() >>>
[appserverTarget] 2015-10-22 06:47:14,511 [main] INFO
com.sas.sdw.SDWExceptionHandler - target=startMidtierServers,
task=com.sas.sdw.SDWExceptionHandler
[appserverTarget] 2015-10-22 06:47:14,511 [main] INFO
com.sas.sdw.SDWExceptionHandler - message=Timeout for Application Server startup
has reached before port opened.
[propertyfile] Updating property file:
C:\SAS\Config\Lev1\Logs\Configure\vfabrictcsvr_config_status.properties
[propertyfile] Updating property file:
C:\SAS\Config\Lev1\Logs\Configure\vfabrictcsvr_config_status.properties
2015-10-22 06:47:14,527 [main] INFO com.sas.sdw.SDWExceptionHandler -
configStatusFile set.
2015-10-22 06:47:14,542 [main] ERROR com.sas.sdw.SDWExceptionHandler -
com.sas.appserver.utils.AppServerException: Timeout for Application Server
startup has reached before port opened.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorI
mpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorA
ccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
......
2015-10-22 06:47:14,558 [main] INFO com.sas.sdw.SDWExceptionHandler - Forcing
failure.
BUILD FAILED
: Timeout for Application Server startup has reached before port opened.
at org.apache.tools.ant.taskdefs.Exit.execute(Exit.java:142)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:43)
......
This issue has been encountered when two GemFire processes are configured in a mixed operating system scenario and one of the systems is Solaris.
To work around this problem, update the TCP tuning parameters on the Solaris machine:
- Check the value of tcp_init_wnd_chk using mdb (the default value is 4096):
- Change the window check so that it is less than the advertised window:
- To permanently change this setting, enter the following in the /etc/system file:
# echo "tcp_init_wnd_chk/D" | mdb -k
tcp_init_wnd_chk:
tcp_init_wnd_chk: 4096
# echo tcp_init_wnd_chk/W 0x1ff | mdb -kw
Note: The decimal representation of the hexadecimal value 1FF is 511.
set ip:tcp_init_wnd_chk = 511
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Enterprise BI Server | Solaris for x64 | 9.4 | 9.4 TS1M0 | ||
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2015-11-25 10:45:22 |
| Date Created: | 2015-11-06 14:56:37 |