WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

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.  Issue to connect webservice

    Posted 07/18/13 09:22 PM
    We have problem to connect one of the backend webservice from application.We are getting below exception when the application is hosted on WAS 7.0.0.25 ND:

    [7/18/13 17:26:31:420 CDT] 0000001e SystemErr     R   com.citigroup.ebusiness.jfp.service.simple.transport.exception.HTTPTransportException: Failed to call HTTP transport
    [7/18/13 17:26:31:421 CDT] 0000001e SystemErr     R       at com.citigroup.ebusiness.jfp.service.simple.transport.HttpTransport.send(HttpTransport.java:31)
    [7/18/13 17:26:31:421 CDT] 0000001e SystemErr     R       at com.citigroup.ebusiness.jfp.service.simple.mapping.MappingBasedService.getResponse(MappingBasedService.java:102)
    [7/18/13 17:26:31:421 CDT] 0000001e SystemErr     R       at com.citigroup.ebusiness.jfp.service.simple.mapping.MappingBasedService.invokeInternal(MappingBasedService.java:48)
    [7/18/13 17:26:31:421 CDT] 0000001e SystemErr     R       at com.citigroup.ebusiness.jfp.service.simple.AbstractContractBasedService.invoke(AbstractContractBasedSer

    [7/18/13 17:26:31:429 CDT] 0000001e SystemErr     R   Caused by: java.net.SocketException: Broken pipe

    [7/18/13 17:27:00:696 CDT] 0000001e SystemErr     R   Caused by: org.apache.commons.httpclient.NoHttpResponseException: The server failed to respond

    The same webservice we are able to connect from same application if it's hosted in WAS 7.0.0.21


    We will be thankful for every useful comment.



  • 2.  Issue to connect webservice

    Posted 07/19/13 06:57 AM
    "java.net.SocketException: Broken pipe"
    looks like the connection is dropped or broken. Pls try ping/telnet/trace .. to the target host/url.


  • 3.  Issue to connect webservice

    Posted 07/19/13 09:10 AM
    Yes..Ping to that host and telnet that host and port is working fine.More over the same webservice is being called from same server with WAS 7.0.0.21.


  • 4.  Issue to connect webservice

    Posted 07/19/13 09:20 AM
    if any FFDC logs are generated.. pls post them.


  • 5.  Issue to connect webservice

    Posted 07/19/13 12:44 PM
    I don't see any any ffdc other than this:

    FFDC Exception:java.net.MalformedURLException SourceId:com.ibm.ws.webcontainer.srt.WebGroup.getResourceAsStream ProbeId:602 Reporter:com.ibm.ws.webcontainer.webapp.WebAppImpl@66196619



    java.net.MalformedURLException: SRVE0238E: Resource paths should have a leading slash



    But don't think it's related with the webservice call.


  • 6.  Issue to connect webservice

    Posted 07/22/13 05:27 AM
    Hi Joy

    I suggest to enable traces of webservices in runtime to determine the problem:

      Troubleshooting > Logging and tracing > SERVER > Diagnostic trace service > RUNTIME TAB > Change log detail levels

      com.ibm.ws.webservices.engine.*=all=enabled
     
      [OK]

      Reproduce the problem and then disable again the trace (put *=info and click OK in runtime)  
     
    For the second error (java.net.MalformedURLException: SRVE0238E: Resource paths should have a leading slash)

    you have two options:
    www.albeesonline.com/blog/2008/09/22/jav...

    1.- In the web.xml file. ie, Open your web.xml file and search for WEB-INF/struts-config.xml and change this entry to /WEB-INF/struts-config.xml. Yes just a slash in front of the WEB-INF.

    2.- Set prependSlashToResource propertie to true.

    pic.dhe.ibm.com/infocenter/wasinfo/v7r0/...
    prependSlashToResource


    Hope this helps.  Tell us if you need more support.

    Regards


  • 7.  Issue to connect webservice

    Posted 09/04/13 03:46 PM
    Hi Joy,

    I think there a Possibility/ Problem   Regarding the HTTP Inbound and Outbound Transport Chain ports  during Start up.

     Just change those ports by using admin console  and restart once to see if your problem got solved.


    Thank you.