Error when deploy Java Proxy Server EAR to PI

We are trying to deploy our Java Proxy Server EAR to PI using Visual Administrator. However, it gives the following error:
Deploy of the ear has errors :
java.rmi.RemoteException: Cannot deploy application sap.com/TestBatch
Reason: Errors while compiling:
.... .java:91 illegal escape character
if (method.equals("U0024descriptor")) { ....
We have tried to deploy the same EAR to another PI system and it works fine. As a result, we think we might have missed something when installing or configuring this PI but don't have a clue where to start. We have also tried deploying using SDM but also didn't succeed.

Hi Pikad !
I understand that it the very same EAR deployed with no hassle in another PI, here it should work ok, but I think you should check the backslash you are using. If you need to use the backslash character, you must use ("
U0024descriptor") or change the U to \u0024 for the dollar sign.
Check:
Regards,
Matias.

Similar Messages

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

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

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

Error when deploying a new forms .ear file

Hi all
I get the following eror when trying to start forms:
Starting OPMN managed FORMS OC4J instance ...
Calling txkChkFormsDeployment.pl to check whether latest FORMSAPP.EAR is deployed...
Program : /u01/apps/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkChkFormsDeployment.pl started @ Tue Nov 16 11:16:23 2010
*** Log File = /u01/apps/inst/apps/DEV_ikhsmappdev1/logs/appl/rgf/TXK/txkChkFormsDeployment_Tue_Nov_16_11_16_23_2010/txkChkFormsDeployment_Tue_Nov_16_11_16_23_2010.log
File "/u01/apps/apps/tech_st/10.1.3/j2ee/forms/applications/forms/formsweb/WEB-INF/lib/frmsrv.jar" exists. Proceeding to check the size...
=================================================
*** Latest formsapp.ear has NOT been deployed ***
Deploying the latest EAR file...
=================================================
Program : /u01/apps/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkChkFormsDeployment.pl completed @ Tue Nov 16 11:16:30 2010
* W A R N I N G *
Error while executing the perl script txkChkFormsDeployment.pl
We have determined that you need to redeploy Forms (using txkChkFormsDeployment.pl).
But could not do it automatically for you, due to some issues.
For details refer the log files.
Follow Note: 397174.1 to redeploy Forms manually.
I then try and deploy a new Forms EAR file as per doc 397174.1 and run into errors as follows:
Errors encountered running /u01/apps/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkCfgOC4JApp.pl
*******FATAL ERROR*******
PROGRAM : /u01/apps/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkCfgOC4JApp.pl(/u01/apps/apps/apps_st/appl/fnd/12.0.0/bin/txkrun.pl)
TIME : Tue Nov 16 16:33:03 2010
FUNCTION: (eval) [ Level 1 ]
ERRORMSG: Invalid 10.1.3 Oracle Home: /u01/apps/apps/tech_st/10.1.3
How do I fix this?

Still the same issue, yes.
I have already logged an SR for this, but all is very quiet on that front.
One funny, is that this HOME was never attached to the orainst.loc, so I did it manually.
When I try and run opatch with lsinventory parm, it does not list any patches, although there are patches installed, if you look at $OH/.patch_storage.
Any idea of how I should attach this home correctly?

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

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

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

Error when deploying ear file

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

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

Getting Error when deploying the WD application

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

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

Gettind error when deploying XI module

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

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

Error when starting Java(TM) ME Platform SDK 3.0

hey guys, I get this error when starting Java(TM) ME Platform SDK 3.0. When I installed it it installed 'successfully' and then I double clicked the file on the desktop (I'm using Windows Vista 32bit Home premium) and it gave me the following error when saying 'Starting Modules':-------------------------------------------------------------------------------
Log Session: Sunday, February 13, 2011 1:52:25 PM GMT
System Info: Product Version = Java(TM) ME Platform SDK 3.0
Operating System = Windows Vista version 6.0 running on x86
Java; VM; Vendor = 1.6.0_23; Java HotSpot(TM) Client VM 19.0-b09; Sun Microsystems Inc.
Runtime = Java(TM) SE Runtime Environment 1.6.0_23-b05
Java Home = C:\Program Files\Java\jdk1.6.0_23\jre
System Locale; Encoding = en_GB (cdctoolbar); Cp1252
Home Directory = C:\Users\Molten Ice
Current Directory = C:\Program Files\Java\Java_ME_platform_SDK_3.0\bin
User Directory = C:\Users\Molten Ice\javame-sdk\toolbar\3.0
Installation = C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\javamesdk1
 C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\ide10
 C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\java2
 C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\mobility8
 C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\profiler2
 C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9
Boot & Ext. Classpath = C:\Program Files\Java\jdk1.6.0_23\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\rt.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\jce.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\modules\jdk.boot.jar;C:\Program Files\Java\jdk1.6.0_23\jre\classes;C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext\dnsns.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext\localedata.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext\sunjce_provider.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext\sunmscapi.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext\sunpkcs11.jar
Application Classpath = C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9\lib\boot.jar;C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9\lib\org-openide-modules.jar;C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9\lib\org-openide-util.jar;C:\Program Files\Java\jdk1.6.0_23\lib\dt.jar;C:\Program Files\Java\jdk1.6.0_23\lib\tools.jar
Startup Classpath = C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9\core\core.jar;C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9\core\org-openide-filesystems.jar;C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\javamesdk1\core\locale\core_cdctoolbar.jar
WARNING [org.netbeans.core.projects.cache]: Inefficient to include an empty layer in a module: jar:file:/C:/Program%20Files/Java/Java_ME_platform_SDK_3.0/toolbar/javamesdk1/modules/org-netbeans-modules-javame-common.jar!/org/netbeans/modules/javame/common/resources/layer.xml
WARNING [org.netbeans.core.projects.cache]: Inefficient to include an empty layer in a module: jar:file:/C:/Program%20Files/Java/Java_ME_platform_SDK_3.0/toolbar/javamesdk1/modules/org-netbeans-modules-e2e.jar!/org/netbeans/modules/e2e/layer.xml
WARNING [org.openide.filesystems.Ordering]: Not all children in Services/MIMEResolver/ marked with the position attribute: [org-netbeans-modules-javame-netmon-data-NetMonDataResolver.xml], but some are: [org-netbeans-modules-java-mime-resolver.xml, org-apache-tools-ant-module-mime-resolver.xml, org-netbeans-modules-editor-settings-storage-mime-resolver.xml, org-netbeans-modules-url-mime-resolver.xml, org-netbeans-modules-pdf-mime-resolver.xml, org-netbeans-modules-jar-mime-resolver.xml, org-netbeans-modules-editor-codetemplates-mime-resolver.xml]
WARNING [org.openide.filesystems.Ordering]: Not all children in Services/MIMEResolver/ marked with the position attribute: [org-netbeans-modules-javame-netmon-data-NetMonDataResolver.xml], but some are: [org-netbeans-modules-java-mime-resolver.xml, org-apache-tools-ant-module-mime-resolver.xml, org-netbeans-modules-editor-settings-storage-mime-resolver.xml, org-netbeans-modules-url-mime-resolver.xml, org-netbeans-modules-pdf-mime-resolver.xml, org-netbeans-modules-jar-mime-resolver.xml, org-netbeans-modules-editor-codetemplates-mime-resolver.xml]
[ 0] INFO - ootstrap.PropertyEditorManager - Registering custom property editors
[ 117] INFO - bootstrap.ObjectGraphProcessor - Consolidating dependencies...
[ 217] INFO - bootstrap.ObjectGraphProcessor - Consolidated dependencies...
[ 317] INFO - bootstrap.ObjectGraphProcessor - Calculating order...
[ 417] INFO - bootstrap.ObjectGraphProcessor - Calculated order
[ 523] INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[ 627] INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[ 732] INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[ 832] INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[ 932] INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[ 1032] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 2166] WARN - mpl.ObjectServerConnectionImpl - Remote object server is not running at service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 2268] INFO - l.process.GenericProcessRunner - Starting process: C:\Program Files\Java\Java_ME_platform_SDK_3.0/bin/device-manager.exe
[ 3384] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 5476] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 7576] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 9677] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 11777] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 13877] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 15977] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 18077] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 20177] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 22277] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 23379] ERROR - un.jme.toolkit.bootstrap.Batch - Problem calling start() on DeviceManagerConnection
java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.sun.jme.toolkit.bootstrap.Batch.invoke(Unknown Source)
 at com.sun.jme.toolkit.bootstrap.Batch.tryInvoke(Unknown Source)
 at com.sun.jme.toolkit.bootstrap.Batch.startObjects(Unknown Source)
 at org.netbeans.modules.javame.common.container.Module.start(Module.java:21)
 at org.netbeans.modules.javame.common.container.ContainerSupport.startModule(ContainerSupport.java:67)
 at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManagerConnection(DevicemanagerHelper.java:41)
 at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.ensureConnected(DevicemanagerHelper.java:48)
 at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManager(DevicemanagerHelper.java:84)
 at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.ensureDMStarted(AutoInstaller.java:292)
 at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.restored(AutoInstaller.java:63)
 at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:421)
 at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:342)
 at org.netbeans.ModuleManager.enable(ModuleManager.java:906)
 at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:428)
 at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:364)
 at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276)
 at org.netbeans.core.startup.Main.getModuleSystem(Main.java:165)
 at org.netbeans.core.startup.Main.start(Main.java:312)
 at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110)
 at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
 java.net.ConnectException: Connection refused: connect]
 at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
 at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
 at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.connect(Unknown Source)
 at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.start(Unknown Source)
 ... 24 more
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
 java.net.ConnectException: Connection refused: connect]
 at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
 at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
 at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
 at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
 ... 27 more
Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
 java.net.ConnectException: Connection refused: connect
 at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
 at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
 at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
 at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
 at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
 at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
 ... 32 more
Caused by: java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
 at java.net.Socket.connect(Socket.java:529)
 at java.net.Socket.connect(Socket.java:478)
 at java.net.Socket.<init>(Socket.java:375)
 at java.net.Socket.<init>(Socket.java:189)
 at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
 at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
 at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
 ... 37 more
SEVERE [org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper]: Cannot connect to device manager
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
 at java.net.Socket.connect(Socket.java:529)
 at java.net.Socket.connect(Socket.java:478)
 at java.net.Socket.<init>(Socket.java:375)
 at java.net.Socket.<init>(Socket.java:189)
 at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
 at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
 at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
Caused: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
 java.net.ConnectException: Connection refused: connect
 at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
 at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
 at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
 at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
 at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
 at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
Caused: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
 java.net.ConnectException: Connection refused: connect]
 at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
 at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
 at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
 at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
Caused: java.io.IOException: Failed to retrieve RMIServer stub
 at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
 at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
 at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.connect(Unknown Source)
 at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.start(Unknown Source)
Caused: java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.sun.jme.toolkit.bootstrap.Batch.invoke(Unknown Source)
 at com.sun.jme.toolkit.bootstrap.Batch.tryInvoke(Unknown Source)
 at com.sun.jme.toolkit.bootstrap.Batch.startObjects(Unknown Source)
 at org.netbeans.modules.javame.common.container.Module.start(Module.java:21)
 at org.netbeans.modules.javame.common.container.ContainerSupport.startModule(ContainerSupport.java:67)
 at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManagerConnection(DevicemanagerHelper.java:41)
 at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.ensureConnected(DevicemanagerHelper.java:48)
[catch] at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManager(DevicemanagerHelper.java:84)
 at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.ensureDMStarted(AutoInstaller.java:292)
 at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.restored(AutoInstaller.java:63)
 at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:421)
 at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:342)
 at org.netbeans.ModuleManager.enable(ModuleManager.java:906)
 at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:428)
 at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:364)
 at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276)
 at org.netbeans.core.startup.Main.getModuleSystem(Main.java:165)
 at org.netbeans.core.startup.Main.start(Main.java:312)
 at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110)
 at java.lang.Thread.run(Thread.java:662)
[ 23598] INFO - bootstrap.ObjectGraphProcessor - Consolidating dependencies...
[ 23698] INFO - bootstrap.ObjectGraphProcessor - Consolidated dependencies...
[ 23798] INFO - bootstrap.ObjectGraphProcessor - Calculating order...
[ 23898] INFO - bootstrap.ObjectGraphProcessor - Calculated order
[ 23998] INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[ 24098] INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[ 24198] INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[ 24298] INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[ 24398] INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[ 24498] INFO - un.jme.toolkit.bootstrap.Batch - Objects started
[ 24600] INFO - bootstrap.ObjectGraphProcessor - Consolidating dependencies...
[ 24700] INFO - bootstrap.ObjectGraphProcessor - Consolidated dependencies...
[ 24800] INFO - bootstrap.ObjectGraphProcessor - Calculating order...
[ 24900] INFO - bootstrap.ObjectGraphProcessor - Calculated order
[ 25000] INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[ 25100] INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[ 25202] INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[ 25302] INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[ 25402] INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[ 25502] INFO - un.jme.toolkit.bootstrap.Batch - Objects started
[ 25602] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 26699] WARN - mpl.ObjectServerConnectionImpl - Remote object server is not running at service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 26799] INFO - l.process.GenericProcessRunner - Starting process: C:\Program Files\Java\Java_ME_platform_SDK_3.0/bin/device-manager.exe
[ 27914] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 30005] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 32106] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 34206] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 36306] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 38406] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 40506] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 42607] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 44706] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 46806] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
SEVERE [org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper]: Cannot connect to device manager
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
 at java.net.Socket.connect(Socket.java:529)
 at java.net.Socket.connect(Socket.java:478)
 at java.net.Socket.<init>(Socket.java:375)
 at java.net.Socket.<init>(Socket.java:189)
 at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
 at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
 at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
Caused: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
 java.net.ConnectException: Connection refused: connect
 at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
 at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
 at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
 at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
 at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
 at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
Caused: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
 java.net.ConnectException: Connection refused: connect]
 at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
 at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
 at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
 at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
Caused: java.io.IOException: Failed to retrieve RMIServer stub
 at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
 at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
 at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.connect(Unknown Source)
 at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.start(Unknown Source)
 at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.lookupMBean(Unknown Source)
 at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.findObject(Unknown Source)
[catch] at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.openConnection(DevicemanagerHelper.java:53)
 at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManager(DevicemanagerHelper.java:86)
 at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.ensureDMStarted(AutoInstaller.java:292)
 at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.restored(AutoInstaller.java:63)
 at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:421)
 at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:342)
 at org.netbeans.ModuleManager.enable(ModuleManager.java:906)
 at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:428)
 at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:364)
 at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276)
 at org.netbeans.core.startup.Main.getModuleSystem(Main.java:165)
 at org.netbeans.core.startup.Main.start(Main.java:312)
 at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110)
 at java.lang.Thread.run(Thread.java:662)
[ 48018] INFO - bootstrap.ObjectGraphProcessor - Consolidating dependencies...
[ 48118] INFO - bootstrap.ObjectGraphProcessor - Consolidated dependencies...
[ 48218] INFO - bootstrap.ObjectGraphProcessor - Calculating order...
[ 48318] INFO - bootstrap.ObjectGraphProcessor - Calculated order
[ 48418] INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[ 48518] INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[ 48618] INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[ 48718] INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[ 48818] INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[ 48918] INFO - un.jme.toolkit.bootstrap.Batch - Objects started
[ 49018] INFO - bootstrap.ObjectGraphPI did install Nokia's SDK with NetBeans and this works perfectly.
I went through with everything recommended here: http://blogs.sun.com/javamesdk/entry/first_aid_when_emulator_doesn
But nothing worked.
Any help appreciated!
Thanks.

Note: This thread was originally posted in the [Sun Java Wireless Toolkit|http://forums.sun.com/forum.jspa?forumID=82] forum, but moved to this forum for closer topic alignment.

Application does not load correctly when deploying to standalone server

All,
I have created simple application implementing fusion theme. Applicaiton works fine when I run on integrated server but when deployed on standalone server it does not load any images or the theme itself. afrloop keep incrementing in status bar and ends up with java script error while later.
I deployed another test application on standalone server and that works fine i.e. theme gets loaded correctly. Also, how should I include images on the page? I have a images folder in web content folder but they dont get loaded.
Any help will be appreciated.
Thanks,
Dipal

LabVIEW now uses the Microsoft installer. It's possible that you need to upgrade the version that's on the Win2K box. I think the latest service packs from Microsoft include it.

Open source Java proxy server?!

Hi,
I want to use a java proxy server in my application.Can someone suggest me some popular java proxy server with free source code? Also, the proxy should log URL details that the user navigates to.
Any help is greatly appreciated.
Thanks
Aparna

Hi michael,
In fact i have downloaded the proxy but running into problems while using it.I am using it on windows platform and when i give some URL in the browser, the request is taken by our RabbIT but after that the browser is asking me for the authentication for a number of times and then show me some error.Why is RabbIT asking me for authentication though i am specifying it in the configuration file?
Any help is appreciated.
Aparna

JNLPDownload servlet issue when deployed in iPlanet server

Hi all,
I am doing a POC to check how JWS works to launch an applet on a workstation having two different JRE versions (14.2_06 and 1.6.0_01 installed in lower to higher version order)
I deployed the sample application files in iPlanet server 6.0. In the JNLP file, under resources tag, I included a jar file with some version. However JWS is failing to download the file, with an exception (as seen from JNLP servle log file)
JnlpDownloadServlet(4): JnlpResource: JnlpResource[WAR Path: /lib/SampleApplet__V1.1.jar versionId=1.1 name=SampleApplet.jar lastModified=Thu Jan 01 05:30:00 GMT+05:30 1970] returnVersionId=1.1]
JnlpDownloadServlet(3): Resource returned: /lib/SampleApplet__V1.1.jar
Error in processing request
JnlpDownloadServlet(1): Internal error:
java.lang.NullPointerException
     at com.sun.javaws.servlet.DownloadResponse$ResourceFileDownloadResponse.getContentLength(DownloadResponse.java:178)
     at com.sun.javaws.servlet.DownloadResponse$FileDownloadResponse.sendRespond(DownloadResponse.java:117)
     at com.sun.javaws.servlet.JnlpDownloadServlet.handleRequest(JnlpDownloadServlet.java:115)
     at com.sun.javaws.servlet.JnlpDownloadServlet.doGet(JnlpDownloadServlet.java:79)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:919)
     at com.iplanet.server.http.servlet.NSServletRunner.Service(NSServletRunner.java:483)
The same application when deployed in tomcat server 4.1.32 is working fine.
All the jar file is available in the correct location and I have verified it. After some investigation with JNLP servlet source code, I found that iplanet 6.0 is throwing nullpointer excepton due to null return from following line from com.sun.javaws.servlet.JNLPResource.java file.
_resource = context.getResource(path); // here context is ServletContext and path input is relative path.
Has any one come across this problem in iplanet server? Does getResourcePath always return null in iPlanet server?
I don't want to change code in jnlp-servlet.jar, and it's the best case. Your inputs on this are appreciated.
Thanks & Regards,
Sudhakar

Below is our reuirment.
1. We will route the request based on urlprefix, these url prefix can be added and removed at runtime. We want to handle this situation automatically(not by obj conf changes). Also we will chnage the destination of request.
2. We want insert string in the url for our internal purpose.
So we opted for plugin.
BTW: I built the plugin for 32-bit environment.
$ file archMini-90.0.0.1.so
archMini-90.0.0.1.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped
Below is my cc options.
CC_CMD=/usr/bin/gcc -m32 -fpic -DNET_SSL -DLinux -DLINUX -D_REENTRANT
LD_SHAREDCMD=/usr/bin/gcc -m32 -shared

Error in Deploying java components - SAP NW CE 7.2 installation on Windows

Hi,
I am installing NW CE 7.2 on a windows machine. I opted for custom installation. I get the below error at "Deploy java components step. Any clue on why is this happening and how to resolve ?
<html> <head> </head> <body> An error occurred while processing option SAP NetWeaver 7.2 Developer Edition > Install > Custom Server Installation( Last error reported by the step :Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW72\INSTALL\DEVSYSTEM\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jce.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jsse.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_smime.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_ssl.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/w3c_http.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcexceptionimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcjeclientlibimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcloggingjavaimpl.jar;C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib/tcje~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host L-156007555 --port 50004' aborts with return code 104. Error message is 'undefinedStatus:AlreadyDeployedDescription: 1. Already deployed component has version:1000.7.20.1.0.20091117001100. SOLUTION: Check 'undefined' and '' for more information.). You can now: <ul> <li> Choose Retry to repeat the current step. </li> <li> Choose View Log to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> Log files are written to C:\Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM. </body></html>
Regards,
Rukmani

The below msg is from sapinst_dev.log
<html> <head> </head> <body> An error occurred while processing option SAP NetWeaver 7.2 Developer Edition > Install > Custom Server Installation( Last error reported by the step :Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW72\INSTALL\DEVSYSTEM\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jce.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jsse.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_smime.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_ssl.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/w3c_http.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcexceptionimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcjeclientlibimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcloggingjavaimpl.jar;C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib/tcje~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host L-156007555 --port 50004' aborts with return code 104. Error message is 'undefinedStatus:AlreadyDeployedDescription: 1. Already deployed component has version:1000.7.20.1.0.20091117001100. SOLUTION: Check 'undefined' and '' for more information.). You can now: <ul> <li> Choose Retry to repeat the current step. </li> <li> Choose View Log to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> Log files are written to C:\Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM. </body></html>

Error when deploying a map

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

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

Synchronous Java Proxy Server template - filling reponse message elements

Hi !
I'm writing a java proxy server for a synchronous interface. I'm somehow new in java...and I don't know how should I create elements for my response message inside the java method used to process the request message.
The response message format is something like this:
<field1>abc</field1>
<field2>
....<field2a>
........<fields2a1>
........</fields2a1>
....</field2a>
....<field2a>
....</field2a>
</field2>
according to the type "DT_Output_Type" type of the public class MyMethod defined in the java template generated by XI repository..
I think I should do something like this:
DT_Output_Type response = new DT_Output_Type();
DT_Output_Type.field2_List field2values = new DT_Output_Type.field2_List();
field2values.setfield2a(0,"1234");
response.setfield1 = "abc";
response.setfield2(field2values);
return response;
But I receive "Error invoking method". If I comment out the code where I assign values to sub-elements, everything works ok.
Thanks !
Matias

Hi Matias,
>>DT_Output_Type.field2_List field2values = new DT_Output_Type.field2_List();
This will create instance for field2 only.
Before setting field2a using field2values.setfield2a(0,"1234"); you must creat instance of field2a and also for field2a1.
I guess field2a will be an array.
so the order of creating instance and setting values can be ...
1. create instance of field2
2. create instance of field2a array
3. create instance of first array element of field2a
4. create instance of field2a1
5. set value for field2a1
6. set field2a1 in first array element of field2a
repeat steps 3-6 for next elements of field2a
7. set field2a array object (created in step 2) in field2
8. response.setfield2(field2values);
Also,
as mentioned by Amol, set value for filed1 should be
response.setfield1("abc");
Regards,
Uma

WLST - error when i start managed server using nmstart() command.

i am receiving an error when start the managed server using nmstart(). Please advise.
Do I have add any parameter to nodemanager.properties file?
Thankyou
pasted below is the error message i am receiving when i start managed server.
Starting server hssclient ...This Exception occured at Thu Mar 19 10:30:02 EDT 2
009.
java.lang.IllegalArgumentException: Invalid host name: Null or empty
at weblogic.nodemanager.client.NMClient.checkNullOrEmpty(NMClient.java:7
2)
at weblogic.nodemanager.client.NMClient.setHost(NMClient.java:79)
at weblogic.nodemanager.mbean.NodeManagerRuntime.getNMClient(NodeManager
Runtime.java:527)
at weblogic.nodemanager.mbean.NodeManagerRuntime.getNMClient(NodeManager
Runtime.java:565)
at weblogic.nodemanager.mbean.NodeManagerRuntime.start(NodeManagerRuntim
e.java:188)
at weblogic.server.ServerLifeCycleRuntime.startServer(ServerLifeCycleRun
time.java:439)
at weblogic.server.ServerLifeCycleRuntime.start(ServerLifeCycleRuntime.j
ava:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean
.java:428)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImp
l.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBea
nServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:248)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.
run(WLSMBeanServerInterceptorBase.java:443)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.inv
oke(WLSMBeanServerInterceptorBase.java:441)
at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterce
ptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:63)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.
run(WLSMBeanServerInterceptorBase.java:443)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.inv
oke(WLSMBeanServerInterceptorBase.java:441)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(
SecurityInterceptor.java:426)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
ptor$10$1.run(AuthenticatedSubjectInterceptor.java:582)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
ptor$10.run(AuthenticatedSubjectInterceptor.java:580)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
ptor.invoke(AuthenticatedSubjectInterceptor.java:573)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanSer
ver.java:310)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnecti
onImpl.java:1410)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectio
nImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run
(RMIConnectionImpl.java:1247)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(R
MIConnectionImpl.java:1350)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImp
l.java:784)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown S
ource)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:553)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:443)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:439)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:6
1)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicSer
verRef.java:983)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Hi I am getting below exception, is nmStart only start AdminServer ????
There are 1 nested errors:
weblogic.management.ManagementException: Booting as admin server, but servername, MS1, does not match the admin server name, AdminServer
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:803)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:493)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
>
<Feb 10, 2010 1:45:17 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Feb 10, 2010 1:45:17 PM UTC> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Feb 10, 2010 1:45:17 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Feb 10, 2010 1:45:17 PM> <FINEST> <NodeManager> <Waiting for the process to die: 8275>
<Feb 10, 2010 1:45:17 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Feb 10, 2010 1:45:17 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
~

Error when deploy Java Proxy Server EAR to PI

Similar Messages

Maybe you are looking for