Error when deploying an EAR

Hi,
I think this is a common error for newbes. When I deploy an EAR I get the following,
[24-dic-2009 12:42:35] Inicio de Application Deployer para MyFirstOC4JApp.
[24-dic-2009 12:42:35] Copiar archivado en C:\oc4j\j2ee\home\applications\MyFirstOC4JApp.ear
[24-dic-2009 12:42:35] Inicio de la inicialización de C:\oc4j\j2ee\home\applications\MyFirstOC4JApp.ear...
[24-dic-2009 12:42:35] Desempaquetando MyFirstOC4JApp.ear
[24-dic-2009 12:42:35] Desempaquetado listo MyFirstOC4JApp.ear
[24-dic-2009 12:42:35] Desempaquetando EclipseLinkWeb.war
[24-dic-2009 12:42:35] Desempaquetado listo EclipseLinkWeb.war
[24-dic-2009 12:42:35] Fin de la inicialización de C:\oc4j\j2ee\home\applications\MyFirstOC4JApp.ear...
[24-dic-2009 12:42:35] Iniciando la aplicación: MyFirstOC4JApp
[24-dic-2009 12:42:35] Inicializando ClassLoaders
[24-dic-2009 12:42:35] Inicializando contenedor EJB
[24-dic-2009 12:42:35] Cargando conectores
[24-dic-2009 12:42:35] Iniciando los adaptadores de recursos
[24-dic-2009 12:42:35] estado fallido de la aplicación: MyFirstOC4JApp
[24-dic-2009 12:42:35] Operation failed with error: Falta la clase: org.eclipse.persistence.jpa.PersistenceProvider Clase Dependiente: com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl Cargador: oc4j:10.1.3 Origen del Código: /C:/oc4j/j2ee/home/lib/oc4j-internal.jar Configuración: in META-INF/boot.xml in C:\oc4j\j2ee\home\oc4j.jar Esta carga se ha iniciado en MyFirstOC4JApp.root:0.0.0 mediante el método Class.forName(). La clase que falta no está disponible desde ningún origen de código o cargador del sistema.
Well, the text is into Spanish but I think you know what it means.
For mor information, this is what ten comman line console says,
2009-12-24 12:42:35.359 NOTIFICATION Inicio de Application Deployer para MyFirst
OC4JApp.
2009-12-24 12:42:35.390 NOTIFICATION Copiar archivado en C:\oc4j\j2ee\home\appli
cations\MyFirstOC4JApp.ear
2009-12-24 12:42:35.390 NOTIFICATION Inicio de la inicializaci¾n de C:\oc4j\j2ee
\home\applications\MyFirstOC4JApp.ear...
2009-12-24 12:42:35.390 NOTIFICATION Auto-unpacking C:\oc4j\j2ee\home\applicatio
ns\MyFirstOC4JApp.ear...
2009-12-24 12:42:35.406 NOTIFICATION Desempaquetando MyFirstOC4JApp.ear
2009-12-24 12:42:35.406 NOTIFICATION Unjar C:\oc4j\j2ee\home\applications\MyFirs
tOC4JApp.ear in C:\oc4j\j2ee\home\applications\MyFirstOC4JApp
2009-12-24 12:42:35.453 NOTIFICATION Desempaquetado listo MyFirstOC4JApp.ear
2009-12-24 12:42:35.453 NOTIFICATION Finished auto-unpacking C:\oc4j\j2ee\home\a
pplications\MyFirstOC4JApp.ear
2009-12-24 12:42:35.468 NOTIFICATION Auto-unpacking C:\oc4j\j2ee\home\applicatio
ns\MyFirstOC4JApp\EclipseLinkWeb.war...
2009-12-24 12:42:35.468 NOTIFICATION Desempaquetando EclipseLinkWeb.war
2009-12-24 12:42:35.468 NOTIFICATION Unjar C:\oc4j\j2ee\home\applications\MyFirs
tOC4JApp\EclipseLinkWeb.war in C:\oc4j\j2ee\home\applications\MyFirstOC4JApp\Ecl
ipseLinkWeb
2009-12-24 12:42:35.703 NOTIFICATION Desempaquetado listo EclipseLinkWeb.war
2009-12-24 12:42:35.703 NOTIFICATION Finished auto-unpacking C:\oc4j\j2ee\home\a
pplications\MyFirstOC4JApp\EclipseLinkWeb.war
2009-12-24 12:42:35.734 NOTIFICATION Fin de la inicializaci¾n de C:\oc4j\j2ee\ho
me\applications\MyFirstOC4JApp.ear...
2009-12-24 12:42:35.734 NOTIFICATION Iniciando la aplicaci¾n: MyFirstOC4JApp
2009-12-24 12:42:35.734 NOTIFICATION Inicializando ClassLoaders
2009-12-24 12:42:35.734 NOTIFICATION Inicializando contenedor EJB
2009-12-24 12:42:35.750 NOTIFICATION Cargando conectores
2009-12-24 12:42:35.781 NOTIFICATION Iniciando los adaptadores de recursos
2009-12-24 12:42:35.796 NOTIFICATION estado fallido de la aplicaci¾n: MyFirstOC4
JApp
09/12/24 12:42:35 ADVERTENCIA: Application.setConfig Application: MyFirstOC4JApp
is in failed state as initialization failed.
com.evermind.server.ejb.exception.DeploymentException: [MyFirstOC4JApp]: Excepci
¾n al crear EntityManagerFactory con la clase PersistenceProvider org.eclipse.pe
rsistence.jpa.PersistenceProvider para la unidad de persistencia example.
09/12/24 12:42:35 oracle.oc4j.admin.internal.DeployerException: java.lang.Instan
tiationException: Application: MyFirstOC4JApp is in failed state as initializati
on failed
09/12/24 12:42:35 at oracle.oc4j.admin.internal.ApplicationDeployer.addApp
lication(ApplicationDeployer.java:779)
09/12/24 12:42:35 at oracle.oc4j.admin.internal.ApplicationDeployer.doDepl
oy(ApplicationDeployer.java:273)
09/12/24 12:42:35 at oracle.oc4j.admin.internal.DeployerBase.execute(Deplo
yerBase.java:100)
09/12/24 12:42:35 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeploy
erRunnable.doRun(OC4JDeployerRunnable.java:52)
09/12/24 12:42:35 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRu
nnable.run(DeployerRunnable.java:81)
09/12/24 12:42:35 at com.evermind.util.ReleasableResourcePooledExecutor$My
Worker.run(ReleasableResourcePooledExecutor.java:298)
09/12/24 12:42:35 at java.lang.Thread.run(Thread.java:595)
09/12/24 12:42:35 Caused by: java.lang.InstantiationException: Application: MyFi
rstOC4JApp is in failed state as initialization failed
09/12/24 12:42:35 at com.evermind.server.Application.setConfig(Application
.java:518)
09/12/24 12:42:35 at com.evermind.server.Application.setConfig(Application
.java:361)
09/12/24 12:42:35 at com.evermind.server.ApplicationServer.addApplication(
ApplicationServer.java:1919)
09/12/24 12:42:35 at oracle.oc4j.admin.internal.ApplicationDeployer.addApp
lication(ApplicationDeployer.java:776)
09/12/24 12:42:35 ... 6 more
09/12/24 12:42:35 Caused by: com.evermind.server.ejb.exception.DeploymentExcepti
on: [MyFirstOC4JApp]: Excepci¾n al crear EntityManagerFactory con la clase Persi
stenceProvider org.eclipse.persistence.jpa.PersistenceProvider para la unidad de
persistencia example.
09/12/24 12:42:35 at com.evermind.server.ejb.exception.DeploymentException
.exceptionCreatingEntityManagerFactory(DeploymentException.java:130)
09/12/24 12:42:35 at com.evermind.server.ejb.persistence.PersistenceUnitMa
nagerImpl.createContainerEntityManagerFactory(PersistenceUnitManagerImpl.java:19
7)
09/12/24 12:42:35 at com.evermind.server.ejb.persistence.PersistenceUnitMa
nagerImpl.initializePersistenceUnit(PersistenceUnitManagerImpl.java:159)
09/12/24 12:42:35 at com.evermind.server.ejb.persistence.PersistenceUnitMa
nagerImpl.initialize(PersistenceUnitManagerImpl.java:87)
09/12/24 12:42:35 at com.evermind.server.ApplicationStateRunning.initializ
eApplication(ApplicationStateRunning.java:232)
09/12/24 12:42:35 at com.evermind.server.Application.setConfig(Application
.java:460)
09/12/24 12:42:35 ... 9 more
09/12/24 12:42:35 Caused by: oracle.classloader.util.AnnotatedClassNotFoundExcep
tion:
Falta la clase: org.eclipse.persistence.jpa.PersistenceProvider
Clase Dependiente: com.evermind.server.ejb.persistence.PersistenceUnitMa
nagerImpl
Cargador: oc4j:10.1.3
Origen del C¾digo: /C:/oc4j/j2ee/home/lib/oc4j-internal.jar
Configuraci¾n: <code-source> in META-INF/boot.xml in C:\oc4j\j2ee\home
\oc4j.jar
Esta carga se ha iniciado en MyFirstOC4JApp.root:0.0.0 mediante el mÚtodo Class.
forName().
La clase que falta no estß disponible desde ning·n origen de c¾digo o cargador d
el sistema.
09/12/24 12:42:35 at oracle.classloader.PolicyClassLoader.handleClassNotFo
und(PolicyClassLoader.java:2204)
09/12/24 12:42:35 at oracle.classloader.PolicyClassLoader.internalLoadClas
s(PolicyClassLoader.java:1726)
09/12/24 12:42:35 at oracle.classloader.PolicyClassLoader.loadClass(Policy
ClassLoader.java:1682)
09/12/24 12:42:35 at oracle.classloader.PolicyClassLoader.loadClass(Policy
ClassLoader.java:1667)
09/12/24 12:42:35 at java.lang.ClassLoader.loadClassInternal(ClassLoader.j
ava:319)
09/12/24 12:42:35 at java.lang.Class.forName0(Native Method)
09/12/24 12:42:35 at java.lang.Class.forName(Class.java:242)
09/12/24 12:42:35 at com.evermind.server.ejb.persistence.PersistenceUnitMa
nagerImpl.createContainerEntityManagerFactory(PersistenceUnitManagerImpl.java:19
2)
09/12/24 12:42:35 ... 13 more
2009-12-24 12:42:35.859 NOTIFICATION Fallo de Application Deployer para MyFirstO
C4JApp.
2009-12-24 12:42:35.859 NOTIFICATION Inicio de Application UnDeployer para MyFir
stOC4JApp.
2009-12-24 12:42:35.875 NOTIFICATION Eliminando todos los enlaces Web para la ap
licaci¾n MyFirstOC4JApp de todas las direcciones Web
2009-12-24 12:42:36.109 NOTIFICATION Se ha terminado Application UnDeployer para
MyFirstOC4JApp.
09/12/24 12:42:36 ADVERTENCIA: DeployerRunnable.run java.lang.InstantiationExcep
tion: Application: MyFirstOC4JApp is in failed state as initialization failedora
cle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException: App
lication: MyFirstOC4JApp is in failed state as initialization failed
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:133
at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun
(OC4JDeployerRunnable.java:52)
at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(Deplo
yerRunnable.java:81)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(Relea
sableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.InstantiationException: Application: MyFirstOC4JApp is in f
ailed state as initialization failed
at com.evermind.server.Application.setConfig(Application.java:518)
at com.evermind.server.Application.setConfig(Application.java:361)
at com.evermind.server.ApplicationServer.addApplication(ApplicationServe
r.java:1919)
at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(Applica
tionDeployer.java:776)
at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDe
ployer.java:273)
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:100
... 4 more
Caused by: com.evermind.server.ejb.exception.DeploymentException: [MyFirstOC4JAp
p]: Excepci¾n al crear EntityManagerFactory con la clase PersistenceProvider org
.eclipse.persistence.jpa.PersistenceProvider para la unidad de persistencia exam
ple.
at com.evermind.server.ejb.exception.DeploymentException.exceptionCreati
ngEntityManagerFactory(DeploymentException.java:130)
at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.create
ContainerEntityManagerFactory(PersistenceUnitManagerImpl.java:197)
at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.initia
lizePersistenceUnit(PersistenceUnitManagerImpl.java:159)
at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.initia
lize(PersistenceUnitManagerImpl.java:87)
at com.evermind.server.ApplicationStateRunning.initializeApplication(App
licationStateRunning.java:232)
at com.evermind.server.Application.setConfig(Application.java:460)
... 9 more
Caused by: oracle.classloader.util.AnnotatedClassNotFoundException:
Falta la clase: org.eclipse.persistence.jpa.PersistenceProvider
Clase Dependiente: com.evermind.server.ejb.persistence.PersistenceUnitMa
nagerImpl
Cargador: oc4j:10.1.3
Origen del C¾digo: /C:/oc4j/j2ee/home/lib/oc4j-internal.jar
Configuraci¾n: <code-source> in META-INF/boot.xml in C:\oc4j\j2ee\home
\oc4j.jar
Esta carga se ha iniciado en MyFirstOC4JApp.root:0.0.0 mediante el mÚtodo Class.
forName().
La clase que falta no estß disponible desde ning·n origen de c¾digo o cargador d
el sistema.
at oracle.classloader.PolicyClassLoader.handleClassNotFound(PolicyClassL
oader.java:2204)
at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoa
der.java:1726)
at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java
:1682)
at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java
:1667)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.create
ContainerEntityManagerFactory(PersistenceUnitManagerImpl.java:192)
... 13 more
09/12/24 12:42:36 GRAVE: ProgressObjectImpl.reportError java.lang.InstantiationE
xception: Application: MyFirstOC4JApp is in failed state as initialization faile
doracle.oc4j.admin.jmx.shared.exceptions.InternalException: java.lang.Instantiat
ionException: Application: MyFirstOC4JApp is in failed state as initialization f
ailed
at oracle.oc4j.admin.jmx.shared.deploy.NotificationUserData.<init>(Notif
icationUserData.java:107)
at oracle.oc4j.admin.internal.Notifier.reportError(Notifier.java:429)
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:130
at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun
(OC4JDeployerRunnable.java:52)
at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(Deplo
yerRunnable.java:81)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(Relea
sableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:595)
Caused by: oracle.oc4j.admin.internal.DeployerException: java.lang.Instantiation
Exception: Application: MyFirstOC4JApp is in failed state as initialization fail
ed
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:133
... 4 more
Caused by: java.lang.InstantiationException: Application: MyFirstOC4JApp is in f
ailed state as initialization failed
at com.evermind.server.Application.setConfig(Application.java:518)
at com.evermind.server.Application.setConfig(Application.java:361)
at com.evermind.server.ApplicationServer.addApplication(ApplicationServe
r.java:1919)
at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(Applica
tionDeployer.java:776)
at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDe
ployer.java:273)
at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:100
... 4 more
Caused by: com.evermind.server.ejb.exception.DeploymentException: [MyFirstOC4JAp
p]: Excepci¾n al crear EntityManagerFactory con la clase PersistenceProvider org
.eclipse.persistence.jpa.PersistenceProvider para la unidad de persistencia exam
ple.
at com.evermind.server.ejb.exception.DeploymentException.exceptionCreati
ngEntityManagerFactory(DeploymentException.java:130)
at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.create
ContainerEntityManagerFactory(PersistenceUnitManagerImpl.java:197)
at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.initia
lizePersistenceUnit(PersistenceUnitManagerImpl.java:159)
at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.initia
lize(PersistenceUnitManagerImpl.java:87)
at com.evermind.server.ApplicationStateRunning.initializeApplication(App
licationStateRunning.java:232)
at com.evermind.server.Application.setConfig(Application.java:460)
... 9 more
Caused by: oracle.classloader.util.AnnotatedClassNotFoundException:
Falta la clase: org.eclipse.persistence.jpa.PersistenceProvider
Clase Dependiente: com.evermind.server.ejb.persistence.PersistenceUnitMa
nagerImpl
Cargador: oc4j:10.1.3
Origen del C¾digo: /C:/oc4j/j2ee/home/lib/oc4j-internal.jar
Configuraci¾n: <code-source> in META-INF/boot.xml in C:\oc4j\j2ee\home
\oc4j.jar
Esta carga se ha iniciado en MyFirstOC4JApp.root:0.0.0 mediante el mÚtodo Class.
forName().
La clase que falta no estß disponible desde ning·n origen de c¾digo o cargador d
el sistema.
at oracle.classloader.PolicyClassLoader.handleClassNotFound(PolicyClassL
oader.java:2204)
at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoa
der.java:1726)
at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java
:1682)
at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java
:1667)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl.create
ContainerEntityManagerFactory(PersistenceUnitManagerImpl.java:192)
... 13 more
Any help will be appreciate.
Merry Christmas,
Jose

Broker log has this entry in it:
[23/Feb/2011:03:43:57 UTC] WARNING [B3168]: Invalid broker address for this broker to run in cluster: Loopback IP address is not allowed in broker address mq://127.0.0.1:7676/?instName=imqbroker&brokerSessionUID=6326201025350530816 for cluster
[23/Feb/2011:03:43:57 UTC] WARNING [B1137]: Cluster initialization failed. Disabling the cluster service.
When looking at the working instance, this warning is not displayed but instead is displayed as:
[25/Jan/2011:17:06:49 MST] [B1041]: Cluster initialization successful.
I am not sure what setting needs to change here though.
I was looking at the code and is seems that the combination of not using a cluster and that glassfish sends a namespace prefix to JMS is what results in this final error being thrown.
Edited by: user4187078 on Feb 23, 2011 8:33 AM

Similar Messages

  • Error when deploying as ear, ok when deploying as war, why?

    Hello all,
    I have a strange problem with a JSF project that uses myfaces and shale. I'm using Netbeans 5.5, and all works fine when the web application is deployed independently as a war, but when deploy the full ear i have the following error:
    java.lang.NullPointerException
    at org.apache.myfaces.taglib.core.ViewTag.doStartTag(ViewTag.java:75)
    . I'm using a 'mock' application with no complex ejbs and jsps, so I discard a component problem. Someone have experimented this problem?
    Thanks in advance.

    Thanks vbk,
    I resolved 'partially' the problem not including the myfaces jars in the ear. So the application server uses the sun jsf implementation and all works fine. lamentably I don't know the answer, i suppose a class loading preference problem ... I any case, i would be interested if someone uses the myfaces implementation in the sun app server 9 (myfaces includes some interesting features). I proved the myfaces 1.1.3, 1.1.4 and 1.1.5 versions and all have the same problem.
    In relation with this same post, i found anohter problem: shale tiger annotations make jee5 annotations fail. I looked in the shale forums and seems this combination is incompatible. Someone use tiger annotations?
    Thanks.

  • 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)

  • Error when deploying ear file

    Hello
    What could be the problem that I get this error when deploying my ear file with a web service within.
    [#|2008-03-29T17:43:02.640+0100|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=12;_ThreadName=Thread-26;_RequestID=0a164c90-57bc-4d4a-8b3f-270fc4584891;|Exception occured in J2EEC Phase
    com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- C:\Sun\AppServer\domains\domain1\generated\xml\j2ee-apps\agency_app\agency_jar\META-INF\wsdl\AgencyModuleWebServiceService.wsdl (The system cannot find the file specified)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
         at java.io.FileInputStream.<init>(FileInputStream.java:66)
         at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
         at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
         at java.net.URL.openStream(URL.java:1007)
         at com.sun.enterprise.webservice.WsUtil.generateFinalWsdl(WsUtil.java:699)
         at com.sun.enterprise.webservice.WsUtil.generateFinalWsdl(WsUtil.java:643)
         at com.sun.enterprise.deployment.backend.WebServiceDeployer.doWebServiceDeployment(WebServiceDeployer.java:165)
         at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:855)
         at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:580)
         at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:339)
         at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:222)
         at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:359)
         at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:214)
         at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:129)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
         at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
         at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)
    |#]when I deployed this application on a custom domain setup, it does not fail. But it fails on default domain.
    Regards
    Michael

    How did you create your datasource, can you post the content, without passwords of course.
    Greetings.

  • 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 while deploying the ear fie

    When I try to deploy the EAR file from the Netweaver Studio to the CE environment getting the below error..I am using both trial versions and this is my first application trying to test. Is there any preliminary configuration we need to do.
    Please help me out in resolving the error.
    Aug 11, 2007 1:17:00 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [002]Deployment aborted
    Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !

    Hi,
    <b><u>Just restart the server and try deploying again</u>.</b>
    Also refer to following links.
    <b>How to configure "J2EE Engine/SDM" and Deploy new archive and run</b> - How to configure "J2EE Engine/SDM" and Deploy new archive and run
    <b>SDM Error when Deploying Web Dynpro Application</b>   - Cannot determine sdm host error
    <b>error SDM "Deployment exception : Cannot determine sdm host (is empty). "</b>  - error SDM "Deployment exception : Cannot determine sdm host (is empty). "
    <b>Error: Cannot determine sdm host (is empty).</b>  - Deploy Error: Cannot determine sdm host (is empty).
    <b>Deploy Error: Cannot determine sdm host (is empty).</b>  - Deploy Error: Cannot determine sdm host (is empty).
    I hope this will help you.
    Regards,
    Vaibhav

  • UndeclaredThrowableException when deploying a ear file in admin server 6.1

    Hi,
    I am trying to run ATG Dynamo 5.6 on top of weblogic 6.1
    Dynamo provides a EAR file which will be deployed at the time of weblogic startup.
    But, when i start weblogic, I got the following error:
    Error in deploying dyn.ear
    java.util.UndeclaredThrowableException
    When i checked in the log file, I saw error in loading dyn.ear - StringIndexOutofBounds Exception.
    Please help,
    Thanks
    Bala.

    Can you show us the full stack trace / error message?
    -- Rob
    Bala wrote:
    Hi,
    I am trying to run ATG Dynamo 5.6 on top of weblogic 6.1
    Dynamo provides a EAR file which will be deployed at the time of weblogic startup.
    But, when i start weblogic, I got the following error:
    Error in deploying dyn.ear
    java.util.UndeclaredThrowableException
    When i checked in the log file, I saw error in loading dyn.ear - StringIndexOutofBounds Exception.
    Please help,
    Thanks
    Bala.

  • UndeclaredThrowableException when deploying a ear file in admin server 6.1, SP1 on Solaris 8.

    WLS 6.1, SP1, Solaris 8.
    When deploying an ear file, I get this stack trace:
    javax.management.MBeanException
         at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:979)
         at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:932)
         at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:917)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:620)
         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 $Proxy13.addTarget(Unknown Source)
         at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:837)
         at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:936)
         at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:856)
         at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:772)
         at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:705)
         at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:200)
         at weblogic.management.mbeans.custom.ApplicationManager.startAdminManager(ApplicationManager.java:272)
         at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:146)
         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 $Proxy5.start(Unknown Source)
         at weblogic.management.Admin.startApplicationManager(Admin.java:1155)
         at weblogic.management.Admin.finish(Admin.java:570)
         at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:506)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
         at weblogic.Server.main(Server.java:35)
    with this error message:
    <Mar 5, 2002 3:15:10 PM GMT+00:00> <Error> <Management> <Error deploying application
    ./config/lnuatgorwlsdomain2/applications/NostroCheck.ear: java.lang.reflect.UndeclaredThrowableException>
    A number of other people in other newsgroups have had similar problems, but no
    good concrete answers so far.
    This has only recently started to happen, and only on Solaris. Ear file deploys
    just fine on NT (same version/SP of WLS on both environments).
    Attached is a segment of log file which may give someone more details.
    simon.
    [weblogic-error-log-segment.txt]

    Can you show us the full stack trace / error message?
    -- Rob
    Bala wrote:
    Hi,
    I am trying to run ATG Dynamo 5.6 on top of weblogic 6.1
    Dynamo provides a EAR file which will be deployed at the time of weblogic startup.
    But, when i start weblogic, I got the following error:
    Error in deploying dyn.ear
    java.util.UndeclaredThrowableException
    When i checked in the log file, I saw error in loading dyn.ear - StringIndexOutofBounds Exception.
    Please help,
    Thanks
    Bala.

  • 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.

  • Gettind error when deploying XI module

    Hi,
    I am getting the following error when deploying XI module in J2EE Engine. can anyone help me to proceed. Thanks.
    08/02/22 16:16:59 -  Start updating EAR file...
    08/02/22 16:16:59 -  start-up mode is lazy
    08/02/22 16:17:12 -  EAR file updated successfully for 13047ms.
    08/02/22 16:17:12 -  Start deploying ...
    08/02/22 16:18:27 -  EAR file uploaded to server for 2656ms.
    08/02/22 16:18:29 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/SignEncrypt..
                         Reason: Exception during generation of components of application sap.com/SignEncrypt in container EJBContainer.; nested exception is:
                              com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/SignEncrypt in container EJBContainer.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/SignEncrypt in container EJBContainer.
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
                              ... 10 more
                         Caused by: java.lang.NoClassDefFoundError: Lcom/sap/aii/af/service/auditlog/AuditMessageKey;
                              at java.lang.Class.getDeclaredFields0(Native Method)
                              at java.lang.Class.privateGetDeclaredFields(Class.java:1522)
                              at java.lang.Class.getDeclaredFields(Class.java:1098)
                              at com.sap.engine.services.ejb.deploy.verifier.BeanClassCheck.check(BeanClassCheck.java:78)
                              at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:51)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
                              at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)

    Hi Indira.
    As I can see in your log, you're getting the exception
    Caused by: java.lang.NoClassDefFoundError: Lcom/sap/aii/af/service/auditlog/AuditMessageKey
    May be you need to include aii_af_svc.jar (AuditLog classes are located into this JAR library) in your EAR archive.
    Regards,
    Gari.

  • Error While Deploying the Ear .

    HI ,
    I am getting an error while deploying my ear through Deploy Tool . the ear get loaded but fails to deploy... the error message i got is pasted below...
    It gives error about EJBContainer, but the J2EE Engine's Visual Admin shows the service is runing
    Any help is highly appreaciated
    Eror Message.....
    06/05/13 18:49:09 -  ***********************************************************
    06/05/13 18:49:10 -  Start updating EAR file...
    06/05/13 18:49:10 -  start-up mode is lazy
    06/05/13 18:49:12 -  EAR file updated successfully for 2078ms.
    06/05/13 18:49:12 -  Start deploying ...
    06/05/13 18:49:14 -  EAR file uploaded to server for 1172ms.
    06/05/13 18:49:16 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/omnidocs_ejb..
                         Reason: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.; nested exception is:
                              com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3139)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:539)
                              ... 10 more
                         Caused by: java.lang.NoClassDefFoundError: com/newgen/omni/jts/txn/NGOServerInterface
    Loader Info -
                         ClassLoader name: [Deployment:Runtime:sap.com/omnidocs_ejb]
                          Parent loader name: [Frame ClassLoader]
                          References:
                            common:service:http;service:servlet_jsp
                            service:ejb
                            common:service:iiop;service:naming;service:p4;service:ts
                            service:jmsconnector
                            library:jsse
                            library:servlet
                            common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
                            library:ejb20
                            library:j2eeca
                            library:jms
                            library:opensql
                            common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
                            interface:resourcecontext_api
                            interface:webservices
                            interface:cross
                            interface:ejbserialization
                          Resources:
                            C:\usr\sap\J2E\JC00\j2ee\cluster\server0\temp\deploy\1147526354539
                            C:\usr\sap\J2E\JC00\j2ee\cluster\server0\temp\deploy\1147526354539\omnidocs_ejb.jar
                          Loading model: {parent,references,local}
                         The error occurred while trying to load "com.newgen.omni.jts.txn.oracle.docdb.NGOConnectCabinet".
                              at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
                              at com.sap.engine.services.ejb.deploy.verifier.CheckUtils.loadClass(CheckUtils.java:25)
                              at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:42)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:253)
                              at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2144)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                              ... 16 more
                         For detailed information see the log file of the Deploy Service.
    06/05/13 18:49:16 -  ***********************************************************
    <b></b>

    Hi
    I would suggest you to do the deployment of the EAR using NWDS rather that using deploy tool. for Doing this please follow this link for creating ,building and deplopying as ear using dev studio
    http://help.sap.com/saphelp_nw04/helpdata/en/08/51ec41b9a24f4a8359c61ae4a02db1/frameset.htm
    Anyways if you ar still tied up using deploy tool pleas cross verify that all the dependent jars (including jars which  NgoServerinterface will beusing internally has to be in the classpath . Would be great if you can post the stack trace
    hope this helps !<b>  please mark points for helpful answers .</b>
    regards
    rajeshkr

  • Error when deploying a map

    hello i have the following error when deploying a map in a local database, the mapping is a simple transfert of data between two table,
    ORA-06550: line 0, column 0:
    ORA-04052: erreurs lors de la consultation de l'objet distant [email protected]@KCDBDEV
    ORA-00604: une erreur s'est produite au niveau SQL récursif 1
    ORA-01882: région de fuseau horaire introuvable
    ORA-02063: pré
    any help please
    thanks,
    tarek

    Hello thank u for helping, i have exactly the same problème in Error executing a query using a DB-Link
    but i am not inderstanding the solution, i found the same probleme in metalink, and the solution posted is:
    1. Create an errorstack of the ORA-1882 to see the ALTER SESSION SET TIME_ZONE statement that is causing the ORA-1882 during deployment. To create this errorstack, follow step 1 to 4 below:
    1. Just before you reproduce the error, open a SQL*Plus session with user SYSTEM.
    SQL> alter system set events '1882 trace name ERRORSTACK level 3'
    2. Deploy the mapping to reproduce the ORA-1882
    3. Disable the system event
    SQL> alter system set events '1882 trace name errorstack off';
    4. Take a look at the errorstack (located in the udump directory). Suppose the following statement is in there:
    ALTER SESSION SET TIME_ZONE = 'GMT+02:00'
    2. Modify the run_service.sh(.bat) file as follow:
    * For UNIX:
    Modify owb_server_home/owb/bin/unix/run_service.sh as follows:
    Add the parameter -Duser.timezone="+02:00" to the line where java is started (last line of run_service.sh)
    $JAVAPATH/bin/java -Xmx768M -Djava.awt.headless=true -DORACLE_HOME.....
    e.g:
    $JAVAPATH/bin/java -Xmx768M -Duser.timezone="+02:00" -Djava.awt.headless=true -DORACLE_HOME
    * For Windows:`
    Modify owb_server_home\owb\bin\win32\run_service.bat as follows:
    Add the parameter -Duser.timezone="+02:00" to the line where java is started
    %JAVAPATH%\jre\bin\javaw.exe %JVM_OPTIONS%
    e.g.:
    %JAVAPATH%\jre\bin\javaw.exe -Duser.timezone="+02:00" %JVM_OPTIONS%
    3. Save the file and re-start the Runtime Service using stop_service.sql/start_service.sql.
    but in creating the errorstack of the ORA-1882 i not found the ALTER SESSION SET TIME_ZONE
    and i Modify the run_service i fixed -Duser.timezone="+01:00" cause the time zone here is Europe/Paris but there is no changes.
    the db link is from Oracle 10.2.0.2.0 to 9.2.0.1.0. and owb 10g R2
    other solution?
    thanks,
    tarek

  • 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.

  • Using ADWrapper but has error when deploy to IIS

    Dear all,
    I am using below link to develop the program.
    Active Directory in VB.Net
    But has error when deploy to IIS as attached screen. Do you  know how to solve??

    Dear all,
    I am using below link to develop the program.
    Active Directory in VB.Net
    But has error when deploy to IIS as attached screen. Do you  know how to solve??
    Hi,
    I am moving this thread to Using Forums >Where is the Forum For…?
    forum, the owner of the forum will direct you to a proper forum.
    I would recommend you check this thread
    http://social.msdn.microsoft.com/Forums/en-US/13bb6961-720d-4604-8eff-22251604cd94/active-directory?forum=whatforum
     which shared a place where you could get help, and since this thread has lasted for a long time, you could create a new thread of that forum to get supports.
    Hello,
    Thank you for the post.  I would suggest posting your question in one of the below mentioned Web sites. Hope this helps you.
    http://social.technet.microsoft.com/Forums/en/winserverDS/threads
    http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.active_directory&cat=en_us_5bd43452-4bab-4720-8df9-d5f37d3153b9&lang=en&cr=us
    Have a great day!
    Tier 2 Application Support  Server and Tools Online Operations Team
    Thanks for your understanding.
    Regards.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

Maybe you are looking for