Topic
  • 9 replies
  • Latest Post - ‏2013-04-24T23:49:17Z by YPS1_guybrush_guybrush
NehaSawant
NehaSawant
14 Posts

Pinned topic Error while invoking SOAP webservice

‏2012-09-17T05:37:51Z |
Hi All,

I am getting following error when I try to invoke a SOAP webservice.
Internal error: java.lang.RuntimeException: Parameter 'header' is not an XmlCursor; instead has type com.approuter.maestro.opera.rdbms.RdbmsXmlString

I can access the same service using SOAP UI & it is running fine. However it is giving above error when invoked from Cast Iron.

Can anyone please help me on this?

Best Regards,
Neha
Updated on 2012-10-19T11:13:12Z at 2012-10-19T11:13:12Z by NehaSawant
  • PingLu
    PingLu
    44 Posts

    Re: Error while invoking SOAP webservice

    ‏2012-09-17T15:38:24Z  
    Are you using the Invoke Web Service Activity or an HTTP Request Activity?
  • NehaSawant
    NehaSawant
    14 Posts

    Re: Error while invoking SOAP webservice

    ‏2012-10-19T11:13:12Z  
    • PingLu
    • ‏2012-09-17T15:38:24Z
    Are you using the Invoke Web Service Activity or an HTTP Request Activity?
    Yes I am using Invoke Service activity.
  • JonLaL
    JonLaL
    4 Posts

    Re: Error while invoking SOAP webservice

    ‏2013-04-24T05:16:27Z  

    I'm getting this error as well using 6.3.0.0.  Did you find a resolution?

     

    A simple Invoke Service activity works fine in Studio.  When Published and started on the appliance, the Invoke Service activity errors.

     

    From the WMC i have been able to find a log of the following:

     

    Exception while processing Web Service activity.  Error message: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml].  Caused by: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]

     

    I've added an httpheader name/value pair to the Invoke Service to try and force Content-Type to be text/xml.  It did not work.

     

  • NehaSawant
    NehaSawant
    14 Posts

    Re: Error while invoking SOAP webservice

    ‏2013-04-24T07:04:39Z  
    • JonLaL
    • ‏2013-04-24T05:16:27Z

    I'm getting this error as well using 6.3.0.0.  Did you find a resolution?

     

    A simple Invoke Service activity works fine in Studio.  When Published and started on the appliance, the Invoke Service activity errors.

     

    From the WMC i have been able to find a log of the following:

     

    Exception while processing Web Service activity.  Error message: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml].  Caused by: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]

     

    I've added an httpheader name/value pair to the Invoke Service to try and force Content-Type to be text/xml.  It did not work.

     

    Yes this error get resolved for me. It seems the SOAP services I was using had some issues due to which i was unable to invoke services.

    SOAP team did some changes post to which my flow worked fine.

  • YPS1_guybrush_guybrush
    46 Posts

    Re: Error while invoking SOAP webservice

    ‏2013-04-24T09:10:39Z  

     

    I'm having the same issue as well. The webservice runs fine when invoke via SoapUI, but when it's invoked via invoke service activity of cast iron, the following error message obtained from the response. Any idea what's wrong with it? I'm suspecting the request that Cast Iron send out is different from the format that the receiving end expect. If we strictly follow the format that SOAPUI has, and use a http endpoint invoke activity to send the request to the receiving end, however it's behaving correctly.

    SOAP fault: <?xml version="1.0"?>
    <SOAP-ENV:Fault xmlns:SOAP-ENV="http:// schemas.xmlsoap.org/soap/ envelope/"><faultcode> VersionMismatch.ExpatError</ faultcode><faultstring>syntax error: line 1, column 0</faultstring><detail/></ SOAP-ENV:Fault>
     
    Encountered fault of type (VersionMismatch.ExpatError), please see rest of the log for more information
     
    Exception invoking the webservice activity. The Exception is: <html><body><h1>Internal error</h1>Ticket issued: <a href="/admin/default/ticket/ webservice/192.169.120.231. 2013-04-17.16-01-57.c83815c2- e185-41ba-9225-24ac4e6bf240" target="_blank">webservice/ 192.169.120.231.2013-04-17.16- 01-57.c83815c2-e185-41ba-9225- 24ac4e6bf240</a></body><!-- this is junk text else IE does not display the page: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xx //--></html> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxx
     
    Exception while processing web service activity.  Error message: syntax error: line 1, column 0.  Caused by: syntax error: line 1, column 0.

     

    and 

     

    Exception while processing Web Service activity.  Error message: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml].  Caused by: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]

  • JonLaL
    JonLaL
    4 Posts

    Re: Error while invoking SOAP webservice

    ‏2013-04-24T14:13:47Z  

    I forgot to mention the web service that I am trying to invoke is to the castiron management API.

    calling "Login"

    http://castironappliance.domain.com/ws/security?wsdl

    Works perfect from Studio.  Dies on the appliance.

  • YPS1_guybrush_guybrush
    46 Posts

    Re: Error while invoking SOAP webservice

    ‏2013-04-24T14:26:09Z  
    • JonLaL
    • ‏2013-04-24T14:13:47Z

    I forgot to mention the web service that I am trying to invoke is to the castiron management API.

    calling "Login"

    http://castironappliance.domain.com/ws/security?wsdl

    Works perfect from Studio.  Dies on the appliance.

    Well, you can get an example on how to use the web management API webservice from TIPS repository. That TIPs is working and basically you just need to configure the endpoints and mapping accordingly.

  • JonLaL
    JonLaL
    4 Posts

    Re: Error while invoking SOAP webservice

    ‏2013-04-24T16:50:15Z  

    I have looked at the TIPS and also downloaded a sample project from an article:

    http://www.ibm.com/developerworks/websphere/library/techarticles/1203_ray/1203_ray.html

    They all exhibit the same problem.

    I have done some more digging into the logs and have noticed that the "Unsupported Content-Type" error message is not from the web service but instead from the Invoke Service activity.  Of course, it is expecting text/xml in back from the service provider.  However it is receiving a 404 HTML page that castiron is returning and stating that "/ws/security" is not found.

    I have two appliances:  PRD (6.1.0.6)  and DEV (6.3.0.0) and I decided to do some testing directly in PRD which I hadn't tried before.

     

    Studio works pointing to http://PRD/ws/security

    Studio works pointing to http://DEV/ws/security

    SoapUI works pointing to http://PRD/ws/security

    SoapUI works pointing to http://DEV/ws/security

     

     

    Orch running on PRD and pointing to http://PRD/ws/security works

     

    Orch running on PRD and pointing to http://DEV/ws/security works

     

    Orch running on DEV and pointing to http://PRD/ws/security works

    Orch running on DEV and pointing to http://DEV/ws/security  does NOT work

    In short, the only configuration that doesn't work is when DEV is calling itself.

     

    Is a bug/enhancement on 6.3.0.0?

     

     

     

  • YPS1_guybrush_guybrush
    46 Posts

    Re: Error while invoking SOAP webservice

    ‏2013-04-24T23:49:17Z  
    • JonLaL
    • ‏2013-04-24T16:50:15Z

    I have looked at the TIPS and also downloaded a sample project from an article:

    http://www.ibm.com/developerworks/websphere/library/techarticles/1203_ray/1203_ray.html

    They all exhibit the same problem.

    I have done some more digging into the logs and have noticed that the "Unsupported Content-Type" error message is not from the web service but instead from the Invoke Service activity.  Of course, it is expecting text/xml in back from the service provider.  However it is receiving a 404 HTML page that castiron is returning and stating that "/ws/security" is not found.

    I have two appliances:  PRD (6.1.0.6)  and DEV (6.3.0.0) and I decided to do some testing directly in PRD which I hadn't tried before.

     

    Studio works pointing to http://PRD/ws/security

    Studio works pointing to http://DEV/ws/security

    SoapUI works pointing to http://PRD/ws/security

    SoapUI works pointing to http://DEV/ws/security

     

     

    Orch running on PRD and pointing to http://PRD/ws/security works

     

    Orch running on PRD and pointing to http://DEV/ws/security works

     

    Orch running on DEV and pointing to http://PRD/ws/security works

    Orch running on DEV and pointing to http://DEV/ws/security  does NOT work

    In short, the only configuration that doesn't work is when DEV is calling itself.

     

    Is a bug/enhancement on 6.3.0.0?

     

     

     

    Hi Jon,

     

    Once you've managed to identified the pattern, you should use your ibm ID to log a PMR case with IBM support and let them investigate it. You need to provide them with the information you have so that they can have a look on that and try to simulate it out.