Troubleshooting
Problem
GIS / SI - HTTP Server Adapter doesn't shut down completely when re-enabled immediately after disabling
Symptom
If the HTTP Server adapter is disabled through Deployment > Services > Configuration and then is immediately re-enabled, there is a good chance that the adapter will go into an unstable state, where it becomes disconnected from the rest of the application, and there is no way to control it. In this odd state, a netstat on the adpater port displays it in a LISTEN state and remote TPs can still establish new connections but the BP HTTP Respond Service will post status Service Configuration Error when attempting to send a HTTP response or MDN outbound. In this case, after the customer disabled and restarted the HTTP Server adapter they noticed AS2 documents continued to come into BP EDIINTParse and process successfully, but it failed the on the HTTP Respond Service attempting to send the MDN back to the TP.
Error MessageHTTP log:
[2011-06-10 00:00:05.998] ERROR 000000000000 GLOBAL_SCOPE HttpRespondService.processData() - ServicesControllerImpl could not find an adapter by the transport instance id [ABC_HttpsServer_n1_Dmz2_Ps1_HttpServerAdapter_node1]
[2011-06-10 00:00:06.924] ERROR 000000000000 GLOBAL_SCOPE The servlet caught a throwable (of type class EDU.oswego.cs.dl.util.concurrent.TimeoutException) and is erroring out: A total of 11 milliseconds have elapsed since this SoonResult instance [SoonResult(wait for 3600000ms starting at Thu Jun 09 23:00:06 CDT 2011)] expired.
EDU.oswego.cs.dl.util.concurrent.TimeoutException: A total of 11 milliseconds have elapsed since this SoonResult instance [SoonResult(wait for 3600000ms starting at Thu Jun 09 23:00:06 CDT 2011)] expired.
at com.sterlingcommerce.woodstock.services.pshttp.SoonResult.get(SoonResult.java:119)
at com.sterlingcommerce.woodstock.services.pshttp.servlet.PSHttpServletHandler.handle(PSHttpServletHandler.java:343)
at com.sterlingcommerce.woodstock.services.pshttp.servlet.PSHttpServlet.process(PSHttpServlet.java:181)
at com.sterlingcommerce.woodstock.services.pshttp.servlet.PSHttpServlet.doGet(PSHttpServlet.java:115)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)
at org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHandler.java:657)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
at com.sterlingcommerce.woodstock.services.pshttp.jetty.FlushingHttpConnection.handleNext(FlushingHttpConnection.java:133)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806)
at com.sterlingcommerce.woodstock.services.pshttp.jetty.ConduitStreamListener.handleNewConnection(ConduitStreamListener.java:217)
at com.sterlingcommerce.woodstock.services.pshttp.jetty.ConduitStreamListener.access$400(ConduitStreamListener.java:82)
at com.sterlingcommerce.woodstock.services.pshttp.jetty.ConduitStreamListener$1.run(ConduitStreamListener.java:275)
at org.mortbay.util.ThreadPool.handle(ThreadPool.java:385)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520)
Resolving The Problem
To recreate this problem, do the following steps:
1. Deployment > Services > Configuration > Search for the "HTTP_server_adapter"
2. Uncheck the adapter and re-enable it as soon as it shows up disabled.
Be aware that this is not the proper procedure to restart an adapter. An improper restart of the HTTP Server adapter was the root cause in Inquira article NFX6532 and NFX6921. This can cause the adapter to be left in an odd unstable state and this is a known issue. The only way to clear out the inconsistent adapter state is by bouncing the application.
Resolution: Our GIS 4.3 System Administration documentation has been updated to clearly explain the proper procedure to stop and restart an adapter, go to url http://www.sterlingcommerce.com/Documentation/GIS43/Content/SystemAdmin…, see below:
Stopping a Service or Adapter
You can stop a service or an adapter for a variety of reasons. The service or adapter may not stop immediately, because Gentran Integration Suite gives services the opportunity to first complete any pending requests.
To stop a service or adapter:
1. From the Administration menu, select Operations > System > Troubleshooter.
2. In the Adapters area under the Environment section, clear the On/Off check box next to the service or adapter you want to stop.
Gentran Integration Suite stops the adapter and refreshes the System Troubleshooting page showing the status of the selected service or adapter as Stopped.
Note: If the user wants to restart the HTTP Server Adapter from the Main Service Configuration screen, the user has to start the HTTP Server Adapter once the HTTP Server Adapter's status is changed to Stopped.
Historical Number
NFX11407
Product Synonym
[<p><b>]Function Area[</b><p>];Adapaters - HTTP Server;[<p><b>]Escalation ID[</b><p>];316962;[<p><b>]Severity[</b><p>];Normal
Was this topic helpful?
Document Information
Modified date:
06 December 2019
UID
swg21557849