Error when deploy application on weblogic's console(weblogic 10 on AIX)

?:|
After successfully start weblogic,I access console and select "Deployment".While I click "Finish" after choose the application named "ls_app", an error appears as follow.
- Messages
The deployment has not been installed.
java.lang.NullPointerException
The log information from weblogic is as follow::-(
Failures were detected while initiating distribute task for application 'ls_app'. Error is: ''
WARN [PageFlowRequestProcessor] Struts module is configured to use com.bea.console.internal.ConsolePageFlowRequestProcessor as the request processor, but the <controller> element does not contain a <set-property> for "controllerClass".
Page Flow actions in this module may not be handled correctly.
Please help on this issue.Thanks!!:-)

I have in log:
2009.26.3 20:12:52 oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImp
l setLifecycleContextBuilder
WARNING: ADFc: Replacing the ADF Page Lifecycle implementation with 'oracle.adfi
nternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
2009.26.3 20:12:52 oracle.adfinternal.controller.util.model.AdfmInterface initia
lize
INFO: ADFc: BindingContext is present, using ADFm APIs for DataControlFrames.
2009.26.3 20:12:52 oracle.adfinternal.controller.metadata.provider.MdsMetadataRe
sourceProvider <init>
INFO: ADFc: Controller caching of MDS metadata resources ENABLED.
2009.26.3 20:12:52 oracle.adf.controller.internal.metadata.MetadataService$Boots
trap add
INFO: ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
2009.26.3 20:12:54 oracle.adf.share.security.providers.jps.CSFCredentialStore fe
tchCredential
WARNING: Unable to locate the credential for key AUGI in D:\bea\user_projects\do
mains\base_domain\config\oracle.
2009.26.3 20:12:54 oracle.adf.share.jndi.ReferenceStoreHelper throwPartialResult
Exception
WARNING: Incomplete connection information
Edited by: Debuger on Mar 26, 2009 11:18 AM

Similar Messages

Error when deploying application in wiblogic WebLogic Server Version: 10.3.

hi when doing deployment in my WebLogic Server Version: 10.3.6.0 am geitng this error
weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false], [Extension-Name: oracle.jsp.next, exact-match: false], [Extension-Name: oracle.webcenter.framework, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.webcenter.skin, Specification-Version: 11.1.1, exact-match: false].
how can i install this libraires in weblogic i have install this in jdeveloper by help->check updatesEdited by: adf009 on 2013/01/29 11:47 AM

Solution:
open the weblogic server console, in home page--> click the Deployments-->Select the adf.oracle.domain-->select target tab-->Click Lock & Edit-->
select the servers (admin and managed Server) and save.--> click Activate All changes.
Redeploy the application.

Ejb-ref error when deploying a previously working ear on weblogic 8.1

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

Ejb-ref errore when deploying a previously working ear on weblogic 8.1

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
Thanks in advance!
Greets,
Luca
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

The issue is that WLS 6.1 didn't really support ejb-links properly. An
ejb-link should allow you to link a webapp or an ejb to another EJB
without requiring additional information or a global JNDI name on the
target EJB.
WLS 8.1 is following your ejb-link and telling you there's not enough
information.
You have 2 options:
1) Remove the <ejb-link>...</ejb-link> from your web.xml. You'll be
using just an ejb-reference at that point, but you've already included
the necessary information in the weblogic.xml that we can locate the EJB
via its global jndi-name
or
2) Change the ejb-link to be
<ejb-link>CustomMessaginBrick.jar#CustomMessagingBrick</ejb-link>
If you wanted to, you could then remove the reference info from the
weblogic.xml
-- Rob
luca wrote:
when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
Thanks in advance!
Greets,
Luca
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

Error when deploying application in WebLogic6.1SP1

Hi,
I am trying to deploy an application from the console on Web Logic 6.1 SP1 and
keep getting the attached error. I un-installed Web Logic several times to start
from scratch and yet the error($Proxy66) won't go away. Could anyone please help?
Details of $Proxy66:
java.lang.ClassCastException: $Proxy66
     at weblogic.management.mbeans.custom.Application.initializeMBean(Application.java:859)
     at weblogic.management.mbeans.custom.Application.initializeMBeans(Application.java:824)
     at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:525)
     at weblogic.management.mbeans.custom.Application.load(Application.java:384)
     at weblogic.management.mbeans.custom.Application.load(Application.java:223)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
     at $Proxy65.load(Unknown Source)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:183)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.DeploymentException: mydomain:Name=SWApplication,Type=Application
- with nested exception:
[java.lang.ClassCastException: $Proxy66]
     at weblogic.management.mbeans.custom.Application.initializeMBeans(Application.java:844)
     at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:525)
     at weblogic.management.mbeans.custom.Application.load(Application.java:384)
     at weblogic.management.mbeans.custom.Application.load(Application.java:223)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
     at $Proxy65.load(Unknown Source)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:183)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Console Release Build6.1.1.0Server Release Build6.1.1.0Server BuildWebLogic Server
6.1 SP1 09/18/2001 14:28:44 #138716 All Server Product VersionsWebLogic Server
6.1 SP1 09/18/2001 14:28:44 #138716 WebLogic XML Module 6.1 SP1 09/18/2001
14:43:02 #138716

Hi.
Please open a case with support on this issue.
Thanks,
Michael
Gopal Iyer wrote:
Hi,
I am trying to deploy an application from the console on Web Logic 6.1 SP1 and
keep getting the attached error. I un-installed Web Logic several times to start
from scratch and yet the error($Proxy66) won't go away. Could anyone please help?
Details of $Proxy66:
java.lang.ClassCastException: $Proxy66
at weblogic.management.mbeans.custom.Application.initializeMBean(Application.java:859)
at weblogic.management.mbeans.custom.Application.initializeMBeans(Application.java:824)
at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:525)
at weblogic.management.mbeans.custom.Application.load(Application.java:384)
at weblogic.management.mbeans.custom.Application.load(Application.java:223)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy65.load(Unknown Source)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:183)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.DeploymentException: mydomain:Name=SWApplication,Type=Application
- with nested exception:
[java.lang.ClassCastException: $Proxy66]
at weblogic.management.mbeans.custom.Application.initializeMBeans(Application.java:844)
at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:525)
at weblogic.management.mbeans.custom.Application.load(Application.java:384)
at weblogic.management.mbeans.custom.Application.load(Application.java:223)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy65.load(Unknown Source)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:183)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Console Release Build6.1.1.0Server Release Build6.1.1.0Server BuildWebLogic Server
6.1 SP1 09/18/2001 14:28:44 #138716 All Server Product VersionsWebLogic Server
6.1 SP1 09/18/2001 14:28:44 #138716 WebLogic XML Module 6.1 SP1 09/18/2001
14:43:02 #138716--
Michael Young
Developer Relations Engineer
BEA Support

Errors when deploying application to a remote WebLogic server using Eclipse

I'm using Eclipse with OEPE for WebLogic 10.3.5 on linux and running a weblogic server versioned the same.
I've created a new EAR which combined several EARs that I had, and deployed it on my local server using the 'servers' tab in Eclipse. It went well.
When I tried to deploy the EAR into my remote server, I got the exception:
Application archive not found : myworkspace/.metadata/.plugins/org.eclipse.core.resources/.projects/MyEAR/beadep/remote_weblogic/MyEAR/split_src.ear
This also happens when trying to deploy the EAR to a server that runs on my computer but configured as 'remote' in Eclipse. This does not happen for any other application of mine.
Next thing I tried is to update my Eclipse OEPE and server to 12.1.1, so I've downloaded the two, installed them both as new, and now when I'm looking for remote servers in the Eclipse, instead of writing the server status (republish/synchronized) it writes:
User: myuser, failed to be authenticated
I'm lost. How can I deploy my application with Eclipse OEPE to a remote weblogic server?
Edited by: wafwaf on 02:03 02/02/2012

I'm using Eclipse with OEPE for WebLogic 10.3.5 on linux and running a weblogic server versioned the same.
I've created a new EAR which combined several EARs that I had, and deployed it on my local server using the 'servers' tab in Eclipse. It went well.
When I tried to deploy the EAR into my remote server, I got the exception:
Application archive not found : myworkspace/.metadata/.plugins/org.eclipse.core.resources/.projects/MyEAR/beadep/remote_weblogic/MyEAR/split_src.ear
This also happens when trying to deploy the EAR to a server that runs on my computer but configured as 'remote' in Eclipse. This does not happen for any other application of mine.
Next thing I tried is to update my Eclipse OEPE and server to 12.1.1, so I've downloaded the two, installed them both as new, and now when I'm looking for remote servers in the Eclipse, instead of writing the server status (republish/synchronized) it writes:
User: myuser, failed to be authenticated
I'm lost. How can I deploy my application with Eclipse OEPE to a remote weblogic server?
Edited by: wafwaf on 02:03 02/02/2012

Error when deploying application in weblogic 10.0

weblogic.application.ModuleException: [HTTP:101216]Servlet: "cds-service" failed to preload on startup in Web application: "/cds-wsclient".
          org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hdr2PersistenceManager' defined in class path resource [gov/va/med/cds/config/hdr2PersistenceContext.xml]: Cannot resolve reference to bean 'hdr2SessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hdr2SessionFactory' defined in class path resource [gov/va/med/cds/config/hdr2PersistenceContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: VitalSignObservationEvent.patient.date, VitalSignObservationEvent.patient, IntoleranceCondition.patient.date, IntoleranceCondition.patient
          Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hdr2SessionFactory' defined in class path resource [gov/va/med/cds/config/hdr2PersistenceContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: VitalSignObservationEvent.patient.date, VitalSignObservationEvent.patient, IntoleranceCondition.patient.date, IntoleranceCondition.patient
          Caused by: org.hibernate.HibernateException: Errors in named queries: VitalSignObservationEvent.patient.date, VitalSignObservationEvent.patient, IntoleranceCondition.patient.date, IntoleranceCondition.patient
               at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:339)
               at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1176)
               at org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:805)
               at org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:745)
               at org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet(AbstractSessionFactoryBean.java:134)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1202)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1172)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:428)
               at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
               at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
               at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
               at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
               at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:261)
               at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:109)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1100)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:862)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:424)
               at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
               at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
               at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
               at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
               at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:287)
               at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
               at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:330)
               at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:266)
               at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:236)
               at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:126)
               at javax.servlet.GenericServlet.init(GenericServlet.java:241)
               at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
               at weblogic.security.service.SecurityManager.runAs(Unknown Source)
               at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
               at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
               at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
               at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
               at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
               at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
               at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
               at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
               at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
               at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
               at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
               at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
               at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
               at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
               at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
               at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
               at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
               at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
               at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
               at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
               at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
               at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
               at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
               at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
               at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
               at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
               at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
               at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
               at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
               at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
               at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
               at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
               at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:950)
               at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
               at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
               at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
               at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
               at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
               at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
               at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
               at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
               at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
               at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
               at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
               at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
               at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
               at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
               at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
               at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
               at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
               at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
               at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
               at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
               at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
               at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
               at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

I was trying to deploy a Hibernate based application on WL 10.0 . I was getting this exception.
          your help would be greatly appreciated.

OutOfMemory Error when deploying application in WL10

I've got an application that I am able to deploy from the WL9 console without hickups. But when I try to deploy it through WL10 console, it hangs and eventualy throws an OutOfMemory error. I've tried doubling the memory I allocate to WL but this does nothing. I can manually edit the config.xml to deploy the application and it works but I am unable to expand or view it from the console without getting the same OutOfMemory error. Any ideas?

I ran a profiler on wl when getting the OutOfMemory error and the class weblogic.j2ee.descriptor.wl.WeblogicEjbJarBeanDConfig seems to be the culprit. Does WL10 load EJBs differently into memory than WL9?
Also, I added the -verbosegc option to my vm args and it looks like the eden space isnt getting released. Not sure what that is supposed to tell me...
1318.268: [Full GC {Heap before gc invocations=166:
def new generation   total 56576K, used 56576K [0xccc00000, 0xd04e0000, 0xd04e0000)
eden space 54912K, 100% used [0xccc00000, 0xd01a0000, 0xd01a0000)
from space 1664K, 100% used [0xd01a0000, 0xd0340000, 0xd0340000)
to   space 1664K,   0% used [0xd0340000, 0xd0340000, 0xd04e0000)
tenured generation   total 466048K, used 466048K [0xd04e0000, 0xecc00000, 0xecc00000)
   the space 466048K, 100% used [0xd04e0000, 0xecc00000, 0xecc00000, 0xecc00000)
compacting perm gen total 83456K, used 83263K [0xecc00000, 0xf1d80000, 0xf8c00000)
   the space 83456K, 99% used [0xecc00000, 0xf1d4fdf0, 0xf1d4fe00, 0xf1d80000)
No shared spaces configured.
1318.268: [Tenured: 466048K->466048K(466048K), 6.4704001 secs] 522624K->513170K(522624K), [Perm : 83263K->83263K(83456K)]Heap after gc invocations=167:
def new generation total 56576K, used 47122K [0xccc00000, 0xd04e0000, 0xd04e0000)
eden space 54912K, 85% used [0xccc00000, 0xcfa04970, 0xd01a0000)
from space 1664K, 0% used [0xd01a0000, 0xd01a0000, 0xd0340000)
to space 1664K, 0% used [0xd0340000, 0xd0340000, 0xd04e0000)
tenured generation total 466048K, used 466048K [0xd04e0000, 0xecc00000, 0xecc00000)
the space 466048K, 100% used [0xd04e0000, 0xecc00000, 0xecc00000, 0xecc00000)
compacting perm gen total 83456K, used 83263K [0xecc00000, 0xf1d80000, 0xf8c00000)
the space 83456K, 99% used [0xecc00000, 0xf1d4fdf0, 0xf1d4fe00, 0xf1d80000)
No shared spaces configured.
Edited by kadire at 06/20/2008 7:41 AM

Error when deploying application

Hello!
We are trying to migrate our application from Tomcat 5.5 to WebLogic Server and we are getting some problems.
When we deploy the application we are getting the following error:
####<Sep 11, 2008 11:51:22 AM WEST> <Error> <HTTP> <VMWEBLOGIC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1221130282164> <BEA-101216> <Servlet: "flashgateway.controller.GatewayServlet" failed to preload on startup in Web application: "application.war".flashgateway.GatewayException: [Flash Remoting MX]-> Unable to load configuration. Reason: null
Web.xml inside WEB-INF folder has the following lines:
<servlet>
     <servlet-name>flashgateway.controller.GatewayServlet</servlet-name>
     <display-name>Flash Remoting Gateway Servlet</display-name>
     <description>Servlet-based plugin to Flash Remoting</description>
     <servlet-class>flashgateway.controller.GatewayServlet</servlet-class>
          <init-param>
                    <param-name>gateway.configuration.file</param-name>
               <param-value>/WEB-INF/gateway-config.xml</param-value>
               </init-param>
          <init-param>
          <param-name>whitelist.configuration.file</param-name>
          <param-value>/WEB-INF/gateway-config.xml</param-value>
          </init-param>
          <init-param>
          <param-name>whitelist.parent.node</param-name>
          <param-value>gateway-config</param-value>
          </init-param>
     <load-on-startup>2</load-on-startup>
     </servlet>
It's our first contact with WebLogic and maybe we are forgetting someting important. Could you help us to find the problem and the best way to solve it?
Thanks a lot for your help
AC

You do not need to clear metadata (It will also delete all data and journals). You shoud do your required task in 2 stages.
Assuming you have to make a base account a parent account with some new children.
1. Extract data for that base level account (say BS100100) for all entity, scenario, period combination and save the file(s).
2. Delete account BS100100 from metadata and deploy the application (1st time deployment)
3. Now create an account BS100100 in metadata and also create required children (Say BS100101 and BS100102)
4. Deploy the application (2nd time deployment)
5. Take your data back up and do a find replace for one of the new base account (BS100100 -> BS100101)
6. Load the data and consolidate.
Hope this helps....

Error when deploying an ear file on the weblogic 6.0 admin server

####<Feb 6, 2001 8:48:27 AM EST> <Error> <Management> <wSDWAPW95A452> <petstoreServer>
<Application Manager Thread> <> <> <141004> <IOException opening application petstore:Name=s3,Type=Application,
loading from path C:\bea\wlserver6.0\config\petstore\applications\s3.ear>
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:110)
at java.util.jar.JarFile.<init>(JarFile.java:115)
at java.util.jar.JarFile.<init>(JarFile.java:82)
at weblogic.utils.jars.VirtualJarFile.<init>(VirtualJarFile.java:24)
at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:229)
at weblogic.management.mbeans.custom.Application.load(Application.java:205)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:559)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:545)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:431)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:172)
at $Proxy7.load(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:461)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:379)
at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:151)
at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:642)

####<Feb 6, 2001 8:48:27 AM EST> <Error> <Management> <wSDWAPW95A452> <petstoreServer>
<Application Manager Thread> <> <> <141004> <IOException opening application petstore:Name=s3,Type=Application,
loading from path C:\bea\wlserver6.0\config\petstore\applications\s3.ear>
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:110)
at java.util.jar.JarFile.<init>(JarFile.java:115)
at java.util.jar.JarFile.<init>(JarFile.java:82)
at weblogic.utils.jars.VirtualJarFile.<init>(VirtualJarFile.java:24)
at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:229)
at weblogic.management.mbeans.custom.Application.load(Application.java:205)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:559)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:545)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:431)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:172)
at $Proxy7.load(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:461)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:379)
at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:151)
at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:642)

Getting Error when deploying the WD application

hi all,
Anybody have idea about , what is the reason for the following error. Till now it is working properly. suddenly it is giving the following error when deploying the application.
2.4.2007 13:17:36 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[004]Deployment aborted
Settings
SDM host : eimkopdvs4
SDM port : 50118
URL to deploy : file:/C:/WINDOWS/TEMP/temp2898TestWebDynproProj.ear
Result
=> deployment aborted : file:/C:/WINDOWS/TEMP/temp2898TestWebDynproProj.ear
Aborted: development component 'TestWebDynproProj'/'local'/'LOKAL'/'0.2007.04.02.13.17.28'/'0':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [EIMKOPDVS4] with user name: [Administrator]                     Check your login information.                     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)
     at javax.naming.InitialContext.<init>(InitialContext.java:195)
     at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)
     at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51)
     at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:45)
     at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:32)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerImpl.java:173)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:167)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
     at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
     at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
     at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
     at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
     at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:120)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:89)
     at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
     at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
     at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
     at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
     at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
     at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
     at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
     at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
     at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
     at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
     at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
     at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
     ... 37 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/10.4.71.36,port=50104,localport=3057]
     at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:420)
     ... 1 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment exception : The deployment of at least one item aborted

Hi,
Check if the server is running. If so, try restarting it and then retry.

Error while deploying applications in ALBPM 6.0 ! Please help.

Hi,
We are testing the migration from ALBPM 5.7 to 6.0.4. We followed the steps of the upgrade guide from 5.7 to 6.0. However after migrating and deploying our existing 5.7 workflow projects using process administrator to 6.0.4 , we see the following exception in the logs. Has anyone encountered this before. Any possible suggestions on how to resolve this.
Main: Message: Unexpected Exception....
[     (cont)     ] Main: Exception message in the remote host: class java.lang.RuntimeException: Error while deploying application [ear=Fuego-WebLogic-Deployer/fuego_webapp_expanded/07-papiws-albpmdirectoryservicedatasource.ear, name=07-papiws-ALBPMDirectoryServiceDataSource.ear]......
Main: Caused by: java.sql.SQLException: Invalid column type
[     (cont)     ] Main: at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
[     (cont)     ] Main: at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
[     (cont)     ] Main: at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
(cont) ] Main: at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
[     (cont)     ] Main: at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
[     (cont)     ] Main: at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
[     (cont)     ] Main: ... 2 more
[     (cont)     ] Main: Caused by: java.lang.RuntimeException: Critical Error.
[     (cont)     ] Main: Detail:
[     (cont)     ] Main: Exception [java.sql.SQLException: Invalid column type].
[     (cont)     ] Main: Caused by: Invalid column type
[     (cont)     ] Main: fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: Invalid column type].
[     (cont)     ] Main: at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
[     (cont)     ] Main: at fuego.directory.provider.jdbc.oracle.OraclePersistenceManager.mapSQLException(OraclePersistenceManager.java:145)
[     (cont)     ] Main: at fuego.directory.provider.jdbc.datadirect.oracle.DataDirectOraclePersistenceManager.mapSQLException(DataDirectOraclePersistenceManager.java:51)
Any help would be appreciated.

I am getting the same error...when I created engine and directory service, i got a sql script which I executed in engine and directory service schema..
worked fine...is there any i need to do extra...i am getting this error....need to solve this out ASAP..Gurus please help !!!
Edited by: user12053514 on Oct 15, 2009 6:31 AM

Error while deploying application on portal domain

Hi All,
I am getting following error while deploying application on portal domain :( :( Not sure what I am missing.......
Anyone has any idea on this???
<Oct 6, 2010 7:49:03 AM EDT> <Warning> <com.bea.wlw.netui.pageflow.internal.WebLogicURLTemplateFactory> <BEA-000000> <In webapp <Workshop Application>, the url template <http://{url:domain}:{url:port}/{url:path}?{url:queryString}{url:currentPage}> uses the {url:port} token. The system may not pick up the correct ports if you are using a proxy server. Consider hardcoding the ports in a production environment.>
<Oct 6, 2010 7:49:05 AM EDT> <Error> <com.bea.p13n.util.jdbc.internal.JdbcSequencer> <BEA-000000> <Cannot allocate sequence block:
java.sql.SQLException: Cannot call commit when using distributed transactions
at weblogic.jdbc.wrapper.JTAConnection.commit(JTAConnection.java:349)
at com.bea.p13n.util.jdbc.internal.JdbcSequencer.allocateSequenceBlockNewTx(JdbcSequencer.java:626)
at com.bea.p13n.util.jdbc.internal.JdbcSequencer.getNext(JdbcSequencer.java:456)
at com.bea.netuix.application.manager.persistence.jdbc.MarkupDefinitionDelegate.createMarkupDefinition(MarkupDefinitionDelegate.java:785)
at com.bea.netuix.application.manager.persistence.jdbc.MarkupDefinitionManagerImpl.createMarkupDefinition(MarkupDefinitionManagerImpl.java:161)
Truncated. see log file for complete stacktrace
>
<Oct 6, 2010 7:49:05 AM EDT> <Error> <netuix> <BEA-423147> <Exception [javax.transaction.TransactionRolledbackException: EJB Exception: : javax.ejb.EJBException: SQL Error while trying to createMarkupDefinition: SQL [insert into PF_MARKUP_DEFINITION ( MARKUP_DEFINITION_ID, MARKUP_NAME, MARKUP_TYPE, WEBAPP_NAME, MARKUP_FILE) values (?,?,?,?,?)] database error code [0] SQL state [null]. Possible markup duplication of [
MarkupDefinition:
webAppName = plassPortalWeb
type = Menu
name = multiLevelMenu
file = /framework/markup/menu/multilevel.menu
beginXml = <netuix:multiLevelMenu $(markupType) $(markupName)>
endXml = </netuix:multiLevelMenu>
MarkupDefinitionId = null].; nested exception is: java.sql.SQLException: Cannot call commit when using distributed transactions
java.sql.SQLException: Cannot call commit when using distributed transactions
at weblogic.jdbc.wrapper.JTAConnection.commit(JTAConnection.java:349)
at com.bea.p13n.util.jdbc.internal.JdbcSequencer.allocateSequenceBlockNewTx(JdbcSequencer.java:626)
at com.bea.p13n.util.jdbc.internal.JdbcSequencer.getNext(JdbcSequencer.java:456)
at com.bea.netuix.application.manager.persistence.jdbc.MarkupDefinitionDelegate.createMarkupDefinition(MarkupDefinitionDelegate.java:785)
at com.bea.netuix.application.manager.persistence.jdbc.MarkupDefinitionManagerImpl.createMarkupDefinition(MarkupDefinitionManagerImpl.java:161)
at com.bea.netuix.application.manager.persistence.jdbc.MarkupDefinitionManager_twpn9c_EOImpl.createMarkupDefinition(MarkupDefinitionManager_twpn9c_EOImpl.java:138)
at com.bea.netuix.servlets.repository.MenuFilePersistenceManager.onNewFile(MenuFilePersistenceManager.java:160)
at com.bea.netuix.servlets.repository.MenuFilePersistenceManager.createUpdateMenuDefinitions(MenuFilePersistenceManager.java:267)
at com.bea.netuix.servlets.repository.MenuFilePersistenceManager.startupSync(MenuFilePersistenceManager.java:529)
at com.bea.netuix.servlets.repository.AbstractFilePersistenceManager$StartupSync.run(AbstractFilePersistenceManager.java:155)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.netuix.servlets.repository.AbstractFilePersistenceManager.startup(AbstractFilePersistenceManager.java:97)
at com.bea.netuix.servlets.repository.MenuFilePersistenceManager.onNewFiles(MenuFilePersistenceManager.java:228)
at com.bea.netuix.poller.FrameworkPoller.newFiles(FrameworkPoller.java:256)
at com.bea.netuix.poller.NetuixFilePoller.start(NetuixFilePoller.java:172)
at com.bea.netuix.servlets.manager.PortalServlet.reinitInternal(PortalServlet.java:390)
at com.bea.netuix.servlets.manager.PortalServlet.initInternal(PortalServlet.java:261)
at com.bea.netuix.servlets.manager.PortalServlet.access$100(PortalServlet.java:125)

Hello Everybody,
I solved this error by myself as follows:
So, what I did was; I started the RemoteGui.bat (C:\usr\sap\J2E\JC00\SDM\program) and from the Undeployment tab, I selected mainapp01 and com.sap.engine.docs.examples.
The reason I undeployed the above applications was because when I was trying to deploy the mainapp01 application, it gave an error saying that : Cannot deploy application pcbp.com/mainapp01.. Reason: Application alias [/] for application [pcbp.com/mainapp01] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.engine.docs.examples .
And, then I restarted the J2EE engine and from the SAP Netweaver Developer Studio, I again deployed the mainapp01 application on the local J2EE engine and it was deployed successfully.
Oct 10, 2006 9:45:30 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[002]Finished Deployment
Settings
SDM host : RPIKOER
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/krunalra/LOCALS1/Temp/temp9270pcbp.com~mainapp01.ear
Result
=> successfully deployed : file:/C:/DOCUME1/krunalra/LOCALS1/Temp/temp9270pcbp.com~mainapp01.ear
Thank You
With Regards,
Krunal Rana.

Invalid change to class error when deploying EJB

We have EJBs that were built by Webgain Visual Cafe and successfully deploy
to WLS 5.1. We then use the WLE EJB Deployer Tool to build WLE container
classes and deploy the same EJBs in WLE 5.1.
One EJB does not deploy in WLE. The ULOG error message is:
133929.EA-LAWSTUC!JavaServer.517: main: IJENGINE_CAT:150: ERROR: Invalid
change to class service.Request
133929.EA-LAWSTUC!JavaServer.517: main: EJB_CAT:29: ERROR: While deploying
jar ServiceEJB : com.beasys.weblogic.classloader.RedeploymentException:
ERROR: Invalid change to class service.Request
133929.EA-LAWSTUC!JavaServer.517: Finalizer: IJENGINE_CAT:152: INFO: Closing
jar C:\aj\ServiceEJB_WLE.jar
Does anyone know what can cause an "invalid change to class" error when
deploying to WLE 5.1? Especially since the EJB deploys successfully in
WLS.
Carl Lawstuen

Reason: database keeps a reference of the class in JAVA$CLASS$MD5$TABLE table. This table keeps a refrence to all java classes loaded in database, and is present in each schema you deploy classes. That's the reason why if you change the application module name, you can load this classes. It instead keeps a reference if you use DROP JAVA CLASS command to drop a java class from de database. Use DROP JAVA command to clear the reference of the dropped classes when dropping it.
You can see this table as a class dictionary of the database, and you don't have to handle this records manually.

Exception when deploying a JSR 286 portlet into WebLogic+WebCenter

I get the following exception when deploying a JSR 286 portlet into WebLogic:
"<19-ene-2010 13H32' CET> <Error> <oracle.portlet.server.containerimpl.PortletApplicationImpl> <BEA-000000> <Error al procesar el archivo "/WEB-INF/portlet.xml" en la lÝnea 6 columna 68.
org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'portlet-app'"
The error message is in spanish. It means:
"Error processing the file "/WEB-INF/portlet.xml at line 6 column 68"
The portlet.xml of my portlet seems to be correct and I've deployed it in other portal servers. So I don't understand the error message.
This is the portlet.xml of my portlet (eclipse XML validator said it was a valid XML)
{code}
<?xml version="1.0" encoding="UTF-8"?>
<portlet-app version="2.0"
xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd
http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd"
xmlns:dnd="http://www.denodo.com/widget/portlet/portletjsr286">
<portlet>
<description>Test Inter Portlet Communication (JSR286)</description>
<portlet-name>Test IPC</portlet-name>
<display-name>Test IPC</display-name>
<portlet-class>com.denodo.ipc.TestIPCPortlet</portlet-class>
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>VIEW</portlet-mode>
</supports>
<supported-locale>en</supported-locale>
<resource-bundle>PortletMessages</resource-bundle>
<portlet-info>
<title>Test IPC</title>
<short-title>Test IPC</short-title>
<keywords>Test IPC,Denodo</keywords>
</portlet-info>
</portlet>
</portlet-app>
{code}
*How do I deploy my portlet*
<li> I convert my portlet into to a WSRP portlet by executing
+java -jar wsrp-predeploy.jar source EAR target EAR+
as explained in http://download.oracle.com/docs/cd/E12839_01/webcenter.1111/e12405/wcadm_portlet_prod.htm#CHDECJHI)
</li>
<li>I try to deploy it into WebLogic with the WebLogic Console and I get this exception.
</li>
*My Environment*
WebCenter Suite (11.1.1.2.0) + WebLogic Server (10.3.2) downloaded from the oracle.com. Default configuration
S.O: Windows XP SP3
*Thanks in advance for your time.*

Hi,
Are you including the Toplink jars in your EAR?
-Patrick

Error when deploy application on weblogic's console(weblogic 10 on AIX)

Similar Messages

Maybe you are looking for