EJB deployment aborted : UnsupportedClassVersionError

Hi All,
I am working on ejb project , i have created entity , session bean build it successfully. even i hv created EJB application Dc , which also deployed successfully. Then i createde webservice for session bean and tried to deploy , but deployment aborted and i am getting following error.
Mar 12, 2008 3:31:49 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [ThreadDeploy Thread,5,main] INFO:
004Additional log information about the deployment
<!LOGHEADERSTART/>
<!HELPManual modification of the header may cause parsing problem!/>
<!LOGGINGVERSIONhttp://1.5.3.7186 - 630/>
<!NAME[/usr/sap/J2E/JC00/SDM/program/log/sdmcl20080312081657.log]/>
<!PATTERNhttp://sdmcl20080312081657.log/>
<!FORMATTERcom.sap.tc.logging.TraceFormatter(%24d %s: %m)/>
<!ENCODINGISO8859_1/>
<!LOGHEADEREND/>
Mar 12, 2008 1:46:58 PM Info:
Starting deployment
Mar 12, 2008 1:46:58 PM Info: Error handling strategy: OnErrorStop
Mar 12, 2008 1:46:58 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Mar 12, 2008 1:46:58 PM Info: Update strategy: UpdateAllVersions
Mar 12, 2008 1:46:58 PM Info: Starting deployment prerequisites:
Mar 12, 2008 1:46:58 PM Info: Loading selected archives...
Mar 12, 2008 1:46:58 PM Info: Loading archive '/usr/sap/J2E/JC00/SDM/program/temp/temp37374asianpaints.com~probsEA.ear'
Mar 12, 2008 1:47:10 PM Info: Selected archives successfully loaded.
Mar 12, 2008 1:47:10 PM Info: Actions per selected component:
Mar 12, 2008 1:47:10 PM Info: Initial deployment: Selected development component 'probsEA'/'asianpaints.com'/'J2E_BODYSHOP_D'/'20080312153111' will be deployed.
Mar 12, 2008 1:47:11 PM Info: Ending deployment prerequisites. All items are correct.
Mar 12, 2008 1:47:11 PM Info: Saved current Engine state.
Mar 12, 2008 1:47:11 PM Info: Starting: Initial deployment: Selected development component 'probsEA'/'asianpaints.com'/'J2E_BODYSHOP_D'/'20080312153111' will be deployed.
Mar 12, 2008 1:47:11 PM Info: SDA to be deployed: /usr/sap/J2E/JC00/SDM/root/origin/asianpaints.com/probsEA/J2E_BODYSHOP_D/20080312153111/temp37374asianpaints.com~probsEA.ear
Mar 12, 2008 1:47:11 PM Info: Software type of SDA: J2EE
Mar 12, 2008 1:47:11 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2008 1:47:14 PM Info: Begin of log messages of the target system:
08/03/12 13:47:11 - ***********************************************************
08/03/12 13:47:12 - Start updating EAR file...
08/03/12 13:47:12 - start-up mode is lazy
08/03/12 13:47:12 - EAR file updated successfully for 256ms.
08/03/12 13:47:12 - Start deploying ...
08/03/12 13:47:13 - EAR file uploaded to server for 391ms.
08/03/12 13:47:14 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application asianpaints.com/probsEA..
Reason: Exception during generation of components of application asianpaints.com/probsEA in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application asianpaints.com/probsEA in container EJBContainer.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application asianpaints.com/probsEA in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3139)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:539)
... 10 more
Caused by: java.lang.UnsupportedClassVersionError: com/apil/Userdetails/UserdetailsBean (Unsupported major.minor version 50.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at com.sap.engine.frame.core.load.ResourceLoader.loadLocalClass(ResourceLoader.java:262)
at com.sap.engine.frame.core.load.ResourceLoader.loadClass(ResourceLoader.java:127)
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:353)
at com.sap.engine.services.ejb.deploy.xml.CMPParser.parseFields(CMPParser.java:116)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:174)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:297)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:247)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2144)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 16 more
For detailed information see the log file of the Deploy Service.
08/03/12 13:47:14 - ***********************************************************
Mar 12, 2008 1:47:14 PM Info: End of log messages of the target system.
Mar 12, 2008 1:47:14 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2008 1:47:14 PM Error: Aborted: development component 'probsEA'/'asianpaints.com'/'J2E_BODYSHOP_D'/'20080312153111':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application asianpaints.com/probsEA..
Reason: Exception during generation of components of application asianpaints.com/probsEA in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application asianpaints.com/probsEA in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Mar 12, 2008 1:47:27 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Mar 12, 2008 1:47:27 PM Error:
At least one of the Deployments failed
Please help me to resolve this issue
Regards
Ravi

Hi
see whether j2ee engine started or not?
Hazrath

Similar Messages

Deployment Aborted (EJB and Web Services)

Hello All.
In SAP Netweaber Developer Studio I created a Project with an Entity EJB and another Sesion EJB.
The Sesion Bean uses the Entity Bean (persistence). After this, it generate a Web Services.
After building the project ejb and project EAP. Within the Project EAP I took file Persistent_EAP.ear and to make respective deploy on the Server, in the Deploy out View I get the message 'Deploy Aborted'.
The log of the message say,
++Sep 30, 2011 5:43:05 PM Info: - Starting deployment -++
++Sep 30, 2011 5:43:05 PM Info: Error handling strategy: OnErrorStop++
++Sep 30, 2011 5:43:05 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop++
Sep 30, 2011 5:43:05 PM Info: Update strategy: UpdateAllVersions
Sep 30, 2011 5:43:05 PM Info: Starting deployment prerequisites:
Sep 30, 2011 5:43:10 PM Info: Loading selected archives...
Sep 30, 2011 5:43:10 PM Info: Loading archive 'C:\usr\sap\J2E\JC01\SDM\program\temp\temp38292Persistencia_Mod_EAP.ear'
Sep 30, 2011 5:43:16 PM Info: Selected archives successfully loaded.
Sep 30, 2011 5:43:16 PM Info: Actions per selected component:
Sep 30, 2011 5:43:16 PM Info: Update: Selected development component 'Persistencia_Mod_EAP'/'sap.com'/'localhost'/'2011.09.30.16.03.19'/'1' updates currently deployed development component 'Persistencia_Mod_EAP'/'sap.com'/'localhost'/'2011.09.30.16.03.19'/'0'.
Sep 30, 2011 5:43:16 PM Info: Ending deployment prerequisites. All items are correct.
Sep 30, 2011 5:43:16 PM Info: Saved current Engine state.
Sep 30, 2011 5:43:16 PM Info: Starting: Update: Selected development component 'Persistencia_Mod_EAP'/'sap.com'/'localhost'/'2011.09.30.16.03.19'/'1' updates currently deployed development component 'Persistencia_Mod_EAP'/'sap.com'/'localhost'/'2011.09.30.16.03.19'/'0'.
Sep 30, 2011 5:43:16 PM Info: SDA to be deployed: C:\usr\sap\J2E\JC01\SDM\root\origin\sap.com\Persistencia_Mod_EAP\localhost\1\2011.09.30.16.03.19\temp38292Persistencia_Mod_EAP.ear
Sep 30, 2011 5:43:16 PM Info: Software type of SDA: J2EE
Sep 30, 2011 5:43:16 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 30, 2011 5:46:13 PM Info: Begin of log messages of the target system:
11/09/30 17:43:16 - ***********************************************************
11/09/30 17:43:21 - Start updating EAR file...
11/09/30 17:43:21 - start-up mode is lazy
11/09/30 17:43:22 - EAR file updated successfully for 922ms.
11/09/30 17:43:22 - Start updating...
11/09/30 17:43:25 - EAR file uploaded to server for 1594ms.
11/09/30 17:46:13 - ERROR: Not updated. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/Persistencia_Mod_EAP..
                     Reason: Webservices common deployment exception! The reason is: Error occurred, trying to update web services for application sap.com/Persistencia_Mod_EAP. . Additional info: none; nested exception is:
                     +     java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to update web services for application sap.com/Persistencia_Mod_EAP. . Additional info: none+
I don't know what is wrong, when say: Error occurred, trying to update web services for application...
Could someone please help me?
Thanks in advanced,
Esther

Dear Esther,
This exception usually happens when the application is not packaged properly.
It seems that the J2EE engine web services deployment processor is looking for a descriptor which is absent in the jar file.
This could happen for instance if you forget to save all the modified files before rebuilding.
Unfortunately I cannot tell you which web service descriptor is missing, without looking at the packaged application.
Try the following:
1) Regenerate your virtual interfaces
2) Save all modified files
3) Rebuild the application
4) Deploy the application again.
Best Regards,
Abhishek

Error in deployment JAva Module : deployment aborted

Hi,
yesterday i posted a message (cfr java.lang.NoSuchMethodError
Posted: Aug 28, 2007 10:54 AM )
There was some advice that i don't have to watch out the error. Some told me it was concerning a anti-virus programme (which doesn't run in this environment)
so i deploy it with this error :
could someone guide me thru the solution?
thx in advance , points will be given for good answers , i don't gave points at earlier post because it wasn't helpfull
Gwen
error message :
29-aug-2007 12:50:32 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : sideshow-mel
SDM port : 50018
URL to deploy : file:/C:/Users/Admin/AppData/Local/Temp/temp13798ExcelFileAdapterModuleApplication.ear
Result
=> deployment aborted : file:/C:/Users/Admin/AppData/Local/Temp/temp13798ExcelFileAdapterModuleApplication.ear
Aborted: development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication.. Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is:      com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
additional information:
29-aug-2007 12:50:32 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[001]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\XID\DVEBMGS00\SDM\program\log\sdmcl20070829125021.log]/>
<!PATTERN[sdmcl20070829125021.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Aug 29, 2007 2:50:21 PM Info: -
Starting deployment -
Aug 29, 2007 2:50:21 PM Info: Error handling strategy: OnErrorStop
Aug 29, 2007 2:50:21 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Aug 29, 2007 2:50:21 PM Info: Update strategy: UpdateAllVersions
Aug 29, 2007 2:50:21 PM Info: Starting deployment prerequisites:
Aug 29, 2007 2:50:24 PM Info: Loading selected archives...
Aug 29, 2007 2:50:24 PM Info: Loading archive 'C:\usr\sap\XID\DVEBMGS00\SDM\program\temp\temp13798ExcelFileAdapterModuleApplication.ear'
Aug 29, 2007 2:50:25 PM Info: Selected archives successfully loaded.
Aug 29, 2007 2:50:25 PM Info: Actions per selected component:
Aug 29, 2007 2:50:25 PM Info: Initial deployment: Selected development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0' will be deployed.
Aug 29, 2007 2:50:25 PM Info: Ending deployment prerequisites. All items are correct.
Aug 29, 2007 2:50:25 PM Error: Unable to compare host[sideshow-mel] and host[PC4D] Throwable: java.net.UnknownHostException Throwable message: PC4D
Aug 29, 2007 2:50:25 PM Info: Saved current Engine state.
Aug 29, 2007 2:50:25 PM Info: Starting: Initial deployment: Selected development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0' will be deployed.
Aug 29, 2007 2:50:25 PM Info: SDA to be deployed: C:\usr\sap\XID\DVEBMGS00\SDM\root\origin\sap.com\ExcelFileAdapterModuleApplication\localhost\0\2007.07.25.10.07.01\temp13798ExcelFileAdapterModuleApplication.ear
Aug 29, 2007 2:50:25 PM Info: Software type of SDA: J2EE
Aug 29, 2007 2:50:27 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 29, 2007 2:50:28 PM Error: Unable to compare host[sideshow-mel] and host[PC4D] Throwable: java.net.UnknownHostException Throwable message: PC4D
Aug 29, 2007 2:50:31 PM Info: Begin of log messages of the target system:
07/08/29 14:50:28 - ***********************************************************
07/08/29 14:50:29 - Start updating EAR file...
07/08/29 14:50:29 - start-up mode is lazy
07/08/29 14:50:29 - EAR file updated successfully for 125ms.
07/08/29 14:50:29 - Start deploying ...
07/08/29 14:50:29 - EAR file uploaded to server for 94ms.
07/08/29 14:50:31 - ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication..
                     Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is:
                          com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                          at java.security.AccessController.doPrivileged(Native Method)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                     Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
                          ... 10 more
                     Caused by: java.lang.NoClassDefFoundError: com/sap/aii/af/mp/module/Module
Loader Info -
                     ClassLoader name: [Deployment:Runtime:sap.com/ExcelFileAdapterModuleApplication]
                      Parent loader name: [Frame ClassLoader]
                      References:
                        common:service:http;service:servlet_jsp
                        service:ejb
                        common:service:iiop;service:naming;service:p4;service:ts
                        service:jmsconnector
                        library:jsse
                        library:servlet
                        common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
                        library:ejb20
                        library:j2eeca
                        library:jms
                        library:opensql
                        common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
                        interface:resourcecontext_api
                        interface:webservices
                        interface:cross
                        interface:ejbserialization
                        library:com.sap.aii.ai.lib
                        service:com.sap.aii.adapter.xi.svc
                        service:com.sap.aii.af.svc
                        service:com.sap.aii.af.cpa.svc
                      Resources:
                        C:\usr\sap\XID\DVEBMGS00\j2ee\cluster\server0\temp\deploy\1188391830231
                        C:\usr\sap\XID\DVEBMGS00\j2ee\cluster\server0\temp\deploy\1188391830231\ExcelFileAdapterModule.jar
                      Loading model: {parent,references,local}
                     The error occurred while trying to load "com.kk.ExcelModule.GetExcelFileBean".
                          at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
                          at com.sap.engine.services.ejb.deploy.verifier.CheckUtils.loadClass(CheckUtils.java:25)
                          at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:42)
                          at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
                          at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
                          at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
                          at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                          ... 16 more
                     For detailed information see the log file of the Deploy Service.
07/08/29 14:50:31 - ***********************************************************
Aug 29, 2007 2:50:31 PM Info: End of log messages of the target system.
Aug 29, 2007 2:50:31 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 29, 2007 2:50:31 PM Error: Aborted: development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication..
Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Aug 29, 2007 2:50:31 PM Info: Starting to save the repository
Aug 29, 2007 2:50:32 PM Info: Finished saving the repository
Aug 29, 2007 2:50:32 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Aug 29, 2007 2:50:32 PM Error: -
At least one of the Deployments failed -
Message was edited by:
        Gwen Baert

Hi,
yesterday i posted a message (cfr java.lang.NoSuchMethodError
Posted: Aug 28, 2007 10:54 AM )
There was some advice that i don't have to watch out the error. Some told me it was concerning a anti-virus programme (which doesn't run in this environment)
so i deploy it with this error :
could someone guide me thru the solution?
thx in advance , points will be given for good answers , i don't gave points at earlier post because it wasn't helpfull
Gwen
error message :
29-aug-2007 12:50:32 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : sideshow-mel
SDM port : 50018
URL to deploy : file:/C:/Users/Admin/AppData/Local/Temp/temp13798ExcelFileAdapterModuleApplication.ear
Result
=> deployment aborted : file:/C:/Users/Admin/AppData/Local/Temp/temp13798ExcelFileAdapterModuleApplication.ear
Aborted: development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication.. Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is:      com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
additional information:
29-aug-2007 12:50:32 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[001]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\XID\DVEBMGS00\SDM\program\log\sdmcl20070829125021.log]/>
<!PATTERN[sdmcl20070829125021.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Aug 29, 2007 2:50:21 PM Info: -
Starting deployment -
Aug 29, 2007 2:50:21 PM Info: Error handling strategy: OnErrorStop
Aug 29, 2007 2:50:21 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Aug 29, 2007 2:50:21 PM Info: Update strategy: UpdateAllVersions
Aug 29, 2007 2:50:21 PM Info: Starting deployment prerequisites:
Aug 29, 2007 2:50:24 PM Info: Loading selected archives...
Aug 29, 2007 2:50:24 PM Info: Loading archive 'C:\usr\sap\XID\DVEBMGS00\SDM\program\temp\temp13798ExcelFileAdapterModuleApplication.ear'
Aug 29, 2007 2:50:25 PM Info: Selected archives successfully loaded.
Aug 29, 2007 2:50:25 PM Info: Actions per selected component:
Aug 29, 2007 2:50:25 PM Info: Initial deployment: Selected development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0' will be deployed.
Aug 29, 2007 2:50:25 PM Info: Ending deployment prerequisites. All items are correct.
Aug 29, 2007 2:50:25 PM Error: Unable to compare host[sideshow-mel] and host[PC4D] Throwable: java.net.UnknownHostException Throwable message: PC4D
Aug 29, 2007 2:50:25 PM Info: Saved current Engine state.
Aug 29, 2007 2:50:25 PM Info: Starting: Initial deployment: Selected development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0' will be deployed.
Aug 29, 2007 2:50:25 PM Info: SDA to be deployed: C:\usr\sap\XID\DVEBMGS00\SDM\root\origin\sap.com\ExcelFileAdapterModuleApplication\localhost\0\2007.07.25.10.07.01\temp13798ExcelFileAdapterModuleApplication.ear
Aug 29, 2007 2:50:25 PM Info: Software type of SDA: J2EE
Aug 29, 2007 2:50:27 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 29, 2007 2:50:28 PM Error: Unable to compare host[sideshow-mel] and host[PC4D] Throwable: java.net.UnknownHostException Throwable message: PC4D
Aug 29, 2007 2:50:31 PM Info: Begin of log messages of the target system:
07/08/29 14:50:28 - ***********************************************************
07/08/29 14:50:29 - Start updating EAR file...
07/08/29 14:50:29 - start-up mode is lazy
07/08/29 14:50:29 - EAR file updated successfully for 125ms.
07/08/29 14:50:29 - Start deploying ...
07/08/29 14:50:29 - EAR file uploaded to server for 94ms.
07/08/29 14:50:31 - ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication..
                     Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is:
                          com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                          at java.security.AccessController.doPrivileged(Native Method)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                     Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
                          ... 10 more
                     Caused by: java.lang.NoClassDefFoundError: com/sap/aii/af/mp/module/Module
Loader Info -
                     ClassLoader name: [Deployment:Runtime:sap.com/ExcelFileAdapterModuleApplication]
                      Parent loader name: [Frame ClassLoader]
                      References:
                        common:service:http;service:servlet_jsp
                        service:ejb
                        common:service:iiop;service:naming;service:p4;service:ts
                        service:jmsconnector
                        library:jsse
                        library:servlet
                        common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
                        library:ejb20
                        library:j2eeca
                        library:jms
                        library:opensql
                        common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
                        interface:resourcecontext_api
                        interface:webservices
                        interface:cross
                        interface:ejbserialization
                        library:com.sap.aii.ai.lib
                        service:com.sap.aii.adapter.xi.svc
                        service:com.sap.aii.af.svc
                        service:com.sap.aii.af.cpa.svc
                      Resources:
                        C:\usr\sap\XID\DVEBMGS00\j2ee\cluster\server0\temp\deploy\1188391830231
                        C:\usr\sap\XID\DVEBMGS00\j2ee\cluster\server0\temp\deploy\1188391830231\ExcelFileAdapterModule.jar
                      Loading model: {parent,references,local}
                     The error occurred while trying to load "com.kk.ExcelModule.GetExcelFileBean".
                          at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
                          at com.sap.engine.services.ejb.deploy.verifier.CheckUtils.loadClass(CheckUtils.java:25)
                          at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:42)
                          at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
                          at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
                          at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
                          at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                          ... 16 more
                     For detailed information see the log file of the Deploy Service.
07/08/29 14:50:31 - ***********************************************************
Aug 29, 2007 2:50:31 PM Info: End of log messages of the target system.
Aug 29, 2007 2:50:31 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 29, 2007 2:50:31 PM Error: Aborted: development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication..
Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Aug 29, 2007 2:50:31 PM Info: Starting to save the repository
Aug 29, 2007 2:50:32 PM Info: Finished saving the repository
Aug 29, 2007 2:50:32 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Aug 29, 2007 2:50:32 PM Error: -
At least one of the Deployments failed -
Message was edited by:
        Gwen Baert

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

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 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:<I> <ConMan> Bootstrap unable to get a http connection to localhost/127.0.0.1Wed May 02 12:28:30 CDT 2001:<I> <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.

Deployment aborted while deploying a webdynpro application

Hi SDNers,
While deploying a webdynpro application deployment aborted and shown the following error.
Aug 8, 2006 4:51:38 PM /userOut/deploy
(com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]]
ERROR:
[010]Deployment aborted
Settings
SDM host : incata90
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/veer/LOCALS1/Temp/temp9590TutWD_DynamicForm.ear
Deployment exception : Server incata90 did not accept login request as apiadmin on port
50018 - Cannot log in. There are already active sessions:
Session id 8 / An administrator logged in via API /
Inner exception was :
Server incata90 did not accept login request as apiadmin on port 50018 - Cannot log in.
There are already active sessions:
Session id 8 / An administrator logged in via API /
can somebody help me in resolving this problem?
Regards
Veeru

Hi,
Sometimes I get this error. It is usually solved by restarting the SDM server.
Switch to the J2EE Engine view in NWDS and right click the SDM server. Restart process.
Good luck,
Roelof

EAR Deployment Aborted...

I am creating a servlet client to test a secured web service (Document Authentication Basic (Username/Password)).
When I deploy the EAR,I get error:
Result
=> deployment aborted : file:/C:/DOCUME~1/uname/LOCALS~1/Temp/temp1530011368822716654CapsWS_EAR.ear
Aborted: development component 'CapsWS_EAR'/'sap.com'/'localhost'/'2009.08.21.09.06.42'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/CapsWS_EAR.ear. Reason: Cannot make reference between sap.com/CapsWS_EAR and sap.com/CapsWS_EAR. Cycle of references is created, which is not allowed for the current version of the server.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
The version of J2EE engine is 7.00 SP17
Anybody have any idea how to resolve this...
Do I need an upgrade for this ?
Thanks
Srinivas
Edited by: srinivas M on Aug 21, 2009 5:55 PM

Hi Srinivas,
The reason is clear:
Reason: Cannot make reference between sap.com/CapsWS_EAR and sap.com/CapsWS_EAR. Cycle of references is created, which is not allowed for the current version of the server
You may have created an entry for the same EAR in the application.xml file of your EAR Project. Remove it and redeploy.
Regards,
Alka.

Can't access EJB deployed on remote OC4J - what am I doing wrong?

I'm unable to access an EJB deployed on a remote OC4J instance (ie, part of a 9iAS installation on another machine vs local in JDeveloper).
I've reverted to a stupid-simple EJB in hopes of getting it going prior to trying my actual code. The EJB works fine in JDev (9.0.3) - I 'run' the EJB to start the local OC4J instance, run my client code (generated via the "New Sample Java Client..." option in the Navigator context popup) and all is well.
I then create an EAR file via the the "Create EJB Jar Deployment Profile..." context popup of the ejb-jar.xml node, followed by "Deploy to EAR file" from the context popup of the resulting ejb1.deploy node. I next "Deploy EAR File" via the "Oracle Enterprise Manager" that comes with 9iAS (the :1810 port). After successfully deploying, I modify my client code in JDeveloper, specifying the new connection information for the remote machine via the Hashtable constructor of InitialContext and attempt to run it. I've tried a number of Context.PROVIDER_URL forms, including: ormi://registered_pingable_host_name:23791/deployed_application_name
ormi://registered_pingable_host_name:23791/session_deployment_name (from the <enterprise-beans><session-deployment name="xxx"/></enterprise-beans> section of my orion-ejb-jar.xml file, as per a tip in this forum)
I've tried prefixing ormi:// with http:, but get no response whatesoever in this case.
I've also tried it without the port number (this port number matches that in my remote OC4J's <oc4j_instance_home>/config/rmi.xml file).
On the Context.SECURITY_PRINCIPAL and Context.SECURITY_CREDENTIALS settings, I've tried various values, generally using the 'admin' user, with passwords taken from:
<oc4j_instance_home>/principals.xml
<oc4j_instance_home>/application-deployments/application_name/principals.xml
I've also tried matching the password in the jazn-data.xml, to no avail - this password appears encrypted anyway, but thought I'd give it a try on the off-chance that it was just a randomly-generated password - no go.
I've also tried SCOTT/TIGER, anonymous, etc. Incidentally, the 'deactivated' attribute of the <user> tag is set to "false" in my principals.xml files.
No matter what I do, I always get back "javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect"
Additionally, I get this same message when I try to establish an Application Server Connection via JDev.
Clearly, I'm missing something critical (and probably simple), but I can't for the life of me figure it out.
Any help would be much appreciated!
Thanks,
Jim Stoll

Ok, well this is a bit strange...
3103 - 3103 also fails, and some experimentation has led me to find that any time that I specify a range smaller than 6 (3101 - 3106 works, 3101 - 3105, 3101-3101, 3103-3103, etc does not), the OC4J instance will not restart. I get "An error occurred while starting. The opmn request has failed. From opmn: HTTP/1.1 204 No Content Content-Length: 0 Content-Type: text/html Response: 0 of 1 processes started. Check opmn log files such as ipm.log and ons.log for detailed." in the OEM window (I specify the RMI port range, hit Apply, go to the OC4J instance home page, see that the Status is 'Down', hit Start, and get that message.) <ORACLE_HOME>/product/iasinfra/opmn/logs/ipm.log tells me:
02/12/03 09:41:12 There is no rmi port left for starting an OC4J process. Please check oc4j's port property in OPMN's configuration file.
02/12/03 09:41:12 start_proc: UID 3719788: failed to build args
02/12/03 09:41:12 start_proc_req: failed to start a process in GID OC4JJim2, type: 2
If I bump it up to 3101 - 3106 or higher, it starts right up. Running opmnadmin debug, as suggested by Venky (thanks Venky!), yields:
PROCESS TABLE
UID PID FLAGS TYPE STATUS REF HTTP AJP RMI JMS
3654011 84 00000040 OC4J Alive 1 0 3005 3106 3206
424987 604 00000000 Apache Alive 1 7777 0 0 0
2932088 14849 00000000 OC4J Alive 1 0 3003 3103 3203
3063160 14878 00000000 OC4J Alive 1 0 3001 3101 3201
3194232 14906 00000000 OC4J Alive 1 0 3000 3105 3205
3325304 14936 00000000 OC4J Alive 1 0 3002 3102 3202
3456376 14964 00000000 OC4J Alive 1 0 3004 3104 3204
Which is what I would expect, given the specified range of 3101-3106. Trying each of these ports in turn, I've found that I can hit the EJB successfully on 3106, but 3101 - 3105 all fail with:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: No such domain/application: Project7_2; nested exception is:
     javax.naming.AuthenticationException: No such domain/application: Project7_2
     java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
          RMIContext.java:134
     java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
          InitialContext.java:350
     void Samplemypackage9.MySessionEJBClient1.main(java.lang.String[])
          MySessionEJBClient1.java:15
I'm a little concerned about assuming the high-end of the range to be the active port on a regular basis (though thus far, among about 20 - 30 tries spaced over 20 - 30 minutes, it has been...) - I guess I can have my code loop through the range until it finds a good port or exhausts the list, but that seems a bit excessive.
Can you think of a reason that my OC4J instance won't start with a range size of less than 6? I'm on 9iAS 9.0.2, if that makes any difference.
Thanks,
Jim

Memory leak in a client using EJBs deployed in a Bea Weblogic 10.0.0 cluste

Hi all,
We are having a memory leak in a client using stateless EJBs deployed in cluster. The client is a Tomcat 6.0.18 with java 6 but it is reproduced using Tomcat 5 with java 5. The client is calling a Weblogic Server 10.0 making
calls to an EJB deployed in cluster that has two instances installed in two different machines.
The client works fine if we shutdown one of the server instances and so when the client is using only one instance.
Resuming the environment:
Client Side:
1 HP-Itanium machine with HP-UX.
1 Tomcat 6 with java 6 (reproduced with java 5)
Bea Weblogic client (wlclient.jar) for Weblogic 10.0.0
Server Side:
2 HP-Itanium machines with HP-UX
Bea Weblogic Server 10.0.0 installed in both machines
An unique domain
Two Bea instances (one per machines) associated to a Bea Cluster
EJBs deployed in both instances
We have monitored the memory consumed in Tomcat and we have noticed that the VM memory PS OLD GEN grows up permanently when we make tests having the two server side Bea Instances up. We have extended
the memory VM parameters in Tomcat client till 1G and it's only a way to delay the end: the free memory is empty, the GC is not able to free no more byte and the CPU is 100% consumed by the GC work. At the end Tomcat Client
doesn't accept more http petitions and must be restarted.
Besides, we have studied the VM memory in Tomcat using jmap and importing it using Eclipse Memory Analyzer. We have seen some strange memory blocks of several Mbytes that are always growing up and that are stored
under data structures in the package com.sun.corba:
com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl (4.5Mb)
|
-> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl
|
-> java.util.Hashtable
|
-> java.util.Hashtable$Entry
|
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
Has anybody any idea about this problem?
Thanks in advance.

Hi all,
We are having a memory leak in a client using stateless EJBs deployed in cluster. The client is a Tomcat 6.0.18 with java 6 but it is reproduced using Tomcat 5 with java 5. The client is calling a Weblogic Server 10.0 making
calls to an EJB deployed in cluster that has two instances installed in two different machines.
The client works fine if we shutdown one of the server instances and so when the client is using only one instance.
Resuming the environment:
Client Side:
1 HP-Itanium machine with HP-UX.
1 Tomcat 6 with java 6 (reproduced with java 5)
Bea Weblogic client (wlclient.jar) for Weblogic 10.0.0
Server Side:
2 HP-Itanium machines with HP-UX
Bea Weblogic Server 10.0.0 installed in both machines
An unique domain
Two Bea instances (one per machines) associated to a Bea Cluster
EJBs deployed in both instances
We have monitored the memory consumed in Tomcat and we have noticed that the VM memory PS OLD GEN grows up permanently when we make tests having the two server side Bea Instances up. We have extended
the memory VM parameters in Tomcat client till 1G and it's only a way to delay the end: the free memory is empty, the GC is not able to free no more byte and the CPU is 100% consumed by the GC work. At the end Tomcat Client
doesn't accept more http petitions and must be restarted.
Besides, we have studied the VM memory in Tomcat using jmap and importing it using Eclipse Memory Analyzer. We have seen some strange memory blocks of several Mbytes that are always growing up and that are stored
under data structures in the package com.sun.corba:
com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl (4.5Mb)
|
-> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl
|
-> java.util.Hashtable
|
-> java.util.Hashtable$Entry
|
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
Has anybody any idea about this problem?
Thanks in advance.

Issues in looking up a ejb deployed on glassfish from tomcat.

Hi all,
I have followed the steps mentioned in the EJB FAQ in the glassfish site and was able to lookup a remote ejb deployed in glassfish from a standalone client.
In case of standalone client, i set the appropriate jndi properties in the initial context as mentioned in the FAQ and added the 4 jars specified to the classpath of the application.
It all worked perfectly well.
But I attempted to do the same from a servlet running under tomcat.
I set the appropriate jndi properties in the intial context and added 4 jars specified in the lib directory of the war file.
But this did not turn out well and tomcat complained me with some servlet init errors.
Then i searched through the web and found this posting from you:
http://www.archivesat.com/GlassFish_Enterprise_JavaBeans_Developers/thread1399339.htm
Then i created a folder called "shared/lib" under TOMCAT_HOME directory in my machine and ran the same example. Wow.....miraculously the application ran well.
But i found that the "index.jsp" which i configured in the welcome file list does not appear now. But i was able to access the servlet without any problem. And the servlet was able to successfully lookup the ejb deployed in glassfish.
Then i thought, let me try to access the ejb from a jsf application.
Then i created a jsf application in netbeans 5.5.1 and tried to access the bean deployed in glassfish.
(Note: the jsf application runs in tomcat 5.5.17 which is bundled with netbeans)
OOPSS....
Tomcat now complains me that it cannot compile the jsp page..
This is the error i got...
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
C:\Documents and Settings\james\.netbeans\5.5.1\apache-tomcat-5.5.17_base\work\Catalina\localhost\CityExplorer-WebClient1\org\apache\jsp\index_jsp.java:7: org.apache.jsp.index_jsp is not abstract and does not override abstract method getDependants() in org.apache.jasper.runtime.JspSourceDependent
public final class index_jsp extends org.apache.jasper.runtime.HttpJspBase
^
Generated servlet error:
C:\Documents and Settings\james\.netbeans\5.5.1\apache-tomcat-5.5.17_base\work\Catalina\localhost\CityExplorer-WebClient1\org\apache\jsp\index_jsp.java:12: getDependants() in org.apache.jsp.index_jsp cannot implement getDependants() in org.apache.jasper.runtime.JspSourceDependent; attempting to use incompatible return type
found : java.lang.Object
required: java.util.List
public Object getDependants() {
^
2 errors
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
Any ideas...
Can you please help me.
I've noticed that you were eagerly answering questions related to ejb lookup in many places.
I feel there is some potential compatability issue between tomcat and glassfish...
I request you to investigate on this and clarify the community with your response.
Thanks in advance,
James Selvakumar

Thank you guys!
I've found the answer myself.

How to access EJB deployed in JBOSS 4 from Creator

Hello.
I am trying to access EJBs deployed on JBOSS in order to develop a web app client, when I import the EJB set from Creator (sessions and entities packages in a jar file) I got the following error message....."No EJB set found in file....." .
I presume there is an kind of xml file description specific for Sun App Server missing. I would like to know if there is other way to expose EJB in creator?....maybe write a config file by hand.
I already read the tutorials related to EJB but those only use pre build EJB jars for Sun App Sserver.
Also I read all the posted about JBoos and EJB in this forum but those are pretty general.
By the way I have Delegate classes to access the EJB. How do I register my delegates in Creator in order to expose their methods?
I�ll really appreciate some light in this matter.
Thanks in advance!!!

Hi,
The below forum thread may help you :
http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=51321
Thanks,
Runa.

Calling an EJB deployed in OC4J from Java Stored Proc in Oracle

Hello!
Trying to make a call to an EJB deployed in OCJ4 from a oracle java stored proc. After loaded orion.jar and crimson.jar lib into SCOTT schema, I can't get the JNDI Context working because of this error:
============================================
javax.naming.NoInitialContextException: Cannot instantiate class:
com.evermind.server.ApplicationClientInitialContextFactory. Root exception is
java.lang.ClassNotFoundException:
com/evermind/server/ApplicationClientInitialContextFactory
at java.lang.Class.forName0(Class.java)
at java.lang.Class.forName(Class.java)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:45)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java)
at javax.naming.InitialContext.init(InitialContext.java)
at javax.naming.InitialContext.<init>(InitialContext.java)
===============================
I did load the java with "loadjava" with on time with the "resolve" option and time time no option and still no working.
Here is the EJB client code:
=======================================
import java.sql.*;
import java.util.*;
import javax.naming.*;
import com.evermind.server.ApplicationClientInitialContextFactory;
class EmpRemoteCall {
public static void main(String[] args) {
System.out.println(getEmpName());
public static String getEmpName() {
String ejbUrl = "java:comp/env/ejb/Emp";
String username = "admin";
String password = "admin";
Hashtable environment = new Hashtable();
environment.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.ApplicationClientInitialContextFactory");
environment.put(Context.PROVIDER_URL, "ormi://127.0.0.1/testemp");
environment.put(Context.SECURITY_PRINCIPAL, username);
environment.put(Context.SECURITY_CREDENTIALS, password);
//environment.put(Context.SECURITY_AUTHENTICATION, ServiceCtx.NON_SSL_LOGIN);
//environment.put(javax.naming.Context.URL_PKG_PREFIXES, "oracle.aurora.jndi");
com.kboum.sertir.essais.EmpHome homeInterface = null;
try {
Class.forName("com.evermind.server.ApplicationClientInitialContextFactory", true, ClassLoader.getSystemClassLoader());
System.out.println("Creating an initial context");
Context ic = new InitialContext(environment);
System.out.println("Looking for the EJB published as 'java:comp/env/ejb/Emp'");
homeInterface = (com.kboum.sertir.essais.EmpHome) ic.lookup(ejbUrl);
catch (CommunicationException e) {
System.out.println("Unable to connect: " + ejbUrl);
e.printStackTrace();
//System.exit(1);
catch (NamingException e) {
System.out.println("Exception occurred!");
System.out.println("Cause: This may be an unknown URL, or some" +
" classes required by the EJB are missing from your classpath.");
System.out.println("Suggestion: Check the components of the URL," +
" and make sure your project includes a library containing the" +
" EJB .jar files generated by the deployment utility.");
e.printStackTrace();
//System.exit(1);
catch (ClassNotFoundException e) {
System.out.println("Unable to connect: " + ejbUrl);
e.printStackTrace();
//System.exit(1);
try {
System.out.println("Creating a new EJB instance");
com.kboum.sertir.essais.Emp remoteInterface = homeInterface.findByPrimaryKey(Integer.valueOf("7369"));
System.out.println(remoteInterface.getENAME());
System.out.println(remoteInterface.getSAL());
remoteInterface.setSAL(2);
System.out.println(remoteInterface.getSAL());
return remoteInterface.getENAME();
catch (Exception e) {
System.out.println(e.getMessage());
e.printStackTrace();
return "error";
null

What I did to solve this problem was to
create a simple RMI remote object that
resides outside the database JVM and that
serves as a proxy EJB client for your java
stored procedure. The stored procedure can
invoke a method on the remote RMI object
which then looks up the EJBean's home
interface and invokes the relevant method on
the bean's remote interface, and relays any
return values back to the java stored
procedure.
Hope this helps,
Avi.
null

EJB deployment Warning

Hi I´m facing this problem, I test the queue destination with an external client and everything is ok, but then when I try to deploy the Message - Driver - bean on CE the next error comes out , any help will be appreciated.
--- Deploying file(s):
     C:Documents and Settingse100009workspace.jdi xenapjmsEAR xenapjmsEAR.ear
--- Status:
     Deploy finished with warnings.
--- Description:
            S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed:           0
Deployed with warnings:           1
Failed deployments:                0
~~~~~~~~~~~~~~~~~~~
1. File:C:Documents and Settingse100009workspace.jdi xenapjmsEAR xenapjmsEAR.ear
     Name:fxenapjmsEAR
     Vendor:com.sap
     Location:localhost
     Version:2010.02.02.12.47.07
     Deploy status:Warning
     Version:HIGHER
     Description:
          1. Warning occurred on server 9111850 during update com.sap/fxenapjmsEAR : SessionsTakerTest: Following tests could not be executed because of failed precondition test "SessionsTakerTest" : Classes Exposure Check, Business Interfaces Check, file: fxenapjms.jar, column -1, line -1, severity: warning
          2. Exception has been returned while the [com.sap/fxenapjmsEAR] was starting. Warning/Exception :[
][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 9111850:The destination jmsqueues/default/sapDemoQueue cannot be looked up. Last attempt performed : jms_vendor_queues_global/jmsqueues/default/sapDemoQueue
           -> Path to object does not exist at jmsqueues, the whole lookup name is jms_vendor_queues_global/jmsqueues/default/sapDemoQueue.
server ID 9111850:com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean com.sap/fxenapjmsEAR*annotation|fxenapjms.jar*annotation|fxenapmjbBean
     at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:903)
     at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:435)
     at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:228)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:186)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:286)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:555)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3432)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3418)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3308)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3280)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.ejb3.container.ActionException: Cannot activate endpoint for message-driven bean com.sap/fxenapjmsEAR*annotation|fxenapjms.jar*annotation|fxenapmjbBean
     at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:94)
     at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
     at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:59)
     at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:897)
     ... 35 more
Caused by: javax.resource.NotSupportedException: javax.resource.spi.UnavailableException: The destination jmsqueues/default/sapDemoQueue cannot be looked up. Last attempt performed : jms_vendor_queues_global/jmsqueues/default/sapDemoQueue
     at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:128)
     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:531)
     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findResourceAdapterByName(EndpointActivationImpl.java:155)
     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findAdapter(EndpointActivationImpl.java:86)
     at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:59)
     at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:84)
     ... 38 more
Caused by: javax.resource.spi.UnavailableException: The destination jmsqueues/default/sapDemoQueue cannot be looked up. Last attempt performed : jms_vendor_queues_global/jmsqueues/default/sapDemoQueue
     at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:361)
     at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:126)
     at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:115)
     ... 43 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsqueues, the whole lookup name is jms_vendor_queues_global/jmsqueues/default/sapDemoQueue.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:184)
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:489)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:321)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:619)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:359)
     ... 45 more

It means that bean classes are in the system classpath and therefore
cannot be reloaded. If you do not plan on hot-redeploying your beans
you can ignore this message.
Dragan-Sassler <[email protected]> wrote:
Hi,
i have developed some EJB, that are dependent from each others.
So I set the classpath to a lib-directory with my EJB.
When i try to deploy, i become a warning
<Warning> <EJB> <EJB Deployment: Fnv cannot be redeployed while the server is
running. de.dr_staedtler.extern.audi.fnv.data.ejb.FnvBean is located in the server's
classpath.>
But the EJB's are deployed and the client can connect it.
Why is the warning? It is important or I can ignore it?
Thanks for your time.
dragan-sassler--
Dimitri

HFM EPMA application deployment aborted with error Object reference not set

HFM EPMA application deployment aborted with error Object reference not set to an instance of an object when trying to validate/deploy any HFM application in EPMA. This has started happending after we have deleted a Dimension in one of HFM applications. The deleted dimension is a shared dimension.
We are facing this issue in a distributed environment with version 11.1.2.1. This applications are built here newly.
Following is the error log entry
16] ERROR Object reference not set to an instance of an object.
at Hyperion.DimensionServer.CompareCriteria.<>c__DisplayClass5.<GetMemberClassProperties>b__4(Dimension dim)
at Hyperion.DimensionServer.Library.IterateDimensions(Action`1 action)
at Hyperion.DimensionServer.CompareCriteria.GetMemberClassProperties(ApplicationClass appClass, DimensionClass dimClass, MemberClass mbrClass)
at Hyperion.DimensionServer.CompareCriteria.GetCommonMemberClassProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass)
at Hyperion.DimensionServer.CompareMemberEvaluator.CompareProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass, List`1 propertyDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(RelationshipMember sourceMember, Application sourceApp, Application targetApp, Boolean firstPass, Int32 level, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(List`1 sourceTopMembers, List`1 targetTopMembers, Application sourceApp, Application targetApp, Boolean firstPass, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Execute(List`1 fromTopMembers, List`1 toTopMembers, Dimension fromDimension, Dimension toDimension, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareDimensionEvaluator.Execute(Dimension fromDimension, Dimension toDimension, ApplicationClass fromAppClass, ApplicationClass toAppClass)
at Hyperion.DimensionServer.CompareEngine.CompareDimensions(Dimension fromDimension, Dimension toDimension)
at Hyperion.DimensionServer.CompareEngine.StartCompare()
at Hyperion.DimensionServer.Validations.HFMApplicationValidation.CheckStaticDimension(Library snapShot, Dimension dim, Application oldApp, String[] skipProperties)
at Hyperion.DimensionServer.Validations.HFMApplicationValidation.CheckStaticDimensions(Application baselineApp)
at Hyperion.DimensionServer.Validations.ApplicationValidation.ValidateAgainstBaseline()
at Hyperion.DimensionServer.Validations.HFMApplicationValidation.InternalValidate()
at Hyperion.DimensionServer.Validations.ApplicationValidation.Validate()
at Hyperion.DimensionServer.Validations.ApplicationValidation.<ValidateAsync>b__0()System.NullReferenceException: Object reference not set to an instance of an object.
at Hyperion.DimensionServer.CompareCriteria.<>c__DisplayClass5.<GetMemberClassProperties>b__4(Dimension dim)
at Hyperion.DimensionServer.Library.IterateDimensions(Action`1 action)
at Hyperion.DimensionServer.CompareCriteria.GetMemberClassProperties(ApplicationClass appClass, DimensionClass dimClass, MemberClass mbrClass)
at Hyperion.DimensionServer.CompareCriteria.GetCommonMemberClassProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass)
at Hyperion.DimensionServer.CompareMemberEvaluator.CompareProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass, List`1 propertyDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(RelationshipMember sourceMember, Application sourceApp, Application targetApp, Boolean firstPass, Int32 level, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(List`1 sourceTopMembers, List`1 targetTopMembers, Application sourceApp, Application targetApp, Boolean firstPass, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Execute(List`1 fromTopMembers, List`1 toTopMembers, Dimension fromDimension, Dimension toDimension, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareDimensionEvalua
There was a bug in earlier releases for deleting dimensions with children, making the children orphans.
Heard from release notes that it has been fixed, but we are seeing this issue in 11.1.2.1 again.
Please help us out in resolving this error.

Hi,
I always ask this first, have you installed all the planning and epma patches as there have been many issues addressed in 9.3.1
Cheers
John
http://john-goodwin.blogspot.com/

EJB deployment aborted : UnsupportedClassVersionError

Similar Messages

Maybe you are looking for