Error deploying sample application

Hi experts,
I am getting following error while deploying OAAM sample application:
Error: Unresolved Webapp Library references for "ServletContext@285871212[app:OAAMTester module:OAAMTester.war path:/OAAMTester spec-version:2.5]", defined in weblogic.xml [Extension-Name: oracle.oaam.libs, exact-match: false]
Even though i have deployed required libraries
My weblogic.xml :
<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd
http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<library-ref>
<library-name>oracle.oaam.libs</library-name>
</library-ref>
</weblogic-web-app>
web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
<display-name>OAAMTester</display-name>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.html</welcome-file>
<welcome-file>default.htm</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
<servlet>
<description></description>
<display-name>OAAMTestServlet</display-name>
<servlet-name>OAAMTestServlet</servlet-name>
<servlet-class>com.au.oaam.test.OAAMTestServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>OAAMTestServlet</servlet-name>
<url-pattern>/OAAMTestServlet</url-pattern>
</servlet-mapping>
<listener>
<listener-class>com.au.oaam.test.listener.SessionListener</listener-class>
</listener>
</web-app>
~
~
Thanks
H

Hi!
Seems application missing this library. You need to add this library to either application or to the Weblogic server.
Note:
Also don't duplicate the same library in application and the server. You can use following entry to force the app to use only web-inf/lib libraries.
(weblogic.xml)
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
Nilum.

Similar Messages

  • Deploying sample applications in mosaic

    Hello, i want to deploy the applications in Mosaic. I'm following these instructions:
    Use the Ant build files provided with the Mosaic ES2 installation to deploy sample applications to the server.
    To run Ant, type ant from the command line. When you do not provide arguments, Ant looks for a build.xml file in the current directory.
    For descriptions of the sample applications, see Sample applications.
    Deploy all samples and demos
    In the following directory, run Ant:
    [Mosaic ES2 install directory]/samples/
    Deploy the general sample applications
    In the following directory, run Ant:
    [Mosaic ES2 install directory]/samples/general/
    Deploy the MAX2009 application
    In the following directory, run Ant:
    [Mosaic ES2 install directory]/samples/max2009/
    I've set the ant_home enviromment variable but it still gives me the 'ant' is not recognized as an internal or external command,
    operable program or batch file.
    Thanks.

    Hodmi, i've done that but now i got this error:
    C:\MOSAIC_HOME\samples>ant
    Buildfile: build.xml
    deploy:
    deploy-catalogs:
       [delete] Deleting: C:\MOSAIC_HOME\samples\general\sample_catalog.zip
          [zip] Building zip: C:\MOSAIC_HOME\samples\general\sample_catalog.zip
    [mosaic-catalog] Exception in thread "Thread-2" C:\MOSAIC_HOME\samples\general\b
    uild.xml:21: Read failed: Server returned HTTP response code: 403 for URL: http:
    //localhost:9080/mosaic/catalogs/sample_catalog
    [mosaic-catalog]        at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:413)
    [mosaic-catalog] Caused by: java.io.IOException: Server returned HTTP response c
    ode: 403 for URL: http://localhost:9080/mosaic/catalogs/sample_catalog
    [mosaic-catalog]        at sun.net.www.protocol.http.HttpURLConnection.getInputS 
    tream(HttpURLConnection.java:1313) 
    [mosaic-catalog]        at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask 
    .java:407) 
    [mosaic-catalog] --- Nested Exception --- 
    [mosaic-catalog] java.io.IOException: Server returned HTTP response code: 403 fo 
    r URL: http://localhost:9080/mosaic/catalogs/sample_catalog 
    [mosaic-catalog]        at sun.net.www.protocol.http.HttpURLConnection.getInputS 
    tream(HttpURLConnection.java:1313) 
    [mosaic-catalog]        at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask 
    .java:407) 
         [echo] ${response} 
    deploy-applications:
    [mosaic-application] Exception in thread "Thread-4" C:\MOSAIC_HOME\samples\gener
    al\build.xml:33: Read failed: Server returned HTTP response code: 403 for URL: h
    ttp://localhost:9080/mosaic/applications/Basic
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:413)
    [mosaic-application] Caused by: java.io.IOException: Server returned HTTP respon
    se code: 403 for URL: http://localhost:9080/mosaic/applications/Basic
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
    [mosaic-application] --- Nested Exception ---
    [mosaic-application] java.io.IOException: Server returned HTTP response code: 40
    3 for URL: http://localhost:9080/mosaic/applications/Basic
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
         [echo] ${response}
    [mosaic-application] Exception in thread "Thread-6" C:\MOSAIC_HOME\samples\gener
    al\build.xml:42: Read failed: Server returned HTTP response code: 403 for URL: h
    ttp://localhost:9080/mosaic/applications/Brokerage
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:413)
    [mosaic-application] Caused by: java.io.IOException: Server returned HTTP respon
    se code: 403 for URL: http://localhost:9080/mosaic/applications/Brokerage
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
    [mosaic-application] --- Nested Exception ---
    [mosaic-application] java.io.IOException: Server returned HTTP response code: 40
    3 for URL: http://localhost:9080/mosaic/applications/Brokerage
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
         [echo] ${response}
    [mosaic-application] Exception in thread "Thread-8" C:\MOSAIC_HOME\samples\gener
    al\build.xml:51: Read failed: Server returned HTTP response code: 403 for URL: h
    ttp://localhost:9080/mosaic/applications/TileGame
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:413)
    [mosaic-application] Caused by: java.io.IOException: Server returned HTTP respon
    se code: 403 for URL: http://localhost:9080/mosaic/applications/TileGame
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
    [mosaic-application] --- Nested Exception ---
    [mosaic-application] java.io.IOException: Server returned HTTP response code: 40
    3 for URL: http://localhost:9080/mosaic/applications/TileGame
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
         [echo] ${response}
    [mosaic-application] Exception in thread "Thread-10" C:\MOSAIC_HOME\samples\gene
    ral\build.xml:60: Read failed: Server returned HTTP response code: 403 for URL:
    http://localhost:9080/mosaic/applications/Default
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:413)
    [mosaic-application] Caused by: java.io.IOException: Server returned HTTP respon
    se code: 403 for URL: http://localhost:9080/mosaic/applications/Default
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
    [mosaic-application] --- Nested Exception ---
    [mosaic-application] java.io.IOException: Server returned HTTP response code: 40
    3 for URL: http://localhost:9080/mosaic/applications/Default
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
         [echo] ${response} 
    deploy: 
    deploy-catalogs:
       [delete] Deleting: C:\MOSAIC_HOME\samples\max2009\max2009_catalog.zip
          [zip] Building zip: C:\MOSAIC_HOME\samples\max2009\max2009_catalog.zip
    [mosaic-catalog] Exception in thread "Thread-12" C:\MOSAIC_HOME\samples\max2009\
    build.xml:21: Read failed: Server returned HTTP response code: 403 for URL: http
    ://localhost:9080/mosaic/catalogs/max2009_catalog
    [mosaic-catalog]        at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:413)
    [mosaic-catalog] Caused by: java.io.IOException: Server returned HTTP response c
    ode: 403 for URL: http://localhost:9080/mosaic/catalogs/max2009_catalog
    [mosaic-catalog]        at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-catalog]        at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
    [mosaic-catalog] --- Nested Exception ---
    [mosaic-catalog] java.io.IOException: Server returned HTTP response code: 403 fo
    r URL: http://localhost:9080/mosaic/catalogs/max2009_catalog
    [mosaic-catalog]        at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-catalog]        at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
         [echo] ${response} 
    deploy-applications:
    [mosaic-application] Exception in thread "Thread-14" C:\MOSAIC_HOME\samples\max2
    009\build.xml:33: Read failed: Server returned HTTP response code: 403 for URL:
    http://localhost:9080/mosaic/applications/MAX2009
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:413)
    [mosaic-application] Caused by: java.io.IOException: Server returned HTTP respon
    se code: 403 for URL: http://localhost:9080/mosaic/applications/MAX2009
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
    [mosaic-application] --- Nested Exception ---
    [mosaic-application] java.io.IOException: Server returned HTTP response code: 40
    3 for URL: http://localhost:9080/mosaic/applications/MAX2009
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
         [echo] MAX2009 : ${response}
    [mosaic-application] Exception in thread "Thread-16" C:\MOSAIC_HOME\samples\max2
    009\build.xml:42: Read failed: Server returned HTTP response code: 403 for URL:
    http://localhost:9080/mosaic/applications/RedMAX2009
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:413)
    [mosaic-application] Caused by: java.io.IOException: Server returned HTTP respon
    se code: 403 for URL: http://localhost:9080/mosaic/applications/RedMAX2009
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
    [mosaic-application] --- Nested Exception ---
    [mosaic-application] java.io.IOException: Server returned HTTP response code: 40
    3 for URL: http://localhost:9080/mosaic/applications/RedMAX2009
    [mosaic-application]    at sun.net.www.protocol.http.HttpURLConnection.getInputS
    tream(HttpURLConnection.java:1313)
    [mosaic-application]    at com.adobe.mosaic.ant.MosaicTask$Reader.run(MosaicTask
    .java:407)
         [echo] RedMAX2009 : ${response} 
    deploy: 
    BUILD SUCCESSFUL
    Total time: 7 seconds
    C:\MOSAIC_HOME\samples>
    I'm using websphere 6.1.0.2.
    I've got the 403 server in websphere.
    Is there any procedure or any example to workaround this problem in websphere?
    Thanks

  • Urgent : Deployment error OWSM Sample application

    Hi Gurus,
    I am trying to deploy the LoanDemoOWSM sample application.I am getting the following error while trying to reference oasis-200401-wss-wssecurity-secext-1.0.xsd from my local oc4j server.
    BUILD FAILED
    D:\bpeljdev10131\jdev\mywork\LoanDemoOWSM\LoanFlowOWSM\build.xml:79: A problem occured while connecting to server "localhost" using port "8888": bpel_LoanFlowOWSM_1.0.jar failed to deploy. Exception message is: ORABPEL-05215
    Error while loading process.
    The process domain encountered the following errors while loading the process "LoanFlowOWSM" (revision "1.0"): BPEL validation failed.
    BPEL source validation failed, the errors are:
    [Error ORABPEL-10902]: compilation failed
    [Description]: in "bpel.xml", XML parsing failed because "undefined part element.
    In WSDL at "file:/D:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_LoanFlowOWSM_1.0_a7dfb5af8756c092cf44f709a7d9ac84.tmp/LoanFlowOWSM.wsdl", message part element "{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security" is not defined in any of the schemas.
    Please make sure the spelling of the element QName is correct and the WSDL import is complete.
    [Potential fix]: n/a.
    If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:285)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(DeploymentManager.java:773)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:639)
    at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:452)
    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:585)
    at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
    at com.evermind.server.ThreadState.runAs(ThreadState.java:618)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
    at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
    at DomainManagerBean_RemoteProxy_4bin6i8.deploySuitcase(Unknown Source)
    at com.oracle.bpel.client.BPELDomainHandle.deploySuitcase(BPELDomainHandle.java:318)
    at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:340)
    at deployHttpClientProcess.jspService(_deployHttpClientProcess.java:376)
    at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
    at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
    at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
    at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
    at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
    at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
    at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Total time: 23 seconds
    I tried adding the oasis-200401-wss-wssecurity-secext-1.0.xsd file to the same location as my bpel process and referenced it as a local file in my BPEL process.
    Now the error I get is as follows
    Error while loading process.
    The process domain encountered the following errors while loading the process "LoanFlowOWSM" (revision "1.0"): BPEL validation failed.
    BPEL source validation failed, the errors are:
    [Error ORABPEL-10902]: compilation failed
    [Description]: in "bpel.xml", XML parsing failed because "undefined part element.
    In WSDL at "file:/D:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_LoanFlowOWSM_1.0_a7dfb5af8756c092cf44f709a7d9ac84.tmp/LoanFlowOWSM.wsdl", message part element "{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security" is not defined in any of the schemas.
    Please make sure the spelling of the element QName is correct and the WSDL import is complete.
    [Potential fix]: n/a.
    If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:285)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(DeploymentManager.java:773)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:639)
    at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:452)
    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:585)
    at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
    at com.evermind.server.ThreadState.runAs(ThreadState.java:618)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
    at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
    at DomainManagerBean_RemoteProxy_4bin6i8.deploySuitcase(Unknown Source)
    at com.oracle.bpel.client.BPELDomainHandle.deploySuitcase(BPELDomainHandle.java:318)
    at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:340)
    at deployHttpClientProcess.jspService(_deployHttpClientProcess.java:376)
    at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
    at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
    at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
    at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
    at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
    at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
    at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Total time: 23 seconds
    In both cases , I think the BPEL process is not able to access the type definitions in oasis-200401-wss-wssecurity-secext-1.0.xsd file.
    Please help me fix this error.
    Thanks in Advance,
    Prasanna

    Like i have mentioned in the question.. i am using NWDS 7.0.
    To be precise NWDS: 7.0.12
    WAS 7.0 SP 13
    Project BuUild is succesful but deployment aborts with the error mentioned in the question.

  • Error deploying Web application

    Hello Everyone, i have a problem with my web application that is not able to be deployed.
    the first time i deployed the application everything worked correctly i performed the contex lookup with no problem as was able to connect to the EJB application, i performed some changes, and now everytime i tried to deploy again the application i get this error
    [#|2010-02-12T23:03:34.661+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=23;_ThreadName=Thread-434;Servlet;WebServiceInterface;http://vmlinux:8024/WebServiceInterface/WebServiceInterface;|DPL5306:Servlet Web Service Endpoint [WebServiceInterface] listening at address [http://vmlinux:8024/WebServiceInterface/WebServiceInterface]|#]
    [#|2010-02-12T23:03:38.107+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=23;_ThreadName=Thread-434;_RequestID=3610621f-da38-477d-b37a-088311a00a42;|Exception occured in J2EEC Phase
    com.sun.enterprise.deployment.backend.IASDeploymentException: Deployment Error -- Could not resolve a persistence unit corresponding to the persistence-context-ref-name [com.testing.myEJBapplication.ReferenceServiceLocalBean/entityManager] in the scope of the module called [product/servers/glassfish/domains/domain1/applications/j2ee-modules/WebServiceInterface]. Please verify your application.
         at com.sun.enterprise.deployment.BundleDescriptor.findReferencedPUsViaPCRefs(BundleDescriptor.java:702)
         at com.sun.enterprise.deployment.WebBundleDescriptor.findReferencedPUs(WebBundleDescriptor.java:722)
         at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.getAllPersistenceUnitDescriptors(PersistenceProcessor.java:171)
         at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.processApplication(PersistenceProcessor.java:132)
         at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processApplication(DeploymentEventListenerImpl.java:211)
         at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processEvent(DeploymentEventListenerImpl.java:172)
         at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.notifyDeploymentEvent(DeploymentEventListenerImpl.java:122)
         at com.sun.enterprise.deployment.backend.DeploymentEventManager.notifyDeploymentEvent(DeploymentEventManager.java:79)
         at com.sun.enterprise.deployment.backend.ModuleDeployer.handlePostDeployEvent(ModuleDeployer.java:636)
         at com.sun.enterprise.deployment.backend.ModuleDeployer.postDeploy(ModuleDeployer.java:625)
         at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:188)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:788)
         at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)
         at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223)
    |#]
    any ideas for this?? Thank you in advance regards
    Edited by: White_Merovingian on Feb 13, 2010 5:55 AM

    yeah these stacktraces are big scary blobs of text, but somewhere hidden among all the nonsense there is always the little piece of information you need:
    "Could not resolve a persistence unit corresponding to the persistence-context-ref-name [com.testing.myEJBapplication.ReferenceServiceLocalBean/entityManager]"
    So you are referring to a persistence unit in ReferenceServiceLocalBean that does not seem to exist. Do you have your persistence.xml deployed in the META-INF directory of the EJB module? Does it contain a persistence unit with the name that is declared in the bean?

  • Error Deploying ADF application to ADF Server

    Hi Team,
    Iam unable to deploy the ADF application to server.
    The following is the log :
    *[08:25:11 PM] ---- Deployment started. ----*
    *[08:25:11 PM] Target platform is (Weblogic 10.3).*
    *[08:25:11 PM] Retrieving existing application information*
    *[08:25:11 PM] Running dependency analysis...*
    *[08:25:11 PM] Building...*
    *[08:25:15 PM] Deploying profile...*
    *[08:25:15 PM] Wrote Web Application Module to D:\sridhar\SampleADF\ADFWorld\ViewController\deploy\ADFWorld_ViewController_webapp1.war*
    *[08:25:15 PM] Deploying Application...*
    *[08:25:16 PM] [Deployer:149191]Operation 'deploy' on application 'ADFWorld_ViewController_webapp1' is initializing on 'ADFServer'*
    *[08:25:17 PM] [Deployer:149193]Operation 'deploy' on application 'ADFWorld_ViewController_webapp1' has failed on 'ADFServer'*
    *[08:25:17 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application ADFWorld_ViewController_webapp1 on ADFServer.: Failed to load webapp: 'ADFWorld_ViewController_webapp1.war'.*
    *[08:25:17 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'ADFWorld_ViewController_webapp1.war'*
    *[08:25:17 PM] Caused by: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@6261447[app:ADFWorld_ViewController_webapp1 module:ADFWorld_ViewController_webapp1.war path:/ADFWorld spec-version:2.5]", defined in weblogic.xml [Extension-Name: adf.oracle.domain.webapp, exact-match: false], [Extension-Name: jstl, Specification-Version: 1.2, exact-match: false], [Extension-Name: jsf, Specification-Version: 1.2, exact-match: false]*
    *[08:25:17 PM] See server logs or server console for more details.*
    *[08:25:17 PM] weblogic.application.ModuleException: Failed to load webapp: 'ADFWorld_ViewController_webapp1.war'*
    *[08:25:17 PM] #### Deployment incomplete. ####*
    *[08:25:17 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)*
    Please suggest me what is the error.
    Regards
    Sridhar Yerram

    Hi Sridhar,
    Try to get more details from your Server related to Deployer:149026.
    This indicates failure of app due some issues on your services.
    paste the error stack to get the clue of issue.
    Regards,
    Kal

  • Error deploying adf application to weblogic

    hi am deploying my adf application using weblogic but am geting this error
    weblogic 10.3.5
    jeveloper is 11.1.6.0
    [12:14:21 PM] ----  Deployment started.  ----
    [12:14:21 PM] Target platform is  (Weblogic 10.3).
    [12:14:22 PM] Retrieving existing application information
    [12:14:22 PM] Running dependency analysis...
    [12:14:22 PM] Building...
    [12:14:32 PM] Deploying profile...
    [12:14:33 PM] Wrote Web Application Module to C:\JDeveloper\mywork\Align\ViewController\deploy\Align_ViewController_webapp.war
    [12:14:33 PM] Deploying Application...
    [12:14:35 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Align_ViewController_webapp on AdminServer.: [Deployer:149145]Unable to contact 'madimad-b533821'. Deployment is deferred until 'madimad-b533821' becomes available.; nested exception is:
        java.rmi.UnknownHostException: Could not discover administration URL for server 'madimad-b533821'.
    [12:14:35 PM] [Deployer:149193]Operation 'deploy' on application 'Align_ViewController_webapp' has failed on 'AdminServer'
    [12:14:35 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Align_ViewController_webapp on AdminServer.: Failed to load webapp: 'Align_ViewController_webapp.war'.
    [12:14:35 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'Align_ViewController_webapp.war'
    [12:14:35 PM] Caused by: java.lang.ClassNotFoundException: oracle.adf.model.servlet.ADFBindingFilter
    [12:14:35 PM]   See server logs or server console for more details.
    [12:14:35 PM] weblogic.application.ModuleException: Failed to load webapp: 'Align_ViewController_webapp.war'
    [12:14:35 PM] Deployment cancelled.
    [12:14:35 PM] ----  Deployment incomplete  ----.
    [12:14:35 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)

    Hi,
    ADF applications that use business components need the weblogic-application.xml deployment
    descriptor to be present to be able to work on a WLS.
    http://docs.oracle.com/cd/E12839_01/web.1111/b31974/deployment_topics.htm#CHDCICJH
    35.4 Creating and Editing Deployment Descriptors
    mentions the need of :
    <library-ref>
      <library-name>adf.oracle.domain</library-name>
    </library-ref>
    in the weblogic-application.xml
    ==> please execute the following steps:
    1. Wrap the WAR file in an EAR file configured to be deployed to a WebLogic server as follows, so that  JDeveloper includes the needed deployment descriptor file:
    2.Right-click the project containing the web contents (usually ViewController), and select New -> Deployment Profile. Then select EAR Deployment Profile.
    3. Enter the name for the application, and then in the EAR profile properties dialog, in the Application Assembly, include the ViewController project, and in the Platform node, make sure Default Platform is set to WebLogic 10.3. Click OK.
    4. In the next dialog box (Project properties), open the node ADF Model, and make sure the checkbox "Contains Data Controls" is checked, and click OK
    5. Now to deploy, right click the ViewController project and select Deploy, then the name of the recently created application deployment profile, and then "to EAR file". This will result in a .ear file, deployable from the WLS administration page.
    Thanks,
    Sharmela

  • Error deploying several applications

    Hello,
    I have a problem deploying several applications. They are 3 wars that are continuously deployed. The error obtained is the following
    deploy_:
    +[java]+
    +[java] Initializing WebLogic Scripting Tool (WLST) ...+
    +[java]+
    +[java] WARNING - Unable to create log file </bea/bea1035/modules/../logs/wlst_20110901091225.log>: java.io.IOException: No space left on device+
    +[java] Welcome to WebLogic Server Administration Scripting Shell+
    +[java]+
    +[java] Type help() for help on available commands+
    +[java]+
    +[java] Could not find the properties file to load properties from /config/wl11_extra_ava/w63/w63Resources.properties.+
    +[java] ==> Fichero de configuracion: /config/wl11_extra_ava/w63/w63Config.properties+
    +[java] ==> Fichero de recursos: /config/wl11_extra_ava/w63/w63Resources.properties+
    +[java] unlocking ...+
    +[java] Connecting to t3://wl11admin27.ejiepru.net:8124 with userid weblogic11 ...+
    +[java] Successfully connected to Admin Server 'admin' that belongs to domain 'wl11_extra_ava'.+
    +[java]+
    +[java] Warning: An insecure protocol was used to connect to the+
    +[java] server. To ensure on-the-wire security, the SSL port or+
    +[java] Admin port should be used instead.+
    +[java]+
    +[java] Location changed to edit tree. This is a writable tree with+
    +[java] DomainMBean as the root. To make changes you will need to start+
    +[java] an edit session via startEdit().+
    +[java]+
    +[java] For more help, use help(edit)+
    +[java]+
    +[java] Starting an edit session ...+
    +[java] Started edit session, please be sure to save and activate your+
    +[java] changes once you are done.+
    +[java] Saving all your changes ...+
    +[java] Saved all your changes successfully.+
    +[java] Activating all your changes, this may take a while ...+
    +[java] The edit lock associated with this edit session is released+
    +[java] once the activation is completed.+
    +[java] Activation completed+
    +[java] weblogic.Deployer invoked with options: -adminurl t3://wl11admin27.ejiepru.net:8124 -userconfigfile /j2se/apache-ant-1.7.1/ejie_wls11/user.secure -userkeyfile /j2se/apache-ant-1.7.1/ejie_wls11/password.secure -name ispacmgr -targets gestExp1 -deploy /aplic/w63/dist/ispacmgr.war -stage -timeout 3600 -debug -verbose+
    +[java] [WebLogicDeploymentManagerImpl.<init>():115] : Constructing DeploymentManager for J2EE version V1_4 deployments+
    +[java] [WebLogicDeploymentManagerImpl.getNewConnection():158] : Connecting to admin server at wl11admin27.ejiepru.net:8124, as user weblogic11+
    +[java] [ServerConnectionImpl.getEnvironment():286] : setting environment+
    +[java] [ServerConnectionImpl.getEnvironment():289] : getting context using t3://wl11admin27.ejiepru.net:8124+
    +[java] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://wl11admin27.ejiepru.net:8124/jndi/weblogic.management.mbeanservers.domainruntime+
    +[java] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://wl11admin27.ejiepru.net:8124/jndi/weblogic.management.mbeanservers.runtime+
    +[java] [DomainManager.resetDomain():36] : Getting new domain+
    +[java] [DomainManager.resetDomain():39] : Using pending domain: false+
    +[java] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@83fbeb1+
    +[java] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@83fbeb1+
    +[java] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@8313beb+
    +[java] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@8313beb+
    +[java] [ServerConnectionImpl.initialize():169] : Connected to WLS domain: wl11_extra_ava+
    +[java] [ServerConnectionImpl.init():159] : Initializing ServerConnection : [email protected]cc7+
    +[java] [BasicOperation.dumpTmids():713] : Incoming tmids:+
    +[java] [BasicOperation.dumpTmids():715] : {Target=gestExp1, WebLogicTargetType=cluster, Name=ispacmgr}, targeted=true+
    +[java] [BasicOperation.deriveAppName():141] : appname established as: ispacmgr+
    +[java] <Sep 1, 2011 9:12:59 AM CEST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, ispacmgr [archive: /aplic/w63/dist/ispacmgr.war], to gestExp1 .>+
    +[java] [BasicOperation.dumpTmids():713] : Incoming tmids:+
    +[java] [BasicOperation.dumpTmids():715] : {Target=gestExp1, WebLogicTargetType=cluster, Name=ispacmgr}, targeted=true+
    +[java] [BasicOperation.loadGeneralOptions():628] : Delete Files:false+
    +[java] Timeout :3600000+
    +[java] Targets:+
    +[java] gestExp1+
    +[java] ModuleTargets={}+
    +[java] SubModuleTargets={}+
    +[java] }+
    +[java] Files:+
    +[java] null+
    +[java] Deployment Plan: null+
    +[java] App root: /tmp/webl11/./config/deployments/ispacmgr+
    +[java] App config: /tmp/webl11/./config/deployments/ispacmgr/plan+
    +[java] Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=stage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=ispacmgr,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=3600,defaultSubmoduleTargets=true,timeout=3600000,deploymentPrincipalName=null,useExpiredLock=false}+
    +[java]+
    +[java] [BasicOperation.execute():445] : Initiating deploy operation for app, ispacmgr, on targets:+
    +[java] [BasicOperation.execute():447] : gestExp1+
    +[java] Task 164 initiated: [Deployer:149026]deploy application ispacmgr on gestExp1.+
    +[java] dumping Exception stack+
    +[java] Task 164 failed: [Deployer:149026]deploy application ispacmgr on gestExp1.+
    +[java] Target state: deploy failed on Cluster gestExp1+
    +[java] weblogic.management.DeploymentException: [Deployer:149189]An attempt was made to execute the 'deploy' operation on an application named 'ispacmgr' that is not currently available. The application may have been created after non-dynamic configuration changes were activated. If so, the operation can not be performed until server is restarted so that the application will be available.+
    +[java] at weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1319)+
    +[java] at weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1360)+
    +[java] at weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1050)+
    +[java] at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1406)+
    +[java] at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:162)+
    +[java] at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.updateDeploymentContext(DeploymentServiceDispatcher.java:156)+
    +[java] at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:147)+
    +[java] at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:29)+
    +[java] at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203)+
    +[java] at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:114)+
    +[java] at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52)+
    +[java] at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211)+
    +[java] at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:458)+
    +[java] at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)+
    +[java] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)+
    +[java] at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)+
    +[java]+
    +[java]+
    +[java] Target Assignments:+
    +[java] + ispacmgr gestExp1+
    +[java] [ServerConnectionImpl.close():332] : Closing DM connection+
    +[java] [ServerConnectionImpl.close():352] : Unregistered all listeners+
    +[java] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection+
    +[java] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection+
    +[java] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection+
    +[java] Java Result: 1+
    BUILD SUCCESSFUL
    This error doesn`t appear always in the same war file. In admin log I can see this:
    +79740> <BEA-149038> <Initiating Task for ispacmgr : [Deployer:149026]deploy application ispacmgr on gestExp1.>+
    +####<Sep 1, 2011 9:13:19 AM CEST> <Warning> <Deployer> <ejlf031> <admin> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <131+
    +4861199984> <BEA-149004> <Failures were detected while initiating deploy task for application 'ispacmgr'.>+
    +####<Sep 1, 2011 9:13:19 AM CEST> <Warning> <Deployer> <ejlf031> <admin> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <131+
    +4861199985> <BEA-149078> <Stack trace for message 149004+
    +weblogic.management.DeploymentException: [Deployer:149189]An attempt was made to execute the 'deploy' operation on an application named 'ispacmgr' that is not currently available.+
    The application may have been created after non-dynamic configuration changes were activated. If so, the operation can not be performed until server is restarted so that the appl
    ication will be available.
    at weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1319)
    at weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1360)
    at weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1050)
    at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1406)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:162)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.updateDeploymentContext(DeploymentServiceDispatcher.java:156)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:147)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:29)
    at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203)
    at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:114)
    at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52)
    at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211)
    at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:458)
    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)
    +>+
    So, is the same error. There isn`t any more. After this error, If I try to deploy the war (only the one with the error), it works!!!!
    Restarting the server is not the solution.
    Thanks in advance
    Endika

    Hi, I think you should delete all apps using WebLogic console instead of editing config.xml, is more safe. Then shutdown your instance and eliminate all that is inside in stage and .wlnotdelete directories. Start again your instance and deploy your apps.

  • Error Deploying Sample Portal from Development Guide

    I am going through creating a New Portal from WebLogic Portal 7 Development
    Guide and I am running into the following problem.
    After completing Step 2: Create the New Portal, when I try to Hot Deploy the
    application, I get the following error.
    Hot deploy failed with the following message:
    Unable to add module: NewPortalWebApp to application descriptor for:
    portalApp.
    The log has the following information..
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    portlets\Portlet1.portlet to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\tools.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\webflow-extensions.wfx to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\user_account.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\portal.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\security.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\NewPortal.portal to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    Error - please check log for details.

    That's great, Mike, you're welcome. I'm glad it's working for you. Thanks for letting me know.
    -Scott
    Mike Friesen wrote:
    I'm sorry you were right.. I tried it and everything works... thanks..
    Mike
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    I hear what you are saying and I believe you. But the error you describedis the known issue related to Internet access
    (down to the exact line numbers in the stack trace). Is it possible yourconnection was down last time you attempted
    hot-deploy?
    If you are sure your Internet connection is up, I would recommend tryinghot-deploy again. If it still does not work,
    something very strange is going on. At that point I would recommendtrying the workaround anyway or escalating the issue
    to BEA Support.
    Now my curiosity is piqued so I hope you'll let me know either way.
    Best Regards,
    Scott Ellis
    BEA Systems
    Mike Friesen wrote:
    yes..
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Can you please try something for me? Paste the following URL into abrowser:
    http://java.sun.com/dtd/application_1_3.dtd
    Does it come up?
    Thanks,
    Scott
    Mike Friesen wrote:
    Actually, my computer does have internet access, so I don't think that
    is
    the problem.
    Mike
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    I would bet that you are working on a machine that doesn't have
    Internet
    access, correct?
    The problem is that the EBCC is trying and failing to access the J2EEapplication descriptor
    dtd from Sun's website.
    If you can't get Internet access, here is the workaround:
    - save the attached file to your harddrive (just save it to c:\)
    - edit the application.xml file for your project as follows:
    - first copy the entire DOCTYPE declaration and save it somewhere
    in
    a
    separate text file (in case want to revert back to it later)
    - edit the DOCTYPE declaration so that it looks like this:
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EEApplication 1.3//EN' 'file:///application_1_3.dtd'>
    ( notice that the java.sun.com web address is replaced with the URI
    to
    the file on your harddrive)
    - save your changes and hotdeploy will work with or without Internetaccess
    Thanks,
    Scott Ellis
    BEA Systems
    Mike Friesen wrote:
    I am going through creating a New Portal from WebLogic Portal 7
    Development
    Guide and I am running into the following problem.
    After completing Step 2: Create the New Portal, when I try to Hot
    Deploy
    the
    application, I get the following error.
    Hot deploy failed with the following message:
    Unable to add module: NewPortalWebApp to application descriptor for:
    portalApp.
    The log has the following information..
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    portlets\Portlet1.portlet to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\tools.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\webflow-extensions.wfx to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\user_account.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\portal.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\security.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\NewPortal.portal to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    Error - please check log for details.
    <!--
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, U.S.A.
    All rights reserved.
    Sun Microsystems, Inc. has intellectual property rights relating to
    technology embodied in the product that is described in this document.
    In particular, and without limitation, these intellectual property
    rights may include one or more of the U.S. patents listed at
    http://www.sun.com/patents and one or more additional patents or
    pending patent applications in the U.S. and in other countries.
    This document and the product to which it pertains are distributed
    under licenses restricting their use, copying, distribution, and
    decompilation. This document may be reproduced and distributed but
    may
    not be changed without prior written authorization of Sun and its
    licensors, if any.
    Third-party software, including font technology, is copyrighted and
    licensed from Sun suppliers.
    Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail and and
    Enterprise JavaBeans are trademarks or registered trademarks of Sun
    Microsystems, Inc. in the U.S. and other countries.
    Federal Acquisitions: Commercial Software - Government Users Subjectto
    Standard License Terms and Conditions.
    DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
    CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
    WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
    NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
    DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, E'tats-Unis.
    Tous droits re'serve's.
    Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
    relatants a` la technologie incorpore'e dans le produit qui est
    de'crit
    dans ce document. En particulier, et sans la limitation, ces droits de
    proprie'te' intellectuels peuvent inclure un ou plus des brevets
    ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
    brevets plus supple'mentaires ou les applications de brevet en attente
    dans les E'tats-Unis et dans les autres pays.
    Ce produit ou document est prote'ge' par un copyright et distribue'
    avec des licences qui en restreignent l'utilisation, la copie, la
    distribution, et la de'compilation. Ce documention associe n peut
    e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
    l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
    licence, le cas e'che'ant.
    Le logiciel de'tenu par des tiers, et qui comprend la technologie
    relative aux polices de caracte`res, est prote'ge' par un copyright et
    licencie' par des fournisseurs de Sun.
    Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail et and
    Enterprise JavaBeans sont des marques de fabrique ou des marques
    de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
    pays.
    LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
    DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
    EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
    NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
    L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
    CONTREFAC,ON.
    -->
    <!--
    This is the XML DTD for the J2EE 1.3 application deployment
    descriptor. All J2EE 1.3 application deployment descriptors
    must include a DOCTYPE of the following form:
    <!DOCTYPE application PUBLIC
    "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
    "http://java.sun.com/dtd/application_1_3.dtd">
    -->
    <!--
    The following conventions apply to all J2EE deployment descriptor
    elements unless indicated otherwise.
    - In elements that contain PCDATA, leading and trailing whitespace
    in the data may be ignored.
    - In elements whose value is an "enumerated type", the value is
    case sensitive.
    - In elements that specify a pathname to a file within the same
    JAR file, relative filenames (i.e., those not starting with "/")
    are considered relative to the root of the JAR file's namespace.
    Absolute filenames (i.e., those starting with "/") also specify
    names in the root of the JAR file's namespace. In general, relative
    names are preferred. The exception is .war files where absolute
    names are preferred for consistency with the servlet API.
    -->
    <!--
    The application element is the root element of a J2EE application
    deployment descriptor.
    -->
    <!ELEMENT application (icon?, display-name, description?, module+,
    security-role*)>
    <!--
    The alt-dd element specifies an optional URI to the post-assembly
    version of the deployment descriptor file for a particular J2EEmodule.
    The URI must specify the full pathname of the deployment descriptor
    file relative to the application's root directory. If alt-dd is not
    specified, the deployer must read the deployment descriptor from the
    default location and file name required by the respective component
    specification.
    Used in: module
    -->
    <!ELEMENT alt-dd (#PCDATA)>
    <!--
    The connector element specifies the URI of a resource adapter archive
    file, relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT connector (#PCDATA)>
    <!--
    The context-root element specifies the context root of a web
    application.
    Used in: web
    -->
    <!ELEMENT context-root (#PCDATA)>
    <!--
    The description element is used to provide text describing the parent
    element. The description element should include any information that
    the application ear file producer wants to provide to the consumer of
    the application ear file (i.e., to the Deployer). Typically, the tools
    used by the application ear file consumer will display the description
    when processing the parent element that contains the description.
    Used in: application, security-role
    -->
    <!ELEMENT description (#PCDATA)>
    <!--
    The display-name element contains a short name that is intended to be
    displayed by tools. The display name need not be unique.
    Used in: application
    Example:
    <display-name>Employee Self Service</display-name>
    -->
    <!ELEMENT display-name (#PCDATA)>
    <!--
    The ejb element specifies the URI of an ejb-jar, relative to the top
    level of the application package.
    Used in: module
    -->
    <!ELEMENT ejb (#PCDATA)>
    <!--
    The icon element contains small-icon and large-icon elements that
    specify the file names for small and a large GIF or JPEG icon images
    used to represent the parent element in a GUI tool.
    Used in: application
    -->
    <!ELEMENT icon (small-icon?, large-icon?)>
    <!--
    The java element specifies the URI of a java application clientmodule,
    relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT java (#PCDATA)>
    <!--
    The large-icon element contains the name of a file
    containing a large (32 x 32) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <large-icon>employee-service-icon32x32.jpg</large-icon>
    -->
    <!ELEMENT large-icon (#PCDATA)>
    <!--
    The module element represents a single J2EE module and contains a
    connector, ejb, java, or web element, which indicates the module type
    and contains a path to the module file, and an optional alt-ddelement,
    which specifies an optional URI to the post-assembly version of the
    deployment descriptor.
    The application deployment descriptor must have one module element for
    each J2EE module in the application package.
    Used in: application
    -->
    <!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
    <!--
    The role-name element contains the name of a security role.
    The name must conform to the lexical rules for an NMTOKEN.
    Used in: security-role
    -->
    <!ELEMENT role-name (#PCDATA)>
    <!--
    The security-role element contains the definition of a security
    role. The definition consists of an optional description of the
    security role, and the security role name.
    Used in: application
    Example:
    <security-role>
    <description>
    This role includes all employees who are authorized
    to access the employee service application.
    </description>
    <role-name>employee</role-name>
    </security-role>
    -->
    <!ELEMENT security-role (description?, role-name)>
    <!--
    The small-icon element contains the name of a file
    containing a small (16 x 16) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <small-icon>employee-service-icon16x16.jpg</small-icon>
    -->
    <!ELEMENT small-icon (#PCDATA)>
    <!--
    The web element contains the web-uri and context-root of a web
    application module.
    Used in: module
    -->
    <!ELEMENT web (web-uri, context-root)>
    <!--
    The web-uri element specifies the URI of a web application file,
    relative to the top level of the application package.
    Used in: web
    -->
    <!ELEMENT web-uri (#PCDATA)>
    <!--
    The ID mechanism is to allow tools that produce additional deployment
    information (i.e., information beyond the standard deployment
    descriptor information) to store the non-standard information in a
    separate file, and easily refer from these tool-specific files to the
    information in the standard deployment descriptor.
    Tools are not allowed to add the non-standard information into the
    standard deployment descriptor.
    -->
    <!ATTLIST alt-dd id ID #IMPLIED>
    <!ATTLIST application id ID #IMPLIED>
    <!ATTLIST connector id ID #IMPLIED>
    <!ATTLIST context-root id ID #IMPLIED>
    <!ATTLIST description id ID #IMPLIED>
    <!ATTLIST display-name id ID #IMPLIED>
    <!ATTLIST ejb id ID #IMPLIED>
    <!ATTLIST icon id ID #IMPLIED>
    <!ATTLIST java id ID #IMPLIED>
    <!ATTLIST large-icon id ID #IMPLIED>
    <!ATTLIST module id ID #IMPLIED>
    <!ATTLIST role-name id ID #IMPLIED>
    <!ATTLIST security-role id ID #IMPLIED>
    <!ATTLIST small-icon id ID #IMPLIED>
    <!ATTLIST web id ID #IMPLIED>
    <!ATTLIST web-uri id ID #IMPLIED>

  • Errors deploying Planning application to EPMA

    Hello,
    We have successfully migrated our v4.02 planning application over to v11.1.1.1 and upgraded it successfully. However, we I attempt to to deploy the application witin EPMA the following errors are received:
    Validation Log
    ==============
    Job Id: 26
    Created : 4/9/2009 5:36:38 PM GMT
    Application :SDSPlan
    Validation Summary
    ==================
    Result : Failure
    Summary : There were 89 errors and 0 warnings during the validation process. For details refer the error and warning section of this log.
    Error Details
    =============
    Error : Attribute dimension "01a Rents" is associated with 0 base dimensions or has 0 associations to the same base dimension. It should be associated exactly once with only one base dimension.
    Error : Attribute dimension "02a Property Tax" is associated with 0 base dimensions or has 0 associations to the same base dimension. It should be associated exactly once with only one base dimension.
    Error : Attribute dimension "03a Equipment Leases" is associated with 0 base dimensions or has 0 associations to the same base dimension. It should be associated exactly once with only one base dimension.
    Error : Attribute dimension "04a Copier Paper" is associated with 0 base dimensions or has 0 associations to the same base dimension.
    I am currently reading the EPMA Admin documentation but i am not finding the resolution. Can anyone please give me some insight / direction.
    Thank you,
    Tony

    Hi,
    To associate an attribute dimension with a dimension you will need to do this in EPMA.
    Go to the application in EPMA and to the dimension library (you can right click the application > edit)
    Right click the dimension you want to an attribute associated with > "Create Association" > Select Attribute from the property dropdown.
    Select the attribute dimension from the dimension dropdown.
    To associate an attribute member, click on a dimension member and in the property section you can click Attribute and select the member.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Error deploy SOA application "Deployment Failed: Unable to register service

    Hi All
    I have build a SOA application and tried to build and deploy to my SOA server but stuck with below error msg.
    Step-1: Created the application, with BPEL components etc.
    Step-2: Right click on the application, then Deploy -> To -> My Server..
    Step-3: SOA build msg
    Buildfile: F:\PF\Oracle\Middleware\jdeveloper\bin\ant-sca-compile.xml
    BUILD SUCCESSFUL
    Total time: 5 seconds
    Step-4: Deployment msg
    +[03:09:24 PM] ---- Deployment started. ----+
    +[03:09:24 PM] Target platform is (Weblogic 10.3).+
    +[03:09:24 PM] Running dependency analysis...+
    +[03:09:24 PM] Building...+
    +[03:09:32 PM] Deploying profile...+
    +[03:09:32 PM] Wrote SAR file to F:\SSID\Oracle_WS\Clawback\CustomerSubscriptionStatusMonitor\deploy\sca_CustomerSubscriptionStatusMonitor_rev1.0.jar+
    +[03:09:32 PM] Deploying sca_CustomerSubscriptionStatusMonitor_rev1.0.jar to soa_server1 [9.184.173.34:8001]+
    +[03:09:32 PM] Processing sar=/F:/SSID/Oracle_WS/Clawback/CustomerSubscriptionStatusMonitor/deploy/sca_CustomerSubscriptionStatusMonitor_rev1.0.jar+
    +[03:09:32 PM] Adding sar file - F:\SSID\Oracle_WS\Clawback\CustomerSubscriptionStatusMonitor\deploy\sca_CustomerSubscriptionStatusMonitor_rev1.0.jar+
    +[03:09:32 PM] Preparing to send HTTP request for deployment+
    +[03:09:33 PM] Creating HTTP connection to host:9.184.173.34, port:8001+
    +[03:09:33 PM] Sending internal deployment descriptor+
    +[03:09:33 PM] Sending archive - sca_CustomerSubscriptionStatusMonitor_rev1.0.jar+
    +[03:09:53 PM] Received HTTP response from the server, response code=500+
    +[03:09:53 PM] Error deploying archive sca_CustomerSubscriptionStatusMonitor_rev1.0.jar to soa_server1 [9.184.173.34:8001]+
    +[03:09:53 PM] HTTP error code returned [500]+
    +[03:09:53 PM] Error message from server:+
    Error during composite deployment: oracle.fabric.common.FabricDeploymentException: oracle.fabric.common.FabricException: Deployment Failed: Unable to register service.: Deployment Failed: Unable to register service..
    +[03:09:53 PM] Check server log for more details.+
    +[03:09:53 PM] #### Deployment incomplete. ####+
    +[03:09:53 PM] Error deploying archive file:/F:/SSID/Oracle_WS/Clawback/CustomerSubscriptionStatusMonitor/deploy/sca_CustomerSubscriptionStatusMonitor_rev1.0.jar+
    +(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)+
    Also I have check the http://localhost:8001/soa-infra/ and it says*
    Welcome to the Oracle SOA Platform on WebLogic
    SOA Version: v11.1.1.0.0 - 11.1.1.1.0_090609.1407.5182 built on Tue Jun 09 15:06:41 PDT 2009
    WebLogic Server 10.3.1.0 Wed Jun 10 22:24:41 MDT 2009 1227385 (10.3.1.0)
    There are no composites deployed to the platform
    Edited by: user11263460 on Dec 13, 2009 2:39 AM

    If this still needed. Take a look in Your WSDL file - any references to schemas etc. Are they accessible on server? For example - XSD file have absolute file system link - change it to project level import (copy xsd file to project) or publish to MDS.

  • Duplicate persistence error -- deploying GlassFish application in Weblogic

    Hi,
    I am using NetBeans to deploy a web application which has RESTful web services. I am using Weblogic 12c and MySQL database. The NBproject MyAppServer includes another NB project MyAppLibrary. Both MyAppServer and MyAppLibrary have their own perisitence.xml files. Both projects are referencing the same database. The application was previously deployed in GlassFish and worked perfectly. However, migrating to Weblogic gives me the following error:
    "Deployment failed. The message was: weblogic.application.naming.EnvironmentException: duplicate persistence units with name MyAppLibraryPU in scope web. First PU location: file:/C:/cygwin/home/test/myfolder/apps/MyApp/MyAppServer/build/web/WEB-INF/classes/. Second PU location: file:/C:/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/MyAppServer/ub3nr6/war/WEB-INF/lib/MyAppLibrary.jar"
    I changed the name of the persistence unit in persistence.xml of MyAppServer, which resulted in no error being logged, but the server-side of the application doesn't run correctly now i.e. apparently no data was retrieved from the database.
    Any help will be appreciated.
    Thanks.

    Nothing to do with WebLogic JDBC so far...

  • Error deploying J2EE Application (EAR) to standalone OC4J

    Hi
    I'm invoking the admin_client.jar utility to deploy a webservice on a standalone OC4J, here is the command:
    java -jar %OC4J_HOME%\j2EE\home\admin_client.jar deployer:oc4j:localhost:23791 oc4jadmin test -deploy -file C:\10GIDS\BIN\johnTestWS.ear -deploymentname johnsws -bindAllWebApps default-web-site -contextRoot johnsws
    I get the following error:
    Deploy error: Deploy error: Operation failed with error:Error compiling :C:\JDeveloper_10g\j2ee\home\applications\johnsws\johnTestWS-web: Syntax error in source or compilation failed in: C:\JDeveloper_10g\j2ee\home\application-deployments\johnsws\johnTestWS-web\oracle\generated\runtime\XmlreturnBase__SOAPSerializer.java java.lang.NoClassDefFoundError: com/sun/tools/javac/MainException in thread "main"
    The java.lang.NoClassDefFoundError: com/sun/tools/javac/MainException in thread "main" error string (from my limited understanding) would mean there is a jar file missing from the CLASSPATH or something, yet, because the '-jar' option is selected when running the java command I don't have the option to include any classpath in the command string. What am I doing wrong?
    I've been trying to assemble and deploy this web service for ages now and I think I'm very close to the end, can someone please show me that I'm doing something very simple wrong....?

    smydo,
    I see you answered yourself in the other forum where you posted the same question:
    Problems deploying Web Service to standalone OC4J from Windows command line
    Good Luck,
    Avi.

  • Error in Sample Application v1.6

    When I launch the Sample Application v1.6 in IE (after I enter the demo/workspace), I get a Javascript error box with something to the effect of
    divTag is null or not an object
    Works fine in Firefox
    What is the issue? Thanks

    Well, I just ran it from a FF that does NOT have the SVG plugin and looked in the Firefox JS console and see the same error
    Clicking on the displayed JS link there takes me to the following
    //Display download plugin message
    function noPlugin(tDiv){
         divTag = document.getElementById(tDiv);     
         divTag.innerHTML = "Please install SVG Viewer to view the chart. <a href='http://www.adobe.com/svg/viewer/install/main.html'>Click here to download.</a>";     
    } // End noPlugin()
    There is obviously something amiss here. The intent seems to be to show that message above somewhere, but the "tDiv" element doesnt seem to be defined yet.
    Thanks

  • Error running sample application

    Not able to run sample application. while compiling *.java files it's giving error oracle.ifs.bean.* not found. pls. suggest asap.

    Do you have your CLASSPATH setup correctly? Your CLASSPATH must include the iFS libraries if you want to compile anything. Read the devkit documentation for more info.

  • Problem in deploying sample application HelloDB application iPlanet.

    I installed iPlanet 6.5 on my windows NT work station and then as per iPlanet documentation I tried deploying the sample HelloDB application. It gives the following error when I say build install
    Searching for build.xml ...
    Buildfile: E:\iPlanet\ias6\ias\ias-samples\database\hellodb\src\build.xml
    install_javadocs:
    [delete] Deleting directory E:\iPlanet\ias6\ias\ias-samples\database\hellodb\docs\api
    [mkdir] Created dir: E:\iPlanet\ias6\ias\ias-samples\database\hellodb\docs\api
    BUILD FAILED
    E:\iPlanet\ias6\ias\ias-samples\database\hellodb\src\build.xml:164: E:\iPlanet\ias6\ias\ias-samples\database\hellodb\build\d
    ocs\api not found.
    Total time: 1 second
    Can you please tell me where I'm doing wrong.

    Hi,
    Could you please post the entire messages that is on the screen right from the time you invoke build followed by the option.
    A quick answer from looking at the posted message that I can guess is that, may be build fails at the stage when the directory is created.
    Regards
    Ganesh .R
    Developer Technical Support
    Sun Microsystems
    http://www.sun.com/developers/support

Maybe you are looking for

  • F.01 & FBL3N amounts mismatched at Company Code Level

    Hello Gurus,         At Client side, we are facing problem of mismatch in FBL3N & F.01 Report for some GL accounts and this is at Company Code level not Profit Center or Segment Level.         I have also verified the Master Data of GLs which are hav

  • Stream not found null error

    Hello everybody, I am able to embed the strobe player on a web page and play flv videos. However, if I don't let the videoplay through and refresh my web page, then I am getting  "We are unable to connect to the content you've requested" error. When

  • How to extract  Blob using java

    hai have a peace day. i want to extract the data from BLOB thro java i using getblob, but i don,t know properly please tell any ideas r give some sample codes thank u raja

  • Incorrect russian code page in messages in iAS 9i and Oracle8i R3

    The Oracle iAS 9i and Oracle 8i Release 3 for Windows NT has strange code page for this platform: ISO-8859-5 (UNIX Russian), but must be CP-1251 (Windows Russian). I can't install iAS on Windows platform, because messages in installer not correspond

  • XCode Java project - can you compile both a Mac .app and a Windows .exe?

    I'm working on a project for my computer science class, and it has to be done in Java. I'd like to be able to build a .app for the Mac and a .exe for Windows, and ideally I'd like to do it straight from within XCode. Is it somehow (at all) possible t