DDBeanCreateException when deploying web service EAR

Hi All,
I would very much appreciate any help on the following problem.
I used WorkSpace 1.1 to develop my app and tested in on WLS 10.0 within it. In WorkSpace the server runs on port 7021 and it has ALSB as well on the same port.
I created EARs and tryed deploying them to another WLS 10.0 that was used by ALSB, outside of Work Space. All module deployed fine.
Then I created a standalone WLS 10.0 server and tried deploying my modules on it. The server by default is on port 7001. Deployment failed with this error:
javax.enterprise.deploy.model.exceptions.DDBeanCreateException: [J2EE Deployment SPI:260142]The descriptor at 'META-INF/annotation-manifest.xml' in module 'XXX.war' is not recognized, and could not be parsed.
I found this article in Chris Hogue's blog (http://dev2dev.bea.com/blog/hogue/archive/2006/09/changing_annota.html_)
He recommends adding weblogic J2EE weblogic-controls-1.0 library to the EAR. I already have weblogic-controls-10.0 library attached. The only thing that jumps at me is the difference in ports. I manually changed references in annotation.xml from port 7021 to port 7001, but it did not help.
Thoughts?? Thanks in advance!
Edited by svitlana.dukhovna at 05/09/2008 3:05 PM

Hi Dipesh,
well, if you are using J2EE Engine 6.20 you cannot deploy directly from the NetWeaver Developer Studio (as far as I know, this feature is available only after 6.30/6.40 versions).
Also, web services are only partially implemented on J2EE Engine 6.20! So it is possible that the web service you've developed with the Developer studio depends on features that are not available on J2EE Engine 6.20. My recommendation is to give a try to the J2EE Engine 6.40, if possible for you at all.
Finally, there is an alternative to Deploy Tool for deployment on the J2EE Engine 6.20. This is the DEPLOY shell command that you can execute in the server console. For more info about that, refer to the Shell Commands Reference section in the Administration Manual for J2EE Engine 6.20 located here: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/administration manual for sap j2ee engine 6.20.pdf
Hope that helps!

Similar Messages

  • Error while deploying Web Service EAR to weblogic 10.3

    Hello All,
    I am getting the following errors when I "Activate changes" on the console after deploying the EAR file.
    An error occurred during activation of changes, please see the log for details.
    Error weblogic.application.ModuleException:
    Error port component:"StockQuotePortImpl" - wsdl port:{http://sun.com/stockquote.wsdl}StockQuotePortImplPort is not found in wsdl.
    The stack trace in the Workshop has the following:
    Caused by: weblogic.wsee.ws.WsException: port component:"StockQuotePortImpl" - wsdl port:{http://sun.com/stockquote.wsdl}StockQuotePortImplPort is not found in wsdl.
    I don't understand the problem. Is it something to do with the contextPath of the WS. If so, I have the <WLHttpTransport> element as a child of <jws> element and that has teh contextPath, port seviceURI etc.
    The WS builds fine and WAR/EAR created fine but I get this exception when I deploy.
    Any clues as to what is going wrong will be very helpful..
    Thanks much.

    Nevermind, I figured it out.
    I had to change the name of my JWS class (the one that implements the web service methods) and then it worked fine.
    Thanks to all who responded.

  • ServletException When Deploying Web Service Application to WL 10.3.1

    I'm attempting to deploy a web service application to WebLogic 10.3.1 built using the ANT jwsc task. The majority of the build is being done by Maven to produce and EAR file which contains the web service application WAR file, but I'm using ANT for the jwsc task due to classpath issues in Maven. Here is my task definition from by ANT build script:
    <jwsc srcdir="src" destdir="${basedir}/target"
    classpathref="weblogic.jar.classpath" verbose="on" debug="on"
    keepgenerated="yes">
    <module contextpath="testapp" name="TestWSApp" explode="true">
    <jws type="JAXWS" file="test/src/TestWSImpl.java"/>
    <descriptor file="${basedir}/src/main/webapp/WEB-INF/web.xml"/>
    <descriptor file="${basedir}/src/main/webapp/WEB-INF/weblogic.xml"/>
    </module>
    </jwsc>
    When the process completes, within the WAR file is the web.xml, which has been modified by the jwsc process to contain a servlet definition and mapping:
    <servlet>
    <servlet-name>TestWSAppServlethttp</servlet-name>
    <servlet-class>test.src.TestWSImpl</servlet-class>
    <load-on-startup>0</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>TestWSAppServlethttp</servlet-name>
    <url-pattern>/TestWSAppServlethttp</url-pattern>
    </servlet-mapping>
    The problem comes when I try to deploy to WebLogic. The deployment fails and I get errors. The stack track is really long, but here is the main problem:
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "DataIntegrityServiceServlethttp" failed to preload on startup in Web application: "/testapp".
    javax.servlet.ServletException: Servlet class: 'test.src.TestWSImpl' does not implement javax.servlet.Servlet
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:276)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    This error actaully makes sense if I was trying to deploy a servlet and not a web service class. If I manually remove the <load-on-startup>0</load-on-startup> element from the web.xml, then this deploys fine. I've tried to define the servlet in the web.xml permenantly, but jwsc throws an error saying the context is already in use.
    So what I need to do is either have jwsc skip the modification of the web.xml or just not have it create the <load-on-startup>0</load-on-startup> element. Any ideas?

    Nevermind, I figured it out.
    I had to change the name of my JWS class (the one that implements the web service methods) and then it worked fine.
    Thanks to all who responded.

  • Error when deploying web service do not have a property of the name return

    Using Jdeveloper 11.1.1.6 and Oracle 11g database.
    I created entities classes from tables then created a Java Service Facade and then a web service from the facade.
    When I delpoy (to Integrated WLS) or try to test the web service I get:
    javax.xml.ws.WebServiceException: class src.jaxws.persistXXX do not have a property of the name return. (I put the XXX there because if I remove the class from the web service then another persist* class gives the same error.
    I've checked the definitions and there's not a name 'return' anywhere other than return statements in the methods.
    TIA,
    Dave
    Here's a stacktrace after the above error:
    at com.sun.xml.ws.server.sei.EndpointResponseMessageBuilder$DocLit.(EndpointResponseMessageBuilder.java:206) at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.createResponseMessageBuilder(EndpointMethodHandlerImpl.java:213) at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.(EndpointMethodHandlerImpl.java:119) at com.sun.xml.ws.server.sei.EndpointMethodHandlerFactory.create(EndpointMethodHandlerFactory.java:15) at com.sun.xml.ws.server.sei.PayloadQNameBasedDispatcher.(PayloadQNameBasedDispatcher.java:118) at com.sun.xml.ws.server.sei.EndpointMethodDispatcherGetter.(EndpointMethodDispatcherGetter.java:83) at com.sun.xml.ws.server.sei.SEIInvokerTube.(SEIInvokerTube.java:82) at weblogic.wsee.jaxws.WLSContainer$WLSEndpointFactory$1.createServer(WLSContainer.java:800) at weblogic.wsee.jaxws.ServerLateInitTube.postCreateEndpoint(ServerLateInitTube.java:57) at weblogic.wsee.jaxws.EndpointAwareLateInitTube.postCreateEndpoint(EndpointAwareLateInitTube.java:46) at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:150) at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64) at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205) at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) Caused by: javax.xml.bind.JAXBException: return is not a valid property on class src.jaxws.PersistSubQuestionResponse at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getElementPropertyAccessor(JAXBContextImpl.java:973) at com.sun.xml.ws.server.sei.EndpointResponseMessageBuilder$DocLit.(EndpointResponseMessageBuilder.java:203) ... 55 more

    I found this in a google search:
    OK, I've solved this myself. I was using -p with wsimport to name the package of the generated class. When I removed this from the generated class, everything works fine! I'm not really sure why but I think it's because the wsdl is using target namespace.
    Does JDeveloper use this switch during deployment? If so, how do I remove it? Thanks, Dave

  • Deploying web service ear file

    Hi,
    I've developed a simple web service using NetWeaver Developer studio 2.0.5 and created an .ear file for deployment to SAP WAS 6.2.  While trying to load ear file from the deploy tool it throws an error - "Unable to load ear file".  Has anyone seen this error before?  Any problems with the NetWeaver and SAP WAS versions? Any suggestions on how to deploy a web service on SAP J2EE 6.2?

    Hi Dipesh,
    well, if you are using J2EE Engine 6.20 you cannot deploy directly from the NetWeaver Developer Studio (as far as I know, this feature is available only after 6.30/6.40 versions).
    Also, web services are only partially implemented on J2EE Engine 6.20! So it is possible that the web service you've developed with the Developer studio depends on features that are not available on J2EE Engine 6.20. My recommendation is to give a try to the J2EE Engine 6.40, if possible for you at all.
    Finally, there is an alternative to Deploy Tool for deployment on the J2EE Engine 6.20. This is the DEPLOY shell command that you can execute in the server console. For more info about that, refer to the Shell Commands Reference section in the Administration Manual for J2EE Engine 6.20 located here: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/administration manual for sap j2ee engine 6.20.pdf
    Hope that helps!

  • Java.lang.IncompatibleClassChangeError when deploying web service

    Hi there,
    I'm trying to deploy a jax-rpc web service and get a java.lang.IncompatibleClassChangeError error when I use org.apache.axis.client.AdminClient with the following deploy.wsdd file. The funny thing is the Web Service is deployed and listed in AXIS. Can anyone help me to resolve this.
    <!-- Use this file to deploy some handlers/chains and services      -->
    <!-- Two ways to do this:                                           -->
    <!--   java org.apache.axis.client.AdminClient deploy.wsdd          -->
    <!--      after the axis server is running                          -->
    <!-- or                                                             -->
    <!--   java org.apache.axis.utils.Admin client|server deploy.wsdd   -->
    <!--      from the same directory that the Axis engine runs         -->
    <deployment
        xmlns="http://xml.apache.org/axis/wsdd/"
        xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
      <!-- Services from FlightInfoServiceIFService WSDL service -->
      <service name="flightservice" provider="java:RPC" style="rpc" use="encoded">
          <parameter name="wsdlTargetNamespace" value="urn:flightservice"/>
          <parameter name="wsdlServiceElement" value="FlightInfoServiceIFService"/>
          <parameter name="wsdlServicePort" value="flightservice"/>
          <parameter name="className" value="flightCompany.rpcservice.FlightserviceSoapBindingImpl"/>
          <parameter name="wsdlPortType" value="FlightInfoServiceIF"/>
          <parameter name="typeMappingVersion" value="1.2"/>
          <operation name="getFlights" qname="operNS:getFlights" xmlns:operNS="urn:flightservice" returnQName="getFlightsReturn" returnType="rtns:string" xmlns:rtns="http://schemas.xmlsoap.org/soap/encoding/" soapAction="" >
            <parameter qname="in0" type="tns:string" xmlns:tns="http://schemas.xmlsoap.org/soap/encoding/"/>
          </operation>
          <parameter name="allowedMethods" value="getFlights"/>
          <parameter name="scope" value="Session"/>
      </service>
    </deployment>

    I was getting this error running AdminClient from a ant task, but the got no error when I ran it from the commanr line. But I'm getting the same thing back from the actual service itself whrn I try and invoke it using stubs generated by the wsdl2java tool with the following code
        public String getFlightsFromWSService(String date) throws Exception {
         String REMOTE_ENDPOINT_URL = "http://localhost:7070/axis/services/flightservice";
         String namespace = "flightservice";
         String portName = "FlightInfoServiceIF";
         String servicename = "flightservice";
         //make a service
         FlightInfoServiceIFService service = new FlightInfoServiceIFServiceLocator();
         //get a stub to the service
         FlightInfoServiceIF flightSvc = service.getflightservice( new URL( REMOTE_ENDPOINT_URL ));
         //make a call
         return flightSvc.getFlights(date);
        }TCPMonitor gives me this pile of stuff
    HTTP/1.1 500 Internal Server Error
    Content-Type: text/html;charset=ISO-8859-1
    Content-Language: en-IE
    Date: Tue, 31 May 2005 22:43:12 GMT
    Server: Apache-Coyote/1.1
    Connection: close
    <html>
       <head>
          <title>Apache Tomcat/4.1.31 - Error report</title>
          <STYLE>
             <!--H1{font-family : sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;}
    H3{font-family : sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;}
    BODY{font-family : sans-serif,Arial,Tahoma;color : black;background-color : white;}
    B{color : white;background-color : #0086b2;} HR{color : #0086b2;} --></STYLE>
          </head>
          <body>
             <h1>HTTP Status 500 - </h1>
             <HR size="1" noshade="noshade">
                <p>
                   <b>type</b> Exception report
                </p>
                <p>
                   <b>message</b>
                   <u></u>
                </p>
                <p>
                   <b>description</b>
                   <u>The server encountered an internal error () that prevented it from
    fulfilling this request.</u>
                </p>
                <p>
                   <b>exception</b>
                   <pre>javax.servlet.ServletException: Servlet execution threw an exception
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
    (ApplicationFilterChain.java:222)     at org.apache.catalina.core.ApplicationFilterChain.doFilter
    (ApplicationFilterChain.java:146)     at  ...........lots more exceptions.........
                </p>
                <p>
                   <b>root cause</b>
                   <pre>java.lang.IncompatibleClassChangeError     at
    org.apache.axis.message.MessageElement.addTextNode
    (MessageElement.java:1387)
         at org.apache.axis.message.SOAPHandler.endElement
    (SOAPHandler.java:118)
         at org.apache.axis.encoding.DeserializationContext.endElement
    (DeserializationContext.java:1083)     at
    org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement
    (Unknown Source)     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
    Dispatcher.dispatch(Unknown Source)
         at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument
    (Unknown Source)
         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
         at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
         at javax.xml.parsers.SAXParser.parse(Unknown Source)
         at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:226)
         at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645)
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
         at java.lang.Thread.run(Thread.java:595)
    </pre>
                </p>
                <HR size="1" noshade="noshade">
                   <h3>Apache Tomcat/4.1.31</h3>
                </body>
             </html>

  • Problems when deploying web service onto Weblogic 12c

    Hello everybody:
    Created a web service with MyEclipse 8.5; when deploying onto Weblogic I'm facing this next problem:
    Nov 3, 2012 7:44:40 AM com.sun.xml.ws.transport.http.servlet.WSServletDelegate destroy
    INFO: WSSERVLET15: JAX-WS servlet destroyed
    Nov 3, 2012 7:44:40 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextDestroyed
    INFO: WSSERVLET13: JAX-WS context listener destroyed
    <Nov 3, 2012 7:44:40 AM CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1351950260963' for task '0'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
    javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
    at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
    at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
    at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
    at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
    at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
    ... 54 more
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
    javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
    at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
    at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
    at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
    at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
    at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
    ... 54 more
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    Truncated. see log file for complete stacktrace
    Caused By: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
    at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
    Truncated. see log file for complete stacktrace
    >
    <Nov 3, 2012 7:44:40 AM CST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application '_appsdir_WSConsultaTrabajadorCurp_dir'.>
    <Nov 3, 2012 7:44:40 AM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_WSConsultaTrabajadorCurp_dir'.>
    <Nov 3, 2012 7:44:40 AM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
    javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
    at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
    at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
    at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
    at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
    at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
    ... 54 more
    :com.sun.xml.ws.policy.PolicyException:[failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
    at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
    Truncated. see log file for complete stacktrace
    It seems it is looking for the file; it is in the specified path so I cannot figure out what's wrong. No reference about the problem found over internet. Same web service deploys without problem on Tomcat, but by requirement, needed to deploy onto Weblogic 10g or above. Any help?
    Thanks in advance.

    how did you configured this ws-policy file?
    are you using any @Policy annotations?
    Regards,
    Sunil P

  • Connection error when deploying Web Services example

    C:\java\sample\how-to-web-services\ejb>ant deploy-usingadmin.jar
    Buildfile: build.xml
    common:
    [echo] BuildName: EJB Stateless Web Service
    [echo] BuildHome: C:\java\sample\how-to-web-services\ejb
    [echo] BuildFile: C:\java\sample\how-to-web-services\ejb\build.xml
    [echo] BuildJVM: 1.3
    init:
    deploy-ear:
    [java] Error: javax.naming.NamingException: Lookup error: java.net.ConnectE
    xception: Connection refused: connect; nested exception is:
    [java] java.net.ConnectException: Connection refused: connect
    bind-web-app: [java] Java Result: 1
    [java] Error: javax.naming.NamingException: Lookup error: java.net.ConnectE
    xception: Connection refused: connect; nested exception is:
    [java] java.net.ConnectException: Connection refused: connect
    deploy-usingadmin.jar:
    BUILD SUCCESSFUL
    Total time: 7 seconds
    Thanks,

    You have to start OC4J and make changes in the common.xml/buld.xml to have connection information for your OC4J instance.
    Otherwise you can take this EAR file and deploy in your OC4J instance.
    regards
    Debu

  • Issue when deploying web service

    Hi,
    I'm new to web services. Im currently using netbeans 6.0 beta 1 to create my web services. After creating and deploying it on the bundled tomcat 6 server, i get this error that says that requested resource not found. What could be the cause of it as it works in netbeans 5.5? Could it be that the error is caused by the difference in the JAX WS 2.0 and 2.1 libraries?
    note: netbeans 5.5 uses JAX WS 2.0. netbeans 6.0 beta 1 uses JAX WS 2.1.
    much help would be appreciated. Thank you...
    coderDuck

    here's the log
    Oct 29, 2007 11:15:59 PM org.apache.catalina.core.StandardContext listenerStart
    SEVERE: Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
    **************************************WARNING***************************************
    To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
    before rt.jar. To do this you can use Java endorsed mechanism to override what is in
    Java platform. The easiest way to do so is to copy all jars from the
    C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
    C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
    com.sun.xml.ws.transport.http.servlet.WSServletException: WSSERVLET11: failed to parse runtime descriptor: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:118)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:511)
    at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1220)
    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:597)
    at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1458)
    at org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:820)
    at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:348)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Thread.java:619)
    **************************************WARNING***************************************
    To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
    before rt.jar. To do this you can use Java endorsed mechanism to override what is in
    Java platform. The easiest way to do so is to copy all jars from the
    C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
    C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
    Caused by: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
    at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:172)
    at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
    at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
    at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
    at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
    at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:146)
    at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:145)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:144)
    at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:83)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:260)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
    at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:253)
    at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:147)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:108)
    ... 36 more
    Oct 29, 2007 11:15:59 PM org.apache.catalina.core.StandardContext listenerStart
    SEVERE: Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
    **************************************WARNING***************************************
    To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
    before rt.jar. To do this you can use Java endorsed mechanism to override what is in
    Java platform. The easiest way to do so is to copy all jars from the
    C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
    C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
    com.sun.xml.ws.transport.http.servlet.WSServletException: WSSERVLET11: failed to parse runtime descriptor: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:118)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
    at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1237)
    at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:373)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Thread.java:619)
    **************************************WARNING***************************************
    To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
    before rt.jar. To do this you can use Java endorsed mechanism to override what is in
    Java platform. The easiest way to do so is to copy all jars from the
    C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
    C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
    Caused by: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
    at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:172)
    at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
    at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
    at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
    at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
    at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:146)
    at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:145)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:144)
    at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:83)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:260)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
    at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:253)
    at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:147)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:108)
    ... 22 more

  • Error deploying Web Service in Oracle 10g AS (10.1.3.0)

    When deploying a secured web service from Oracle EM 10.1.3 i'm getting the following exception
    "Failed in uploading archive. Invalid archive file: Invalid value: AES-256"
    The same web service (.ear) file is getting uploaded without exception when deploying directly from Oracle JDeveloper 10.1.3.0

    The problem solved when creating a webservice ear file with the keystore generated in the machine where the application server is installed.
    We created a secure web service (in client machineA) with public/private key encryption (AES 256) and tried deploying it in an application server instance (Server machineA). Doing this gives the following expection (when deploying the ear file through EM)
    "Failed in uploading archive. Invalid archive file: Invalid value: AES-256"
    We solved the problem by creating a keystore file in the application server instance machine (instead of doing it in client machine) and used the same keystore file to create the ear file which got deployed succesfully.
    Thanks for your help

  • Error where deploying web services

    HI every bady ,
    i deploye web service but when i start admin server for weblogic i got this log (i copy some lines) :
    #*###<1 mars 2012 19 h 05 CET> <Notice> <Security> <ACER-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330625142623> <BEA-090082> <Security initializing using security realm myrealm.>*
    *####<1 mars 2012 19 h 05 CET> <Critical> <WebLogicServer> <ACER-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330625152620> <BEA-000286> <Failed to invoke startup class "JRF Startup Class", java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup*
    *####<1 mars 2012 19 h 05 CET> <Critical> <WebLogicServer> <ACER-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330625152625> <BEA-000286> <Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass*
    java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
    *     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)*
    *     at java.security.AccessController.doPrivileged(Native Method)*
    *>*
    *####<1 mars 2012 19 h 05 CET> <Critical> <WebLogicServer> <ACER-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330625152630> <BEA-000286> <Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration*
    *     at weblogic.man
    *>*
    *####<1 mars 2012 19 h 05 CET> <Critical> <WebLogicServer> <ACER-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330625152635> <BEA-000286> <Failed to invoke startup class "AWT Application Context Startup Class", java.lang.ClassNotFoundException: oracle.jrf.AppContextStartup*
    java.lang.ClassNotFoundException: oracle.jrf.AppContextStartup
    *     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)*
    *     at java.security.AccessController.doPrivileged(Native Method)*
    *     at java.net.URLClassLoader.findClass(URLClassLoader.java:190)*
    *     at java.lang.ClassLoader.loadClass(ClassLoader.java:307)*
    *     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)*
    *     at java.lang.ClassLoader.loadClass(ClassLoader.java:248)*
    *     at java.lang.Class.forName0(Native Method)*
    *>*
    *####<1 mars 2012 19 h 05 CET> <Critical> <WebLogicServer> <ACER-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330625152638> <BEA-000286> <Failed to invoke startup class "JMX Framework Startup Class", java.lang.ClassNotFoundException: oracle.as.jmx.framework.wls.spi.StartupListener*
    java.lang.ClassNotFoundException: oracle.as.jmx.framework.wls.spi.StartupListener
    *     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)*
    *     at java.lang.ClassLoader.loadClass(ClassLoader.java:307)*
    *     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)*
    *     at java.lang.ClassLoader.loadClass(ClassLoader.java:248)*
    *     at java.lang.Class.forName0(Native Method)*
    *     at java.lang.Class.forName(Class.java:247)*
    *     at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:262)*
    *     at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)*
    *     at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)*
    *     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)*
    *     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)*
    *     at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:207)*
    *     at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppDeployments(ClassDeploymentManager.java:149)*
    *     at weblogic.management.deploy.classdeployment.ClassDeploymentService.start(ClassDeploymentService.java:20)*
    *     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)*nerInvoker.java:60)*
    *     at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)*
    *     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)*
    *     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)*
    *     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)*
    *     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)*
    *     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)*
    *     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)*
    *     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)*
    *     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)*
    *     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)*
    *>*
    *####<1 mars 2012 19 h 07 CET> <Error> <Deployer> <ACER-PC> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330625251045> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean vaccination#V2.0. Error - weblogic.management.DeploymentException: C:\JDeveloper\mywork\VaccinCapt initial\deploy\vaccination.ear (Le fichier spécifié est introuvable) with : C:\JDeveloper\mywork\VaccinCapt initial\deploy\vaccination.ear.*
    weblogic.management.DeploymentException: C:\JDeveloper\mywork\VaccinCapt initial\deploy\vaccination.ear (Le fichier spécifié est introuvable) with : C:\JDeveloper\mywork\VaccinCapt initial\deploy\vaccination.ear
    *     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)*
    *     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)*
    *     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)*
    *     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)*
    *     a
    *####<1 mars 2012 19 h 07 CET> <Notice> <Server> <ACER-PC> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <f0ed2a6d7fb07688:-641bbda5:135cf7208d9:-8000-0000000000000008> <1330625252247> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.1.2:7001 for protocols iiop, t3, ldap, snmp, http.>*
    n(BaseLifecycleFlow.java:140)
    *>*
    *####<1 mars 2012 19 h 15 CET> <Warning> <netuix> <ACER-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <AppN> <> <f0ed2a6d7fb07688:-641bbda5:135cf7208d9:-8000-0000000000000024> <1330625732284> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=AppApplicationOverviewPage&AppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3DVaccinCapt_application1%23V2.0%2CType%3DAppDeployment%22%29.>*
    the Admin server consol run correctly localhost:7001/console
    i need help please
    thank you

    You can ask the one who installed the server...
    Or run the quickstart utility and try to install some other extension. In this process you see all installed extensions grayed out.
    Our you open the admin console and check which libraries are installed.
    Timo

  • How to deploy web service/client on websphere

    Hi,
    I have developed a web service client on Jdeveloper 10.1.3.1.0 and I deployed it on the embeded OC4J and OAS and it worked fine. BUT when I packaged it as EAR file and deployed it on websphere 6.0 {the production enviroment at the client side} It gave me NoClassForService00.
    And in websphere application server it didn't recognize it as Web service client.
    Any one faced this problem b4. PLZ advice.
    Thnx

    Hi Amol,
    Thank you very much for replying my question. The contents in my application.xml are:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
    <application>
    <display-name>testwsapp</display-name>
    <description>J2EE Application testwsapp</description>
    <module>
    <web>
    <web-uri>testws_War.war</web-uri>
    <context-root>testws</context-root>
    </web>
    <alt-dd>testws_War.xml</alt-dd>
    </module>
    </application>
    The contents in jaxrpc-ri-runtime.xml are:
    <?xml version="1.0" encoding="UTF-8"?>
    <endpoints xmlns='http://java.sun.com/xml/ns/jax-rpc/ri/runtime' version='1.0'>
    <endpoint
    name='testws'
    interface='contactws.testwsGenServer.testwsRPC'
    implementation='contactws.testwsGenServer.testwsRPCBean'
    tie='contactws.testwsGenServer.testwsRPC_Tie'
    model='null'
    wsdl='/WEB-INF/testws.wsdl'
    service='{urn:testws/wsdl}Testws'
    port='{urn:testws/wsdl}testwsRPCPort'
    urlpattern='/testws'
    </endpoint></endpoints>
    I tried to access and check the web service using:
    http://servername:port/testws/testws
    The first testws is contextroot named and the second testws is url pattern, which was exactly like what you mentioned but I got "404 Not Found" error.
    By the way, using the same ear to deploy to Windows Sun ONE App. Server 7 env. and then using the same url, I can access the web service. I am wondering if there is any special for deploying Web Service on Unix Sun ONE app. Server 7 env. or I missed something?
    I hope I can hear from you soon.
    Thank you again,
    Jackie

  • To launch Oracle BPM deployed Web Services [In BPM Enterprise]

    Hi all,
    I have expose my Process Instance into Web Services in Studio.
    It is working well. In Studio, I start the Engine (Run -> Start Engine),
    Then, I Start the Web Services (Run -> Launch deployed Web Services webapps).
    It would show me my local webservice links.
    http://localhost:9000/albpmServices/<ProjectName>/ws
    But, I unable to launch this Web Service Webapps, when i deploy the project into Oracle BPM Enterprise with Weblogic Server.
    May know what is the link for BPM Enterprise?
    Regards,
    Chris

    My URL is:-
    http://localhost:9000/albpmServices/TestProject/ws/TestProcessServiceListener?wsdl=true
    and it does not seem to open the WSDL when I start the enterprise server engine..
    I have the process exposed as a web-service with two methods..
    One for Process Creation and another for Notification Wait Activity...
    I have also checked the box to start PAPI WS Services on my standalone server
    Is there some other config that I need to make inside my standalone server to get this WSDL?
    I understand that standalone works on Tomcat...

  • Parameter names change when generating web service from WSDL

    Hi,
    I have a problem with BEAs web services that I'm hoping someone can help me with.
    I have a
    WSDL file, and from that I want to generate a web service implementation and a
    web service
    client. In the WSDL file, I have a message defined like this:
    <message name="someRequest">
    <part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
    name="data"/>
    </message>
    I generate the server using the server using the wsdl2service Ant task, I implement
    the necessary classes, and I deploy it. When I access the deployed web service,
    the parameter name has changed, from "data" to "bytes". If I access the WSDL file
    of the deployed web service, it says:
    <message name="someRequest">
    <part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
    name="bytes"/>
    </message>
    This happens for all parameters, string parameters are renamed to "string", base64Binary
    parameters are renamed to "bytes", etc...
    This poses a problem to me, because if I generate a web service client from the
    original WSDL file, it will not be able to talk to my web service. Is there any
    way of forcing a web service generated from a WSDL file to keep the parameter
    names of the original WSDL file?
    Any help in this is greatly appreciated.
    Regards,
    Petter

    From a quick look of your WSDL, it seams that you are mixing document-literal-bare and document-literal-wrapped flavor of web services. WSA may be able to do a better job at working around this mixed flavors than JDeveloper.
    If you have hand crafted this WSDL, I would recomend that you spend some time looking at the way WSDL are generated, with the java-first mode (or bottom-up), then author the WSDL you need for the final service.
    Here are sample of bare-style :
    <xsd:element name="getPupilAddressResponse" type="xsd:string"/>
    <xsd:element name="getPupilAddressRequest" type="xsd:int"/>
    Wrapped will looks like that:
    <xsd:element name="getSENLevelResponse">
    <xsd:complexType>
    <xsd:sequence maxOccurs="1" minOccurs="1">
    <xsd:element name="LevelDetails" type="tns:SENLevelRecord"/>
    <xsd:element name="RecordCount" type="xsd:int">
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    Hope this helps,
    Eric

  • How to deploy web service as part of console.war

    Hello,
    I need to expose the deploy functionality of bpel console as web service. I see that there is a JSP page which pretty much does the same thing in console.war. So I know what my Java class is going to look like the problem is I am very new to OC4J so I don't know how to deploy it as web service on this container. Any help is greatly appreciated.
    I tried going through the tutorial on deploying web services on OC4J but the sample stateless class does not compile because it cannot find some proxy classes. Also next I copied ws_example.ear in 'D:\OraBPEL_1\bpel\system\appserver\oc4j\j2ee\home\applications' and restarted server but it is not deployed.
    Thank you,
    Meghana

    Thank you for replying to my post.
    The requirement is that we deploy BPEL suitcase remotely. My impression was that one can get handle to the Locator object only if running on local machine so I was looking at how to create web service on Oracle BPEL PM itself that will accept the stream of jar and deploy it locally.
    However now looking at this tutorial and the Java docs, I know it supports RMI calls. So I can use this constructor to get Locator instance -
    public Locator(java.lang.String domainId,
    java.lang.String password,
    java.util.Hashtable pInitialContextProperties)
    throws ServerException
    Can you let me know sample initial context properties? I checked the sample InvokingProcesses' context.properties
    orabpel.platform=oc4j_10g
    java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
    java.naming.provider.url=ormi://ca-guru/orabpel
    java.naming.security.principal=default
    java.naming.security.credentials=welcome1
    My guess is I have to change that url but I don't know where to point it. Also could you please let me know what are the jars I will need on the client side?
    Thank you. I appreciate your help.
    Meghana

Maybe you are looking for