Topic
  • 9 replies
  • Latest Post - ‏2010-12-09T21:38:12Z by SystemAdmin
SystemAdmin
SystemAdmin
557 Posts

Pinned topic Error deploying WebService

‏2010-12-09T01:41:37Z |
Hi I have a web service that I have enabled through the service definition builder. Now this web service runs just fine whenever I auto deploy it from WPF, but whenever I deploy it manually on WAS or Process Server I always get this error.

<soapenv:Envelope xmlns:soapenv=
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=
"http://www.w3.org/2001/XMLSchema" xmlns:xsi=
"http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Server.userException</faultcode> <faultstring>com.bowstreet.webapp.engine.WebAppRuntimeException: Multiple web service enabled models or methods found matching namespace http:
//generatedschema.bowstreet.com/Services/Investment_Services/GetAllContractDataInputSchema The following models were found. Services/Investment_Services Services/Investment_Services</faultstring> <detail> <ns1:hostname xmlns:ns1=
"http://xml.apache.org/axis/">vmwps01t.metro.universalgrouppr.com</ns1:hostname> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope>

Now I have tried it on 3 different servers My local WebSphere Portal application server (6.1), another different development portal (6.1.0.1), and to Process Server.

I've never been able to deploy successfully deploy it manually. I even tried to deploy it manually in my local application server, but the only time this works is through the WPF client.

This makes me think that I'm not deploying it correctly whenever I do it manually. Now this is what I'm doing:

  • Install Application
  • Provide war file and specify context root
  • Check "Deploy web services"
  • Map application server
  • Finish

Am I missing some step?
Updated on 2010-12-09T21:38:12Z at 2010-12-09T21:38:12Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    557 Posts

    Re: Error deploying WebService

    ‏2010-12-09T01:46:36Z  
    Oh I forgot. After I deploy the was manually (before starting the app) I go into
    the application>>Manage Module>>Go into the module and change the class loader
    order to "Classes load with application class loader first".

    Otherwise I get an error like this:

    Axis can't find its target target is null.

    So that's basically my process.

    Is something missing?
  • SystemAdmin
    SystemAdmin
    557 Posts

    Re: Error deploying WebService

    ‏2010-12-09T12:36:39Z  
    FYI: I created this schema manually which I'm using for all the
    result schemas for my operations.

    Maybe there's an error in my schema.
  • SystemAdmin
    SystemAdmin
    557 Posts

    Re: Error deploying WebService

    ‏2010-12-09T13:56:23Z  
    OK new development!

    I created a new Hello World proyect. No custom schemas, no other models, etc.
    I deployed this project onto the process server and the portal server and guess
    what I get the following error:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <soapenv:Body>
          <soapenv:Fault>
             <faultcode>soapenv:Server.userException</faultcode>
             <faultstring>com.bowstreet.webapp.engine.WebAppRuntimeException: Multiple web service enabled models or methods found matching namespace HelloWorld_Services/HelloWorld/HelloWorld_ServicesGetHelloWorldReservedMethodDispatcher
    The following models were found.
    HelloWorld_Services
    HelloWorld_Services</faultstring>
             <detail>
                <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">vmwps01t.metro.universalgrouppr.com</ns1:hostname>
             </detail>
          </soapenv:Fault>
       </soapenv:Body>
    </soapenv:Envelope>
    


    My next steps will be trying to install the WS with as many options as I can, and maybe Upgrade WPF from 6.1.5.1 to 6.1.5.2.

    Any additional input will be more than welcome.

    Thank you,
    Updated on 2014-03-25T15:53:54Z at 2014-03-25T15:53:54Z by iron-man
  • mburati
    mburati
    352 Posts

    Re: Error deploying WebService

    ‏2010-12-09T15:24:02Z  
    OK new development!

    I created a new Hello World proyect. No custom schemas, no other models, etc.
    I deployed this project onto the process server and the portal server and guess
    what I get the following error:

    <pre class="java dw" data-editor-lang="java" data-pbcklang="java" dir="ltr"><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Server.userException</faultcode> <faultstring>com.bowstreet.webapp.engine.WebAppRuntimeException: Multiple web service enabled models or methods found matching namespace HelloWorld_Services/HelloWorld/HelloWorld_ServicesGetHelloWorldReservedMethodDispatcher The following models were found. HelloWorld_Services HelloWorld_Services</faultstring> <detail> <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">vmwps01t.metro.universalgrouppr.com</ns1:hostname> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> </pre>

    My next steps will be trying to install the WS with as many options as I can, and maybe Upgrade WPF from 6.1.5.1 to 6.1.5.2.

    Any additional input will be more than welcome.

    Thank you,
    To support incoming web services (where you're building a web service provider),
    it requires the classloader to be set to use the WAR/app's classloader first (as do most WPF apps anyway),
    so that it loads the WPF-extended-axis configuration in the WAR for AXIS incoming service dispatching,
    so it's good that you're setting that.
    A generic AXIS already loaded at the appserver level wouldn't know about the axis config extensions specific to that WAR and/or other WPF WARs also supporting incoming services...

    I don't know what the circumstances are that are causing your model to declare that it supports web service ops for that namespace twice,
    but it sounds like it's a bug that the duplicate namespace detection code isn't noticing that the duplicate is for the same model,
    which it could probably ignore (the issue would be more for when two different models say they're a doc/literal provider for that same ns then it wouldn't know which to call with the envelope).

    I suggest contacting WPF customer support to report the issue and have a WPF web service expert look into it...

    In the meantime, one possible workaround might be to delete the WEB-INF/models/ExternalModelProperties.xml from your project
    (which is a cache of properties about models that those models want to expose to other WPF models/components)
    and redeploy the (non-portlet) WAR that hosts the web service, to see if that removes the duplicate from the cache.

    ..mb1
  • kevintap
    kevintap
    9 Posts

    Re: Error deploying WebService

    ‏2010-12-09T15:25:24Z  
    OK new development!

    I created a new Hello World proyect. No custom schemas, no other models, etc.
    I deployed this project onto the process server and the portal server and guess
    what I get the following error:

    <pre class="java dw" data-editor-lang="java" data-pbcklang="java" dir="ltr"><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Server.userException</faultcode> <faultstring>com.bowstreet.webapp.engine.WebAppRuntimeException: Multiple web service enabled models or methods found matching namespace HelloWorld_Services/HelloWorld/HelloWorld_ServicesGetHelloWorldReservedMethodDispatcher The following models were found. HelloWorld_Services HelloWorld_Services</faultstring> <detail> <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">vmwps01t.metro.universalgrouppr.com</ns1:hostname> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> </pre>

    My next steps will be trying to install the WS with as many options as I can, and maybe Upgrade WPF from 6.1.5.1 to 6.1.5.2.

    Any additional input will be more than welcome.

    Thank you,
    It looks like there may be an issue in the code that locates the WS enabled model for the provided namespace. This is determined by scanning the ExternalModelProperties.xml file in the WEB-INF/models directory of your project. If ExternalModelProperties.xml has duplicate entries in it, this problem will occur. I would suggest scanning your ExternalModelProperties.xml file to see if this is indeed the case - that it has duplicate entries.

    Specifically, look for a <PropertyName>WebServiceEnabled</PropertyName> tag, and look for <PropertyName>WSE_Namespace_...</PropertyName> tag. These are the elements that inform WPF that your model provides Web Services and what namespaces it handles. If you see multiple <Quadruple> elements identifying your model as web service enabled and/or multiple <Quadruple> elements declaring the Web Service namespace for your model, this would cause the problem.

    To work-around the problem, you can try editing ExternalModelProperties.xml to remove the duplicate <Quadruple> elements. Or, I think you can simply delete ExternalModelProperties.xml and the Designer should re-create it when it detects that it is missing (hopefully without duplicate elements).
  • SystemAdmin
    SystemAdmin
    557 Posts

    Re: Error deploying WebService

    ‏2010-12-09T16:26:42Z  
    • kevintap
    • ‏2010-12-09T15:25:24Z
    It looks like there may be an issue in the code that locates the WS enabled model for the provided namespace. This is determined by scanning the ExternalModelProperties.xml file in the WEB-INF/models directory of your project. If ExternalModelProperties.xml has duplicate entries in it, this problem will occur. I would suggest scanning your ExternalModelProperties.xml file to see if this is indeed the case - that it has duplicate entries.

    Specifically, look for a <PropertyName>WebServiceEnabled</PropertyName> tag, and look for <PropertyName>WSE_Namespace_...</PropertyName> tag. These are the elements that inform WPF that your model provides Web Services and what namespaces it handles. If you see multiple <Quadruple> elements identifying your model as web service enabled and/or multiple <Quadruple> elements declaring the Web Service namespace for your model, this would cause the problem.

    To work-around the problem, you can try editing ExternalModelProperties.xml to remove the duplicate <Quadruple> elements. Or, I think you can simply delete ExternalModelProperties.xml and the Designer should re-create it when it detects that it is missing (hopefully without duplicate elements).
    Hi mburati and kevin thank you for your time and your help.

    I have tried deleting the ExternalModelProperties file before without success, but I just tried two things:
    Deleting it and Scanning the file, and what I is that each item is references only once (snippet below)

    
    - <Quadruple> <ModelID>Services/Investment_Services</ModelID> <ProcessorName>com.bowstreet.factory.model.implementation.StandardModelProcessor</ProcessorName> <PropertyName>Description</PropertyName> <PropertyValue /> </Quadruple> - <Quadruple> <ModelID>Services/Investment_Services</ModelID> <ProcessorName>com.bowstreet.factory.model.implementation.StandardModelProcessor</ProcessorName> <PropertyName>Service2Enabled</PropertyName> <PropertyValue>true</PropertyValue> </Quadruple> - <Quadruple> <ModelID>Services/Investment_Services</ModelID> <ProcessorName>com.bowstreet.factory.model.implementation.StandardModelProcessor</ProcessorName> <PropertyName>WebServiceEnabled</PropertyName> <PropertyValue>true</PropertyValue> </Quadruple> - <Quadruple> <ModelID>Services/Investment_Services</ModelID> <ProcessorName>com.bowstreet.factory.model.implementation.StandardModelProcessor</ProcessorName> <PropertyName>WSE_Namespace_IXml GetOwnerInfo(IXml)</PropertyName> <PropertyValue>Services/Investment_Services/sql_getQwnerInfo/sql_getQwnerInfoInputs</PropertyValue> </Quadruple>
    


    My project only has one model as you saw.

    Now picking up from my earlier tests on the hello world after I upgraded WPF from 6.1.5.1 to 6.1.5.2 I was
    able to install the project on all servers. Sadly I did not have such luck with the real project.

    My next test will be to create a new project and recreate the model.

    Any other suggestions are more than welcome.

    Thank you
  • mburati
    mburati
    352 Posts

    Re: Error deploying WebService

    ‏2010-12-09T16:40:54Z  
    Hi mburati and kevin thank you for your time and your help.

    I have tried deleting the ExternalModelProperties file before without success, but I just tried two things:
    Deleting it and Scanning the file, and what I is that each item is references only once (snippet below)

    <pre class="jive-pre"> - <Quadruple> <ModelID>Services/Investment_Services</ModelID> <ProcessorName>com.bowstreet.factory.model.implementation.StandardModelProcessor</ProcessorName> <PropertyName>Description</PropertyName> <PropertyValue /> </Quadruple> - <Quadruple> <ModelID>Services/Investment_Services</ModelID> <ProcessorName>com.bowstreet.factory.model.implementation.StandardModelProcessor</ProcessorName> <PropertyName>Service2Enabled</PropertyName> <PropertyValue>true</PropertyValue> </Quadruple> - <Quadruple> <ModelID>Services/Investment_Services</ModelID> <ProcessorName>com.bowstreet.factory.model.implementation.StandardModelProcessor</ProcessorName> <PropertyName>WebServiceEnabled</PropertyName> <PropertyValue>true</PropertyValue> </Quadruple> - <Quadruple> <ModelID>Services/Investment_Services</ModelID> <ProcessorName>com.bowstreet.factory.model.implementation.StandardModelProcessor</ProcessorName> <PropertyName>WSE_Namespace_IXml GetOwnerInfo(IXml)</PropertyName> <PropertyValue>Services/Investment_Services/sql_getQwnerInfo/sql_getQwnerInfoInputs</PropertyValue> </Quadruple> </pre>

    My project only has one model as you saw.

    Now picking up from my earlier tests on the hello world after I upgraded WPF from 6.1.5.1 to 6.1.5.2 I was
    able to install the project on all servers. Sadly I did not have such luck with the real project.

    My next test will be to create a new project and recreate the model.

    Any other suggestions are more than welcome.

    Thank you
    The ExternalModelProperties.xml in the deployed WAR on the appserver that you are calling the WS on would be the one that matters (whether there's a dup there or not) more than the one in the project. Try checking/deleting that one.

    ..mb1
  • mburati
    mburati
    352 Posts

    Re: Error deploying WebService

    ‏2010-12-09T19:02:10Z  
    • mburati
    • ‏2010-12-09T16:40:54Z
    The ExternalModelProperties.xml in the deployed WAR on the appserver that you are calling the WS on would be the one that matters (whether there's a dup there or not) more than the one in the project. Try checking/deleting that one.

    ..mb1
    Also, if you could post your hello world sample web service model here, so we can double check the model and the external model properties within it, that could help...

    ..mb1
  • SystemAdmin
    SystemAdmin
    557 Posts

    Re: Error deploying WebService

    ‏2010-12-09T21:38:12Z  
    • mburati
    • ‏2010-12-09T19:02:10Z
    Also, if you could post your hello world sample web service model here, so we can double check the model and the external model properties within it, that could help...

    ..mb1
    Thank you mburati

    I was finally able to resolve the problem apparently there were some remnants of the bug in the project.
    I was able to fix the problem by creating a new project and copying operation by operation to it (without)
    doing the publish application EVER (I had some odd issues with that).

    So basically I think that the primary issue was solved when I upgraded WPF to version 6.1.5.2.

    And to answer your question I checked in the one ExternalModelProperties.xml in the project, in the war and
    in the application server's installed apps.

    I could still upload the hello world model if you'd like but since the issue was resolved and it proved not
    to be the problem with the ExternalModelProperties maybe it's not necessary.

    I actually saw a few threads mentioning this issue before I created my own thread, but that didn't help me.
    Thanks again guys, and I hope that this thread can help some one else as it did me.