webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  am keep on getting error in MWS--read time out error

    Posted Tue July 28, 2009 06:03 AM

    Hi All,

    Am Using wM7.1.1 mywebmethod server,am keep on getting below error in log file,when am trying to see details of processInstance in my webmethod server.

    2009-07-28 10:05:24 IST (webservice : WARN) [RID:1334] - java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:129)
    at electric.util.io.MonitoringInputStream.read(MonitoringInputStream.java:50)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
    at electric.util.io.Streams.readLine(Streams.java:288)
    at electric.http.InboundHTTPResponse.readHeaders(InboundHTTPResponse.java:118)
    at electric.http.HTTPMessage.readResponseHeaders(HTTPMessage.java:267)
    at electric.http.HTTPMessage.send(HTTPMessage.java:133)
    at electric.soap.http.reference.SOAPToHTTP.invoke(SOAPToHTTP.java:190)
    at electric.soap.http.reference.SOAPToHTTP.handle(SOAPToHTTP.java:136)
    at electric.soap.references.logging.LoggingSOAPReference.handle(LoggingSOAPReference.java:57)
    at electric.jaxrpc.handler.JAXRPCReference.handle(JAXRPCReference.java:76)
    at com.webMethods.soap.module.SOAPModuleReference.handle(SOAPModuleReference.java:70)
    at electric.soap.references.interceptor.InterceptorSOAPReference.handle(InterceptorSOAPReference.java:69)
    at electric.soap.java.reference.JavaToSOAP.handle(JavaToSOAP.java:72)
    at electric.soap.java.reference.JavaToSOAP.invoke(JavaToSOAP.java:238)
    at electric.soap.java.reference.JavaToSOAP.invoke(JavaToSOAP.java:165)
    at electric.proxy.handler.Proxy.invoke(Proxy.java:126)
    at $Proxy5.getTrackingExtensions(Unknown Source)
    at sun.reflect.GeneratedMethodAccessor1061.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invokeMethod(WSClientDynamicProxy.java:84)
    at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invoke(WSClientDynamicProxy.java:128)
    at $Proxy4.getTrackingExtensions(Unknown Source)
    at com.webMethods.bpo.portlet.wm_bam_process_config_details.Bam_process_config_details.getTrackingExtensionsFromWS(Bam_process_config_details.java:1119)
    at com.webMethods.bpo.portlet.wm_bam_process_config_details.Bam_process_config_details.getProcessModelTrackingExtensions(Bam_process_config_details.java:891)
    at com.webMethods.bpo.portlet.wm_bam_process_config_details.Bam_process_config_details.getProcessTimeout(Bam_process_config_details.java:1637)
    at ui.portlets.wm_bam_process_config_details.businessProcessConfigurationDetails._jspService(businessProcessConfigurationDetails.java:2253)
    at com.webMethods.portal.framework.presentation.handlers.Jsp.render(Jsp.java:288)
    at com.webMethods.portal.framework.presentation.handlers.Jsp.render(Jsp.java:228)
    at com.webMethods.portal.framework.portlet.beans.JspPortletBean.generateContent(JspPortletBean.java:123)
    at com.webMethods.portal.framework.portlet.beans.JspPortletBean.getContentInternal(JspPortletBean.java:70)
    at com.webMethods.portal.framework.portlet.beans.BasicPortletBean.getContent(BasicPortletBean.java:143)
    at com.webMethods.portal.mech.portlet.impl.PortletMechanics.getPortletContent(PortletMechanics.java:95)
    at com.webMethods.portal.mech.storage.page.PortletHelper.renderContent(PortletHelper.java:403)
    at com.webMethods.portal.mech.storage.page.PortletHelper.renderContent(PortletHelper.java:375)
    at com.webMethods.portal.framework.presentation.renderers.FolderRenderer.renderPortlet(FolderRenderer.java:260)
    at com.webMethods.portal.framework.presentation.renderers.FolderRenderer.renderColumn(FolderRenderer.java:203)
    at com.webMethods.portal.framework.presentation.renderers.FolderRenderer.renderRow(FolderRenderer.java:164)
    at com.webMethods.portal.framework.presentation.renderers.FolderRenderer.renderContent(FolderRenderer.java:91)
    at com.webMethods.portal.framework.presentation.renderers.FolderRenderer.renderPageContent(FolderRenderer.java:68)
    at com.webMethods.portal.framework.presentation.renderers.DefaultRenderer.render(DefaultRenderer.java:188)
    at com.webMethods.portal.framework.presentation.PresentationManager.handlePres(PresentationManager.java:359)
    at com.webMethods.portal.framework.dispatch.DispatchManager.pres(DispatchManager.java:618)
    at com.webMethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:458)
    at com.webMethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:371)
    at com.webMethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:242)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
    at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
    at com.webMethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:50)
    at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
    at com.webMethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:34)
    at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
    at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
    at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
    at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
    at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
    at com.webMethods.portal.webApplication.WmWebAppContext.handle(WmWebAppContext.java:159)
    at org.mortbay.http.HttpServer.service(HttpServer.java:909)
    at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
    at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
    at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
    at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245)
    at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
    at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

    Regards,
    Anil Kumar Ellendula


    #BPM
    #webMethods
    #webMethods-BPMS


  • 2.  RE: am keep on getting error in MWS--read time out error

    Posted Thu May 24, 2012 04:12 PM

    Hello Anil,

    Did you manage to resolve it?

    I am having the similar thing on 7.1.3

    2012-05-24 15:08:15 CAT (webservice : WARN) [RID:14124] - java.rmi.RemoteException: java.net.SocketTimeoutException: Read timed out; nested exception is:
    java.net.SocketTimeoutException: Read timed out
    at electric.soap.http.reference.SOAPToHTTP.handle(SOAPToHTTP.java:163)
    at electric.soap.references.logging.LoggingSOAPReference.handle(LoggingSOAPReference.java:57)
    at electric.jaxrpc.handler.JAXRPCReference.handle(JAXRPCReference.java:76)
    at com.webMethods.soap.module.SOAPModuleReference.handle(SOAPModuleReference.java:70)

    javascript:emoticon(‘:cry:’);

    Regards
    Leonard


    #webMethods-BPMS
    #BPM
    #webMethods


  • 3.  RE: am keep on getting error in MWS--read time out error

    Posted Wed June 13, 2012 03:18 PM

    Hi Anil,

    Did you try increasing the socket timeout value with which the MWS is connecting to IS?

    If not give it a try, this error occurs when the MWS is still waiting to get the data from IS server and becuase of the low timeout value or due to high traffic, its not able to wait.

    -Gayathri


    #webMethods
    #BPM
    #webMethods-BPMS


  • 4.  RE: am keep on getting error in MWS--read time out error

    Posted Sun March 10, 2013 12:24 AM

    Hi Anil,

    I am facing a similar error with BPM.
    Could you please let me know how you resolved this issue.


    #webMethods-BPMS
    #BPM
    #webMethods


  • 5.  RE: am keep on getting error in MWS--read time out error

    Posted Wed March 20, 2013 08:13 AM

    hi Anil,

    Please check the path Administration>Systemsettings>TaskEngine>IS servers in MWS and make sure IS server details are correct on which your process models are deployed .


    #webMethods
    #webMethods-BPMS
    #BPM