WebSphere Issues

30/08/2013

Asynchronous request dispatching

Filed under: Java, WAS — Ishtiaque @ 12:58 pm

Allow Asynchronous Request Dispatching will enable enable the asynchronous request dispatcher (ARD), which enables servlets and JSP pages to make standard include calls concurrently on separate threads. Additionally, the initiation and the insertion of the include contents can be separated so that the include has more time to execute before it needs to be written to the response. ARD requires aggregation of the include contents with the original response. The application server can aggregate the contents in memory or the client browser can aggregate the contents through AJAX. Aggregation type is configurable at the application level.”

We were getting following exception while calling a web service method via AJAX.

8/22/13 17:42:07:437 PKT] 00000064 servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: An exception was thrown by one of the service methods of the servlet [JAX-RS Servlet] in application. Exception created : [javax.xml.ws.soap.SOAPFaultException: java.net.ConnectException: Connection refused: no further information
at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1326)
at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:1052)
at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMinimalMethodMarshaller.demarshalFaultResponse(DocLitBareMinimalMethodMarshaller.java:440)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:597)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:537)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:403)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:188)

We managed to resolve this issue by checking Allow Asynchronous Request Dispatching.

1. Navigate to Servers > Server Types > WebSphere application servers > server_name > Web Container Settings > Web container > Asynchronous request dispatching

2. Check Allow Asynchronous Request Dispatching and restart the server

References:

http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2Fuweb_ard.html

Advertisements

Create a free website or blog at WordPress.com.

%d bloggers like this: