EJB Deployment Error using JDeveloper3.1

While deploying a session bean (in which I am instantiating a user defined class) to the Oracle Server 8.1.6 using JDeveloper 3.1, I am getting the following error -
"Class not found during deserialization of descriptor".
Why is this error coming?
Do i need to change anything like setting any permissions to the oracle schema which i am using?
Thanks in Advance.
null

When I install the same standalone OC4J version via:
1. setting JAVA_HOME to JDK 1.4.2
2. unpacking the OC4J zip-file
3. running oc4j -start
The application can be deployed.
Does this mean that the default JDK at the time OC4J is installed can not be changed later on?!
Regards, Ronald

Similar Messages

Oracle Application Server 10.1.3 EJB Deployment Error

Hi ,
I am keep getting following error when try to deploy my ear files in 10.1.3. standalone env.
my ejb-jar.xml looks is
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<description>Session Facade Bean ( Stateless )</description>
<display-name>FacadeBean</display-name>
<ejb-name>FacadeBean</ejb-name>
<home>com.sjrwmd.dmsap.ejb.FacadeBeanHome</home>
<remote>com.sjrwmd.dmsap.ejb.FacadeBeanRemote</remote>
<ejb-class>com.sjrwmd.dmsap.ejb.FacadeBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>FacadeBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
Your help appriciated
Thank You
Jigar
2006-02-08 17:13:40.670 NOTIFICATION JMS Router is initiating ...
2006-02-08 17:13:55.702 NOTIFICATION Application Deployer for dmsap STARTS.
2006-02-08 17:13:55.733 NOTIFICATION Copy the archive to C:\JDev1013\j2ee\home\applications\dmsap.ear
2006-02-08 17:13:55.733 NOTIFICATION Initialize ./applications\dmsap.ear begins...
2006-02-08 17:13:55.733 NOTIFICATION Removing everything under: C:\JDev1013\j2ee\home\.\applications\dmsap
2006-02-08 17:13:55.733 NOTIFICATION Auto-unpacking C:\JDev1013\j2ee\home\.\applications\dmsap.ear...
2006-02-08 17:13:55.733 NOTIFICATION Unpacking dmsap.ear
2006-02-08 17:13:55.733 NOTIFICATION Unjar C:\JDev1013\j2ee\home\.\applications\dmsap.ear in C:\JDev1013\j2ee\home\.\applications\dmsap
2006-02-08 17:13:55.998 NOTIFICATION Done unpacking dmsap.ear
2006-02-08 17:13:55.998 NOTIFICATION Finished auto-unpacking C:\JDev1013\j2ee\home\.\applications\dmsap.ear
2006-02-08 17:13:56.045 NOTIFICATION Auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\dmsap-web.war...
2006-02-08 17:13:56.045 NOTIFICATION Unpacking dmsap-web.war
2006-02-08 17:13:56.045 NOTIFICATION Unjar C:\JDev1013\j2ee\home\applications\dmsap\dmsap-web.war in C:\JDev1013\j2ee\home\applications\dmsap\dmsap-web
2006-02-08 17:13:56.498 NOTIFICATION Done unpacking dmsap-web.war
2006-02-08 17:13:56.498 NOTIFICATION Finished auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\dmsap-web.war
2006-02-08 17:13:56.498 NOTIFICATION Auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\uploaddirapp.jar...
2006-02-08 17:13:56.498 NOTIFICATION Unpacking uploaddirapp.jar
2006-02-08 17:13:56.498 NOTIFICATION Unjar C:\JDev1013\j2ee\home\applications\dmsap\uploaddirapp.jar in C:\JDev1013\j2ee\home\applications\dmsap\uploaddirapp
2006-02-08 17:13:56.748 NOTIFICATION Done unpacking uploaddirapp.jar
2006-02-08 17:13:56.748 NOTIFICATION Finished auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\uploaddirapp.jar
2006-02-08 17:13:56.748 NOTIFICATION Auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\downloadfileapp.jar...
2006-02-08 17:13:56.764 NOTIFICATION Unpacking downloadfileapp.jar
2006-02-08 17:13:56.764 NOTIFICATION Unjar C:\JDev1013\j2ee\home\applications\dmsap\downloadfileapp.jar in C:\JDev1013\j2ee\home\applications\dmsap\downloadfileapp
2006-02-08 17:13:56.967 NOTIFICATION Done unpacking downloadfileapp.jar
2006-02-08 17:13:56.967 NOTIFICATION Finished auto-unpacking C:\JDev1013\j2ee\home\applications\dmsap\downloadfileapp.jar
2006-02-08 17:13:56.983 NOTIFICATION Initialize ./applications\dmsap.ear ends...
2006-02-08 17:13:56.983 NOTIFICATION Starting application : dmsap
2006-02-08 17:13:56.983 NOTIFICATION Initializing ClassLoader(s)
2006-02-08 17:13:56.983 NOTIFICATION Initializing EJB container
2006-02-08 17:13:56.983 NOTIFICATION Loading connector(s)
2006-02-08 17:13:57.295 NOTIFICATION Starting up resource adapters
2006-02-08 17:13:57.295 NOTIFICATION Processing EJB module: dmsap-ejb.jar
2006-02-08 17:13:57.405 ERROR J2EE EJB3027 [dmsap] An error occured deploying EJB module: com.evermind.server.ejb.deployment.InvalidEJBAssemblyException: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
 Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
 Loader: dmsap.root:0.0.0
 Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
 Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
 Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
 Loader: oc4j:10.1.3
 Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
 Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
2006-02-08 17:13:57.405 NOTIFICATION application : dmsap is in failed state
Feb 8, 2006 5:13:57 PM com.evermind.server.Application setConfig
WARNING: Application: dmsap is in failed state as initialization failedjava.lang.InstantiationException: Error initializing ejb-modules: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
 Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
 Loader: dmsap.root:0.0.0
 Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
 Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
 Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
 Loader: oc4j:10.1.3
 Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
 Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
06/02/08 17:13:57 oracle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException: Error initializing ejb-modules: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
 Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
 Loader: dmsap.root:0.0.0
 Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
 Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
 Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
 Loader: oc4j:10.1.3
 Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
 Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
06/02/08 17:13:57 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:510)
06/02/08 17:13:57 at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:191)
06/02/08 17:13:57 at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
06/02/08 17:13:57 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
06/02/08 17:13:57 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
06/02/08 17:13:57 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
06/02/08 17:13:57 at java.lang.Thread.run(Thread.java:534)
06/02/08 17:13:57 Caused by: java.lang.InstantiationException: Error initializing ejb-modules: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
 Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
 Loader: dmsap.root:0.0.0
 Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
 Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
 Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
 Loader: oc4j:10.1.3
 Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
 Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
06/02/08 17:13:57 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1056)
06/02/08 17:13:57 at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:210)
06/02/08 17:13:57 at com.evermind.server.Application.setConfig(Application.java:391)
06/02/08 17:13:57 at com.evermind.server.Application.setConfig(Application.java:308)
06/02/08 17:13:57 at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1771)
06/02/08 17:13:57 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:507)
06/02/08 17:13:57 ... 6 more
06/02/08 17:13:57 Caused by: com.evermind.server.ejb.deployment.InvalidEJBAssemblyException: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
 Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
 Loader: dmsap.root:0.0.0
 Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
 Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
 Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
 Loader: oc4j:10.1.3
 Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
 Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
06/02/08 17:13:57 at com.evermind.server.ejb.exception.ValidationExceptions.unableToLoadEJBClass(ValidationExceptions.java:36)
06/02/08 17:13:57 at com.evermind.server.ejb.deployment.BeanDescriptor.initialize(BeanDescriptor.java:298)
06/02/08 17:13:57 at com.evermind.server.ejb.deployment.ExposableBeanDescriptor.initialize(ExposableBeanDescriptor.java:158)
06/02/08 17:13:57 at com.evermind.server.ejb.deployment.SessionBeanDescriptor.initialize(SessionBeanDescriptor.java:190)
06/02/08 17:13:57 at com.evermind.server.ejb.deployment.EJBPackage.initialize(EJBPackage.java:814)
06/02/08 17:13:57 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:855)
06/02/08 17:13:57 ... 11 more
06/02/08 17:13:57 Caused by: oracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
 Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
 Loader: dmsap.root:0.0.0
 Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
 Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
 Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
 Loader: oc4j:10.1.3
 Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
 Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar
06/02/08 17:13:57 at oracle.classloader.PolicyClassLoader.defineClass(PolicyClassLoader.java:2268)
06/02/08 17:13:57 at oracle.classloader.PolicyClassLoader.findLocalClass(PolicyClassLoader.java:1457)
06/02/08 17:13:57 at oracle.classloader.SearchPolicy$FindLocal.getClass(SearchPolicy.java:167)
06/02/08 17:13:57 at oracle.classloader.SearchSequence.getClass(SearchSequence.java:119)
06/02/08 17:13:57 at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1660)
06/02/08 17:13:57 at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1621)
06/02/08 17:13:57 at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1606)
06/02/08 17:13:57 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
06/02/08 17:13:57 at java.lang.Class.forName0(Native Method)
06/02/08 17:13:57 at java.lang.Class.forName(Class.java:219)
06/02/08 17:13:57 at com.evermind.server.ejb.deployment.BeanDescriptor.initialize(BeanDescriptor.java:296)
06/02/08 17:13:57 ... 15 more
06/02/08 17:13:57 Caused by: java.lang.UnsupportedClassVersionError: com.sjrwmd.dmsap.ejb.FacadeBean
06/02/08 17:13:57 at java.lang.ClassLoader.defineClass0(Native Method)
06/02/08 17:13:57 at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
06/02/08 17:13:57 at oracle.classloader.PolicyClassLoader.defineClass(PolicyClassLoader.java:2224)
06/02/08 17:13:57 ... 25 more
2006-02-08 17:13:57.545 NOTIFICATION Application Deployer for dmsap FAILED.
2006-02-08 17:13:57.545 NOTIFICATION Application UnDeployer for dmsap STARTS.
2006-02-08 17:13:59.045 NOTIFICATION Removing all web binding(s) for application dmsap from all web site(s)
2006-02-08 17:13:59.795 NOTIFICATION Application UnDeployer for dmsap COMPLETES.
2006-02-08 17:13:59.795 WARNING java.lang.InstantiationException: Error initializing ejb-modules: [dmsap:dmsap-ejb:FacadeBean] - Unable to load ejb-class com.sjrwmd.dmsap.ejb.FacadeBean, see section 23.2 of the EJB 2.1 specificationoracle.classloader.util.AnnotatedClassFormatError: com.sjrwmd.dmsap.ejb.FacadeBean
 Invalid class: com.sjrwmd.dmsap.ejb.FacadeBean
 Loader: dmsap.root:0.0.0
 Code-Source: /C:/JDev1013/j2ee/home/applications/dmsap/dmsap-ejb.jar
 Configuration: <ejb> in C:\JDev1013\j2ee\home\applications\dmsap
 Dependent class: com.evermind.server.ejb.deployment.BeanDescriptor
 Loader: oc4j:10.1.3
 Code-Source: /C:/JDev1013/j2ee/home/lib/oc4j-internal.jar
 Configuration: <code-source> in META-INF/boot.xml in C:\JDev1013\j2ee\home\oc4j.jar

A point of clarification: Using JDK 1.5, it compiles and "tries" to start, but then gives this error : Unable to load ejb-class com.MyTestEJB see section 23.2 of the EJB 2.1 specificationjava.lang.ExceptionInInitializerError: java.lang.NullPointerException
There are other EJB which are deploying fine.
I really can't tell why one is deploying but this one is not.
Thanks

EJB Deployment error in Weblogic 8.1 very urgent

Hi
Mark I forgot to send my error message. So I am sending again.
Sorry for the trouble.
Murali
[weblogicerr1.txt]

They are reccomended because the next step going from your simple single EJB
to anything interesting, like adding more EJB's adding web-apps, adding
web-services etc etc involves ears. If the setup and overhead for an EAR is
easy, then just start there.
But no if you just doing helloworld you of course dont have to ears.
cheers
mbg
"Christopher R. Gardner" <[email protected]> wrote in message
news:3fc0560e$[email protected]..
>
"Mark Griffith" <[email protected]> wrote:
You can still run ejbc from the command line its still there. And you
can
still run weblogic.Deployer. (I dont ever reccomend jaring up in dev,
it
just takes longer, do exploded its easier and faster).
But ear's are easy, see:So ears are recommended even if you're just doing EJBs (e.g., a simpleHello World)
and no web apps (none needed for the Hello World or a PC client)?
http://www.niffgurd.com/mark/work/blog/
Cheers
mbg
"Christopher R. Gardner" <[email protected]> wrote in message
news:3fbfd6c6$[email protected]..
My understanding is ejbc has been deprecated and replaced with appc.Moreover,
BEA is encourgaging developers to deploy ear files. All I want todo is
to use
ant to deploy a jar file with a single EJB in it. I'm not findingthe WL
documentation
very helpful. Hopefully, you'll have better luck than I.
"skmurali" <[email protected]> wrote:
Hi
In order deploy EJB application in Weblogic 8.1, is it necessary
to compile
the application in WebLogic.ejbc. I did not find such files in
WebLogic
8.1
In weblogic 7.0 versiion has such files.
The present procedure is as follows.
1. Create a jar file contains all class files.
2. Create a jar file contains class jar files, plus .xml files
3. Deploy into weblogic 8.1 server EJB Deployment utility.
==================
Please help me.
Murali

EJB Deployment error(It's Ugent)

Hi there,
i'm gettin the following error while deploying the EJB.
Pl'z lookin into and suggest me some solution for this.
Fri Feb 25 16:20:48 EST 2000:<E> <EJB> Could not deploy: 'D:/ejb+mail/ejb-eg/bea
demo/beanew2.jar': file is not a valid jar file, or does not
contain a valid bean
weblogic.ejb.common.DeploymentException: DeploymentException opening JAR file D:
\ejb+mail\ejb-eg\beademo\beanew2.jar; nested exception is:
weblogic.ejb.deployment.JarLoadException - with nested exception:
[weblogic.ejb.common.DeploymentException: Problem creating deployment D:/ejb+mai
l/ejb-eg/beademo/beanew2.jar from D:\ejb+mail\ejb-eg\beademo\beanew2.jar; nested
exception is:
java.lang.ClassCastException: com.sun.xml.tree.TextNode]
weblogic.ejb.common.DeploymentException: Problem creating deployment D:/ejb+mail
/ejb-eg/beademo/beanew2.jar from D:\ejb+mail\ejb-eg\beademo\beanew2.jar; nested
exception is:
java.lang.ClassCastException: com.sun.xml.tree.TextNode
java.lang.ClassCastException: com.sun.xml.tree.TextNode
at weblogic.xml.dom.DOMUtils.getOptionalElementsByTagName(DOMUtils.java:
204)
at weblogic.xml.dom.DOMUtils.getOptionalElementByTagName(DOMUtils.java:1
70)
at weblogic.xml.dom.DOMUtils.getOptionalValueByTagName(DOMUtils.java:97)
at weblogic.ejb.deployment.dd.EJBReadDOM.getDescriptionValue(EJBReadDOM.
java:404)
at weblogic.ejb.deployment.dd.DescriptorLoader.createDeploymentUnit(Desc
riptorLoader.java:200)
at weblogic.ejb.internal.EJBJarLoader.initialize(EJBJarLoader.java:113)
at weblogic.ejb.internal.EJBJarLoader.<init>(EJBJarLoader.java:85)
at weblogic.ejb.internal.EJBJarDeployment.setupJar(EJBJarDeployment.java
:344)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:21
1)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:18
2)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:16
4)
at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java
:172)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:1
22)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:1
12)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:305)
at weblogic.ejb.internal.EJBManagerImpl.deployBeans(EJBManagerImpl.java:
629)
at weblogic.ejb.internal.EJBManagerImpl.<init>(EJBManagerImpl.java:242)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1295)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
--------------- nested within: ------------------
weblogic.ejb.deployment.JarLoadException - with nested exception:
[weblogic.ejb.common.DeploymentException: Problem creating deployment D:/ejb+mai
l/ejb-eg/beademo/beanew2.jar from D:\ejb+mail\ejb-eg\beademo\beanew2.jar; nested
exception is:
java.lang.ClassCastException: com.sun.xml.tree.TextNode]
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:313)
at weblogic.ejb.internal.EJBManagerImpl.deployBeans(EJBManagerImpl.java:
629)
at weblogic.ejb.internal.EJBManagerImpl.<init>(EJBManagerImpl.java:242)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1295)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
Fri Feb 25 16:20:48 EST 2000: <EJB> 0 EJB jar files loaded, containing 0 EJBs
Fri Feb 25 16:20:48 EST 2000: <EJB> 0 deployed, 0 failed to deploy.
Fri Feb 25 16:20:50 EST 2000: <ZAC> ZAC ACLs initialized
Fri Feb 25 16:20:50 EST 2000: <ZAC> ZAC packages stored in local directory ex
ports
Fri Feb 25 16:20:50 EST 2000: <ListenThread> Listening on port: 7001
Fri Feb 25 16:20:51 EST 2000:<A> <Posix Performance Pack> Could not initialize P
OSIX Performance Pack.
Fri Feb 25 16:20:51 EST 2000:<E> <Performance Pack> Unable to load performance p
ack, using Java I/O.
Fri Feb 25 16:20:51 EST 2000: <WebLogicServer> WebLogic Server started
regards,
Riyaz

Best bet is to use BEA support. They have access to the source code of the classes that are throwing the exception.
But, it's saying that your jar file is invalid and it looks like it's getting a problem whilst parsing one of the xml files (maybe ejb-jar.xml or weblogic-ejb-jar.xml). Did you get the jar through the ejbc process successfully?

Weblogic 9.1 Deployment errors using the ANT task wldeploy

I am not able to deploy applicatons using the ANT task. The same works with Weblogic 8.1. It is throwing a NoClassDefFoundError. It is looking for a class by name javax/management/InvalidAttributeValueException.
This class file is shipped as part of jmx.jar. I tried to include it and then there was another NoClassDefFoundError that occured.
The problem is I don't want to keep adding these different jars to make the ant deployment work. Can anyone please let me know what could be the problem.
I am using a Windows XP OS and 1.4.2_10 as java version.
I have added all the jars in the weblogic91\server\lib directory to the classpath.
Also I have my apache ant tasks set in the classpath.
Thanks
Shankar Chandrasekaran

Have had a bit of these CLASSPATH issues when jumping versions.
Have had the best success when I create a different profile for each one, making sure the version you want is the only one defined. the main thing my profile sets is
unset PATH
unset CLASSPATH
unset JAVA_HOME
then
export PATH=
export CLASSPATH= the weblogic 9 one
export JAVA_HOME= the one with 9
or however they do it in windows, but make sure you CLASSPATH is only refencing the 9 jars

EJB deployment problems using ear

Hi,
I am able to deploy the ejbs in exploded format, but when I deploy
them in an ear, I see 'EJB Deployed message' on the start up console.
But when my servlet is trying to create the EJB, I am getting
CreateException. What is the reason for that?
Thanks,
Mark Pluta

Mark
You'll probably receive more help if you print out the stack trace... in the meanwhile..
there are some things to make sure.. verify that in the application.xml of your
ear file you have your ejb's declared, in the console view the JNDI tree and make
sure that the ejb's are on there as well.. viewing the stacktrace might be able
to get you more help though
Chris
Mark Pluta <[email protected]> wrote:
Hi,
I am able to deploy the ejbs in exploded format, but when I deploy
them in an ear, I see 'EJB Deployed message' on the start up console.
But when my servlet is trying to create the EJB, I am getting
CreateException. What is the reason for that?
Thanks,
Mark Pluta

EJB deployment error for Weblogic server 9.2 mp4

Hi,
While trying to deploy a small EJB jar file which uses EJB 2.1 CMP beans with relationships, getting the following error from Weblogic server 9.2 MP4:
=================================================================================================
<Error> <EJB> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988333> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
>
####<Nov 1, 2011 4:09:48 PM IST> <Error> <Deployer> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988380> <BEA-149265> <Failure occured in the execution of deployment request with ID '1320143984947' for task '1'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
 at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
 at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
 at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
 at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
 at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
 at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
 at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
 at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
 at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
 at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
 at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
 at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
 at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
 at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
 at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
 at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
 at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
 at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
 at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
 at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
 at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
 at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
 at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
 at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
 at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:382)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
 at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
 at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
 at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
 at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
 at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
 at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
 at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
 at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
 at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
 at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
 at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
 at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
 at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
 at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
 at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
=================================================================================================
While I'm able to deploy without the CMP 1-1 relationship, the moment I introduce the 1-1 relationship, I get this error. Database used is Oracle 10g XE.
I have been battling this error for more than a day now. Kindly help me fix this.
Thanks in advance!
Regards,
Vinod

Hi,
I was able to figure out the root cause. I was using the primitive data type "int" for primary key and foreign key for one of the beans in the relationship. After I changed it to "Integer" wrapper type, the issue got resolved.
-Vinod

SunOne ejb deployment error

Hi, I'm trying to deploy an ejb on SunOne AppSvr7 (Solaris8).
However, I always get the following error:
Cannot deploy the component
error received from mbean null
The following message is found on the admin-server log:
[01/Apr/2003:17:54:51] INFO ( 8929): ADM6002:Received remote administration request
[01/Apr/2003:17:54:52] INFO ( 8929): ADM6002:Received remote administration request
[01/Apr/2003:17:54:52] INFO ( 8929): ADM1006:Uploading the file to:[var/tmp/s1astempTDomainadmin-server-1243288101/TInst/ttrepository_idm_ejb.jar]
[01/Apr/2003:17:54:52] INFO ( 8929): ADM1007:Uploaded the remote file at: [var/tmp/s1astempTDomainadmin-server-1243288101/TInst/ttrepository_idm_ejb.jar]
[01/Apr/2003:17:54:52] INFO ( 8929): ADM6002:Received remote administration request
[01/Apr/2003:17:54:59] INFO ( 8929): Total Deployment Time: 6958 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%
[01/Apr/2003:17:54:59] WARNING ( 8929): ADM6004:Remote invocation failed - Detailed Message:
java.lang.RuntimeException: error received from mbean null
at com.iplanet.ias.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:166)
at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:222)
at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.callInvoke(AdminAPIEntryServlet.java:217)
at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.callMBean(AdminAPIEntryServlet.java:176)
at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.doGet(AdminAPIEntryServlet.java:101)
at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.doPost(AdminAPIEntryServlet.java:83)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)
Could any experts out there suggest me with what are the steps/things that I should look into?
At this point I really have no idea what to do.
I'm no expert in this field.
Please, any help would be deeply appreciated.
Thanks in advance.

I have actually run it with veryfier.
The admin-server log still look exactly the same with my first post.
I have run it again with FINER level of logging, the server.log from the instance directory is as follow:
[02/Apr/2003:09:42:39] FINE (14190): RMI TCP Connection(3)-127.0.0.1: (port 37089) connection closed
[02/Apr/2003:09:42:39] FINE (14190): RMI TCP Connection(3)-127.0.0.1: close connection
[02/Apr/2003:09:43:00] FINE (14190): SingleSignOn[tinst]: SSO expiration started. Current entries: 0
[02/Apr/2003:09:43:00] FINE (14190): SingleSignOn[tinst]: SSO cache will expire 0 entries.
[02/Apr/2003:09:43:04] FINE (14190): RMI TCP Connection(4)-127.0.0.1: accepted socket from [127.0.0.1:37095]
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: (port 37089) suggesting 127.0.0.1:37095
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: (port 37089) client using 172.16.1.41:0
[02/Apr/2003:09:43:04] FINE (14190): RMI TCP Connection(4)-127.0.0.1: (port 37089) op = 80
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: getting input stream
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: call dispatcher
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: [127.0.0.1: sun.rmi.transport.DGCImpl[0:0:0, 2]: java.rmi.dgc.Lease dirty(java.rmi.server.
ObjID[], long, java.rmi.dgc.Lease)]
[02/Apr/2003:09:43:04] FINE (14190): RMI TCP Connection(4)-127.0.0.1: name = "[Ljava.rmi.server.ObjID;", codebase = ""
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: (thread context class loader: sun.misc.Launcher$AppClassLoader@a56a7c)
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: class "[Ljava.rmi.server.ObjID;" found via codebase, defined by null
[02/Apr/2003:09:43:04] FINE (14190): RMI TCP Connection(4)-127.0.0.1: name = "java.rmi.dgc.Lease", codebase = ""
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: (thread context class loader: sun.misc.Launcher$AppClassLoader@a56a7c)
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: class "java.rmi.dgc.Lease" found via codebase, defined by null
[02/Apr/2003:09:43:04] FINE (14190): RMI TCP Connection(4)-127.0.0.1: name = "java.rmi.dgc.VMID", codebase = ""
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: (thread context class loader: sun.misc.Launcher$AppClassLoader@a56a7c)
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: class "java.rmi.dgc.VMID" found via codebase, defined by null
[02/Apr/2003:09:43:04] FINE (14190): RMI TCP Connection(4)-127.0.0.1: name = "[B", codebase = ""
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: (thread context class loader: sun.misc.Launcher$AppClassLoader@a56a7c)
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: class "[B" found via codebase, defined by null
[02/Apr/2003:09:43:04] FINE (14190): RMI TCP Connection(4)-127.0.0.1: name = "java.rmi.server.UID", codebase = ""
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: (thread context class loader: sun.misc.Launcher$AppClassLoader@a56a7c)
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: class "java.rmi.server.UID" found via codebase, defined by null
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: vmid = 716a8d8a7ce14e02:899213:f428215830:-7fff
[02/Apr/2003:09:43:04] FINER (14190): RMI TCP Connection(4)-127.0.0.1: getting output stream
[02/Apr/2003:09:43:19] FINE (14190): RMI TCP Connection(4)-127.0.0.1: (port 37089) connection closed
[02/Apr/2003:09:43:19] FINE (14190): RMI TCP Connection(4)-127.0.0.1: close connection
[02/Apr/2003:09:44:00] FINE (14190): SingleSignOn[tinst]: SSO expiration started. Current entries: 0
[02/Apr/2003:09:44:00] FINE (14190): SingleSignOn[tinst]: SSO cache will expire 0 entries.
[02/Apr/2003:09:45:00] FINE (14190): SingleSignOn[tinst]: SSO expiration started. Current entries: 0
[02/Apr/2003:09:45:00] FINE (14190): SingleSignOn[tinst]: SSO cache will expire 0 entries.
[02/Apr/2003:09:46:00] FINE (14190): SingleSignOn[tinst]: SSO expiration started. Current entries: 0
[02/Apr/2003:09:46:00] FINE (14190): SingleSignOn[tinst]: SSO cache will expire 0 entries.
Not really sure if the above log can be any help at all.
I can't seem to understand what they mean.
Thanks for your reply, hope the above will help.
Thanks in advance.

Deployment error using CMS (Component is not a SCA but a SDA)

I haven't seen this message before on the forum so I thought I'd see if anyone else has run into this. My landscape is as follows:
Runtime System: NW04 SP14
JDI System: NW04 SP19
SAP SCA plugins: NW04 SP14
Application: Standard web dynpro with 2 DC's (one for model and one for application)
Landscape: Dev (no runtime), Cons (no runtime), Test (runtime), Production (runtime)
I have migrated my local development of these DC's into the JDI following the standard help documentation for migrating web dynpros. Everything went smoothly (no errors during build in Dev and Cons, Assembly went fine).
I am at the point of attempting to import my new SCA into the Test runtime environment using standard CMS. I first imported the SAP_BUILDT, SAP_JEE, and SAP_TECHS into test. This imported fine and from my understanding nothing will deploy for these so all is good. When I import my SCA, the SDM-deploy step issues the following fatal error:
Info:Starting Step SDM-deploy at 2007-04-06 11:44:20.0344 -7:00
Info:start deployment of archives to SDM:http://myserver:50018
Info:The following archives will be deployed (on http://myserver:50018)
Info:E:\usr\sap\JTrans\CMS\archives\pcbp.comVMRSJDV_VMRS_C~20070406171501.sca
Fatal:Unexpected exception 'Component [Name: vmrs , Vendor: pcbp.com] is not a SCA, but a SDA.' occurred. Stopping processing.
Fatal Exception:java.lang.IllegalArgumentException: Component [Name: vmrs , Vendor: pcbp.com] is not a SCA, but a SDA.:Component [Name: vmrs , Vendor: pcbp.com] is not a SCA, but a SDA.
java.lang.IllegalArgumentException: Component [Name: vmrs , Vendor: pcbp.com] is not a SCA, but a SDA.
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
.....
Has anyone seen this message before or have any thoughts as to what may be the issue? I have searched the forums and OSS for the "Component is not a SCA but a SDA" message and have been unsucessful. I have validated that the archive is in fact packaged as an SCA file. I attempted to rename it from the file system to a .sda to see what would happen but that was not successful. One more bit of info that may be helpful is that there may have been a previous application deployed on the runtime environment with the same name. Prior to attempting to deploy the JDI version, I had removed the app (the non JDI one) from the server using the Deploy service of Visual Administrator so there shouldn't be a conflict there right?
Message was edited by:
 Eric Vota
I think I figured this out. When I remove the application via the Visual Admin deploy service it does not synchronize with the SDM. For that reason, the old application (which was a deployed SDA) was still in the SDM repository. I am in process of using the SDM deploy tool to remove the offending application. After that I will attempt to reimport the SCA via the CMS. Hopefully this works. I'll update the post with the result in case anyone else has this problem.

This was fixed by undeploying from the SDM instead of from Visual Admin. Good to go now

EJB Deployment error in 9.2 (java.lang.OutOfMemoryError: Java heap space at

Hello all,
I am trying to deploy EAR(has more than 25 ejb's) in weblogic 9.2 but currently one EJB ejb-pwc.jar is failing to compile(gives out of memory error). But if i try building ear only with this EJB and its dependencies class it work. Here is the errror. Please help me to figure out this issue. Thanks in advance,
Exception preparing module: EJBModule(ejb-pwc.jar) Unable to deploy EJB: ejb-pwc.jar from ejb-pwc.jar: There are 1 nested errors: java.io.IOException: Compiler failed executable.exec: The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: Java heap space at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435) at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295) at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303) at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:308) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:496) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:463) at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430) at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752) at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Compiler failed executable.exec: The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: Java heap space

I'd suggest pre-compiling the application before deployment.
java weblogic.appc my.ear
(You may need to increase the heap size here as well.)
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

WLS 7.0 SP2 - deploy error using security-permission in weblogic.xml on Win NT (jdk1.3.1)

I am trying to use this in my weblogic.xml and this is the error that I get:
weblogic-web-app>
<description>Test Web App</description>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/TestDSRef</res-ref-name>
<jndi-name>TestJdbc</jndi-name>
</resource-description>
</reference-descriptor>
<security-permission>
<security-permission-spec>
 // grant ability to read any file
 grant codeBase "http://server/virtual_directory/-"
 permission java.io.FilePermission "<<ALL FILES>>", "read";
 </security-permission-spec>
</security-permission>
</weblogic-web-app>
Error parsing descriptor in Web appplication "e:\bea7_2\user_projects\mydomain\.\applications\.wlnotdelete\wl_comp15697.war"
[Path="e:\bea7_2\user_projects\mydomain\.\myserver\upload\ourpeople", URI="ourpeople.war"]
Any ideas on what I might be doing wrong? When I remove the security-permissions,
the application deploys fine.

I am trying to use this in my weblogic.xml and this is the error that I get:
weblogic-web-app>
<description>Test Web App</description>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/TestDSRef</res-ref-name>
<jndi-name>TestJdbc</jndi-name>
</resource-description>
</reference-descriptor>
<security-permission>
<security-permission-spec>
 // grant ability to read any file
 grant codeBase "http://server/virtual_directory/-"
 permission java.io.FilePermission "<<ALL FILES>>", "read";
 </security-permission-spec>
</security-permission>
</weblogic-web-app>
Error parsing descriptor in Web appplication "e:\bea7_2\user_projects\mydomain\.\applications\.wlnotdelete\wl_comp15697.war"
[Path="e:\bea7_2\user_projects\mydomain\.\myserver\upload\ourpeople", URI="ourpeople.war"]
Any ideas on what I might be doing wrong? When I remove the security-permissions,
the application deploys fine.

EJB Deployment error

Hello,
Am trying to deploy an EJB that passes the Sun App Server verifier. Fails with a report in the jar_verified.txt file of " Test Description : Unexpected error in verifier, check for problems related to: [ java.lang.NoClassDefFoundError: mil/osd/dmdc/aatd/rapids/common/to/DodCardDataTO ]" This DodCardDataTO class is included in the deployed jar file, as well as being present in the server's lib directory; the name of that jar file in the lib directory is listed in the JVM Settings/Path Settings of the main page. Have tried setting and unsetting the "Ignore Env. Classpath" checkbox, making sure to apply changes and restart the server. This DodCardDataTO class is the parent of the argument to the business method of the remote interface.
If anyone has the remotest idea of what I'm missing, please reply...Thanks in advance!

I don't know if it helps, but I had a similar problem. The error was in the deployment descriptor. I had some "\n" where you specify the class name. I removed it and I specified all on the same line.

EJB Deployment errors

I'm having problems with deploying my entity bean on Weblogic 6.1. I'm getting error message "Unable to bind EJB Home Interface to the JNDI name planCST". I was able to deploy successfully yesterday. When I'm redeploying, I'm getting this error. Any help is appreciated.
Thanks
Bala

No.. There is no previous binding. Besides that, whatever the name I change to, I'm getting the same message.
Anyhow, I can not keep changing the jndi bind name whenever I update the ejb. There must be some other thing wrong.
Bala

SOA Deployment error using the ant script

I am trying to deploy my composite using the ant-sca-deploy.xml with out any config plan.
In the log file it was shown as build successful but when i checked in the SOA server the project was not deployed. In turn it returned an error http 404 error. Where will be connectivity error comes???
I echoed the host name and port number. they were correct.
log file for better understanding
Buildfile: ant-sca-deploy.xml
[echo] oracle.home = /app/wlsapp/product/SOA/Oracle_SOA1/bin/..
deploy:
[input] skipping input as property serverURL has already been set.
[input] skipping input as property sarLocation has already been set.
[deployComposite] setting user/password..., user=weblogic
[deployComposite] Processing sar=/app/wlsapp/bpelprojects/SAMPLE/deploy/sca_SAMPLE_rev1-cmdline.jar
[deployComposite] Adding sar file - /app/wlsapp/bpelprojects/SAMPLE/deploy/sca_SAMPLE_rev1-cmdline.jar
[deployComposite] Creating HTTP connection to host:10.246.161.148, port:7020
[deployComposite] Received HTTP response from the server, response code=404
[deployComposite] Problem in sending HTTP request to the server. Check standard HTTP response code for 404
[deployComposite] ---->response code=404, error:null
BUILD SUCCESSFUL
Total time: 1 second
Please do the needful.
Thanks
Raja

Hi All,
I found the issue. It was an issue with the port number. It was a clustered environment.
Since it was a clustered environment the port was listening at 8020.
Thanks
Raja

Deployment Error using the Web Services sample ?

All,
I am running the Web Services sample, the compile works fine, but the deployment fails with the following error -
Any suggestions on what needs to be fixed ?
Sameer.
C:\jdev9\jdk\jre\bin\javaw.exe -jar C:\ias\j2ee\home\admin.jar ormi://127.0.0.1/ admin **** -deploy -file C:\jdev9\jdev\mywork\WorkspaceStatelessJava\Project\WorkspaceStatelessJava-ProjectStatelessJava-WS.ear -deploymentName WorkspaceStatelessJava-ProjectStatelessJava-WS
Error: java.lang.NoSuchMethodError: java.net.URL: method getPath()Ljava/lang/String; not found
Exit status of OC4J admin tool (-deploy): 1

Thanks Mike, your guess was right on target.
I realize this sample was originally tested for Oracle9i Web Services
Quickstart Install (9.0.2) , but I have been able to get it running on
(9.0.3) as well.
1) I pointed to a jdk 1.3 directory and then was able to
create a password for oc4j.
C:\jdev9\j2ee\home>D:\jdk1.3.1\bin\java -jar oc4j.jar -install
Enter an admin password to use: admin
Confirm admin password: admin
Installation done
2) This time the deployment worked -
---- Deployment started. ---- Dec 6, 2002 10:57:42 AM
Wrote WAR file to
C:\jdev9\jdev\mywork\WorkspaceStatelessJava\Project\WebServices.war
Wrote EAR file to
C:\jdev9\jdev\mywork\WorkspaceStatelessJava\Project\WorkspaceStatelessJ
ava-ProjectStatelessJava-WS.ear
Invoking OC4J admin tool...
C:\jdev9\jdk\jre\bin\javaw.exe -jar C:\jdev9\j2ee\home\admin.jar
ormi://127.0.0.1/ admin **** -deploy -file
C:\jdev9\jdev\mywork\WorkspaceStatelessJava\Project\WorkspaceStatelessJ
ava-ProjectStatelessJava-WS.ear -deploymentName
WorkspaceStatelessJava-ProjectStatelessJava-WS
Auto-unpacking
C:\jdev9\j2ee\home\applications\WorkspaceStatelessJava-ProjectStateless
Java-WS.ear... done.
Auto-unpacking
C:\jdev9\j2ee\home\applications\WorkspaceStatelessJava-ProjectStateless
Java-WS\WebServices.war... done.
Copying default deployment descriptor from archive at
C:\jdev9\j2ee\home\applications\WorkspaceStatelessJava-ProjectStateless
Java-WS/META-INF/orion-application.xml to deployment directory
C:\jdev9\j2ee\home\application-deployments\WorkspaceStatelessJava-Proje
ctStatelessJava-WS...
Auto-deploying WorkspaceStatelessJava-ProjectStatelessJava-WS (New
server version detected)...
Exit status of OC4J admin tool (-deploy): 0
C:\jdev9\jdk\jre\bin\javaw.exe -jar C:\jdev9\j2ee\home\admin.jar
ormi://127.0.0.1/ admin **** -bindWebApp
WorkspaceStatelessJava-ProjectStatelessJava-WS WebServices
http-web-site /WorkspaceStatelessJava-ProjectStatelessJava-context-root
Exit status of OC4J admin tool (-bindWebApp): 0
Use the following context root(s) to test your web application(s):
http://127.0.0.1:8888/WorkspaceStatelessJava-ProjectStatelessJava-conte
xt-root
Elapsed time for deployment: 22 seconds
---- Deployment finished. ---- Dec 6, 2002 10:58:04 AM
3) Running the Client.java worked.
Project Message Window
C:\jdev9\jdk\bin\javaw.exe -ojvm -classpath
C:\jdev9\jdev\mywork\WorkspaceStatelessJava\Project\classes;C:\jdev9\jd
ev\lib\jdev-rt.jar;C:\jdev9\jdev\lib\jdev-rt.jar;C:\jdev9\soap\lib\soap
.jar;C:\jdev9\lib\xmlparserv2.jar;C:\jdev9\jlib\javax-ssl-1_2.jar;C:\jd
ev9\jlib\jssl-1_2.jar;C:\jdev9\j2ee\home\lib\activation.jar;C:\jdev9\j2
ee\home\lib\mail.jar;C:\jdev9\j2ee\home\lib\http_client.jar Client
Hello Mike! The current time is Fri Dec 06 11:08:36 EST 2002Process
exited with exit code 0.
4) TCP Tunnel Utility runs correctly
HTTP/1.1 100 ContinueServer: Oracle9iAS (9.0.3.0.0) Containers for
J2EEDate: Fri, 06 Dec 2002 16:14:59 GMTHTTP/1.1 200 OKDate: Fri, 06 Dec
2002 16:14:59 GMTServer: Oracle9iAS (9.0.3.0.0) Containers for
J2EEContent-Length: 517Connection: CloseContent-Type: text/xml;
charset=utf-8<?xml version='1.0' encoding='UTF-8'?><SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body><ns1:sayHel
loResponse xmlns:ns1="HelloImpl"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><ret
urn xsi:type="xsd:string">Hello Mike! The current time is Fri Dec 06
11:15:00 EST
2002</return></ns1:sayHelloResponse></SOAP-ENV:Body></SOAP-ENV:Envelope
>
POST
/WorkspaceStatelessJava-ProjectStatelessJava-context-root/HelloImpl
HTTP/1.1Host: 127.0.0.1:8900Connection: Keep-Alive, TETE: trailers,
deflate, gzip, compressUser-Agent: RPT-HTTPClient/0.3-3SOAPAction:
""Accept-Encoding: deflate, gzip, x-gzip, compress,
x-compressContent-type: text/xml; charset=utf-8Content-length: 441<?xml
version='1.0' encoding='UTF-8'?><SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body><ns1:sayHel
lo xmlns:ns1="HelloImpl"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><par
am
xsi:type="xsd:string">Mike</param></ns1:sayHello></SOAP-ENV:Body></SOAP
-ENV:Envelope>
--------------------------

EJB Deployment Error using JDeveloper3.1

Similar Messages

Maybe you are looking for