Weblogic deployment error
I am trying to deploy a Very simple JFS Application that Connects to a Webservice and sends a request.
When I run it in JDeveloper locally it works, but when i Deploy to Weblogic i get the following error: oracle/jrf/PortabilityLayerException
[03:24:53 PM] Building...
[03:24:55 PM] Deploying profile...
[03:24:56 PM] Wrote Web Application Module to C:\JDeveloper\Application1\ViewController\deploy\facestest.war
[03:25:35 PM] Redeploying Application...
[03:26:34 PM] [Deployer:149193]Operation 'deploy' on application 'facestest' has failed on 'AdminServer'
[03:26:34 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application facestest on AdminServer.: oracle/jrf/PortabilityLayerException.
[03:26:34 PM] Weblogic Server Exception: weblogic.application.WrappedDeploymentException: oracle/jrf/PortabilityLayerException
[03:26:34 PM] See server logs or server console for more details.
[03:26:34 PM] weblogic.application.WrappedDeploymentException: oracle/jrf/PortabilityLayerException
[03:26:34 PM] #### Deployment incomplete. ####
[03:26:34 PM] Deployment Failed
Moderators don't move threads here, you'll have to repost here:
JDeveloper and ADF
Make sure to provide all the platform detail and which installer you used and how you created / configured the domain that you are trying to deploy to. That wasn't precisely clear in your original post.
Similar Messages
-
Configuration wizard Weblogic deployment error [Admin Center]
I'm getting an error during the "Executing WLST Script" phase of the configuration wizard.
My environment:
BEA Weblogic Server 10.0 (installed with Workspace Studio 1.1)
Oracle BPM 10g3 (10.3.0.0)
Oracle Database 10g Express
This is what the AdmCenterConsole.log file has:
Deploying application from C:\OraBPMwlHome\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets BPMServer (upload=true) ...
<Jan 28, 2009 11:15:59 AM PST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer archive: C:\OraBPMwlHome\j2ee\weblogic\deployer\wlj2eedeployer.ear, to BPMServer .>
.Completed the deployment of Application with status completed
Current Status of your Deployment:
Deployment command type: deploy
Deployment State : completed
Deployment Message : no message
Deploying application from C:\OraBPMwlHome\ears\engine\01-eng-bpmengine.ear to targets BPMServer (upload=true) ...
<Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine -archive: C:\OraBPMwlHome\ears\engine\01-eng-bpmengine.ear-, to BPMServer .>
WLST-WLS-1233170095995: <Warning> <DeploymentService> <BEA-290003> <Deployment service servlet encountered an exception while handling request of type "app_upload". Exception is: "*Connection reset*".>
Failed to deploy the application with status failed
Current Status of your Deployment:
Deployment command type: deploy
Deployment State : failed
Deployment Message : weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260041 Unable to upload 'C:\OraBPMwlHome\ears\engine\01-eng-bpmengine.ear' to 't3://dmcad00064252:7001'
No stack trace available.
weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed.
at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:49)
at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185)
at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:535)
at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:427)
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 org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:248)
at org.python.core.PyObject.invoke(PyObject.java:2016)
at org.python.pycode._pyx19.deploy$8(<iostream>:223)
at org.python.pycode._pyx19.call_function(<iostream>)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:404)
at org.python.core.PyFunction.__call__(PyFunction.java:184)
at org.python.pycode._pyx18.deploy_Applications$61(C:\Documents and Settings\c742323\.configWizard\tmp\config.py:623)
at org.python.pycode._pyx18.call_function(C:\Documents and Settings\c742323\.configWizard\tmp\config.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:256)
at org.python.core.PyFunction.__call__(PyFunction.java:169)
at org.python.pycode._pyx18.f$0(C:\Documents and Settings\c742323\.configWizard\tmp\config.py:738)
at org.python.pycode._pyx18.call_function(C:\Documents and Settings\c742323\.configWizard\tmp\config.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1135)
at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
at weblogic.management.scripting.WLST.main(WLST.java:106)
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 weblogic.WLST.main(WLST.java:29)Hi. I'm having this same exact issue. My AdmCenterConsole.log contains the same error. Additionally, the log file for my BPMDomain log contains this information:
Current Status of your Deployment:
Deployment command type: deploy
Deployment State : failed
Deployment Message : weblogic.management.ManagementException: [Deployer:149003]Unable to access application source information in '[DeploymentService:290003]Deployment service servlet encountered an exception while handling request of type "app_upload". Exception is: "Read timed out".\app\01-eng-albpmengine.ear' for application '01-eng-albpmengine'. The specific error is: No application files exist.
No stack trace available.
This Exception occurred at Sun Apr 19 14:29:13 CDT 2009.
weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed.
at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)
at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185)
at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536)
at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429)
mick3y -- Did you happen to ever get this issue resolved?
Thanks, Alan -
J dev 11g Weblogic deployment error.
We develop a new web ADF JSF project using Jdev11g production (not migrated from prereleases). We configure weblogic R3 as ADF domain.
When we want to deploy our pğroject to weblogic following exception occurs.
Is there anyone faced before. How can we solve this. Thanks.
....> <Error> <Console> <.......> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1226331993131> <BEA-240003> <Console encountered the following error weblogic.management.DeploymentException:
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener
at java.lang.Class.forName(Class.java:247)
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135)There is no JpsApplicationLifecycleListener in my web.xml code.
I added web.xml source below.
is there any abnormal or problematic situation inside.
Thanks.
<?xml version = '1.0' encoding = 'windows-1254'?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" version="2.5" xmlns="http://java.sun.com/xml/ns/javaee">
<description>Empty web.xml file for Web Application</description>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
<context-param>
<description>If this parameter is true, there will be an automatic check of the modification date of your JSPs, and saved state will be discarded when JSP's change. It will also automatically check if your skinning css files have changed without you having to restart the server. This makes development easier, but adds overhead. For this reason this parameter should be set to false when your application is deployed.</description>
<param-name>org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<description>Whether the 'Generated by...' comment at the bottom of ADF Faces HTML pages should contain version number information.</description>
<param-name>oracle.adf.view.rich.versionString.HIDDEN</param-name>
<param-value>false</param-value>
</context-param>
<filter>
<filter-name>trinidad</filter-name>
<filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-class>
</filter>
<filter>
<filter-name>ServletADFFilter</filter-name>
<filter-class>oracle.adf.share.http.ServletADFFilter</filter-class>
</filter>
<filter>
<filter-name>ADFLibraryFilter</filter-name>
<filter-class>oracle.adf.library.webapp.LibraryFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>trinidad</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>ServletADFFilter</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>ADFLibraryFilter</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>resources</servlet-name>
<servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>adflibResources</servlet-name>
<servlet-class>oracle.adf.library.webapp.ResourceServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>BIGRAPHSERVLET</servlet-name>
<servlet-class>oracle.adfinternal.view.faces.bi.renderkit.graph.GraphServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>BIGAUGESERVLET</servlet-name>
<servlet-class>oracle.adfinternal.view.faces.bi.renderkit.gauge.GaugeServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>MapProxyServlet</servlet-name>
<servlet-class>oracle.adfinternal.view.faces.bi.renderkit.geoMap.servlet.MapProxyServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>GatewayServlet</servlet-name>
<servlet-class>oracle.adfinternal.view.faces.bi.renderkit.graph.FlashBridgeServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>resources</servlet-name>
<url-pattern>/adf/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>resources</servlet-name>
<url-pattern>/afr/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>adflibResources</servlet-name>
<url-pattern>/adflib/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>BIGRAPHSERVLET</servlet-name>
<url-pattern>/servlet/GraphServlet/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>BIGAUGESERVLET</servlet-name>
<url-pattern>/servlet/GaugeServlet/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>MapProxyServlet</servlet-name>
<url-pattern>/mapproxy/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>resources</servlet-name>
<url-pattern>/bi/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>GatewayServlet</servlet-name>
<url-pattern>/flashbridge/*</url-pattern>
</servlet-mapping>
<session-config>
<session-timeout>35</session-timeout>
</session-config>
<mime-mapping>
<extension>html</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
<mime-mapping>
<extension>txt</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
</web-app> -
When I try to deploy to a (successfully) tested weblogic connection I get the following:
Sending EAR file to remote WebLogic server...
C:\jdeveloper\jdk\jre\bin\javaw.exe -Ddeploy.debug=true -classpath C:\bea\weblogic700\server\lib\weblogic.jar weblogic.deploy -host apo -port 7001 -debug deploy iais file:/C:/jdeveloper/jdev/mywork/Workspace1/IAIS/iais.ear
You must specify at least a name and a source when deploying
Usage: java weblogic.deploy [options] list password {name} {source}
Note: when using 'deploy', if the source is specified, the server assumes a new deployment. For updates, use 'update'. If -url is specified, then -host and -port are ignored.
where options include:
-help Print this help message.
-version Print version information.
-port <port> The port to connect on, default is 7001.
-host <host> The host to connect to, default is localhost.
-url <url> The admin server to connect to, default is
t3://localhost:7001
-username <username> The username to connect with.
-component Component to be deployed on various targets,
must be specified as [<component
name>:Target1,Target2]...component
corresponds to the Name attribute for the
component MBean. If you are deploying a new
application or standalone component,
component is the name of the .jar/.war/etc.
minus the .jar/.war suffix.
-jspRefreshFiles <file1.jsp,file2.html,file3.gif,...> This option is only used with the refresh
flag. This is the list of files that are to
be refreshed. Any static file type may be
refreshed. (jsp, gif, jpeg, html, etc).
.class files may not be refreshed. To update
class files, please use the update flag to
redeploy your application. This must be
specified as a comma separated list.
-jspRefreshComponentName <jspRefreshComponentName> This option is only used with the refresh
flag. The name of the component that contains
the files being refreshed.
-debug If set, detailed debug information is
printed.
**** weblogic.deploy returned with non-zero exit status: 1
#### Deployment incomplete. #### Jun 11, 2002 9:36:11 AM
From what I see, it has both a name and a source. The help indicates that the username/password is not required, and so I omitted it. I really need to get this working without a username/password, as my systems folks don't want the developers to have the console password for the weblogic server.When I try to deploy to a (successfully) tested weblogic connection I get the following:
Sending EAR file to remote WebLogic server...
C:\jdeveloper\jdk\jre\bin\javaw.exe -Ddeploy.debug=true -classpath C:\bea\weblogic700\server\lib\weblogic.jar weblogic.deploy -host apo -port 7001 -debug deploy iais file:/C:/jdeveloper/jdev/mywork/Workspace1/IAIS/iais.ear
You must specify at least a name and a source when deploying
Usage: java weblogic.deploy [options] list password {name} {source}
Note: when using 'deploy', if the source is specified, the server assumes a new deployment. For updates, use 'update'. If -url is specified, then -host and -port are ignored.
where options include:
-help Print this help message.
-version Print version information.
-port <port> The port to connect on, default is 7001.
-host <host> The host to connect to, default is localhost.
-url <url> The admin server to connect to, default is
t3://localhost:7001
-username <username> The username to connect with.
-component Component to be deployed on various targets,
must be specified as [<component
name>:Target1,Target2]...component
corresponds to the Name attribute for the
component MBean. If you are deploying a new
application or standalone component,
component is the name of the .jar/.war/etc.
minus the .jar/.war suffix.
-jspRefreshFiles <file1.jsp,file2.html,file3.gif,...> This option is only used with the refresh
flag. This is the list of files that are to
be refreshed. Any static file type may be
refreshed. (jsp, gif, jpeg, html, etc).
.class files may not be refreshed. To update
class files, please use the update flag to
redeploy your application. This must be
specified as a comma separated list.
-jspRefreshComponentName <jspRefreshComponentName> This option is only used with the refresh
flag. The name of the component that contains
the files being refreshed.
-debug If set, detailed debug information is
printed.
**** weblogic.deploy returned with non-zero exit status: 1
#### Deployment incomplete. #### Jun 11, 2002 9:36:11 AM
From what I see, it has both a name and a source. The help indicates that the username/password is not required, and so I omitted it. I really need to get this working without a username/password, as my systems folks don't want the developers to have the console password for the weblogic server. -
Weblogic deployment APIs giving error for deployment on weblogic 10.3.2
I am using weblogic deployment APIs to distribute my war file on weblogic 10.3.2 but it gives the following error on distribute
weblogic.management.ManagementException: [Deployer:149003]Unable to access application source information in '<!DOCTYPE HTML PUBLIC "-/W3C/DTD HTML 4.0 Draft/EN">/app/jamagent.war' for application 'jamagent.war'. The specific error is: No application files exist.
My sample code is below.
DeploymentOptions options = null;
Target[] targets = myConnectedManager.getTargets();
Class wlsFactoryClass = Class.forName("weblogic.deploy.api.tools.SessionHelper");
Method m = wlsFactoryClass.getDeclaredMethod("getDeploymentManager",new Class[]{String.class,String.class,String.class,String.class});
m.setAccessible(true);
WebLogicDeploymentManager myConnectedManager = (WebLogicDeploymentManager)m.invoke(wlsFactoryClass, new Object[]{hostname,port,weblogicUsername,weblogicPasswd});
myConnectedManager.enableFileUploads();
options = new DeploymentOptions();
options.setName(destWarName);
ProgressObject po = myConnectedManager.distribute(targets, new File("/tmp/jamagent_orig.war), null,options);
The header of web.xml is
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
Can someone help why this is happening? I am not including weblogic-application.xml in the war file as i think this is not required for a war file. Is that the reason?
Edited by: user790199 on Dec 28, 2009 7:37 AMHi,
The DTD used in "web.xml" should not cause any issue ...though it's the OLD "web.xml"...Please try to run the Following command to Generate the New Deployment Descriptors from the Existing Application:
Step1). Open a Command Window and Run "setWLSEnv.sh" or "setWLSEnv.cmd".
Step2). In the Command Prompt move to the Current Directory where you have placed your Application and then Run the Following Command
java weblogic.DDConverter -d NewDDs jamagent.war
Here Above Command Will read the "jamagent.war" War archive and then It will generate the New DDs in "NewDDs" directory...Which we need to replace with the OLD DDs present in our WebApplication..
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here) -
Error using weblogic.deploy tool, while deploying a war
Hi all, I'm trying to deploy a war with the follw command:
java weblogic.deploy -host localhost -port 7001 -component NewScreenWar:BEAserver
deploy beasystem NewScreenWar d:\newsscreen\weblogic\NewScreenWar.war
It gives me following error:
weblogic.j2ee.DeploymentException: Application NewScreenWar does not contain com
ponent NewScreenWar at weblogic.deploy.deploy(deploy.java:668) at weblogic.deploy.runBody(deploy.java:358)
at weblogic.utils.compiler.Tool.run(Tool.java:79) at weblogic.deploy.main(deploy.java:1601)
Application NewScreenWar does not contain component NewScreenWar
how do I resolve this...??
thanx --anjaly
Hi,
For a tutorial with source on how to create and deploy a simple quickstart JEE5 JPA enterprise 3-tier application on your Oracle WebLogic 10.3 server - see the following example that uses the EclipseLink JPA provider. You should be able to transition all of your mapping information (the @ManyToOne and table/column overrides and named queries for example) using either JPA via entity annotations or native extensions if you do not want to implement EJB3.
see...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
We also have a similar version for Tomcat 6 except the JPA entity beans run outside a container-managed JTA transaction on the web container - for reference.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial
thank you
/michael
www.eclipselink.org -
Weblogic Portal: Error While Deploying: VALIDATION PROBLEMS WERE FOUND
Hello friends
I am getting following error while deploying EAR on server.
“Module named 'MyEAR' failed to deploy. See Error Log view for more detail.”
Steps I followed:
1: Created one portal domain successfully and was able to start the serve after thatr.
2: Created one Portal EAR Project and added it on server.
Now when I am restarting the server, getting following error/log
**“weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND**
**problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>”**
Exception stack Trace:
java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1566)
at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:470)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1346)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:803)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:623)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:516)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
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)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:245)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:155)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:301)
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:178)
as it is ‘brand new ‘ – IDE generated application, weblogic-application.xml is untouched.
Thanks & RegardsI have seen this problem also. To be clear, this occurs straight out of the box. In other words - launch eclipse, create a new workspace, create a new portal EAR project with the wizard, and then try to deploy it without touching anything. In fact, try changing the portal's facets to anything, plain EAR, 11g default, Portal EAR - it doesn't matter. It will not deploy. Either you get this error or you get deployment errors complaining about missing library references in the weblogic-application.xml. Then - you have to do surgery just to get an 'out of the box' portal to run. Very frustrating.
-
EJB deployment error for Weblogic server 9.2 mp4
Hi,
While trying to deploy a small EJB jar file which uses EJB 2.1 CMP beans with relationships, getting the following error from Weblogic server 9.2 MP4:
=================================================================================================
<Error> <EJB> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988333> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
>
####<Nov 1, 2011 4:09:48 PM IST> <Error> <Deployer> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988380> <BEA-149265> <Failure occured in the execution of deployment request with ID '1320143984947' for task '1'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:382)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
=================================================================================================
While I'm able to deploy without the CMP 1-1 relationship, the moment I introduce the 1-1 relationship, I get this error. Database used is Oracle 10g XE.
I have been battling this error for more than a day now. Kindly help me fix this.
Thanks in advance!
Regards,
VinodHi,
I was able to figure out the root cause. I was using the primitive data type "int" for primary key and foreign key for one of the beans in the relationship. After I changed it to "Integer" wrapper type, the issue got resolved.
-Vinod -
Deployment error - Errors in named queries in weblogic 10
Hi, All.
I got the error message when I tried to deploy my webapp to weblogic 10 & 10.1(10M1).
Stacktrace:
<May 19, 2008 11:51:14 AM EDT> <Error> <Console> <BEA-240003> <Console encounter
ed the following error weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:314)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedM
oduleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme
ntStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App
ContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr
eateAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Prepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr
epare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy
mentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare
(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre
pare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: java.lang.Throwable: Substituted for missing class org.hibernate.Hibe
rnateException - Errors in named queries: SpotType.findById, Spot.findByTopic, T
argetAudience.findById, SpotOrder.findById, SpotAuditDetails.findById, ProjectOf
ficer.findById, SpotOrderAvailable.findById, ProjectOfficer.findByStatus, SpotOr
derTopic.findById, Topic.findById, findAllSpots, SpotOrderDetails.findById, find
AllCategory, SME.findById, SpotAudit.findById, ContactInfo.findById, SpotCategor
y.findById, SpotOrderTopicSpot.findById, ProjectTopic.findById, NetworkType.find
ById, Source.findById, NetworkType.findByStatus, RecordStatus.findById, SpotType
.findByStatus, findAllClient, Spot.findByTitle, findAllRecordStatus, SMETopicCom
ments.findById, ContractInfo.findById, Channel.findById, Client.findById, findAl
lSource, SMETopic.findById, Project.findById, SpotComments.findById, SpotOrderCo
mments.findById, ContactInfoComments.findById, Spot.findById
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:
365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.jav
a:1300)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(Annotat
ionConfiguration.java:859)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Con
figuration.java:669)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFa
ctory(HibernatePersistence.java:132)
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactor
y(PersistenceUnitInfoImpl.java:264)
at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInf
oImpl.java:110)
at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(
AbstractPersistenceUnitRegistry.java:316)
at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDe
scriptors(AbstractPersistenceUnitRegistry.java:96)
at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersis
tenceUnitRegistry.java:53)
at weblogic.servlet.internal.WebAppModule.initPURegistry(WebAppModule.ja
va:1151)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:304)
>
I included named queries on orm.xml file and also in each entities using annotations like following.
orm.xml>
<?xml version="1.0" encoding="UTF-8"?>
<entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm http://java.sun.com/xml/ns/persistence/orm_1_0.xsd"
version="1.0">
<!-- WE PLACE LARGER AND JOIN QUERIES STATEMENTS HERE -->
<named-query name="findAllClient">
<query><![CDATA[SELECT e FROM Client e ORDER BY e.clientName]]></query>
</named-query>
<named-query name="findAllSource">
<query><![CDATA[SELECT e FROM Source e ORDER BY e.sourceDesc]]></query>
</named-query>
<named-query name="findAllCategory">
<query><![CDATA[SELECT e FROM SpotCategory e ORDER BY e.spotCategoryDesc]]></query>
</named-query>
<named-query name="findAllRecordStatus">
<query><![CDATA[SELECT e FROM RecordStatus e ORDER BY e.id]]></query>
</named-query>
<named-query name="findAllSpots">
<query><![CDATA[SELECT e FROM Spot e ORDER BY e.id]]></query>
</named-query>
</entity-mappings>
entity example:
@Entity
@Table(name = "SPOTTYPE")
@NamedQueries( { @NamedQuery(name = "SpotType.findById", query = "SELECT e FROM SpotType e WHERE e.id = :id"),
@NamedQuery(name = "SpotType.findByStatus", query = "SELECT e FROM SpotType e WHERE e.recordStatus.id = :status") })
public class SpotType implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(generator = "spotTypeSeq")
@SequenceGenerator(name = "spotTypeSeq", sequenceName = "SEQ_SPOTTYPE", allocationSize = 1)
@Column(name = "SPOTTYPEID", nullable = false, length = 2)
private Long id;
@Column(name = "SPOTTYPESHRTNM", nullable = false, length = 2)
private String spotTypeShortName;
@Column(name = "SPOTTYPELONGNM", nullable = false, length = 35)
everything works until I clicked the activate the change button. I tried to override libs by putting libs I'm using in my domain, still I have the same error message.
Libs that I have:
Name 5 Size Type Date Modified
antlr-2.7.6.jar 434 KB ALZip jar File 2/13/2008 5:28 PM
asm.jar 26 KB ALZip jar File 2/13/2008 5:28 PM
asm-attrs.jar 17 KB ALZip jar File 3/17/2005 4:05 PM
cglib-2.1.3.jar 276 KB ALZip jar File 2/13/2008 5:28 PM
commons-beanutils-1.7.0.jar 185 KB ALZip jar File 12/15/2007 7:12 PM
commons-codec-1.3.jar 46 KB ALZip jar File 12/15/2007 7:12 PM
commons-collections-3.1.jar 547 KB ALZip jar File 4/24/2008 10:28 AM
commons-digester-1.8.jar 141 KB ALZip jar File 12/15/2007 7:13 PM
commons-discovery-0.4.jar 75 KB ALZip jar File 12/15/2007 9:08 PM
commons-el-1.0.jar 110 KB ALZip jar File 5/15/2008 1:11 PM
commons-logging-1.0.4.jar 38 KB ALZip jar File 7/4/2004 4:49 AM
dom4j-1.6.1.jar 307 KB ALZip jar File 2/13/2008 5:28 PM
ehcache-1.2.jar 116 KB ALZip jar File 2/13/2008 5:28 PM
ejb3-persistence.jar 52 KB ALZip jar File 3/14/2008 4:45 PM
hibernate3.jar 2,222 KB ALZip jar File 2/6/2008 9:31 PM
hibernate-annotations.jar 274 KB ALZip jar File 3/14/2008 4:44 PM
hibernate-commons-annotatio... 65 KB ALZip jar File 3/14/2008 4:45 PM
hibernate-entitymanager.jar 116 KB ALZip jar File 3/14/2008 8:07 PM
jaas.jar 102 KB ALZip jar File 6/3/2004 11:31 AM
javassist.jar 449 KB ALZip jar File 2/13/2008 5:28 PM
jaxen-1.1-beta-7.jar 222 KB ALZip jar File 8/16/2005 2:04 PM
jboss-archive-browsing.jar 13 KB ALZip jar File 2/13/2008 5:28 PM
jhighlight-1.0.jar 92 KB ALZip jar File 12/20/2007 4:51 PM
jsf-facelets.jar 294 KB ALZip jar File 9/27/2007 12:20 PM
jstl-1.2.jar 405 KB ALZip jar File 5/15/2008 1:12 PM
jta.jar 9 KB ALZip jar File 6/3/2004 11:31 AM
junit-4.4.jar 158 KB ALZip jar File 5/15/2008 1:12 PM
log4j-1.2.11.jar 343 KB ALZip jar File 8/13/2005 3:28 PM
myfaces-api-1.2.2.jar 319 KB ALZip jar File 1/22/2008 3:40 PM
myfaces-impl-1.2.2.jar 739 KB ALZip jar File 1/22/2008 3:40 PM
nekohtml-0.9.5.jar 104 KB ALZip jar File 12/20/2007 4:42 PM
ojdbc14.jar 1,322 KB ALZip jar File 2/13/2008 5:30 PM
readme.txt 1 KB Text Document 5/15/2008 3:58 PM
richfaces-api-3.2.0.GA.jar 150 KB ALZip jar File 3/31/2008 4:23 PM
richfaces-impl-3.2.0.GA.jar 1,372 KB ALZip jar File 3/31/2008 4:23 PM
richfaces-ui-3.2.0.GA.jar 2,215 KB ALZip jar File 3/31/2008 4:50 PM
spring.jar 2,604 KB ALZip jar File 5/15/2008 1:12 PM
xerces-2.6.2.jar 988 KB ALZip jar File 12/19/2004 6:14 PM
xml-apis.jar 121 KB ALZip jar File 6/3/2004 11:31 AM
This can be deployed to tomcat 6 without any problems.
Thank you in advance for reading and your help.
Edited by gzson at 05/19/2008 9:07 AMFollow the below link:
http://www.hibernate.org/250.html#A25 -
Hi:
I use jbuilder to deploy the appliacation of Kodo JDO 3.0 to Weblogic
,the error message is :
Deployment failed on Server myserver
java.lang.NoClassDefFoundError:
com/solarmetric/kodo/runtime/ObjectNotFoundException
I checked the package ,and did not find the class .What's wrong ?
ArthurThat is not even a package that exists in Kodo 3.0. Seems to me you
have older Kodo versions running around somewhere. -
Weblogic Server Deployment Error
I have built an ear file and tried to deploy it to local standalone server - the log when deploying is below.
Any help would be appreciated.
weblogic.application.ModuleException: Exception preparing module: EJBModule(SvcHcmLocGBPaySetupDataService_MiddleTier.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was: Error processing annotations: .
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: weblogic.utils.ErrorCollectionException:
There are 1 nested errors:
weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015001]Unable to link class oracle.apps.hcm.locGB.payrollSetup.details.payrollPersonalDeductionService.applicationModule.ser
ver.PayrollPersonalDeductionServiceImpl in Jar /scratch/software/mw_local/FMWTOOLS_11.1.1.6.0_GENERIC_120112.0037.2_PATCHES4FA_11.1.1.6.4_PLATFORMS/nbray/mw_home_standalone/user_
projects/domains/fusion_domain1/servers/AdminServer/upload/HcmPayrollApp/V2.0/app/HcmPayrollApp/SvcHcmLocGBPaySetupDataService_MiddleTier.jar : java.lang.NoClassDefFoundError: oracle/apps/hcm/locGB/payrollSetup/details/payrollPersonalDeductionService/PayrollPersonalDeductionService
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1323)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328) at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204) at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)Hi,
Can you clear cache and tmp file for your specific server and check whether issue is solved or not.
Regards,
Kal -
Receiving ERRORS using WEBLOGIC.DEPLOY
Hi everybody,
I am getting strange errors when using the weblogic.deploy command-line
function. I am using WL6.0 on W2000.
Deploy/Update
command: java weblogic.deploy -port 7001 -host localhost update
beapasword MyWebApplication stage\MyWebApplication.war
error: java.lang.NullPointerException
at
weblogic.deploy.deployApplication(deploy.java:383)
at weblogic.deploy.deploy(deploy.java:340)
at weblogic.deploy.runBody(deploy.java:219)
at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.deploy.main(deploy.java:954)
Undeploy
Command: java weblogic.deploy -port 7001 -host localhost undeploy
beapasword MyWebApplication
error: giving up after two minutes
And it looks that just a Update doens't work. I have to undeploy first and
the do a update to see the changes I've made in my file.
Any suggestions....
M-Hi.
WLS version and service pack level? Please post the entire weblogic.deploy command along
with the exception that follows.
Thanks,
Michael
Harjeet Singh wrote:
I try to use weblogic.deploy to deploy my EAR file on weblogic server called localhost
on 7001. When I try to run it gives me following error:
[java] JNDI naming exception: Naming exception trying to connect to: t3://localhost:7001
as: system: password
system password is correct. I have tried http://localhost:7001 to but doesen't seem
to work.
Any ideas.
HS--
Michael Young
Developer Relations Engineer
BEA Support -
Weblogic 10 - application deployment error: Exception is: "File too large"
I posted this in Weblogic -> general but realise is should have really gone here as it's about admin server/deployment services setup / configuration.
I am using weblogic application server 10 in a weblogic clustered enviornment.
I am trying to deploy an application to a managed server when it starts up, all goes well and I can see it deploying the war files to the managed server.
It hits a certain war and panics with the exception
####<Nov 19, 2011 2:03:59 PM BRST> <Error> <Deployer> <devnode01> <managedserver2> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1321718639109> <BEA-149205> <Failed to initialize the application 'test_war' due to error weblogic.management.DeploymentException: Exception occured while downloading files.
weblogic.management.DeploymentException: Exception occured while downloading files
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
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:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from admin server for deployment request "0". Underlying error is: "[DeploymentService:290065]Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "0" from server "managedserver2". Exception is: "File too large"."
at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:86)
at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
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:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
The error appears to be stating the physical file is too big to be deployed
I'm running the managed servers with a heap size of 3GB and the managed server is running with 2GB - I know these are large but they where being used for debugging
I can't find any documentation on the file size too large error, or how to resolve it
DeploymentService:290065 says to look in the log (details are above) and DeploymentService:290066 says the error will be explained in it's description, which it is, "file size too big", it doesn't say where to see/set the max file size, there is plenty of disk space so I can only assume it's setting for the deployment service that needs to be increase, but I cannot find info on this.I don't think this would help, but would using the nostage option for deployment change this behaviour.
I don't think it would as this is for disk based problems rather than transfer size issues. -
Deploy the JSF app to integrated Weblogic Server Error
Hi, All,
I just created a new ADF app and have only one single JSF page in which have one Calender component. After right click the ViewController project and select deploy to Integrated Weblogic server and i got the below error:
[01:05:25 AM] ---- Deployment started. ----
[01:05:25 AM] Target platform is (Weblogic 10.3).
[01:05:26 AM] #### Deployment incomplete. ####
[01:05:26 AM] [J2EE Deployment SPI:260010]Unable to connect to 't3://127.0.0.1:7101' as user, 'weblogic'. Error received: null
[01:05:26 AM] [J2EE Deployment SPI:260010]Unable to connect to 't3://127.0.0.1:7101' as user, 'weblogic'. Error received: null
[01:05:26 AM] [J2EE Deployment SPI:260010]Unable to connect to 't3://127.0.0.1:7101' as user, 'weblogic'. Error received: null
[01:05:26 AM] t3://127.0.0.1:7101: Destination unreachable; nested exception is:
java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.1 500 Server Error'; No available router to destination
[01:05:26 AM] Destination unreachable; nested exception is:
java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.1 500 Server Error'; No available router to destination
If right click the simple JSF page and run directly will start the wl server and seems not to deploy the demo app. the log as below:
Starting WLS with line:
C:\PROGRA~1\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\PROGRA~1\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy "-Djavax.net.ssl.trustStore=C:\Program Files\Oracle\Middle Ware\wlserver_10.3\server\lib\DemoTrust.jks" -Dhttp.proxyHost=www-proxy.cn.oracle.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts= -Dhttps.proxyHost=www-proxy.cn.oracle.com -Dhttps.proxyPort=80 -Dhttps.nonProxyHosts= -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da -Dplatform.home=C:\PROGRA~1\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\PROGRA~1\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\PROGRA~1\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Ddomain.home=C:\DOCUME~1\gerry\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1 -Dcommon.components.home=C:\PROGRA~1\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\PROGRA~1\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=C:\DOCUME~1\gerry\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1 -Doracle.server.config.dir=C:\DOCUME~1\gerry\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.security.jps.config=C:\DOCUME~1\gerry\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\DOCUME~1\gerry\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\DOCUME~1\gerry\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=C:\PROGRA~1\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\PROGRA~1\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\DOCUME~1\gerry\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\oracle\store\gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\PROGRA~1\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\PROGRA~1\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
<2010-10-15 上午01时13分40秒 VET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 16.0-b13 from Sun Microsystems Inc.>
<2010-10-15 上午01时13分41秒 VET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<2010-10-15 上午01时13分42秒 VET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<2010-10-15 上午01时13分42秒 VET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<2010-10-15 上午01时13分42秒 VET> <Notice> <LoggingService> <BEA-320400> <The log file C:\Documents and Settings\gerry\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<2010-10-15 上午01时13分42秒 VET> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Documents and Settings\gerry\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00020. Log messages will continue to be logged in C:\Documents and Settings\gerry\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
<2010-10-15 上午01时13分42秒 VET> <Notice> <Log Management> <BEA-170019> <The server log file C:\Documents and Settings\gerry\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<2010-10-15 上午01时13分44秒 VET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<2010-10-15 上午01时13分48秒 VET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<2010-10-15 上午01时13分48秒 VET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<2010-10-15 上午01时13分51秒 VET> <Notice> <LoggingService> <BEA-320400> <The log file C:\Documents and Settings\gerry\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<2010-10-15 上午01时13分51秒 VET> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Documents and Settings\gerry\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00020. Log messages will continue to be logged in C:\Documents and Settings\gerry\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
<2010-10-15 上午01时13分51秒 VET> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<2010-10-15 上午01时13分52秒 VET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<2010-10-15 上午01时13分52秒 VET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<2010-10-15 上午01时13分52秒 VET> <Warning> <Server> <BEA-002611> <Hostname "gerry-cn.peoplesoft.com", maps to multiple IP addresses: 10.182.105.125, 192.168.149.1, 192.168.126.1>
<2010-10-15 上午01时13分52秒 VET> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<2010-10-15 上午01时13分52秒 VET> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.126.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<2010-10-15 上午01时13分52秒 VET> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 10.182.105.125:7101 for protocols iiop, t3, ldap, snmp, http.>
<2010-10-15 上午01时13分52秒 VET> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.149.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<2010-10-15 上午01时13分52秒 VET> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<2010-10-15 上午01时13分52秒 VET> <Warning> <Server> <BEA-002611> <Hostname "GERRY-CN", maps to multiple IP addresses: 10.182.105.125, 192.168.149.1, 192.168.126.1>
<2010-10-15 上午01时13分52秒 VET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<2010-10-15 上午01时13分52秒 VET> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
as normal there would have a URL link displayed in the weblogic log, is that right? any one can give tips?Looks like you have a proxy configured, and that proxy (of course) doesn't support routing to 127.0.0.1
[01:05:26 AM] t3://127.0.0.1:7101: Destination unreachable; nested exception is:
java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.1 500 Server Error'; No available router to destinationUnset your proxy (Tools->Preferences->Web Browser & Proxy)
John -
Strange web service deployment error weblogic 10.3.1 fro Jdev 11.1.1.1
We migrate an application from JDev 11.1.1.0 to 11.1.1.1.
Then following deployment error start to occurs.
it says user defined filter and webservices.
But there is no such a filter.
And here is no web service modul inside of our projects.
Thansks...
<Jul 13, 2009 8:30:20 AM EEST> <Warning> <HTTP> <BEA-101162> <User defined liste
ner weblogic.wsee.deploy.ServletDeployListener failed: weblogic.wsee.deploy.WSEE
ServletEndpointException: Deployment Error. Failed to prepare WebService wsse m
odule: Evrak_ViewController_webapp1.war.
weblogic.wsee.deploy.WSEEServletEndpointException: Deployment Error. Failed to
prepare WebService wsse module: Evrak_ViewController_webapp1.war
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDep
loyListener.java:29)
at weblogic.servlet.internal.EventsManager$FireContextPreparedAction.run
(EventsManager.java:503)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
121)
at weblogic.servlet.internal.EventsManager.notifyContextPreparedEvent(Ev
entsManager.java:162)
Truncated. see log file for complete stacktrace
weblogic.wsee.ws.WsException: Error encountered during prepare phase of deployin
g WebService module 'Evrak_ViewController_webapp1.war'. When processing WebServi
ce module 'Evrak_ViewController_webapp1.war'. Can't find wsdl /wsdls/wsat.wsdl
at weblogic.wsee.deploy.WSEEModule.prepare(WSEEModule.java:132)
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDep
loyListener.java:26)
at weblogic.servlet.internal.EventsManager$FireContextPreparedAction.run
(EventsManager.java:503)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
121)
Truncated. see log file for complete stacktrace
weblogic.wsee.ws.WsException: When processing WebService module 'Evrak_ViewContr
oller_webapp1.war'. Can't find wsdl /wsdls/wsat.wsdl
at weblogic.wsee.deploy.WSEEWebModule.loadWsdlDefinitions(WSEEWebModule.
java:159)
at weblogic.wsee.deploy.WSEEModule.loadWsdl(WSEEModule.java:319)
at weblogic.wsee.deploy.WSEEAnnotationProcessor.isWsdlHasPolicy(WSEEAnno
tationProcessor.java:312)
at weblogic.wsee.deploy.WSEEAnnotationProcessor.process(WSEEAnnotationPr
ocessor.java:91)
at weblogic.wsee.deploy.WSEEAnnotationProcessor.process(WSEEAnnotationPr
ocessor.java:51)
Truncated. see log file for complete stacktrace
>
<Jul 13, 2009 8:30:22 AM EEST> <Error> <Deployer> <BEA-149265> <Failure occurred
in the execution of deployment request with ID '1247462999662' for task '19'. E
rror is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:368)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedM
oduleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:37)
Truncated. see log file for complete stacktrace
weblogic.wsee.ws.WsException: When processing WebService module 'Evrak_ViewContr
oller_webapp1.war'. Can't find wsdl /wsdls/wsat.wsdl
at weblogic.wsee.deploy.WSEEWebModule.loadWsdlDefinitions(WSEEWebModule.
java:159)
at weblogic.wsee.deploy.WSEEModule.loadWsdl(WSEEModule.java:319)
at weblogic.wsee.deploy.WSEEAnnotationProcessor.isWsdlHasPolicy(WSEEAnno
tationProcessor.java:312)
at weblogic.wsee.deploy.WSEEAnnotationProcessor.process(WSEEAnnotationPr
ocessor.java:91)
at weblogic.wsee.deploy.WSEEAnnotationProcessor.process(WSEEAnnotationPr
ocessor.java:51)
Truncated. see log file for complete stacktrace
>We recreate deployment profile from scrath and problem is solved.
But there seem like an upgrade bug for deployment profiles.
Maybe you are looking for
-
hai every body when i posting accounting doc manually by F-28 t code the following error is coming "Tax-relevant accounts not defined in this area; please correct Message no. F5536" can anybody send me the steps what i have to do thank you
-
Free issue of materials from customers .....
Experts pls help. In one of our client projects, client receives the Free issue of materials from customers and consumes the same in the projcet and deliveries the end product. How treat the free issue of materials in FICO , MM , SD,PM modules during
-
Hi All, I am having trouble testing a new folio on the desktop of one of my students' computers. I have double checked her files are all setup properly. I checked her articles and her folio too. Everything is set up the way it should be. We can test
-
I have been trying to implement the Multiple Non-Destructive Filters Mode sample at http://labs.adobe.com/technologies/spry/samples/data_region/MultipleFiltersModeSample.html but just cannot get it to work, although the data shows and is sort of sort
-
Radius Health Check - Cisco ISE
I have one Cisco ISE setup with AD authentication. I want to configure radius helth check how it can be confiured on switches. Best Regards,