Proxy to Web service Error

Hi ,
Please let me know about this error?
"" Error Exception caught by adapter framework: Exception in method process.??"
Its a proxy to web service scenario.
Thanks in advance.
Regards
Sai

Hi,
   The best option for searching more information about the error is to use Netweaver Administrator application. In "log viewer application" you can find more detailed information about the error ocurred in your application.
    Another option is to analize the trace information in XML Header.
    Please, put the  detail error text in this forum. It's very difficult for us to help you with this information.
Best regards
Ivá

Similar Messages

  • Proxy to Web Service Communication doesn't work

    Hi,
    We configured the XI demo example “Checking Flight Seat Availability (Proxy to Web Service Communication)“ (chapter 6.2) and everything works fine until we try to execute the szenario (chapter 6.2.3).
    When we try to execute the szenario, we get an error displayed in the runtime Workbench. In the component Integration Server, we get a systemfailure with code “ADAPTER.SOAP_EXCEPTION” of category “PARSING”. The Adapter Engine also displays an error in the audit log:
    “SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Authority check failed”
    The User XIAFUSER has SAP-All-authorizations.
    Has anybody an idea, what’s the problem is?
    Greetings
    Hildegard
    Message was edited by: Hildegard Winter

    Check out, that the URL of the WebService is correct:
    "http://<YourServer>:<<b>ABAP_Port</b>>/sap/bc/srt/xip/sap/SXIDAL_FLIGHTSEATAVAIL_CHECK?sap-client=<<b>YourClient</b>>"
    Change the default values if necessary.
    Check in the client, if the role SAP_XI_APPL_SERV_USER (which should be applied to your user) is generated and has no errors.
    Regards
    Stefan

  • Web Services Error When running Sample Application

    When I was testing "Create a New Customer" from the Sample application in Oracle's provided free new HTML DB 2.0 environment (just out last night), I got the following error message.
    ORA-20001: The webservice was unreachable because either the URL you supplied was invalid, or your environment requires a valid proxy server address for HTTP requests.
    I was using my laptop through SBC Yahoo DSL service (dynamic IP address) to test this HTML DB Sample application.
    Any suggestion for this Web Services Error?

    cckung,
    Oracle's IT team has disabled the ability to call web services from htmldb.oracle.com. We are working with them to resolve this, but I don't have an ETA.
    Thanks,
    - Scott -

  • LS Join Launcher Web Service error 64008

    I getting multiple
    LS Join Launcher Web Service errors (id 64008) on my Front-end servers (LHPv2) and online meetings stopped working. I have reinstalled Web components, but it didn't
    help. Any ideas?
    An exception was encountered when sending Conference Error Report.
     Conference Error Report + Exception Details. CER = Machine:SERVERNAMEBrowserId:Join
    attempted at(UTC):12/10/2013 6:28:13 AMError: request context was lostException = System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.Rtc.Internal.JoinLauncher.JoinLauncherTelemetryProxy.SendCERReport(JoinLauncherAsyncContext asyncContext)
    Cause: Failed to report Conference Error Report. Please look through the exception details for more information.
    Resolution:
    Please check if the Data collection agent is running fine & Storage Service is accepting connections

    Process I followed on my FE servers:
    1. stop-cswindowsservice
    2. net stop w3svc
    3. unistalled Web Components and URL-Rewrite
    4. rebooted FE server
    5. run Bootstrapper and install Web
    Components and URL-rewrite module
    6. run LyncserverUpdateInstaller.exe
    from LHPv2 ISO image and install recent updates for Web Components.
    7. one more reboot 
    Now, Lync Online Meetings are working,
    but LS Join Launcher error 64008 is still there, repeating every 15-20 seconds on every FE servers(I have five)
    I tried Lync Server 2013 Logging Tool
    on one of my FE servers and I found these additional errors:
    TL_ERROR(TF_COMPONENT) [5]0DC8.0FF0::12/12/2013-07:45:57.785.00000117 (JoinLauncher,JoinLauncherProxyRouter.ComputeIncomingURL:3166.idx(2740))
    (0000000000403C61)URL Path is either NULL / empty or points to resources directory
    TL_ERROR(TF_COMPONENT) [5]0DC8.0FF0::12/12/2013-07:45:57.785.00000135 (JoinLauncher,Default_aspx.Page_Load:849.idx(1915))
    (00000000010FCA91)Context flag is missing !
    TL_ERROR(TF_COMPONENT) [5]0DC8.0FF0::12/12/2013-07:45:57.785.00000137 (JoinLauncher,Default_aspx.Page_Load:849.idx(1961))
    (00000000010FCA91)Proxy module didnt find this meeting to be valid. Preparing to send the correct error response !
    TL_ERROR(TF_COMPONENT) [5]0DC8.0FF0::12/12/2013-07:45:57.785.00000138 (JoinLauncher,JoinLauncherTelemetryProxy.SendCERReport:1579.idx(152))
    (0000000003581F88)Failed to report CER to the DB.

  • SAP Web Service error text : The database returned a value containing an error , type  CX_SY_OPEN_SQL_DB

    Hello Guru's,
    we are creating sales order in SAP from a quote created in .NET,  through Web Service created in SAP, and consumed in .NET.
    When ever a order is created in SAP for a given quote, SAP returns the sales order number to .NET.
    Orders are getting created as expected, but once in a while we are getting the following error from webservice :
    Web service processing error; more details in the web service error log on provider side (UTC timestamp 20140609173429; Transaction ID 4DFCEFE33301F1EBB5CE00155D0B4530)
    But the problem is order is getting created in SAP for the perticular quote for which we are getting the above error and this order number is not getting returned to .NET.
    Upon analysis in TCODE  SRT_UTIL for the above transaction ID, has the following details , which are hardly help full to resolve the error.
    ----TYPE                                  CX_SY_OPEN_SQL_DB
    ----ERROR_TEXT                   The database returned a value containing an error
    ----CX_SY_NO_HANDLER
    -----CLASSNAME                     CX_SY_OPEN_SQL_DB
    This Exception raised by Web Service application
    Could you please help in resolving this issue or alteast provide an approach for the same.
    Thank you,
    Suresh.

    Thank you Bhaskar,
    How can we clarify whether the error is from SAP or Web part.
    I have checked ST22, but there is not entry for the perticular  exception transaction ID
    My exception time stamp is
    -------------------START-------------6/9/2014 1:34:33 PM
    Error :Web service processing error; more details in the web service error log on provider side (UTC timestamp 20140609173429; Transaction ID 4DFCEFE33301F1EBB5CE00155D0B4530)
    -------------------END-------------6/9/2014 1:34:33 PM
    In al11, i found the following for the perticular exception time stamp
    **** Trace file opened at 20140609 133431 Eastern Daylight Time, by disp+work
    **** Versions SAP-REL 720,0,500 RFC-VER U 3 1442251 MT-SL
    XRFC> Begin of user trace
    XRFC> ---------------------------------------------------------------------
    XRFC>                                                                     <
    XRFC> TRACE SOAP RUNTIME - header                                         <
    XRFC>                                                                     <
    XRFC> ------------------------------------------------------------------  <
    XRFC> REQ_SIZE   : 2685                                                   <
    XRFC> RESP_SIZE  : 0                                                      <
    XRFC> PARENT_ID  : ROOT_CALL_ID                                           <
    XRFC> TRC_KEY    : 40FCEFE3BD6EF184B5CE00155D0B4530                       <
    XRFC> REQ_BASED  :                                                        <
    XRFC> SESSION_ID : 0003925540FCEFE3BD6EF17DB5CE00155D0B4530               <
    XRFC> TS_CALL    : 20140609173408.2880000                                 <
    XRFC> SY_UNAME   :                                            <
    XRFC> HOSTNAME   :                                              <
    XRFC> SY_SID     : PRD                                                    <
    XRFC> SY_MANDT   : 300                                                    <
    XRFC> SYS_NR     : 19                                                     <
    XRFC> APPLSERVER :                                      <
    XRFC> ISPRESCHED : X                                                      <
    XRFC> DURATION   : 21810                                                  <
    XRFC> NETHDRTIME : 21810                                                  <
    XRFC> CALL_STATE : 2                                                      <
    XRFC> ERRORTYPE  : APPLFAIL                                               <
    XRFC> ERRORAREA  : APPL                                                   <
    XRFC> CTXDP_TYPE : SOAP_RUNTIME                                           <
    XRFC> SYNC_ASYNC : S                                                      <
    XRFC> LOCATION   : P                                                      <
    XRFC> DIRECTION  : I                                                      <
    XRFC> REQ_ID     : 91C57815916E421CA9F3D652FFACE9C7                       <
    XRFC> RESP_ID    : 00155D0B45301EE3BBFF89A0267EB5CE                       <
    XRFC> MSG_STATE  : 114                                                    <
    XRFC> IF_NAME_I  : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> IF_NS_E    : urn:sap-com:document:sap:soap:functions:mc-style       <
    XRFC> IF_NAME_E  : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> ISSHORTCUT :                                                        <
    XRFC> TRC_PATT   : WSTEST                                                 <
    XRFC> TRC_SSID   : PRD_19                                                 <
    XRFC> TRC_USER   :                                           <
    XRFC> TRC_TS     : 20140609173409                                         <
    XRFC> TRC_COUNT  : 99                                                     <
    XRFC> TRC_EXT    :                                                        <
    XRFC> COMPLETE   : OK                                                     <
    XRFC> CALLEDPROG : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> SOAP_APPLI : urn:sap-com:soap:runtime:application:rfc:710           <
    XRFC> CONF_ID    : 00155D0B45301EE3AEFDAD78756555CE                       <
    XRFC> BIND_ID    : 00155D0B45301EE3AEFDAD787565B5CE                       <
    XRFC> OP_NAME    : ZsdCsCreateSalesorder                                  <
    XRFC> COMM_PATRN : Method:ZsdCsCreateSalesorder                           <
    XRFC> OP_NS      : urn:sap-com:document:sap:soap:functions:mc-style       <
    XRFC> REMADDRESS : 172.16.11.43                                           <
    XRFC> DT_OBJ     : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> MEMCONSUMP : 296291                                                 <
    XRFC> WSHOST     :                                                        <
    XRFC> WSPORT     :                                                        <
    XRFC> WSPROT     :                                                        <
    XRFC> WSCLIENT   :                                                        <
    XRFC> WSPATH     :                                                        <
    XRFC> PXYHOST    :                                                        <
    XRFC> PXYPORT    :                                                        <
    XRFC> USEDRFCDES :                                                        <
    XRFC> BONAME     :                                                        <
    XRFC> PROCCOMP   :                                                        <
    XRFC> DEPLOYUNIT :                                                        <
    XRFC> ------------------------------------------------------------------  <
    XRFC>                                                                     <
    XRFC> TRACE SOAP RUNTIME - trace records                                  <
    XRFC>                                                                     <
    XRFC> ------------------------------------------------------------------  <
    XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING Exception handling for IF "ZSD_CS_CREATE       <
    XRFC> _SALESORDER_SERVI" OP name "ZsdCsCreateSalesorder" MSG ID           <
    XRFC> "91C57815916E421CA9F3D652FFACE9C7" user "STULZWEBSERV"              <
    XRFC>                                                                     <
    XRFC>                                                                     <
    XRFC> E SOAP_RUNTIME 20140609173429.7240000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING CX_SOAP_ROOT : An exception has occurred. |    <
    XRFC> program: CL_SOAP_RUNTIME_ROOT==========CP include: CL_SOAP          <
    XRFC> _RUNTIME_ROOT==========CM004 line: 120                              <
    XRFC>                                                                     <
    XRFC>                                                                     <
    XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING CX_SY_NO_HANDLER : An exception with the type  <
    XRFC> CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor    <
    XRFC> declared in a RAISING clause | program: SAPLSTXD include: LSTXDFDB  <
    XRFC> line: 200                                                           <
    XRFC>                                                                     <
    XRFC>                                                                     <
    XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING CX_SY_OPEN_SQL_DB : The database returned a    <
    XRFC> value containing an error | program: SAPLSTXD include: LSTXDFDB     <
    XRFC> line: 227                                                           <
    XRFC>                                                                     <
    XRFC> ---------------------------------------------------------------------
    XRFC> End of user trace

  • SOA - real time proxy to web service scenario

    Hello Experts,
    I am working on PI but really very much new to the SOA concept.
    But i have to prepare document which explains about all steps that we need to follow (technicallly) for the SOA implementation.
    We are going to implement one Proof of Concept for SOA before going for the real project.
    Can someone please help me and tell me what all the things i need to do for Proxy to Web Service Scenario in PI.
    I hope i have made myself clear about it.
    Thanks,
    Hetal

    Hi Gaurav,
    Thanks for your advice.
    I have one more question and i tried to explore SDN alot but didnt get satisfactory answer.
    here is the situation:
    My scenario is like :
    .Net application = consumer
    ECC = Provider
    PI = broker
    SR = Publish ES
    I am using the Outside - In approach, where i am creating proxy structure in ESR and then creating/ Generating Proxy in ECC.
    I am exposing my Inbound Interface on SR, so that the WSDL is available on SR.
    Now the situation is, our consumer is asking data from us in different format.
    I read on help.sap.com that via PI mapping it is possible.
    But i am not understanding that consumer is using ECC WSDL to make a call, then even though mapping is there, how can they get response in their required format.
    They are even providing us their WSDL. I am totally confused that in one interface how come two different WSDLs can work?
    Or is there a way for this?
    I am even ready to use the same structure for my ECC which is provided by consumer, but then i dont see any outcome using PI.
    I also have question, that for standard service also, ECC Enterprise service structure is fixed which we expose, then using PI how can we provide consumers response in their desired way.
    I know that m asking this question again and again, but still it is not getting clear to me... might be m not understanding that how it works in SOA.
    If possible can you tell me the steps that i need to follow technically to develope this interface? so that i can get better understanding?
    Thanks,
    Hetal

  • I get an web service error when trying enable web services. I have latest update and rebooted

    i get an web service error when trying enable web services. I have latest update and rebooted

    hi there philnj,
    could you help the community narrow troubleshooting by providing a little more information? Particularly what model printer are we dealing with?
    You can say thanks by clicking the Kudos Star in my post. If my post resolves your problem, please mark it as Accepted Solution so others can benefit too.

  • What the mechanism of the Java Proxy for Web Services in WLS 8.1

    Hi, all;
    I try to find out how the java proxy of web service in weblogic server 8.1
    works. Suppose I use the java Proxy of a WebSerice in a client application whatever
    whithin or outside the application of the web service, does the proxy actually:
    1. translate my java arguments objects in XML to create SOAP msg,
    2. then send the msg across the network, and web service also response SOAP msg,
    3. then proxy translate it into return value of the method call ?
    If that is true , the Java Proxy seems very inefficient, right?
    Can any body tell me how the proxy works ?
    regards,
    shannon

    Hi Shannon,
    The type of proxy I'm familiar with is at the http connection level and
    associated with the networking properties in the JDK, See:
    http://java.sun.com/j2se/1.4.2/docs/guide/net/properties.html
    Your question may be related to JWS proxies, See:
    http://edocs.bea.com/workshop/docs81/doc/en/workshop/guide/howdoi/howUseTheJavaProxyForAWebService.html
    You may want to ask this question in the workshop newsgroup.
    Hope this helps,
    Bruce
    shannon lee wrote:
    >
    Hi, all;
    I try to find out how the java proxy of web service in weblogic server 8.1
    works. Suppose I use the java Proxy of a WebSerice in a client application whatever
    whithin or outside the application of the web service, does the proxy actually:
    1. translate my java arguments objects in XML to create SOAP msg,
    2. then send the msg across the network, and web service also response SOAP msg,
    3. then proxy translate it into return value of the method call ?
    If that is true , the Java Proxy seems very inefficient, right?
    Can any body tell me how the proxy works ?
    regards,
    shannon

  • HP Photosmart 7520 unable to connect to web services error

    I've used my HP Photosmart 7520 for years without issue scanning to email.  Now I get "Unable to connect to Web Services" error message.  I've done all the procedures listed in the blog, including changing the manual DNS server configuration and still get the same error.  Help!

    Hi @ajbond77,
    Welcome to the HP Support Forums.  I understand that you are getting a connection error message when attempting to use the scan to email feature of your Photosmart 7520 printer.
    If you have already set a manual IP address and manual DNS servers, then please call HP’s Cloud Services at 1-855-785-2777 if you live in the USA/Canada region. If you live outside the USA/Canada region please click here to find the Technical Support number for your country/region.
    Regards,
    Happytohelp01
    Please click on the Thumbs Up on the right to say “Thanks” for helping!
    Please click “Accept as Solution ” on the post that solves your issue to help others find the solution.
    I work on behalf of HP

  • LYNC Server 2013 LS Address Book and Distribution List Expansion Web Service error - Event ID 62005

    Hi,
      Recently,  I found some of LS Address Book and Distribution List Expansion Web Service error from Lync 2013 Front  End Server, kindly advise help how to solve it. many thanks
    Distribution List Expansion Web Service failed to initialize.
    Exception: The server is not operational.
    Cause: Unexpected exception occurred during initialization.
    Resolution:
    Examine exception details in event to determine the resolution.
    Best Regards
    Thomas

    Hi,
    You can do the following steps to solve the issue:
    Please double check the Windows Firewall is turned off.
    Please check if the CMS replication update to the latest version.
    Make sure Lync Server update to the latest version.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • WSDL error during generation of  ABAP proxy for web service

    Hi friends,
    I am getting error during the generation of ABAP proxy object for web service developed in .NET .
    Error : Proxy generation terminated: WSDL error (<extension> not supported).
    How to make this WSDL file compatible  for  ABAP proxy.
    I have tried to edit WSDL file in XML Spy but did not get any option to replace/remove the tag <extention>.
    If any one worked on this. Please help me its urgent.
    Thanks and regards,
    Shivanand.

    HI ,
    I am having the same issue!!!
    Does ABAP Proxy Generation support <extension> ?
    Is there a list available of what is supported and what not (please consider I do not have access to sap notes)?
    Thanks

  • Error calling[Standalone proxy]uFF1Aexternal web service(SSL + anonymous)

    hi SDNer
          I use Standalone proxy to call external web service(SSL + anonymous)
    web service Endpoint is : https://localhost:8443/HelloWorldService/services/HelloWorld
    NWDS VERSION: NWDS-IDE-700SP12
    Standalone SEI is :
    HelloWorld
    HelloWorldHttpBindingStub
    HelloWorldImpl
    HelloWorldPortType
    Calling Code as following:
                   //1. Access the implementation class of the service interface
                   HelloWorldImpl ws = new HelloWorldImpl();
                   //2. Create the instance of a logical port
                   Remote remote = ws.getLogicalPort();
                   HelloWorldHttpBindingStub stub = (HelloWorldHttpBindingStub) remote;
                   //3.
                   SecurityProtocol securityProtocol =
                        (SecurityProtocol) stub._getGlobalProtocols().getProtocol(
                             "SecurityProtocol");
                   AuthenticationContext ac =
                        securityProtocol.getAuthenticationContext();
                   ac.setIgnoreSSLServerCertificate(true);
                   //4. invoke the business methods
                   String ver = stub.example(str1, str2);
    Exception is :
    java.rmi.RemoteException: Service call exception; nested exception is:
         iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure
         at com.sap.ws.HelloWorldHttpBindingStub.example(HelloWorldHttpBindingStub.java:84)
         at com.sap.ws.HelloWorldHttpBindingStub.example(HelloWorldHttpBindingStub.java:94)
         at TestHelloWorld.wsHelloWorld(TestHelloWorld.java:55)
         at TestHelloWorld.main(TestHelloWorld.java:24)
    Caused by: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure
         at iaik.security.ssl.r.f(Unknown Source)
         at iaik.security.ssl.x.b(Unknown Source)
         at iaik.security.ssl.x.a(Unknown Source)
         at iaik.security.ssl.r.d(Unknown Source)
         at iaik.security.ssl.SSLTransport.startHandshake(Unknown Source)
         at iaik.security.ssl.SSLTransport.getOutputStream(Unknown Source)
         at iaik.security.ssl.SSLSocket.getOutputStream(Unknown Source)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:669)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:470)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:427)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:355)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:550)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)
         at com.sap.ws.HelloWorldHttpBindingStub.example(HelloWorldHttpBindingStub.java:77)
         ... 3 more

    Hi
    Answer is pure assumption
    The error "iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure" is mentioned in the the OSS note
    Note 1157248 - SAP Business Connector with SSL / Common Problems
    Pls take opinion from SAP / Basis before implementing the note
    Regards
    Madhan D

  • Invoke Web Service error: WS Client ---Deployable Proxy --WS-https

    hi all:
    I use Deployable Proxy in NWDS to call Web Service(https-SSL)
    working on PI7.0 platform
    Scenario is :
    WSClient(Stateless EJB) -
    >Deployable Proxy ---> WS-https
    Deployable Proxy setting:
    SSL Service Certification : Ignore Service Certification
    Run Result is :
    Sometimes it works(Really amazing)
    Sometimes it doesn't work.
    When it doesn't work:
    The http response is : HTTP/1.1 500 Internal Server Error
    J2EE engine exception log is : pay attention the Strong msg
    [EXCEPTION]
    com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method getVersion.
         at com.sap.ejb.VersionLocalLocalObjectImpl0_0.getVersion(VersionLocalLocalObjectImpl0_0.java:119)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
         at SoapServlet.doPost(SoapServlet.java:51)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: javax.xml.rpc.soap.SOAPFaultException: java.lang.NullPointerException
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:737)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processRpcFault(MimeHttpBinding.java:771)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1470)
         at com.sap.ws.VersionSoapBindingStub.getVersion(VersionSoapBindingStub.java:74)
         at com.sap.ejb.VersionBean.getVersion(VersionBean.java:44)
         at com.sap.ejb.VersionLocalLocalObjectImpl0_0.getVersion(VersionLocalLocalObjectImpl0_0.java:103)
         ... 25 more
    javax.xml.rpc.soap.SOAPFaultException: java.lang.NullPointerException
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:737)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processRpcFault(MimeHttpBinding.java:771)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1470)
         at com.sap.ws.VersionSoapBindingStub.getVersion(VersionSoapBindingStub.java:74)
         at com.sap.ejb.VersionBean.getVersion(VersionBean.java:44)
         at com.sap.ejb.VersionLocalLocalObjectImpl0_0.getVersion(VersionLocalLocalObjectImpl0_0.java:103)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
         at SoapServlet.doPost(SoapServlet.java:51)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Edited by: paul yang on Mar 9, 2009 8:41 AM

    Hi Paul,
    As it sometimes works & throws error in some cases, I would recommend you to try restarting the application server.
    Also, as there is some version related issue, you can also try to re-deploy the webservice (I think you are exposing the EJB as webservice), restart the server, deploy new archive & run the application.
    Hope this helps you.
    Kind Regards,
    Nitin

  • Error While generating Web Service Proxy using Web Service Action in MII 12

    Hi All,
    We are using the Web Service action block in BLS transaction to call a web service from an external legacy system. When we provide the WSDL in the action block configuration and click Next we can see the Port and Operation of the web service which we have selected and finally clicked on Finish. On clicking Finish it is giving an error "[Fatal Error] :-1:-1: Premature end of file." and no web service request/response structures are being generated.
    The WSDL file is attached herwith. Please check and provide the solution. We are using MII 12.2 SP02 with latest patch.
    An error message is also added to the NetWeaver log as below:
    XmlProxy Error: Premature end of file.
    [EXCEPTION]
    org.xml.sax.SAXParseException: Premature end of file.
    at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
    at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
    at com.sap.lhcommon.schema.XmlHelper.loadDocument(XmlHelper.java:38)
    at com.sap.lhcommon.schema.XmlHelper.loadDocumentNS(XmlHelper.java:28)
    at com.sap.lhcommon.webservice.SoapMessage.getExampleXmlAsBytes(SoapMessage.java:103)
    at com.sap.xmii.servlet.XmlProxy.service(XmlProxy.java:204)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
    at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
    at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
    The wsdl file is as follows:
    <wsdl:definitions
    targetNamespace="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://pod.service.server.mesassembly.cis.cat"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:intf="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:impl="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
    >
    <wsdl:types>
       <schema targetNamespace="http://pod.service.server.mesassembly.cis.cat"
       xmlns="http://www.w3.org/2001/XMLSchema">
       <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
       <complexType name="ProductionOrderDetailsInput">
       <sequence>
         <element name="detailsString" type="xsd:base64Binary"/>
         <element name="productionOrderNumber" nillable ="true" type="xsd:string"/>
         <element name="fullExplosionFlag" type="xsd:string"/> 
       </sequence>
       </complexType>
       <complexType name="ProductionOrderDetailsReceipt">
       <sequence>
         <element name="errorMessage" nillable="true" type="xsd:string"/>
         <element name="valid" type="xsd:boolean"/>
       </sequence>
       </complexType>
       </schema>
    </wsdl:types>
    <wsdl:message name="processOrderDetailsResponse">
      <wsdl:part name="podReturn" type="tns:ProductionOrderDetailsReceipt" />
    </wsdl:message>
    <wsdl:message name="processOrderDetailsRequest">
      <wsdl:part name="input" type="tns:ProductionOrderDetailsInput" />
    </wsdl:message>
      <wsdl:portType name="PodService">
        <wsdl:operation name="ProcessOrderDetails" parameterOrder="input">
          <wsdl:input message="impl:processOrderDetailsRequest"
          name="processOrderDetailsRequest"/>
          <wsdl:output message="impl:processOrderDetailsResponse"
          name="processOrderDetailsResponse"/>
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name="ProdOrderDetailsSoapBinding" type="impl:PodService">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="ProcessOrderDetails">
          <soap:operation soapAction="http://pod.service.server.mesassembly.cis.cat/NewOperation"/>
          <wsdl:input name="processOrderDetailsRequest">
            <soap:body  use="literal"  encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod"  />
          </wsdl:input>
          <wsdl:output name="processOrderDetailsResponse">
            <soap:body  use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod"  />
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="PodService_Service">
        <wsdl:port binding="impl:ProdOrderDetailsSoapBinding" name="ProdOrderDetails">
          <soap:address location="http:/localhost:8080/MESAssembly/services/ProdOrderDetails"/>
        </wsdl:port>
      </wsdl:service>
    </wsdl:definitions>

    The WSDL file is as follows:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions
    targetNamespace="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://pod.service.server.mesassembly.cis.cat"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:intf="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:impl="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
    >
    <wsdl:types>
       <schema targetNamespace="http://pod.service.server.mesassembly.cis.cat"
       xmlns="http://www.w3.org/2001/XMLSchema">
       <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
       <complexType name="ProductionOrderDetailsInput">
       <sequence>
         <element name="detailsString" type="xsd:base64Binary"/>
         <element name="productionOrderNumber" nillable ="true" type="xsd:string"/>
         <element name="fullExplosionFlag" type="xsd:string"/> 
       </sequence>
       </complexType>
       <complexType name="ProductionOrderDetailsReceipt">
       <sequence>
         <element name="errorMessage" nillable="true" type="xsd:string"/>
         <element name="valid" type="xsd:boolean"/>
       </sequence>
       </complexType>
       </schema>
    </wsdl:types>
    <wsdl:message name="processOrderDetailsResponse">
      <wsdl:part name="podReturn" type="tns:ProductionOrderDetailsReceipt" />
    </wsdl:message>
    <wsdl:message name="processOrderDetailsRequest">
      <wsdl:part name="input" type="tns:ProductionOrderDetailsInput" />
    </wsdl:message>
      <wsdl:portType name="PodService">
        <wsdl:operation name="ProcessOrderDetails" parameterOrder="input">
          <wsdl:input message="impl:processOrderDetailsRequest"
          name="processOrderDetailsRequest"/>
          <wsdl:output message="impl:processOrderDetailsResponse"
          name="processOrderDetailsResponse"/>
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name="ProdOrderDetailsSoapBinding" type="impl:PodService">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="ProcessOrderDetails">
          <soap:operation soapAction="http://pod.service.server.mesassembly.cis.cat/NewOperation"/>
          <wsdl:input name="processOrderDetailsRequest">
            <soap:body  use="literal"  encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod"  />
          </wsdl:input>
          <wsdl:output name="processOrderDetailsResponse">
            <soap:body  use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod"  />
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="PodService_Service">
        <wsdl:port binding="impl:ProdOrderDetailsSoapBinding" name="ProdOrderDetails">
          <soap:address location="http:/localhost:8080/MESAssembly/services/ProdOrderDetails"/>
        </wsdl:port>
      </wsdl:service>
    </wsdl:definitions>

  • Web Service error com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStack

    Hi,
    I have implemented a Java class which calls some XML RPC 3.0 proxy methods.
    If I test the method input inside a "main ()" method and get the output, it works nice.
    The XML RPC 3.0 procy method is also invoked and there is no problem.
    However, when I expose this java class as a "web service" and invoke the web service from the JDeveloper integrated console or
    even an external test client running on a browser, I get the error mentioned below.
    Which setting must be defined in the JDevelopper ( Studio Edition Version 11.1.1.2.0 on :
    set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false"
    class="java.lang.NoClassDefFoundError"
    +++++++++ Integrated WebLogic server ( + Integrated WebLogic server started on port 7101) +++++++++
    [Running application AllCustomers on Server Instance IntegratedWebLogicServer...]
    [02:47:42 PM] ---- Deployment started. ----
    [02:47:42 PM] Target platform is (Weblogic 10.3).
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Thanks
    YL
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Body>
    <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
    <faultcode>S:Server</faultcode>
    <faultstring>org/opensource/proxy/OpenSourceApiXmlRpcProxy</faultstring>
    <detail>
    <ns2:exception xmlns:ns2="http://jax-ws.dev.java.net/" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" class="java.lang.NoClassDefFoundError">
    <message>org/opensource/proxy/OpenSourceApiXmlRpcProxy</message>
    <ns2:stackTrace>
    <ns2:frame line="246" file="GetAllCustomers.java" method="GetOneCustomerWithProxy" class="com.std.customer.GetAllCustomers" />
    <ns2:frame line="native" file="NativeMethodAccessorImpl.java" method="invoke0" class="sun.reflect.NativeMethodAccessorImpl" />
    <ns2:frame line="39" file="NativeMethodAccessorImpl.java" method="invoke" class="sun.reflect.NativeMethodAccessorImpl" />
    <ns2:frame line="25" file="DelegatingMethodAccessorImpl.java" method="invoke" class="sun.reflect.DelegatingMethodAccessorImpl" />
    <ns2:frame line="597" file="Method.java" method="invoke" class="java.lang.reflect.Method" />
    <ns2:frame line="101" file="WLSInstanceResolver.java" method="invoke" class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" />
    <ns2:frame line="83" file="WLSInstanceResolver.java" method="invoke" class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" />
    <ns2:frame line="152" file="InvokerTube.java" method="invoke" class="com.sun.xml.ws.server.InvokerTube$2" />
    <ns2:frame line="264" file="EndpointMethodHandler.java" method="invoke" class="com.sun.xml.ws.server.sei.EndpointMethodHandler" />
    <ns2:frame line="93" file="SEIInvokerTube.java" method="processRequest" class="com.sun.xml.ws.server.sei.SEIInvokerTube" />
    <ns2:frame line="604" file="Fiber.java" method="__doRun" class="com.sun.xml.ws.api.pipe.Fiber" />
    <ns2:frame line="563" file="Fiber.java" method="_doRun" class="com.sun.xml.ws.api.pipe.Fiber" />
    <ns2:frame line="548" file="Fiber.java" method="doRun" class="com.sun.xml.ws.api.pipe.Fiber" />
    <ns2:frame line="445" file="Fiber.java" method="runSync" class="com.sun.xml.ws.api.pipe.Fiber" />
    <ns2:frame line="275" file="WSEndpointImpl.java" method="process" class="com.sun.xml.ws.server.WSEndpointImpl$2" />
    <ns2:frame line="454" file="HttpAdapter.java" method="handle" class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" />
    <ns2:frame line="250" file="HttpAdapter.java" method="handle" class="com.sun.xml.ws.transport.http.HttpAdapter" />
    <ns2:frame line="140" file="ServletAdapter.java" method="handle" class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" />
    <ns2:frame line="319" file="HttpServletAdapter.java" method="run" class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" />
    <ns2:frame line="232" file="HttpServletAdapter.java" method="post" class="weblogic.wsee.jaxws.HttpServletAdapter" />
    <ns2:frame line="310" file="JAXWSServlet.java" method="doPost" class="weblogic.wsee.jaxws.JAXWSServlet" />
    <ns2:frame line="727" file="HttpServlet.java" method="service" class="javax.servlet.http.HttpServlet" />
    <ns2:frame line="87" file="JAXWSServlet.java" method="service" class="weblogic.wsee.jaxws.JAXWSServlet" />
    <ns2:frame line="820" file="HttpServlet.java" method="service" class="javax.servlet.http.HttpServlet" />
    <ns2:frame line="227" file="StubSecurityHelper.java" method="run" class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" />
    <ns2:frame line="125" file="StubSecurityHelper.java" method="invokeServlet" class="weblogic.servlet.internal.StubSecurityHelper" />
    <ns2:frame line="292" file="ServletStubImpl.java" method="execute" class="weblogic.servlet.internal.ServletStubImpl" />
    <ns2:frame line="26" file="TailFilter.java" method="doFilter" class="weblogic.servlet.internal.TailFilter" />
    <ns2:frame line="56" file="FilterChainImpl.java" method="doFilter" class="weblogic.servlet.internal.FilterChainImpl" />
    <ns2:frame line="326" file="DMSServletFilter.java" method="doFilter" class="oracle.dms.wls.DMSServletFilter" />
    <ns2:frame line="56" file="FilterChainImpl.java" method="doFilter" class="weblogic.servlet.internal.FilterChainImpl" />
    <ns2:frame line="3592" file="WebAppServletContext.java" method="run" class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" />
    <ns2:frame line="321" file="AuthenticatedSubject.java" method="doAs" class="weblogic.security.acl.internal.AuthenticatedSubject" />
    <ns2:frame line="121" file="SecurityManager.java" method="runAs" class="weblogic.security.service.SecurityManager" />
    <ns2:frame line="2202" file="WebAppServletContext.java" method="securedExecute" class="weblogic.servlet.internal.WebAppServletContext" />
    <ns2:frame line="2108" file="WebAppServletContext.java" method="execute" class="weblogic.servlet.internal.WebAppServletContext" />
    <ns2:frame line="1432" file="ServletRequestImpl.java" method="run" class="weblogic.servlet.internal.ServletRequestImpl" />
    <ns2:frame line="201" file="ExecuteThread.java" method="execute" class="weblogic.work.ExecuteThread" />
    <ns2:frame line="173" file="ExecuteThread.java" method="run" class="weblogic.work.ExecuteThread" />
    </ns2:stackTrace>
    </ns2:exception>
    </detail>
    </S:Fault>
    </S:Body>
    </S:Envelope>

    Hello AYVR
    I found your post because I want to suppress the stack trace in my response of the web service. I put the -Dcom.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace=false parameter in the setDomainEnv.cmd in the bin directory of my domain. Maybe this is also a solution for you.
    Cheers Chris
    Edited by: user8989253 on Aug 5, 2011 6:36 AM

Maybe you are looking for

  • SPRY DROP DOWN (VERTICAL) MENU SHOWING HORIZONTALLY IN IE8

    Hi guys, im having hard time figuring out how to fix my spry drop down menu on IE8. when rolled over, it lines up horizontally instead of vertically. please check the site: http://www.rebeccabrooksphotography.com/ and roll over the A bit about and Ga

  • Playhead won't  show and songs repeat

    Playhead won't show and songs repeat. I've turned off phone and tried to tap artwork but it still doesn't show. I just get a place to select stars for the song and it continues to play the same song over

  • How to show start up Disk on Desk top??

    I am use to my iMac having the Hard Disk / Start up disk on my Desk top. Recently bought a Mac Book Pro. Is there a way to have the Hard Disk appear on the Desk Top?

  • TCP communicat​ions via C program with VI on a PC (SGI - Windows)

    I have a pair of simple (more at prototype) client/server C programs on an SGI host. On the SGI, they compile and run fine (using separate windows). I know what the server is supposed to be sending (C floats) and the client is reading the correct val

  • ITunes not accepting my Visa!

    So I decided to start using my Visa instead of always buying cards. I have a CIBC Aero Classic Visa (I am in Canada). I go to enter this information in account changes section and iTunes says my credit card number is not valid for Canada?? my address