webMethods

 View Only
Expand all | Collapse all

Timeout error using pub.client:http

  • 1.  Timeout error using pub.client:http

    Posted Tue September 10, 2024 03:40 AM

    Good day

    I am new to webMethods. I am trying to consume and API using pub.client:http. I get the following error when running the flow service

    Launch started: 2024-09-10 09:17:41.668
    Configuration name: Jokes_flowservice
    Configuration location: C:/Users/keletsom/workspace/.metadata/.plugins/org.eclipse.debug.core/.launches/Jokes_flowservice.launch

    Could not run ‘Jokes_flowservice’
    com.wm.app.b2b.server.ServiceException: java.io.IOException: java.net.ConnectException: Connection timed out: connect

    com.wm.app.b2b.server.ServiceException: java.io.IOException: java.net.ConnectException: Connection timed out: connect
    at pub.clientimpl.http(clientimpl.java:1524)
    at sun.reflect.GeneratedMethodAccessor664.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:411)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:744)
    at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:61)
    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:250)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:56)
    at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:178)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:345)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:41)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:401)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:615)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:425)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:383)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:253)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:236)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:267)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:668)
    at com.wm.lang.flow.FlowState.step(FlowState.java:534)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:501)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1150)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:744)
    at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:61)
    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:250)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:56)
    at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:178)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:345)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:41)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:401)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:615)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:425)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:383)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:253)
    at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:127)
    at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:163)
    at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:223)
    at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:425)
    at com.wm.util.pool.PooledThread.run(PooledThread.java:134)
    at java.lang.Thread.run(Thread.java:748)
    Caused by: java.io.IOException: java.net.ConnectException: Connection timed out: connect
    at com.wm.ext.jsse.JSSESecureSocketFactory.newSocket(JSSESecureSocketFactory.java:586)
    at com.wm.ext.jsse.JSSESecureSocketFactory.createSocket(JSSESecureSocketFactory.java:973)
    at com.wm.ext.jsse.JSSESecureSocketFactory.createSocket(JSSESecureSocketFactory.java:499)
    at com.wm.net.socket.pool.SocketPool.getSocketWrapper(SocketPool.java:216)
    at com.wm.net.socket.pool.SocketPoolManager._getSocketWrapper(SocketPoolManager.java:166)
    at com.wm.net.socket.pool.SocketPoolManager.getSocketWrapper(SocketPoolManager.java:148)
    at com.wm.net.NetURLConnection.getSocket(NetURLConnection.java:988)
    at com.wm.net.NetURLConnection.openDirectConnection(NetURLConnection.java:966)
    at com.wm.net.NetURLConnection.connect(NetURLConnection.java:200)
    at com.wm.net.NetURLConnection.getInputStream(NetURLConnection.java:410)
    at com.wm.net.NetURLConnection.getInputStream(NetURLConnection.java:307)
    at com.wm.net.HttpContext.getFinalInputStream(HttpContext.java:1075)
    at com.wm.net.HttpContext.getInputStream(HttpContext.java:429)
    at com.wm.net.HttpContext.getInputStream(HttpContext.java:400)
    at com.wm.net.HttpContext.get(HttpContext.java:443)
    at com.wm.net.HttpContext.get(HttpContext.java:450)
    at pub.clientimpl.http(clientimpl.java:1362)
    … 42 more
    Caused by: java.net.ConnectException: Connection timed out: connect
    at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
    at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:589)
    at com.wm.ext.jsse.JSSESecureSocketFactory.newSocket(JSSESecureSocketFactory.java:534)


    #webMethods
    #webMethods-io-Integration
    #webMethods-cloud


  • 2.  RE: Timeout error using pub.client:http

    Posted Tue September 10, 2024 03:44 AM

    Hi @keletsom

    Seems like a Network issue. Few pointers below

    1. Is there a Firewall at either your or the Target system? If yes then mostly Whitelisting of Hostnames and IPs must be required.
    2. Have you tried to Access the same API via other tools like Postman and SOAP UI? If yes are you getting response when using these tools

    #webMethods
    #webMethods-cloud
    #webMethods-io-Integration


  • 3.  RE: Timeout error using pub.client:http

    Posted Tue September 10, 2024 05:40 AM

    HI @Kailash_Mishra

    1. Yes. I checked the IS and I get Error [ISP.0046.0019C] (tid=1170) Unable to establish connection to Enterprise Gateway Server .1.**.60:****. Exception: Connection timed out: connect.
    2. I am able to access the API from the server where IS is being hosted.

    #webMethods-io-Integration
    #webMethods-cloud
    #webMethods


  • 4.  RE: Timeout error using pub.client:http

    Posted Tue September 10, 2024 06:42 AM

    Hi,

    looks like an issue with your reverse invoke configuration.
    Can you share more details about your configuration, i.e. why you are using an Enterprise Gateway (Reverse Invoke scenario) here?

    Regards,
    Holger


    #webMethods-io-Integration
    #webMethods-cloud
    #webMethods


  • 5.  RE: Timeout error using pub.client:http

    Posted Wed September 11, 2024 01:30 AM

    HI @Holger_von_Thomsen

    Was already set up when I joined(trying to understand) , I cant give a sure answer as to why or how yet.

    Looks like the IS where Enterprise Gateway is setup has expired licenses.
    I cant connect to it from the server I am working on.

    Thanks

    Keletso


    #webMethods-cloud
    #webMethods
    #webMethods-io-Integration


  • 6.  RE: Timeout error using pub.client:http

    Posted Wed September 11, 2024 06:40 AM

    Hi,

    in this case, you should try to get in contact with the responsible admin for obtaining a new valid license for your Enterprise Gateaway.

    Regards,
    Holger


    #webMethods
    #webMethods-io-Integration
    #webMethods-cloud


  • 7.  RE: Timeout error using pub.client:http

    Posted Wed September 11, 2024 01:29 PM