The BusinessConnect (BC) Gateway Server (GS) fails to start with Idle bootstrap error: Error:[2014-01-17 18:21:25,863(ERROR)]GatewayServer com.tibco.ax.gs.runtime.GatewayRuntimeException: Idle bootstrap failed.at com.tibco.ax.gs.run
book
Article ID: KB0082371
calendar_today
Updated On:
Products
Versions
TIBCO BusinessConnect
6.X.X
Description
The BusinessConnect (BC) Gateway Server (GS) fails to start with Idle bootstrap error:
Error: [2014-01-17 18:21:25,863(ERROR)]GatewayServer com.tibco.ax.gs.runtime.GatewayRuntimeException: Idle bootstrap failed. at com.tibco.ax.gs.runtime.GatewayServer.idleBootStrap(GatewayServer.java:267) at com.tibco.ax.gs.runtime.GatewayServer.init(GatewayServer.java:114) at com.tibco.ax.gs.runtime.GatewayServer.<init>(GatewayServer.java:81) at com.tibco.ax.gs.runtime.GatewayServer.Startup(GatewayServer.java:618) Caused by: com.tibco.ax.gs.runtime.GatewayRuntimeException: RV timeout after 60 seconds. at com.tibco.ax.gs.runtime.impl.GSBootstrapUtil.sendDmzMshRequest(GSBootstrapUtil.java:371) at com.tibco.ax.gs.runtime.GatewayServer.idleBootStrap(GatewayServer.java:255)
Issue/Introduction
The BusinessConnect (BC) Gateway Server (GS) fails to start with Idle bootstrap error:
Error:[2014-01-17 18:21:25,863(ERROR)]GatewayServer com.tibco.ax.gs.runtime.GatewayRuntimeException: Idle bootstrap failed.at com.tibco.ax.gs.runtime.GatewayServer.idleBootStrap(GatewayServer.java:267)at com.tibco.ax.gs.runtime.GatewayServer.init(GatewayServer.java:114)at com.tibco.ax.gs.runtime.GatewayServer.;init;(GatewayServer.java:81)at com.tibco.ax.gs.runtime.GatewayServer.Startup(GatewayServer.java:618)Caused by: com.tibco.ax.gs.runtime.GatewayRuntimeException: RV timeout after 60 seconds.at com.tibco.ax.gs.runtime.impl.GSBootstrapUtil.sendDmzMshRequest(GSBootstrapUtil.java:371)at com.tibco.ax.gs.runtime.GatewayServer.idleBootStrap(GatewayServer.java:255)
Environment
Product: TIBCO BusinessConnect
Version: 6.X.X
OS: All
--------------------
Resolution
To resolve this issue, first make sure that the Rendezvous (RV) Intercomponent Settings are configured correctly. Also, make sure via tibrvsend and tibrvlisten, that RV traffic succeeds between the two servers.
If RV traffic is OK then the RV timeout delay (default 60 seconds) may need to be extended. This may be required if the BC configuration has a larger number of configured users or BusinessAgreements. You can change the delay by adding the following property to the gsengine.tra file:
java.property.gs.dmzrv.timeout=secs value
Be sure to restart the GS from the command line after updating this value.
Additional Information
BusinessConnect Interior Server Administration Guide, BusinessConnect Gateway Server Administration Guide