A error in ejb deployment

i got a error in j2see deployment
i deploy a entity bean,but while the Deployment Progress ,i got a error:
java.rmi.ServerException:RemoteException occurred in server thread;nested exception is:
java.rmi.RemoteException: Error processing ejb jar: Compilation failed

I am having same problem. I have developed a cmp and
using cloudscape as my database. The application got
verified without errors. But while deploying i am
getting the error.i think thats due to----
either bean class is not implementing all the methods as in remote
or
ur jar does not include a
compiled bean class /home/remote or other necessary classes
is it so?

Similar Messages

Error in EJB deployment (Cannot CreateProcess)

Hi,
I have a WebAs 6.40 SP11(J2EE Engine & ABAP Engine) and NDS 2.0.11 installed on
a Windows 2000 server and i am trying to deploy an EJB Application
(the Car-Rental Tutorial.
When I try to deploy the application onto J2EE engine, the deploy aborts and give
me the following error message:
05/07/04 12:30:04 - ***********************************************************
05/07/04 12:30:05 - Start updating EAR file...
05/07/04 12:30:05 - start-up mode is lazy
05/07/04 12:30:05 - EAR file updated successfully for 172ms.
05/07/04 12:30:05 - Start deploying ...
05/07/04 12:30:05 - EAR file uploaded to server for 156ms.
05/07/04 12:30:07 - ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/QuickCarRentalApplication..
                     Reason: Errors while compiling:
                     Cannot CreateProcess: javac @C:/usr/sap/J2E/JC00/j2ee/cluster/server0/compilerTempDir/compiler_Jul_4_at_12.30/O1120491007000.txt @C:/usr/sap/J2E/JC00/j2ee/cluster/server0/compilerTempDir/compiler_Jul_4_at_12.30/S1120491007000.txt error=2; nested exception is:
                          com.sap.engine.services.ejb.exceptions.deployment.EJBFileGenerationException: Errors while compiling:
                     Cannot CreateProcess: javac @C:/usr/sap/J2E/JC00/j2ee/cluster/server0/compilerTempDir/compiler_Jul_4_at_12.30/O1120491007000.txt @C:/usr/sap/J2E/JC00/j2ee/cluster/server0/compilerTempDir/compiler_Jul_4_at_12.30/S1120491007000.txt error=2
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:478)
                          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:294)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                          at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                          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:94)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
                     Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBFileGenerationException: Errors while compiling:
                     Cannot CreateProcess: javac @C:/usr/sap/J2E/JC00/j2ee/cluster/server0/compilerTempDir/compiler_Jul_4_at_12.30/O1120491007000.txt @C:/usr/sap/J2E/JC00/j2ee/cluster/server0/compilerTempDir/compiler_Jul_4_at_12.30/S1120491007000.txt error=2
                          at com.sap.engine.services.ejb.util.AdminUtils.compile(AdminUtils.java:473)
                          at com.sap.engine.services.ejb.deploy.DeployAdmin.deploySingleJar(DeployAdmin.java:625)
                          at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:263)
                          at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2118)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:379)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3033)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:463)
                          ... 10 more
                     Caused by: com.sap.engine.compilation.CompilerProcessFailureException: Cannot CreateProcess: javac @C:/usr/sap/J2E/JC00/j2ee/cluster/server0/compilerTempDir/compiler_Jul_4_at_12.30/O1120491007000.txt @C:/usr/sap/J2E/JC00/j2ee/cluster/server0/compilerTempDir/compiler_Jul_4_at_12.30/S1120491007000.txt error=2
                          at com.sap.engine.compilation.ExternalCompiler.compile(ExternalCompiler.java:77)
                          at com.sap.engine.services.ejb.util.AdminUtils.compile(AdminUtils.java:471)
                          ... 20 more
                     For detailed information see the log file of the Deploy Service.
05/07/04 12:30:07 - ***********************************************************
I will appreciate if someone can help me...
Thanks!

Thanks, Vladimir!
The directory c:\j2sdk_1.4.2_08\bin was in the PATH, the problem was that javac.exe wasn't in the directory.
Thanks again!
Guillermo.

Error when ejb deployment in WLS 9.1 clustered environment

Hello,
We have a WLS 9.1 cluster consisting of one admin server and two managed servers. we are deploying ejb jar,It is succeed on the first managed server but fail on the second managed server. The admin console and for the second managed server contains the following log(below given). I checked the classpath of two managed servers, It is same in two servers. when i restarted the two managed servers, application is in active state but not running in second managed sever complining for one ejb class that the jndi-name in the weblogic-ejb-jar.xml is not correct. If it is not correct it should not run in first managed server also right.
please help me whether Am I doing something wrong or is this a bug?
below given the log when i deployed the ejb.
####<May 18, 2007 9:49:22 AM GMT> <Error> <Deployer> <tool2> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1179481762802> <BEA-149265> <Failure occured in the execution of deployment request with ID '1179481757718' for task '8'. Error is: 'java.lang.AssertionError: Assertion violated'
java.lang.AssertionError: Assertion violated
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.cluster.migration.MigrationManager.unregister(MigrationManager.java:246)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onUndeploy(MessageDrivenBeanInfoImpl.java:999)
at weblogic.ejb.container.manager.BaseEJBManager.undeploy(BaseEJBManager.java:467)
at weblogic.ejb.container.manager.MessageDrivenManager.undeploy(MessageDrivenManager.java:570)
at weblogic.ejb.container.deployer.EJBDeployer.deactivate(EJBDeployer.java:1817)
at weblogic.ejb.container.deployer.EJBModule.doDeactivate(EJBModule.java:1041)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:420)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:60)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:567)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:131)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:101)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:126)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:329)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:845)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1246)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:432)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
java.lang.AssertionError: Assertion violated
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.cluster.migration.MigrationManager.unregister(MigrationManager.java:246)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onUndeploy(MessageDrivenBeanInfoImpl.java:999)
at weblogic.ejb.container.manager.BaseEJBManager.undeploy(BaseEJBManager.java:467)
at weblogic.ejb.container.manager.MessageDrivenManager.undeploy(MessageDrivenManager.java:570)
at weblogic.ejb.container.deployer.EJBDeployer.deactivate(EJBDeployer.java:1817)
at weblogic.ejb.container.deployer.EJBModule.doDeactivate(EJBModule.java:1041)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:420)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:60)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:567)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:131)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:101)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:126)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:329)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:845)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1246)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:432)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
>
####<May 18, 2007 9:49:22 AM GMT> <Error> <Deployer> <tool2> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1179481762823> <BEA-149202> <Encountered an exception while attempting to commit the 7 task for the application 'MyEJB'.
Regards,
mohan
Edited by raj_bea_raj at 05/29/2007 1:35 AM
Edited by raj_bea_raj at 05/29/2007 1:41 AM

If you're using OC4J standalone, use the latest available OC4J, 10.1.3.3.
If you're using a manage OC4J, ie. Application Server, upgrade to the latest available version and upgrade your JDK. The provided JDK might be outdated.
--olaf

How to resolve this Error for Ejb deployment

java weblogic.ejbc -compiler javac a.jar a_ejb.jar
Exception in thread "main" java.lang.NoClassDefFoundError: java/util/logging/Han
dler
at weblogic.ejbc20.<init>(ejbc20.java:82)
at weblogic.ejbc.main(ejbc.java:29)

hello, the pdf viewer is still somewhat experimental and under very active development - you could try if the same error is occurring in the current development version, which you can download as an addon from http://mozilla.github.io/pdf.js/extensions/firefox/pdf.js.xpi
in case it has the the same rendering problems, you could then file a bug report at https://github.com/mozilla/pdf.js/issues (a github account is necessary for it though) - please also provide a sample document where the error is apparent!

Error while accessing EJB deployed in another app

Hi,I have an EJB deployed in another application and was trying to access it from different application (both running on seperate weblogic server 5.1)when i do look-up like this : Hashtable hmRemote = new Hashtable(); hmRemote.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory"); hmRemote.put(Context.PROVIDER_URL, "http://localhost:7001/doc"); Hashtable hmLocal = new Hashtable(); hmLocal.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory"); hmLocal.put(Context.PROVIDER_URL, "http://localhost:7004/amit"); hmLocal.put(WLContext.DELEGATE_ENVIRONMENT, hmRemote); Context ctx = new InitialContext(hmLocal);I get following error on console :Wed May 02 12:28:30 CDT 2001: <ConMan> Bootstrap unable to get a http connection to localhost/127.0.0.1Wed May 02 12:28:30 CDT 2001: <ConMan> Bootstrap unable to get a http connection to localhost/127.0.0.1Exception caught in try javax.naming.CommunicationException [Root exception is java.net.ConnectException: No server found atHTTP://localhost:7001]Please help me.thanksamit

I solved the problem or I learned the process. I forgot to add two jar files in tomcat shared library. It is working now. Thanks.

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?

Deployment error in ejb program

I tried to deploy the ejb as said in tutorial and samples in
C:\bea\weblogic81\workshop\help\doc\en\core\index.html
But at the last stage ie,during deployment, I am getting this error
[Deployment failed:149034]An exception occured for task
[Deployer:14026]Deploy applicaton test on cgServer:
Exception:weblogic.management.ApplicationException.activefailed for webapp
Module: webappError:
weblogic.management.DeploymentException: Could not setup environment-with nested exception:
[weblogic.deployment.EnvironmentException:
[J2EE:160101]Error:The ejb-link 'BandsExampleEJB.jar#Music' declared in the ejb-ref or ejb-local-ref 'ejb/MusicLink' in the application module 'webapp' could not be found.please ensure the link is correct.]
[weblogic.deployment.EnvironmentException:
[J2EE:160101]Error:The ejb-link 'BandsExampleEJB.jar#Music' declared in the ejb-ref or ejb-local-ref 'ejb/MusicLink' in the application module 'webapp' could not be found.please ensure the link is correct.
check the server window and logs for more information.

Hi Rajit,
Thanks for your reply.
The details of the exception id is follows.
[EXCEPTION]
#1#com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID sapcomtcdtrenterpriseapp
     at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
     at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
     at com.tssap.dtr.server.deltav.nameres.impl.SecureStoreNameServerConfig.loadConfiguration(SecureStoreNameServerConfig.java:54)
     at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager.loadNameServerConfiguration(NameReservationManager.java:162)
     at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager.processQueue(NameReservationManager.java:231)
     at com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask._run(ProcessNameReservationsTask.java:35)
     at com.tssap.dtr.pvc.basics.transaction.AbstractSessionBoundTask.run(AbstractSessionBoundTask.java:37)
     at com.tssap.dtr.pvc.util.scheduler.Invocation$Worker.run(Invocation.java:130)
     at java.lang.Thread.run(Thread.java:534)
After deploying CalculatedEar.ear Call the jsp in IE
The Exp has come.
Guide me what is the problem .
Thanks in advance.
regards
nageswar.

Error compiling EJB.jar + cannot resolve symbol+while deploying

I am getting following
Error compiling EJB.jar , cannot resolve symbol ,Syntax error in source, am getting around 17 errors while deploying EAR generated using Jdev905 into standalone oc4jContainers(10g).
Can anyone please help me out where is the problem.
Regards,
Anup

cannot resolve symbol ,Syntax error in source
indicates some jar file is not in the Classpath. Is j2ee.jar in the Classpath?

8iR3; EJB deploy; "Unable to read class bits" error

Hi,
I have a strange situation going on at the moment. Every time I wish to deploy an EJB to 8iR3, the JDeveloper Message View shows the following (after app specific messages):
"Reading Deployment Descriptor...done
Verifying Deployment Descriptor...done
Gathering users...done
Generating Comm Stubs...............................................done
Compiling Stubs...done
Generating Jar File...done
Loading EJB Jar file and Comm Stubs Jar file...
Unable to read class bits from library/sqlhelper/sjb/SQLHelperOperations.class
*** Errors occurred while deploying the EJB to 8i JVM ***
*** Deployment completed ***
If I then just redeploy without changing a thing, it deploys fine and everything works.
I haven't seen a post on this forum like this, is there a configuration problem at my end?
Cheers,
Jono
null

I think it is due to the fact that I am writing a 'business interface' for my EJB, then including it in my deployment package.
This technique is recommended in O'Reilly's 'Enterprise Java Beans' 2nd Edition p344 to ensure the bean interface and the bean match their signature.
I don't get the 'class bits' error when I write EJB from the wizard, but when I add a business interface it happens first deploy, and is OK for the second one.
Hope this helps anyone else who is getting this behaviour, I guess we'll have to see what happens in OC4J/Orion.

IO error writing cache during ejb deployment

I am getting this error a lot when I deploy an ear to standalone oc4j. This happens when I run from the command line or from jdeveloper. Retrying it eventually works, sometimes to speed things up I shutdown oc4j and remove the file. Is there some way to prevent this from happening.
com.evermind.compiler.CompilationException: Error instantiating compiler: IO error writing cache: D:\oc4j\j2ee\home\application-deployments\WebTSApp\WebTSejb.jar\deployment.cache
at com.evermind.server.ejb.compilation.Compilation.compileClasses(Compilation.java:500)

This was a known issue before the preview release.
Workaround for the problem would be to change the Application name and EAR file name.
If you have the EJB deployment profile, Right mouse on it and choose Settings.
Change the name of the EAR file and the Application name and redeploy.
raghu
JDev Team

Error while running ejbc. Fatal error from EJB Compiler ---- Error while pr

Hi!
I was deploying a test application for a session bean with sun 1 studio 5 and I started getting this message while deploying.
I had tested the bean previously and I had no problems.
I found this in the sun app server 7 release notes, but I don't understand what I'm supposed to do...
"Deployment of CMP beans fails.
The following error is thrown because there are no <query-params> entries in the container-managed persistence (CMP) bean in sun-ejb-jar.xml file:
Error while running ejbc. Fatal error from EJB Compiler ---- Error while processing CMP beans.
Solution
Even if it isn't necessary for the CMP beans, add the query-params tag for finders in the sun-ejb-jar.xml file with the empty parameters."
Here is my sun-ejb-jar.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 EJB 2.0//EN" "http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_0-0.dtd">
<sun-ejb-jar>
<enterprise-beans>
<name>GestorDoBanco_EJBModule</name>
<ejb>
<ejb-name>Cliente</ejb-name>
<jndi-name>ejb/Cliente</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/Cliente.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>ClienteAssociadoAConta</ejb-name>
<jndi-name>ejb/ClienteAssociadoAConta</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/ClienteAssociadoAConta.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>Conta</ejb-name>
<jndi-name>ejb/Conta</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/Conta.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>GestorDoBanco</ejb-name>
<jndi-name>ejb/GestorDoBanco</jndi-name>
<pass-by-reference>false</pass-by-reference>
</ejb>
<ejb>
<ejb-name>MensagemM003</ejb-name>
<jndi-name>ejb/MensagemM003</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM003.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>MensagemM003Rejeitada</ejb-name>
<jndi-name>ejb/MensagemM003Rejeitada</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM003Rejeitada.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>MensagemM012</ejb-name>
<jndi-name>ejb/MensagemM012</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM012.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>MensagemM012Rejeitada</ejb-name>
<jndi-name>ejb/MensagemM012Rejeitada</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM012Rejeitada.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>MensagemM103</ejb-name>
<jndi-name>ejb/MensagemM103</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM103.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>MensagemM112</ejb-name>
<jndi-name>ejb/MensagemM112</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM112.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>Registo</ejb-name>
<jndi-name>ejb/Registo</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/Registo.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>TransaccaoConfirmada</ejb-name>
<jndi-name>ejb/TransaccaoConfirmada</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/TransaccaoConfirmada.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>TransaccaoFinalizada</ejb-name>
<jndi-name>ejb/TransaccaoFinalizada</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/TransaccaoFinalizada.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>TransaccaoIniciada</ejb-name>
<jndi-name>ejb/TransaccaoIniciada</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/TransaccaoIniciada.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<pm-descriptors>
<pm-descriptor>
<pm-identifier>SunONE</pm-identifier>
<pm-version>1.0</pm-version>
<pm-class-generator>com.iplanet.ias.persistence.internal.ejb.ejbc.JDOCodeGenerator</pm-class-generator>
<pm-mapping-factory>com.iplanet.ias.cmp.NullFactory</pm-mapping-factory>
</pm-descriptor>
<pm-inuse>
<pm-identifier>SunONE</pm-identifier>
<pm-version>1.0</pm-version>
</pm-inuse>
</pm-descriptors>
<cmp-resource>
<jndi-name>mysqlpmanager</jndi-name>
<default-resource-principal>
<name>bes</name>
<password>besbes</password>
</default-resource-principal>
</cmp-resource>
</enterprise-beans>
</sun-ejb-jar>
Thanks in advance for any help.
Nuno

http://docs.sun.com/source/817-2175-10/decmp.html
Please go to the above docs and look thru the examples given in it.
Example 2
This query returns all products in a specified price range. It defines two query parameters which are the lower and upper bound for the price: double low, double high. The filter compares the query parameters with the price field:
"low < price && price < high"
The finder element of the sun-ejb-jar.xml file would look like this:
<finder>
<method-name>findInRange</method-name>
<query-params>double low, double high</query-params>
<query-filter>low < price && price &lt
high</query-filter
</finder>
I hope this hepls. In your case u just have to make it null.

Error during application deployment in cluster

Hi All,
 I am seeing a weird error when I deploy my application in 2 node cluster. Few months back, the same cluster worked perfectly alright. The error relates to lookup at localhost:7001 which is no where in the configuration as admin server url is http://srai-xp:7001. I created a new domain and see the same problem.
 Any pointers are greatly appreciated.
 Thanks
 --shashi
 Here is the error log:
 D:\apps\bea\user_projects\domains\nclusterdomain>startManagedWebLogic.cmd NodeSR http://srai-xp:7001
 D:\apps\bea\user_projects\domains\nclusterdomain>echo off
 CLASSPATH=CR190380_81sp3.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jax-qname.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\li
 jsafe.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jsafejce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\asn1.jar;;C:\j2sd
 .4.2_04\lib\tools.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic_sp.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic.jar;d:\apps\bea\WEBLOG~1\common\eval\
 intbase\lib\pbserver44.jar;d:\apps\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\j2sdk1.4.2_04\jre\lib\rt.jar;d:\apps\bea\WEBLOG~1\server\lib\webservices.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_base.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_jce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb_jaas.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_license.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_provider.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\mysql-connector-java.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\nls_charset12.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\ojdbc14.jar;
 * To start WebLogic Server, use a username and *
 * password assigned to an admin-level user. For *
 * server administration, use the WebLogic Server *
 * console at http://[hostname]:[port]/console *
 <Mar 17, 2005 4:19:27 PM PST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
 Enter username to boot WebLogic server:weblogic
 Enter password to boot WebLogic server:
 <Mar 17, 2005 4:21:22 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.2_04-b05 fr
 Sun Microsystems Inc.>
 <Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://srai-xp:7001 to ch
 k if there exists a running admin server at this URL.>
 <Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
 <Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
 WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
 <Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://srai-xp:7001 to retriev
 the initial configuration.>
 <Mar 17, 2005 4:21:25 PM PST> <Notice> <Log Management> <BEA-170019> <The server log file D:\apps\bea\user_projects\domains\nclusterdomain\NodeSR\No
 SR.log is opened. All server side log events will be written to this file.>
 <Mar 17, 2005 4:21:30 PM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
 <Mar 17, 2005 4:21:30 PM PST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "NodeSR" for domain "nclusterdomain">
 <Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster XCluster on 237.0.0.101:8050.>
 <Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of XCluster.>
 <Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 153.32.158.12
 <Mar 17, 2005 4:22:08 PM PST> <Notice> <Cluster> <BEA-000102> <Joining cluster XCluster on 237.0.0.101:8050>
 <Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "NodeSR" for domain "nclusterdomain" running i
 Production Mode>
 <Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
 <Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_de': Public ID references the old
 rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
 <Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_fr': Public ID references the old
 rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
 <Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_ja': Public ID references the old
 rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
 <Mar 17, 2005 4:23:35 PM PST> <Warning> <J2EE> <BEA-160081> <The JMS connection factory resource EDCEventQCF declared in the EJB "EventManagerBean"
 part of application "edc-server" does not support XA. It cannot be used inside a transaction context.>
 javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
 java.net.ConnectException: Connection refused: connect; No available router to destination]
 at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
 at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:618)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
 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:175)
 at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
 at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
 at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
 at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
 at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
 at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
 at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
 at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
 at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
 at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
 at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
 at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
 Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
 java.net.ConnectException: Connection refused: connect; No available router to destination
 at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
 at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
 ... 28 more
 --------------- nested within: ------------------
 weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Unable to create InitialContext ] - with nested exception:
 [javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is
 java.net.ConnectException: Connection refused: connect; No available router to destination]]
 at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:770)
 at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
 at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
 at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
 at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
 at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
 at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
 at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
 at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
 at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
 at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
 at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
 <Mar 17, 2005 4:23:40 PM PST> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application edc-server.
 java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
 java.net.ConnectException: Connection refused: connect; No available router to destination
 at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
 at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
 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:175)
 at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
 at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
 at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
 at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
 at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
 at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
 at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
 at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
 at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
 at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
 at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
 at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
 --------------- nested within: ------------------
 weblogic.management.ManagementException: - with nested exception:
 [java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
 java.net.ConnectException: Connection refused: connect; No available router to destination]
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2327)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
 >

I checked all deployment descriptions and there are no references to t3://localhost:7001. Few months back, I had the complete clustering setup working on 2 machines and now when I deploy my application on same configuration, it fails with t3://localhost:7001 unreachable error. I created a new cluster configuration on one machine with 2 managed server and it deploys fine. Can not figure out what has changed ?

Error: Unresolved ejb-link :

I want to call a session bean from a servlet.while deploying i am getting the error
Error: Unresolved <ejb-link>:
I am using Netbeans 6.0 IDE. here i am posting my code.
Calling code in servlet :
Context ctx = new InitialContext();
Object objref = ctx.lookup("java:comp/env/ejb/Etrack");
testBean=(MyHome)PortableRemoteObject.narrow(objref,MyHome.class);
web.xml :
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<servlet>
<servlet-name>MyClientServlet</servlet-name>
<servlet-class>MyClientServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>MyClientServlet</servlet-name>
<url-pattern>/MyClientServlet</url-pattern>
</servlet-mapping>
<ejb-local-ref>
<ejb-ref-name>ejb/Etrack</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>MyHome</local-home>
<local>MyRemote</local>
<ejb-link>Etrack</ejb-link>
</ejb-local-ref>
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
</web-app>
My ejb-jar.xml :
<?xml version="1.0"?>
<!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>
<display-name>Etrack Bean</display-name>
<ejb-name>Etrack</ejb-name>
<local-home>MyHome</local-home>
<local>MyRemote</local>
<ejb-class>MyEjbClass</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<ejb-local-ref>
<ejb-ref-name>ejb/Etrack</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>MyHome</local-home>
<local>MyRemote</local>
<ejb-link>Etrack</ejb-link>
</ejb-local-ref>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>Etrack</ejb-name>
<method-intf>Local</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
My sun-ejb-jar.xml :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 EJB 2.1//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_2_1-1.dtd">
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>Etrack</ejb-name>
<stateless-session-descriptor>
<bean-pool>
<steady-pool-size>10</steady-pool-size>
<resize-quantity>10</resize-quantity>
<max-pool-size>100</max-pool-size>
<pool-idle-timeout-in-seconds>600</pool-idle-timeout-in-seconds>
</bean-pool>
</stateless-session-descriptor>
<jndi-name>ejb/Etrack</jndi-name>
<pass-by-reference>true</pass-by-reference>
<ejb-ref>
<ejb-name>Etrack</ejb-name>
<ejb-ref-name>ejb/Etrack</ejb-ref-name>
<jndi-name>ejb/Etrack</jndi-name>
</ejb-ref>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
Can anyone help me in resolving this issue.It will be a great help for me.Thanks in advance

You could always try removing the ejb-link, and see if the container can inject a reference in the runtime environment (accessible using jndi java:comp/env/ejb/Etrack).
If it doesn't, check these:
1) http://www.redhat.com/docs/manuals/rhaps/jonas-guide/ch-beans-ejbref.html
2) the ejb 2.0 spec, which the original poster was using (although this is the same in 2.1 and 3.0), states the folowing:
+20.3.2 Application Assembler’s responsibilities+
The Application Assembler can use the ejb-link element in the deployment descriptor to link an*
EJB reference to a target enterprise bean.*
The Application Assembler specifies the link between two enterprise beans as follows:*
+• The Application Assembler uses the optional ejb-link element of the ejb-ref or+
ejb-local-ref element of the referencing enterprise bean. The value of the ejb-link*
element is the name of the target enterprise bean. (It is the name defined in the ejb-name element*
of the target enterprise bean.) The target enterprise bean can be in any ejb-jar file in the*
same J2EE application as the referencing application component.*
+• Alternatively, to avoid the need to rename enterprise beans to have unique names within an+
entire J2EE application, the Application Assembler may use the following syntax in the*
ejb-link element of the referencing application component. The Application Assembler*
specifies the path name of the ejb-jar file containing the referenced enterprise bean and*
appends the ejb-name of the target bean separated from the path name by # . The path name*
is relative to the referencing application component jar file. In this manner, multiple beans with*
the same ejb-name may be uniquely identified when the Application Assembler cannot*
change ejb-names.*
+• The Application Assembler must ensure that the target enterprise bean is type-compatible with+
the declared EJB reference. This means that the target enterprise bean must be of the type indicated*
in the ejb-ref-type element, and that the home and component interfaces of the target*
enterprise bean must be Java type-compatible with the interfaces declared in the EJB*
reference.*
The following illustrates an ejb-link in the deployment descriptor.*
+...+
*+<enterprise-beans>+*
*+<session>+*
+...+
*+<ejb-name>EmployeeService</ejb-name>+*
*+<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>+*
+...+
*+<ejb-ref>+*
*+<ejb-ref-name>ejb/EmplRecord</ejb-ref-name>+*
*+<ejb-ref-type>Entity</ejb-ref-type>+*
*+<home>com.wombat.empl.EmployeeRecordHome</home>+*
*+<remote>com.wombat.empl.EmployeeRecord</remote>+*
*+<ejb-link>EmployeeRecord</ejb-link>+*
*+</ejb-ref>+*
+...+
*+</session>+*
+...+
*+<entity>+*
*+<ejb-name>EmployeeRecord</ejb-name>+*
*+<home>com.wombat.empl.EmployeeRecordHome</home>+*
*+<remote>com.wombat.empl.EmployeeRecord</remote>+*
+...+
*+</entity>+*
+...+
*+</enterprise-beans>+*
+...+
The Application Assembler uses the ejb-link element to indicate that the EJB reference “Empl-*
Record” declared in the EmployeeService enterprise bean has been linked to the EmployeeRecord*
enterprise bean.</stro
The following example illustrates using the ejb-link element to indicate an enterprise bean reference*
to the ProductEJB enterprise bean that is in the same J2EE application unit but in a different ejb-jar*
file.*
*+<entity>+*
+...+
*+<ejb-name>OrderEJB</ejb-name>+*
*+<ejb-class>com.wombat.orders.OrderBean</ejb-class>+*
+...+
*+<ejb-ref>+*
*+<ejb-ref-name>ejb/Product</ejb-ref-name>+*
*+<ejb-ref-type>Entity</ejb-ref-type>+*
*+<home>com.acme.orders.ProductHome</home>+*
*+<remote>com.acme.orders.Product</remote>+*
*+<ejb-link>../products/product.jar#ProductEJB</ejb-link>+*
*+</ejb-ref>+*
+...+
*+</entity>+*

A error in ejb deployment

Similar Messages

Maybe you are looking for