ExceptionInInitializerError during InitialContext
Hi,
In my applet I am getting following exception during
creating a InitialContext.
I have recently upgraded from WLS5.1 to WLS6.0 sp2.
There was no error when I was using WLS5.1.
Is any thing wrong with my code or WLS6.0 handles it
differently.
My code where I get exception ----
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, m_baseUrl);
context = new InitialContext(env);
Exception is
java.lang.ExceptionInInitializerError: java.security.AccessControlException: access
denied (java.util.PropertyPermission weblogic.management.debug.logging read)
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
at java.lang.System.getProperty(Unknown Source)
at weblogic.logging.LogManager.<clinit>(LogManager.java:31)
at weblogic.kernel.Kernel.initialize(Kernel.java:127)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:102)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:134)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Unknown Source)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:118)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at applet.MyApp.init(MyApp.java:273)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
java.lang.InternalError: error initializing kernel
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:105)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:134)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Unknown Source)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:118)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at applet.MyApp.init(MyApp.java:273)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Contact [email protected] and reference CR081579.
Tom LeRoux wrote:
Has anyone seen this NPE when creating an InitialContext? We got this for about
a day on one of our cluster instances, and then it magically went away (the other
server in the cluster worked fine).. Solaris, Weblogic 5.1 service pack 10.
java.lang.NullPointerException
at weblogic.rjvm.RJVMFinder.equals(RJVMFinder.java:98)
at java.util.Hashtable.get(Hashtable.java:323)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:190)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:195)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:148)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:123)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support
Similar Messages
-
NullPointerException during InitialContext creation in RJVMFinder (WL 5.1)
Has anyone seen this NPE when creating an InitialContext? We got this for about
a day on one of our cluster instances, and then it magically went away (the other
server in the cluster worked fine).. Solaris, Weblogic 5.1 service pack 10.
java.lang.NullPointerException
at weblogic.rjvm.RJVMFinder.equals(RJVMFinder.java:98)
at java.util.Hashtable.get(Hashtable.java:323)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:190)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:195)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:148)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:123)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)Contact [email protected] and reference CR081579.
Tom LeRoux wrote:
Has anyone seen this NPE when creating an InitialContext? We got this for about
a day on one of our cluster instances, and then it magically went away (the other
server in the cluster worked fine).. Solaris, Weblogic 5.1 service pack 10.
java.lang.NullPointerException
at weblogic.rjvm.RJVMFinder.equals(RJVMFinder.java:98)
at java.util.Hashtable.get(Hashtable.java:323)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:190)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:195)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:148)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:123)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support -
Creation of InitialContext last suspiciously long...
It takes up to 15 seconds to create this InitialContext.
Is there any chance of optimizing it?
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, url);
return new InitialContext(h);
We use WLS 6.1 SP 3 on Linux 7.3.
-Jani PuhakkaWe have the same problem, is there anything weblogic could be doing, like creating
bean pool instances etc, during InitialContext retrieval which makes it take so
long?
"Jane Sampson" <[email protected]> wrote:
Hi Jani,
Sounds like you should open case with Customer Support. You can open
a case
online at http://support.bea.com or call 1-888-232-7878.
Jane
BEA Support
"Jani P." <[email protected]> wrote in message
news:[email protected]..
It takes up to 15 seconds to create this InitialContext.
Is there any chance of optimizing it?
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, url);
return new InitialContext(h);
We use WLS 6.1 SP 3 on Linux 7.3.
-Jani Puhakka -
ERROR IN WAS 6.4 SNEAK PREVIEW INSTALL DURING SP3 - SP5 DEPLOY ONLINE STAG
Hi All,
I have installed WAS 6.4 SP3 sneak preview over SQL server 2000. I get the following error message while patching from WAS SP3 to SP5 ( this patch is included as part of the sneak preview zip package) during DEPLOY ONLINE stage.
ERROR
MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile D:\Program Files\sapinst_instdir\PATCH\MSS\callSdmViaSapinst.log.
Also find below the log file :
Aug 23, 2004 4:09:51 PM Info: Start logging to console
Aug 23, 2004 4:09:51 PM Info:
Aug 23, 2004 4:09:51 PM Info: ============================================
Aug 23, 2004 4:09:51 PM Info: = Starting to execute command 'deploy' =
Aug 23, 2004 4:09:51 PM Info: ============================================
Aug 23, 2004 4:09:51 PM Info: Starting SDM - Software Deployment Manager...
Aug 23, 2004 4:09:53 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.3005.00.0000.20040414093518.0000
Aug 23, 2004 4:09:55 PM Info: SDM operation mode successfully set to: Standalone
Aug 23, 2004 4:09:57 PM Info: Initializing Network Manager (50017)
Aug 23, 2004 4:09:59 PM Info: Checking if another SDM is running on port 50018
Aug 23, 2004 4:09:59 PM Info: -
Starting deployment -
Aug 23, 2004 4:09:59 PM Info: Loading selected archives...
Aug 23, 2004 4:09:59 PM Info: Loading archive 'C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA'
Aug 23, 2004 4:12:27 PM Info: Selected archives successfully loaded.
Aug 23, 2004 4:12:33 PM Info: Actions per selected component:
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040330113610.0000' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031112163623.0000'.
Aug 23, 2004 4:12:33 PM Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
Aug 23, 2004 4:12:33 PM Info: No action: Selected development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' will not update currently deployed development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040309120341.0000' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119160521.0000'.
Aug 23, 2004 4:12:33 PM Info: Initial deployment: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' will be deployed.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031223155421.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170150.0000' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124738.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031210162516.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215150458.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031223155421.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031223155421.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031103173534.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' updates currently deployed development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031015103253.0000'.
Aug 23, 2004 4:12:33 PM Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165832.0000' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133611.0000'.
Aug 23, 2004 4:12:33 PM Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
Aug 23, 2004 4:12:35 PM Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000'.
Aug 23, 2004 4:12:36 PM Info: Initial deployment: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
Aug 23, 2004 4:12:36 PM Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
Aug 23, 2004 4:12:36 PM Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001180520.0000'.
Aug 23, 2004 4:12:36 PM Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
Aug 23, 2004 4:12:36 PM Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007125447.0000'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031210162516.0000'.
Aug 23, 2004 4:12:37 PM Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000'.
Aug 23, 2004 4:12:37 PM Info: Initial deployment: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will be deployed.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:37 PM Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124656.0000'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.30.5.0.20040420063500' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'3.20040113043717'.
Aug 23, 2004 4:12:37 PM Info: Update: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
Aug 23, 2004 4:12:38 PM Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001180520.0000'.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119155233.0000'.
Aug 23, 2004 4:12:38 PM Info: Initial deployment: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164151.0000' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124708.0000'.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164054.0000' updates currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040112231712'.
Aug 23, 2004 4:12:38 PM Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164228.0000' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001181052.0000'.
Aug 23, 2004 4:12:39 PM Info: Initial deployment: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165855.0000' will be deployed.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165842.0000' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133723.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163618.0000' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001180219.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031218123529.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007125447.0000'.
Aug 23, 2004 4:12:39 PM Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170316.0000' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124545.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155021.0000' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031117101211.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031103173534.0000'.
Aug 23, 2004 4:12:40 PM Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
Aug 23, 2004 4:12:53 PM Error: An error occured while storing the cluster instances!
Aug 23, 2004 4:12:53 PM Error: JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
Aug 23, 2004 4:12:53 PM Error: Received exception when saving current Engine state: JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
Aug 23, 2004 4:12:53 PM Info: Error handling strategy: OnErrorStop
Aug 23, 2004 4:12:53 PM Info: Update strategy: UpdateLowerVersions
Aug 23, 2004 4:12:53 PM Info: Starting: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215150458.0000'.
Aug 23, 2004 4:12:53 PM Info: SDA to be deployed: D:\usr\sap\P64\JC00\SDM\root\origin\sap.com\SQLTrace\SAP AG\6.3005.00.0000.20040401154008.0000\SQLTrace.ear
Aug 23, 2004 4:12:53 PM Info: Software type of SDA: J2EE
Aug 23, 2004 4:12:59 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 23, 2004 4:13:00 PM Info: Starting cluster instance processes.
<b><b>Aug 23, 2004 4:13:00 PM Error: An error occured while starting a cluster instance!
Aug 23, 2004 4:13:00 PM Error: JStartup Framework is not able to deliver an information about the cluster control instances!</b></b>
Please check the status of the J2EE Engine
Aug 23, 2004 4:13:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 23, 2004 4:13:00 PM Error: Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000':
SDM could not start the J2EE cluster on the host aol! The online deployment is terminated.
JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Aug 23, 2004 4:13:01 PM Error: An error occured while restoring the cluster instances states
Aug 23, 2004 4:13:01 PM Error: JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
Aug 23, 2004 4:13:01 PM Error: Received exception when restoring Engine state: JStartup Framework is not able to deliver an information about the cluster control instances!
Please check the status of the J2EE Engine
Aug 23, 2004 4:13:01 PM Info: -
Deployment was successful -
Aug 23, 2004 4:13:02 PM Info: Summarizing the deployment results:
Aug 23, 2004 4:13:02 PM Error: Admitted: C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA
Aug 23, 2004 4:13:02 PM Error: Processing error. Return code: 4
Appreciate your prompt help.
Thanks.
NirmalHi,
I am getting the folloing error message now : below is the log file :
Aug 24, 2004 2:36:53 PM Info: Start logging to console
Aug 24, 2004 2:36:53 PM Info:
Aug 24, 2004 2:36:53 PM Info: ============================================
Aug 24, 2004 2:36:53 PM Info: = Starting to execute command 'deploy' =
Aug 24, 2004 2:36:53 PM Info: ============================================
Aug 24, 2004 2:36:53 PM Info: Starting SDM - Software Deployment Manager...
Aug 24, 2004 2:36:54 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.3005.00.0000.20040414093518.0000
Aug 24, 2004 2:36:56 PM Info: SDM operation mode successfully set to: Standalone
Aug 24, 2004 2:36:57 PM Info: Initializing Network Manager (50017)
Aug 24, 2004 2:36:57 PM Info: Checking if another SDM is running on port 50018
Aug 24, 2004 2:36:57 PM Info: -
Starting deployment -
Aug 24, 2004 2:36:58 PM Info: Loading selected archives...
Aug 24, 2004 2:36:58 PM Info: Loading archive 'C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA'
Aug 24, 2004 2:37:17 PM Info: Selected archives successfully loaded.
Aug 24, 2004 2:37:22 PM Info: Actions per selected component:
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040330113610.0000' will not update currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040330113610.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' will not update currently deployed development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000'.
Aug 24, 2004 2:37:22 PM Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040309120341.0000' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119160521.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 24, 2004 2:37:22 PM Info: Initial deployment: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' will be deployed.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170150.0000' will not update currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170150.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' will not update currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' will not update currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' will not update currently deployed development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165832.0000' will not update currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165832.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000'.
Aug 24, 2004 2:37:22 PM Info: Initial deployment: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
Aug 24, 2004 2:37:22 PM Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
Aug 24, 2004 2:37:22 PM Info: No action: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' will not update currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000'.
Aug 24, 2004 2:37:22 PM Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' will not update currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' will not update currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000'.
Aug 24, 2004 2:37:23 PM Info: Initial deployment: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will be deployed.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:23 PM Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.30.5.0.20040420063500' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'3.20040113043717'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' will not update currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000'.
Aug 24, 2004 2:37:23 PM Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119155233.0000'.
Aug 24, 2004 2:37:23 PM Info: Initial deployment: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164151.0000' will not update currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164151.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164054.0000' will not update currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164054.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164228.0000' will not update currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164228.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165855.0000' will not update currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165855.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165842.0000' will not update currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165842.0000'.
Aug 24, 2004 2:37:23 PM Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163618.0000' will not update currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163618.0000'.
Aug 24, 2004 2:37:23 PM Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031218123529.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' will not update currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
Aug 24, 2004 2:37:23 PM Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170316.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170316.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155021.0000' will not update currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155021.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
Aug 24, 2004 2:37:23 PM Info: No action: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
<b>Aug 24, 2004 2:37:23 PM Error: Could not create JStartupClusterController: No route to host: connect Throwable: java.net.NoRouteToHostException Throwable message: No route to host: connect
Aug 24, 2004 2:37:23 PM Error: Received exception when saving current Engine state: Could not create JStartupClusterController: No route to host: connect
Aug 24, 2004 2:37:24 PM Info: Error handling strategy: OnErrorStop</b>Aug 24, 2004 2:37:24 PM Info: Update strategy: UpdateLowerVersions
Aug 24, 2004 2:37:24 PM Info: Starting: Initial deployment: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will be deployed.
Aug 24, 2004 2:37:24 PM Info: SDA to be deployed: D:\usr\sap\P64\JC00\SDM\root\origin\sap.com\tc\monitoring\systeminfo\SAP AG\6.3005.00.0000.20040419174536.0000\SystemInfo.ear
Aug 24, 2004 2:37:24 PM Info: Software type of SDA: J2EE
Aug 24, 2004 2:37:25 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 24, 2004 2:37:28 PM Error: Could not create JStartupClusterController: No route to host: connect Throwable: java.net.NoRouteToHostException Throwable message: No route to host: connect
Aug 24, 2004 2:37:28 PM Info: No information about the J2EE engine cluster is available.
The online deployment process is continuing.
Aug 24, 2004 2:37:30 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 24, 2004 2:37:30 PM Error: Aborted: development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000':
Caught exception while checking the login credentials from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [aol] with UserName: [Administrator]
Check your Login Info.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Aug 24, 2004 2:37:30 PM Error: Could not create JStartupClusterController: No route to host: connect Throwable: java.net.NoRouteToHostException Throwable message: No route to host: connect
Aug 24, 2004 2:37:30 PM Error: Received exception when restoring Engine state: Could not create JStartupClusterController: No route to host: connect
Aug 24, 2004 2:37:31 PM Info: -
Deployment was successful -
Aug 24, 2004 2:37:31 PM Info: Summarizing the deployment results:
Aug 24, 2004 2:37:31 PM Error: Admitted: C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA
Aug 24, 2004 2:37:31 PM Error: Processing error. Return code: 4 -
Error during upgarding sneak preview SP16 to SP18
I have installed sneak preview SP16 which I am trying to upgrade to SP18.
I get an error duing the step Deploy via J2EE/SDM.
The SDM,server0 and dispatcher are all green in the MMC and the SDM is working in "integrated mode".
The callSdmViaSapinst.log indicates the following:-
May 15, 2007 12:33:03... Info: Start logging to console
May 15, 2007 12:33:03... Info:
May 15, 2007 12:33:03... Info: ============================================
May 15, 2007 12:33:03... Info: = Starting to execute command 'deploy' =
May 15, 2007 12:33:03... Info: ============================================
May 15, 2007 12:33:03... Info: Starting SDM - Software Deployment Manager...
May 15, 2007 12:33:04... Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
May 15, 2007 12:33:05... Info: SDM operation mode successfully set to: Integrated
May 15, 2007 12:33:06... Info: Initializing Network Manager (50017)
May 15, 2007 12:33:06... Info: Checking if another SDM is running on port 50018
May 15, 2007 12:33:06... Error: Could not start SDM - another Server may be running already.
May 15, 2007 12:33:06... Error: Another SDM is running already for this SDM_HOME directory. Exiting. Throwable: com.sap.sdm.client_server.launch.SDMRunningException Throwable message: Another SDM instance is running on this host
May 15, 2007 12:33:06... Error: Processing error. Return code: 4
Now, I tried by switching the SDM to "Standalone" mode and during this, the server0 and dispatcher were running while the SDM remains stopped. The CallSdmViaSapinst.log shows:-
May 15, 2007 11:06:42... Info: Start logging to console
May 15, 2007 11:06:42... Info:
May 15, 2007 11:06:42... Info: ============================================
May 15, 2007 11:06:42... Info: = Starting to execute command 'deploy' =
May 15, 2007 11:06:42... Info: ============================================
May 15, 2007 11:06:42... Info: Starting SDM - Software Deployment Manager...
May 15, 2007 11:06:43... Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
May 15, 2007 11:06:44... Info: SDM operation mode successfully set to: Standalone
May 15, 2007 11:06:44... Info: Initializing Network Manager (50017)
May 15, 2007 11:06:45... Info: Checking if another SDM is running on port 50018
May 15, 2007 11:06:45... Info: -
Starting deployment -
May 15, 2007 11:06:45... Info: Error handling strategy: OnErrorStop
May 15, 2007 11:06:45... Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
May 15, 2007 11:06:45... Info: Update strategy: UpdateLowerVersions
May 15, 2007 11:06:45... Info: Starting deployment prerequisites:
May 15, 2007 11:06:46... Info: Loading selected archives...
May 15, 2007 11:06:46... Info: Loading archive 'D:\SAPNetWeaver04_SP16Preview\Patch SP18\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'
May 15, 2007 11:06:54... Info: Selected archives successfully loaded.
May 15, 2007 11:06:55... Info: Actions per selected component:
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'1' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060131164117.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060130172658.0000'/'0'.
May 15, 2007 11:06:55... Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060126165422.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'1' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050606172955.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060126165638.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060201164038.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060130172658.0000'/'0'.
May 15, 2007 11:06:55... Info: No action: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' will not update currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050818153022.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060220135356.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119123152.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060201162907.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'1' updates currently deployed development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119145451.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050606172625.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060201164038.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060201164038.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050818153616.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'1' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119123403.0000'/'0'.
May 15, 2007 11:06:55... Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
May 15, 2007 11:06:55... Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119122320.0000'/'0'.
May 15, 2007 11:06:55... Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060126165638.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4016.00.0000.20051027104030.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060126165422.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050121164722.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050606172625.0000'/'0'.
May 15, 2007 11:06:55... Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'2' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060220135356.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060130172658.0000'/'0'.
May 15, 2007 11:06:55... Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4016.00.0000.20051027101045.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060130172658.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119123152.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.16.0.20060221071338''/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060220135356.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060220135356.0000'/'0'.
May 15, 2007 11:06:55... Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4016.00.0000.20051027104030.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119122320.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050606164207.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818152118.0000'/'1' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050818152118.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'1' updates currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119123827.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119123504.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050331133205.0000'/'1' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050331133205.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413100235.0000'/'1' updates currently deployed development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4016.00.0000.20051027101144.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119123504.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818150135.0000'/'1' updates currently deployed development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050818150135.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' updates currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060130172658.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111540.0000'/'1' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119123418.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060126165422.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164103.0000'/'1' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050606164103.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119122320.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050121164722.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' updates currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060130172658.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119123705.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060119123705.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060126165638.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4018.00.0000.20041104140331.0000'/'1' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4016.00.0000.20041104140331.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4016.00.0000.20050818153616.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060220135356.0000'/'0'.
May 15, 2007 11:06:55... Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060220135356.0000'/'0'.
May 15, 2007 11:06:56... Info: Ending deployment prerequisites. All items are correct.
May 15, 2007 11:06:57... Error: Could not create JStartupClusterController connected to MessageServer[Host:hsehgal-2, Port:3601] : Connection refused: connect Throwable: java.net.ConnectException Throwable message: Connection refused: connect
May 15, 2007 11:06:58... Error: Could not create JStartupClusterController connected to MessageServer[Host:hsehgal-2, Port:3601] : Connection refused: connect Throwable: java.net.ConnectException Throwable message: Connection refused: connect
May 15, 2007 11:06:58... Error: Received exception when saving current Engine state: Could not create JStartupClusterController connected to MessageServer[Host:hsehgal-2, Port:3601] : Connection refused: connect
May 15, 2007 11:06:58... Info: Starting: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4016.00.0000.20060201162907.0000'/'0'.
May 15, 2007 11:06:58... Info: SDA to be deployed: C:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\SQLTrace\SAP AG\1\6.4018.00.0000.20060706112013.0000\SQLTrace.ear
May 15, 2007 11:06:58... Info: Software type of SDA: J2EE
May 15, 2007 11:06:58... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
May 15, 2007 11:06:59... Error: Could not create JStartupClusterController connected to MessageServer[Host:hsehgal-2, Port:3601] : Connection refused: connect Throwable: java.net.ConnectException Throwable message: Connection refused: connect
May 15, 2007 11:06:59... Info: No information about the J2EE engine cluster is available.
The online deployment process is continuing.
May 15, 2007 11:07:01... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
May 15, 2007 11:07:01... Error: Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1':
CPO data could not be get.
com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Error: Caught the following error or exception: "com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException"
Additional error message is:
Caught exception from deploy service of SAP J2EE Engine. 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: [hsehgal-2] with user name: [admin]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances:
hsehgal-2:50004 Reason: Cannot open connection on host: 20.198.103.127 and port: 50004]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:455)
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.EngineJ2EE620OnlineDeployerImpl.getOldDeploymentConfigInternal(EngineJ2EE620OnlineDeployerImpl.java:924)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.getOldDeploymentConfiguration(EngineJ2EE620OnlineDeployerImpl.java:117)
at com.sap.sdm.serverext.servertype.inqmy.EngineJ2EE620OnlineProcessor.getOldDeploymentConfiguration(EngineJ2EE620OnlineProcessor.java:87)
at com.sap.sdm.serverext.servertype.inqmy.EngineJ2EE620OnlineProcessor.createCpo(EngineJ2EE620OnlineProcessor.java:75)
at com.sap.sdm.serverext.servertype.inqmy.EngineJ2EE620OnlineProcessor.getCpo(EngineJ2EE620OnlineProcessor.java:47)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performDeployment(EngineJ2EE620OnlineDeployerImpl.java:179)
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.control.command.cmds.Deploy.execute(Deploy.java:179)
at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)
at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)
at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)
at com.sap.sdm.control.command.Command.exec(Command.java:42)
at SDM.main(SDM.java:21)
Caused by: com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances:
hsehgal-2:50004 Reason: Cannot open connection on host: 20.198.103.127 and port: 50004
at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:53)
at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:33)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:340)
... 40 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.checkLoginCredentials.DMEXC)
Additional error message is:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [hsehgal-2] with user name: [admin]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances:
hsehgal-2:50004 Reason: Cannot open connection on host: 20.198.103.127 and port: 50004]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:455)
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.EngineJ2EE620OnlineDeployerImpl.getOldDeploymentConfigInternal(EngineJ2EE620OnlineDeployerImpl.java:924)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.getOldDeploymentConfiguration(EngineJ2EE620OnlineDeployerImpl.java:117)
at com.sap.sdm.serverext.servertype.inqmy.EngineJ2EE620OnlineProcessor.getOldDeploymentConfiguration(EngineJ2EE620OnlineProcessor.java:87)
at com.sap.sdm.serverext.servertype.inqmy.EngineJ2EE620OnlineProcessor.createCpo(EngineJ2EE620OnlineProcessor.java:75)
at com.sap.sdm.serverext.servertype.inqmy.EngineJ2EE620OnlineProcessor.getCpo(EngineJ2EE620OnlineProcessor.java:47)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performDeployment(EngineJ2EE620OnlineDeployerImpl.java:179)
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.control.command.cmds.Deploy.execute(Deploy.java:179)
at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)
at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)
at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)
at com.sap.sdm.control.command.Command.exec(Command.java:42)
at SDM.main(SDM.java:21)
Caused by: com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances:
hsehgal-2:50004 Reason: Cannot open connection on host: 20.198.103.127 and port: 50004
at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:53)
at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:33)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:340)
... 40 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).NO_CPO)
May 15, 2007 11:07:01... Info: Starting to save the repository
May 15, 2007 11:07:02... Info: Finished saving the repository
May 15, 2007 11:07:02... Info: Starting: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.16.0.20060221071338''/'0'.
May 15, 2007 11:07:02... Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1':
Failed deployment of SDAs:
development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' : aborted
Please, look at error logs above for more information!
May 15, 2007 11:07:02... Info: Starting to save the repository
May 15, 2007 11:07:03... Info: Finished saving the repository
May 15, 2007 11:07:04... Error: Could not create JStartupClusterController connected to MessageServer[Host:hsehgal-2, Port:3601] : Connection refused: connect Throwable: java.net.ConnectException Throwable message: Connection refused: connect
May 15, 2007 11:07:04... Error: Received exception when restoring Engine state: Could not create JStartupClusterController connected to MessageServer[Host:hsehgal-2, Port:3601] : Connection refused: connect
May 15, 2007 11:07:04... Error: -
At least one of the Deployments failed -
May 15, 2007 11:07:07... Info: Summarizing the deployment results:
May 15, 2007 11:07:07... Error: Aborted: D:\SAPNetWeaver04_SP16Preview\Patch SP18\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA
May 15, 2007 11:07:07... Error: Processing error. Return code: 4
Please advise the way ahead.Hi ,
Did you able to solve te issue....kindly let me know. -
Error (MUT-02041) during Installation of Enterprise Portal 6.0
Hi,
I have got a serious problem during the installation of SAP EP 6.0.
<b>Background Information:</b>
I succesfully installed Netweaver '04 Web AS Java 6.40 system. Operating System is Red Hat Enterprise Linux 3. SAP Database is MaxDB 7.50.
<b>Problem Description:</b>
During step 2 (Deploy JDBC Libraries) of the portal installation process the installation routine stops with error code MUT - 02041.
<b>Complete Error Message:</b>
MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile /tmp/sapinst_instdir/NW04SR1/EP/EP/callSdmViaSapist.log.
<b>Output of Logfile:</b>
Error: Aborted: development component 'com.sapportal.datadirect'/'sap.com'/'SAP AG'/'609.20041012102246.0000':
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: [CG-DEV-SERVER] with user name: [Administrator]
Check your login information.
Exception is: com.sap.engine.services.jndi.persistent.exception.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: User not authorized.]
Error: -
At least one of the Deployments failed -
<b>What I tried do solve the problem:</b>
I used the Visual Administrator tool to check the user "Administrator". (I used the user "Administrator" to connect to the J2EE Engine - localhost, port 50004).
Administrator is not locked, is member of group Administrators, member of group Authenticed Users, member of group Everyone, is valid until year 2500 and has 80 succesful logon counts.
The user looks fine to me. I do not know what else I could check to solve the problem. Anything I forgot to check? I am grateful for any kind of help (pointer to docs, advise, step by step solution).
Cheers Martin
Message was edited by: Martin KellermannHi,
here an uodate of the progress I am making to solve the problem described above.
Due to the output of the logfile (User not authorized), I think the "Administration" user does not have enough rights to perform the required actions needed for the installation.
Well, I looked it up (Visual Administrator --> Cluster --> Server 0 ... --> Services --> Security Provider -->Runtime --> Policy Configurations --> "service.naming" in "Components" List --> Security Roles).
According to http://help.sap.com/saphelp_webas630/helpdata/en/de/83343ecc7f892ee10000000a114084/frameset.htm, all users and groups that are granted permission "jndi_all_operations" can perform all operations available in the naming system.
I checked and found out that jndi_all_operations is merely a role reference to security role "administrators". Group "Administrators" is assigend to security role "administrator". As I mention before, user "Administrator" is member of group "Administrators". I think user "Administrator" has been granted all required permissions.
Am I wrong, what else could cause such an error message! Need some guideance.
Martin -
Error during startup of portal service after SPS11
Hi Guys,
After installation of SPS11 to our 2004s portal system we have problem with startup of our Portal service.
Before SPS11 we had SPS9 system and everything was working correctly.
Our service is connecting to Database during its initialization.
This is part of our code:
Properties p = new Properties();
p.put("java.naming.factory.initial", "com.sap.engine.services.jndi.InitialContextFactoryImpl");
try
Context ctx = new InitialContext(p);
_ds = (DataSource)ctx.lookup(POOLNAME);
Connection conn = _ds.getConnection();
conn.close();
LogWriter.traceInfo(LogWrapper.trace,"Connection established.");
} catch (NamingException ex)
The error is:
#1.5#000802A2BF4A00580000038200003E3000042C1F016BDC9A#1174411586934#System.err#sap.com/irj#System.err#Guest#2####a813ff20d70611dbbcd7000802a2bf4a#SAPEngine_Application_Thread[impl:3]_27##0#0#Error##Plain###com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of SABMILLER.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at cz.sap.statemanagement.StateLogRetriever.<init>(StateLogRetriever.java:73)
The probleam appears only during startup of portal!
If you deploy service on running portal it is started without any problems.
We tried to apply note (Note 960199 - 2-Phase Init Mechanism for Portal Services is Deprecated) but without success.
This is modification of our portalapps.xml as described in Note.
<service name="StatemanagementLogService">
<service-config>
<property name="className" value="cz.sap.statemanagement.StatemanagementLogService"/>
<property name="startup" value="true"/>
<property name="twophaseinit" value="always"/>
</service-config>
Please could you help us with this problem?
Anyone has an idea what is wrong?
Thanks a lot
OndrejHi Nirmal,
thanks you for your quick response. This is what the installer returns when I use your suggested command:
Mar 7, 2012 2:35:56 PM [Error]: The parameter jce_policy_zip in externally supplied configuration is invalid.
I looked up the parameters for the STARTUP:
rootdir [guiport] [httpport] [guistart] [guimode] [config] [sid] [instanceNr]
Thus the jce_policy_zip is not a valid parameter.
However, after deleting the file specified I could just run STARTUP again and this worked.
Thanks
Marcel
Edited by: M. Rabe on Mar 7, 2012 2:57 PM -
Message bean does not start automatically during application server startup
I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
Thanks,
Bill
#1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
#1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
#1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
#1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
#1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
#1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
#1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
#1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
#1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
... 12 more
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
#1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
#1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
at java.lang.Class.getConstructor0(Class.java:1930)
at java.lang.Class.newInstance0(Class.java:278)
at java.lang.Class.newInstance(Class.java:261)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:379)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
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)I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve -
Error during deployment of Message Driven Bean
Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
I am getting some error (or perhaps warning) during deployment of Message
Driven Bean. Any one seen this before?
This error only comes on a machine with Dual Network card.
Thanks.
####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010008> <EJB Deploying file: AppRuntime.jar>
####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
<system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
is of a non-final version of the appropriate specification. It is subject to
change in future releases once the specification becomes finalized. This may
cause application code developed for BEA WebLogic Server 6.1 that uses the
new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
supported in future releases of BEA WebLogic Server.>
####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
unable to connect to the JMS destination: CQM_MessageQueue. The EJB
container will automatically attempt to re-establish the connection with the
JMS server. This warning may occur during WebLogic Cluster start-up if the
JMS destination is located on another server. When the JMS server connection
is re-established, the Message-Driven EJB will again receive JMS messages.
The Error was:
Unable to create a JNDI InitialContext to lookup the JMS destination. The
error was:
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
nested exception is:
java.net.ConnectException: Connection refused: connect; No available router
to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:307)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:211)
at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
rivenBeanInfoImpl.java:641)
at
weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
nPoller.java:474)
at
weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
.java:418)
at
weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
nectionPoller.java:286)
at
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
foImpl.java:511)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
at weblogic.j2ee.Application.addComponent(Application.java:170)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy34.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy49.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
>
####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010009> <EJB Deployed EJB with JNDI name
ASYNCMessageDrivenBean.>
Hi Tom
Yes we do have an URL provided in the descriptor. It's
t3://jms.server.net:7001.
and the jms.server.net is resolved via a hosts file in Win2K
eg,
192.168.100.200 jms.server.net
You are right in saying that the loopback in a dual-net card is a problem.
But our solution
above solves the issue as long as your host file does not use 127.0.0.1 as
the IP.
We need the URL b/c depending on our client's deployment , the JMS Server
may be remote or may be local.
"Tom Barnes" <[email protected]> wrote in message
news:[email protected]...
> Hi x,
>
> Something to do with the loopback and dual-network cards is
> messin' with WLS' mind. I do not know what the problem is,
> but I can guess:
>
> You have specified an URL in the MDB descriptor when there
> is no need for one. If t3://127.0.0.1:7001 is in the same
> cluster the MDB is running in (I suspect this URL is
> actually the same WL server), then don't specify the URL.
> This URL is only useful for connecting an MDB to a JMS
> server that is outside local server and outside the cluster.
> The URL may be working on single-network card systems
> as perhaps then WL has enough info to guess that you
> actually mean the local WL server, and simply converts
> the context to a local context.
>
> Note that the URL option in the MDB descriptor is actually
> a WebLogic extension of J2EE.
>
> Tom
>
>
>
> x wrote:
> > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
> >
> > I am getting some error (or perhaps warning) during deployment of
Message
> > Driven Bean. Any one seen this before?
> > This error only comes on a machine with Dual Network card.
> >
> > Thanks.
> >
> >
> >
> > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
> > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
> > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
<main>
> > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
features
> > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
1.2,
> > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
6.1
> > is of a non-final version of the appropriate specification. It is
subject to
> > change in future releases once the specification becomes finalized. This
may
> > cause application code developed for BEA WebLogic Server 6.1 that uses
the
> > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
> > supported in future releases of BEA WebLogic Server.>
> > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
<main>
> > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
> > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
> > container will automatically attempt to re-establish the connection with
the
> > JMS server. This warning may occur during WebLogic Cluster start-up if
the
> > JMS destination is located on another server. When the JMS server
connection
> > is re-established, the Message-Driven EJB will again receive JMS
messages.
> > The Error was:
> > Unable to create a JNDI InitialContext to lookup the JMS destination.
The
> > error was:
> > javax.naming.CommunicationException. Root exception is
> > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
> > nested exception is:
> > java.net.ConnectException: Connection refused: connect; No available
router
> > to destination
> > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
> > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
> > at
> >
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:307)
> > at
> >
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:211)
> > at
> >
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
> > ory.java:149)
> > at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
> > at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
> > at javax.naming.InitialContext.init(InitialContext.java:217)
> > at javax.naming.InitialContext.<init>(InitialContext.java:193)
> > at
> >
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
> > rivenBeanInfoImpl.java:641)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
> > nPoller.java:474)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
> > .java:418)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
> > nectionPoller.java:286)
> > at
> >
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
> > foImpl.java:511)
> > at
weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
> > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
> > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
> > at weblogic.j2ee.Application.addComponent(Application.java:170)
> > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
> > arget.java:360)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
> > Target.java:285)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
> > eploymentTarget.java:239)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
> > entTarget.java:199)
> > at java.lang.reflect.Method.invoke(Native Method)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
> > .java:636)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
> > 21)
> > at
> >
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> > nImpl.java:360)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> > at $Proxy34.updateDeployments(Unknown Source)
> > at
> >
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
> > ServerMBean_CachingStub.java:2977)
> > at
> >
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
> > icationManager.java:372)
> > at
> >
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
> > r.java:160)
> > at java.lang.reflect.Method.invoke(Native Method)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
> > .java:636)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
> > 21)
> > at
> >
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> > nImpl.java:360)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> > at $Proxy49.start(Unknown Source)
> > at
> >
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
> > ApplicationManagerMBean_CachingStub.java:480)
> > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
> > at weblogic.management.Admin.finish(Admin.java:644)
> > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
> > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
> > at weblogic.Server.main(Server.java:35)
> >
> > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
> > <system> <> <010009> <EJB Deployed EJB with JNDI name
> > ASYNCMessageDrivenBean.>
> >
> >
>
-
ERROR: Ldap Authentication failed for dap during installation of iAS 6.0 SP3
I am attempting to install ias Enterprise Edition (6.0 SP3) on solaris 2.8 using typical in basesetup. I am trying to install new Directory server as I don't have an existing one.
During the installation I got the following error.
ERROR: Ldap Authentication failed for url ldap://hostname:389/o=NetScape Root user id admin (151: Unknown Error)
Fatal Slapd did not add Directory server information to config Server.
Warning slapd could'nt populate with ldif file Yes error code 151.
ERROR:Failure installing iPlanet Directory Server.
Do you want to continue: ( I entered yes )
Configuring Administration Server Segmentation fault core dumped.
Error: Failure installing Netscape Administration Server.
Do you want to continue:( I responded with yes).
And during the Extraction I got the following
ERROR:mple_bind: Can't connect to the LDAP server - No route to host
ERROR: Unable to connect to LDAP Directory Server
Hostname: hostname
Port: 389
User: cn=Directory Manager
Password: <password-for-cn=Directory Manager
Please make sure this Directory Server is currently running.
You might need to run 'stop-slapd' and then
'start-slapd' in the Directory Server home directory, in order to restart
LDAP. When finished, press ENTER to continue, or S to skip this step:
Start registering Bootstrap EJB...
javax.naming.NameNotFoundException
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled > Code)
at javax.naming.NamingException.<init>(NamingException.java:114)
at javax.naming.NameNotFoundException.<init>(NameNotFoundException.java: 48)
at com.netscape.server.jndi.RootContext.resolveCtx(Unknown Source)
"ldaperror" 76 lines, 2944 characters
at com.netscape.server.jndi.RootContext.resolveCtx(Unknown Source)
at com.netscape.server.jndi.RootContext.bind(Unknown Source)
at com.netscape.server.jndi.RootContext.bind(Unknown Source)
at javax.naming.InitialContext.bind(InitialContext.java:371)
at com.netscape.server.deployment.EjbReg.deployToNaming(Unknown Source)
at com.netscape.server.deployment.EjbReg.registerEjbJar(Compiled Code)
at com.netscape.server.deployment.EjbReg.registerEjbJar(Compiled Code)
at com.netscape.server.deployment.EjbReg.run(Compiled Code)
at com.netscape.server.deployment.EjbReg.main(Unknown Source)
Start registering iAS 60 Fortune Application...
Start iPlanet Application Server
Start iPlanet Application Server
Start Web Server iPlanet-WebServer-Enterprise/6.0SP1 B08/20/200100:58
warning: daemon is running as super-user
[LS ls1] http://gedemo1.plateau.com, port 80 ready
to accept requests
startup: server started successfully.
After completion of installation, I tried to start the console. But I got the following error;
"Cant connect ot the admin server. The url is not correct or the server is not running.
Finally,when I started the admintool(iASTT),it shows the iAS1
was registered( marked with a red cross mark) and says "cant login. make sure the user
name & passwdord are correct" when i click on it.
Thanks in advance for any help
MadhaviHi,
Make sure that the directory server is installed first. If it is running
ok, then you can try adding an admin user, please check the following
technote.
http://knowledgebase.iplanet.com/ikb/kb/articles/4106.html
regards
Swami
madhavi korupolu wrote:
I am attempting to install ias Enterprise Edition (6.0 SP3) on
solaris 2.8 using typical in basesetup. I am trying to install new
Directory server as I don't have an existing one.
During the installation I got the following error.
ERROR: Ldap Authentication failed for url
ldap://hostname:389/o=NetScape Root user id admin (151: Unknown
Error)
Fatal Slapd did not add Directory server information to config
Server.
Warning slapd could'nt populate with ldif file Yes error code 151.
ERROR:Failure installing iPlanet Directory Server.
Do you want to continue: ( I entered yes )
Configuring Administration Server Segmentation fault core dumped.
Error: Failure installing Netscape Administration Server.
Do you want to continue:( I responded with yes).
And during the Extraction I got the following
ERROR:mple_bind: Can't connect to the LDAP server - No route to host
ERROR: Unable to connect to LDAP Directory Server
Hostname: hostname
Port: 389
User: cn=Directory Manager
Password: <password-for-cn=Directory Manager
Please make sure this Directory Server is currently running.
You might need to run 'stop-slapd' and then
'start-slapd' in the Directory Server home directory, in order to
restart
LDAP. When finished, press ENTER to continue, or S to skip this
step:
Start registering Bootstrap EJB...
javax.naming.NameNotFoundException
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled > Code)
at javax.naming.NamingException.<init>(NamingException.java:114)
at
javax.naming.NameNotFoundException.<init>(NameNotFoundException.java:
48)
at com.netscape.server.jndi.RootContext.resolveCtx(Unknown Source)
"ldaperror" 76 lines, 2944 characters
at com.netscape.server.jndi.RootContext.resolveCtx(Unknown Source)
at com.netscape.server.jndi.RootContext.bind(Unknown Source)
at com.netscape.server.jndi.RootContext.bind(Unknown Source)
at javax.naming.InitialContext.bind(InitialContext.java:371)
at com.netscape.server.deployment.EjbReg.deployToNaming(Unknown
Source)
at com.netscape.server.deployment.EjbReg.registerEjbJar(Compiled
Code)
at com.netscape.server.deployment.EjbReg.registerEjbJar(Compiled
Code)
at com.netscape.server.deployment.EjbReg.run(Compiled Code)
at com.netscape.server.deployment.EjbReg.main(Unknown Source)
Start registering iAS 60 Fortune Application...
Start iPlanet Application Server
Start iPlanet Application Server
Start Web Server iPlanet-WebServer-Enterprise/6.0SP1 B08/20/200100:58
warning: daemon is running as super-user
[LS ls1] http://gedemo1.plateau.com, port 80 ready
to accept requests
startup: server started successfully.
After completion of installation, I tried to start the console. But I
got the following error;
"Cant connect ot the admin server. The url is not correct or the
server is not running.
Finally,when I started the admintool(iASTT),it shows the iAS1
was registered( marked with a red cross mark) and says "cant login.
make sure the user
name & passwdord are correct" when i click on it.
Thanks in advance for any help
Madhavi
Try our New Web Based Forum at http://softwareforum.sun.com
Includes Access to our Product Knowledge Base! -
Error during lookup of remote ejb CaseService - Oracle ACM 12C Standalone
StandAlone Setup:
CD %ORACLE_HOME%\soa\common\bin
set QS_TEMPLATES=%ORACLE_HOME%\soa\common\templates\wls\oracle.soa_template_12.1.3.jar, %ORACLE_HOME%\osb\common\templates\wls\oracle.osb_template_12.1.3.jar
qs_config.cmd
Then ran config.cmd from WLS and extended BPM domain, then was able to see composer app in deployment.
AdminServer Args:
set USER_MEM_ARGS=-Xms512m -Xmx3096m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=1024m
Error
====
Error during ejb lookup from bpm services client.
Error during lookup of remote ejb CaseService .
Contact Oracle support if exception can not be fixed.
at oracle.bpm.client.impl.casemgmt.CaseManagementServiceRemoteClient.get
CaseService(CaseManagementServiceRemoteClient.java:86)
at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.getCaseService(NotificationCallbackUtil.java:158)
at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.isActivityRegistered(NotificationCallbackUtil.java:167)
at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.registerEmailActivity(NotificationCallbackUtil.java:83)
at oracle.bpm.casemgmt.fabric.CaseManagementServiceEngine.stateChanged(C
aseManagementServiceEngine.java:1340)
at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListene
rs(FabricLifecycle.java:54)
at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(Fabr
icLifecycle.java:41)
at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshI
mpl.java:204)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
on(AopUtils.java:318)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
inpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:150)
at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEven
tAspect.java:71)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
cAopProxy.java:202)
at com.sun.proxy.$Proxy324.postDeployInit(Unknown Source)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.r
un(FabricKernelInitializerServlet.java:1008)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
(WorkManagerExecutor.java:184)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
er.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'ejb.bpm.c
ase.CaseService' didn't find subcontext 'bpm'. Resolved 'ejb'; remaining name 'b
pm/case/CaseService'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic
NamingNode.java:1180)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.jav
a:265)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.j
ava:187)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:21
0)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:22
4)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.j
ava:253)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at oracle.bpm.client.impl.casemgmt.CaseManagementServiceRemoteClient.get
CaseService(CaseManagementServiceRemoteClient.java:80)
at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.getCaseService(NotificationCallbackUtil.java:158)
at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.isActivityRegistered(NotificationCallbackUtil.java:167)
at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.registerEmailActivity(NotificationCallbackUtil.java:83)
at oracle.bpm.casemgmt.fabric.CaseManagementServiceEngine.stateChanged(C
aseManagementServiceEngine.java:1340)
at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListene
rs(FabricLifecycle.java:54)
at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(Fabr
icLifecycle.java:41)
at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshI
mpl.java:204)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
on(AopUtils.java:318)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
inpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:150)
at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEven
tAspect.java:71)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
cAopProxy.java:202)
at com.sun.proxy.$Proxy324.postDeployInit(Unknown Source)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.r
un(FabricKernelInitializerServlet.java:1008)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
(WorkManagerExecutor.java:184)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
er.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
>
Please help. The problem does not occur with Integrated WLS. I think the config scripts are correctly running from JDev.Hi,
It's not easy to tell what's wrong with your example.
Maybe you could send me a zip and I'll check when I have some time.
By the way, you're asking a question about the lookup of an EJB3, I wrote an article that covers that topic.
It should give you some interesting input.
http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html
Regards. -
No FINISHED DEPLOYMENT message during deployment in WD
Dear All,
I have made some changes to the existing WD Java application and tried to Build it and Deploy that.
There is no error during build and there is no FINISHED DEPLOYMENT message being displayed.
Start Deployment Message is being displayed
Created a temporary Copy massage is being displayed
Additional log information about the deployment is being displayed.
The additional log details are as below:
Dec 15, 2010 4:02:58 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[014]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[/usr/sap/SBP/JC07/SDM/program/log/sdmcl20101215120250.log]/>
<!PATTERN[sdmcl20101215120250.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Dec 15, 2010 4:02:50 PM Info: -
Starting deployment -
Dec 15, 2010 4:02:50 PM Info: Error handling strategy: OnErrorStop
Dec 15, 2010 4:02:50 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Dec 15, 2010 4:02:50 PM Info: Update strategy: UpdateAllVersions
Dec 15, 2010 4:02:50 PM Info: Starting deployment prerequisites:
Dec 15, 2010 4:02:51 PM Error: Cannot connect to database: Could not load or instantiate some required class.
Additional error message is:
java.lang.NoClassDefFoundError: com.sap.security.core.server.secstorefs.Crypt (initialization failure)
Stack trace of original error or exception is:
java.lang.NoClassDefFoundError: com.sap.security.core.server.secstorefs.Crypt (initialization failure)
at java.lang.Throwable.<init>(Throwable.java:57)
at java.lang.Throwable.<init>(Throwable.java:68)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:123)
at com.sap.security.core.server.secstorefs.SecStoreFS.setDefaultFilenames(SecStoreFS.java:242)
at com.sap.sdm.is.secstore.extern.SecureStoreAccessImpl.initSecStoreFS(SecureStoreAccessImpl.java:91)
at com.sap.sdm.is.secstore.extern.SecureStoreAccessImpl.<init>(SecureStoreAccessImpl.java:30)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1238)
at com.sap.sdm.is.secstore.SecureStoreAccessFactoryImpl.createInstance(SecureStoreAccessFactoryImpl.java:128)
at com.sap.sdm.serverext.servertype.dbsc.DBSCExternalFactory.createConnectionManager(DBSCExternalFactory.java:112)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.createConnectionManager(DatabaseTargetSystem.java:288)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.createNewDataSource(DatabaseTargetSystem.java:233)
at com.sap.sdm.serverext.servertype.dbsc.DBConnectServiceImpl.getDataSource(DBConnectServiceImpl.java:52)
at com.sap.sdm.app.cvers.wrapper.CVersFactory.createCVersManager(CVersFactory.java:63)
at com.sap.sdm.app.cvers.deplobs.impl.CVersProxyImpl.updateCVers(CVersProxyImpl.java:134)
at com.sap.sdm.persistency.RepositoryPersistor.persistRepository(RepositoryPersistor.java:54)
at com.sap.sdm.app.proc.deployment.states.StateManager.processNewInstallation(StateManager.java:142)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:71)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.initStateMachine(DeployerImpl.java:340)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploymentPrerequisite(DeployerImpl.java:484)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:91)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)
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:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
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:758)
Caused by: java.lang.Throwable: java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:195)
at javax.crypto.Cipher.a(Unknown Source)
at javax.crypto.Cipher.getInstance(Unknown Source)
at iaik.security.provider.IAIK.a(Unknown Source)
at iaik.security.provider.IAIK.addAsJDK14Provider(Unknown Source)
at iaik.security.provider.IAIK.addAsJDK14Provider(Unknown Source)
at com.sap.security.core.server.secstorefs.Crypt.<clinit>(Crypt.java:82)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
... 36 more
Caused by: java.lang.Throwable: java.lang.SecurityException: Cannot set up certs for trusted CAs
at javax.crypto.b.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
... 44 more
Caused by: java.lang.Throwable: java.lang.SecurityException: Jurisdiction policy files are not signed by trusted signers!
at javax.crypto.b.a(Unknown Source)
at javax.crypto.b.g(Unknown Source)
at javax.crypto.b$0.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:241)
... 47 moreContinuation to the prev message log....
Dec 15, 2010 4:02:51 PM Warning: Caught CVersProxyAccessException while saving repository: CVersAccessException: Cannot access CVers due to missing or incorrect configuration.
Additional error message is:
com.sap.sdm.apiint.serverext.servertype.TargetServiceException: Cannot provide connect data for database target system "CONFIG_DB".
Additional error message is:
com.sap.sdm.serverext.servertype.dbsc.DatabaseConnectException: Cannot connect to database: Could not load or instantiate some required class.
Additional error message is:
java.lang.NoClassDefFoundError: com.sap.security.core.server.secstorefs.Crypt (initialization failure)
Dec 15, 2010 4:02:51 PM Info: Loading selected archives...
Dec 15, 2010 4:02:51 PM Info: Loading archive '/usr/sap/SBP/JC07/SDM/program/temp/temp31519dewa.gov.aeisumangstc.ear'
Dec 15, 2010 4:02:51 PM Error: Cannot connect to database: Could not load or instantiate some required class.
Additional error message is:
java.lang.NoClassDefFoundError: com.sap.security.core.server.secstorefs.Crypt (initialization failure)
Stack trace of original error or exception is:
java.lang.NoClassDefFoundError: com.sap.security.core.server.secstorefs.Crypt (initialization failure)
at java.lang.Throwable.<init>(Throwable.java:57)
at java.lang.Throwable.<init>(Throwable.java:68)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:123)
at com.sap.security.core.server.secstorefs.SecStoreFS.setDefaultFilenames(SecStoreFS.java:242)
at com.sap.sdm.is.secstore.extern.SecureStoreAccessImpl.initSecStoreFS(SecureStoreAccessImpl.java:91)
at com.sap.sdm.is.secstore.extern.SecureStoreAccessImpl.<init>(SecureStoreAccessImpl.java:30)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1238)
at com.sap.sdm.is.secstore.SecureStoreAccessFactoryImpl.createInstance(SecureStoreAccessFactoryImpl.java:128)
at com.sap.sdm.serverext.servertype.dbsc.DBSCExternalFactory.createConnectionManager(DBSCExternalFactory.java:112)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.createConnectionManager(DatabaseTargetSystem.java:288)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.createNewDataSource(DatabaseTargetSystem.java:233)
at com.sap.sdm.serverext.servertype.dbsc.DBConnectServiceImpl.getDataSource(DBConnectServiceImpl.java:52)
at com.sap.sdm.app.cvers.wrapper.CVersFactory.createCVersManager(CVersFactory.java:63)
at com.sap.sdm.app.cvers.deplobs.impl.CVersProxyImpl.updateCVers(CVersProxyImpl.java:134)
at com.sap.sdm.persistency.RepositoryPersistor.persistRepository(RepositoryPersistor.java:54)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.SduAdderImpl.addSdu(SduAdderImpl.java:99)
at com.sap.sdm.app.proc.deployment.states.StateChooseSDU.processAddSDU(StateChooseSDU.java:286)
at com.sap.sdm.app.proc.deployment.states.StateChooseSDU.processEvent(StateChooseSDU.java:67)
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.loadSelectedArchives(DeployerImpl.java:276)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploymentPrerequisite(DeployerImpl.java:490)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:91)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)
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:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
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:758)
Caused by: java.lang.Throwable: java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:195)
at javax.crypto.Cipher.a(Unknown Source)
at javax.crypto.Cipher.getInstance(Unknown Source)
at iaik.security.provider.IAIK.a(Unknown Source)
at iaik.security.provider.IAIK.addAsJDK14Provider(Unknown Source)
at iaik.security.provider.IAIK.addAsJDK14Provider(Unknown Source)
at com.sap.security.core.server.secstorefs.Crypt.<clinit>(Crypt.java:82)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
at com.sap.security.core.server.secstorefs.SecStoreFS.setDefaultFilenames(SecStoreFS.java:242)
at com.sap.sdm.is.secstore.extern.SecureStoreAccessImpl.initSecStoreFS(SecureStoreAccessImpl.java:91)
at com.sap.sdm.is.secstore.extern.SecureStoreAccessImpl.<init>(SecureStoreAccessImpl.java:30)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1238)
at com.sap.sdm.is.secstore.SecureStoreAccessFactoryImpl.createInstance(SecureStoreAccessFactoryImpl.java:128)
at com.sap.sdm.serverext.servertype.dbsc.DBSCExternalFactory.createConnectionManager(DBSCExternalFactory.java:112)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.createConnectionManager(DatabaseTargetSystem.java:288)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.createNewDataSource(DatabaseTargetSystem.java:233)
at com.sap.sdm.serverext.servertype.dbsc.DBConnectServiceImpl.getDataSource(DBConnectServiceImpl.java:52)
at com.sap.sdm.app.cvers.wrapper.CVersFactory.createCVersManager(CVersFactory.java:63)
at com.sap.sdm.app.cvers.deplobs.impl.CVersProxyImpl.updateCVers(CVersProxyImpl.java:134)
at com.sap.sdm.persistency.RepositoryPersistor.persistRepository(RepositoryPersistor.java:54)
at com.sap.sdm.app.proc.deployment.states.StateManager.processNewInstallation(StateManager.java:142)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:71)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.initStateMachine(DeployerImpl.java:340)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploymentPrerequisite(DeployerImpl.java:484)
... 18 more
Caused by: java.lang.Throwable: java.lang.SecurityException: Cannot set up certs for trusted CAs
at javax.crypto.b.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
... 44 more
Caused by: java.lang.Throwable: java.lang.SecurityException: Jurisdiction policy files are not signed by trusted signers!
at javax.crypto.b.a(Unknown Source)
at javax.crypto.b.g(Unknown Source)
at javax.crypto.b$0.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:241)
... 47 more
Dec 15, 2010 4:02:51 PM Warning: Caught CVersProxyAccessException while saving repository: CVersAccessException: Cannot access CVers due to missing or incorrect configuration.
Additional error message is:
com.sap.sdm.apiint.serverext.servertype.TargetServiceException: Cannot provide connect data for database target system "CONFIG_DB".
Additional error message is:
com.sap.sdm.serverext.servertype.dbsc.DatabaseConnectException: Cannot connect to database: Could not load or instantiate some required class.
Additional error message is:
java.lang.NoClassDefFoundError: com.sap.security.core.server.secstorefs.Crypt (initialization failure)
Dec 15, 2010 4:02:51 PM Info: Selected archives successfully loaded.
Dec 15, 2010 4:02:51 PM Info: Actions per selected component:
Dec 15, 2010 4:02:51 PM Info: Update: Selected development component 'isu/mangstc'/'dewa.gov.ae'/'SBP_SBPDEV_D'/'20101215160243'/'0' updates currently deployed development component 'isu/mangstc'/'dewa.gov.ae'/'SBP_SBPDEV_D'/'1981'/'0'.
Dec 15, 2010 4:02:51 PM Info: Ending deployment prerequisites. All items are correct.
Let me know how this can be resolved.
Regards,
Vijaykumar. -
ECC Error occurred during initialization of VM
Hi guys,
when I installed ecc6 into the suse-10 which is on the Vmware Server 1.0.3, when I installed oracle,there showed some mistakes,
/oracle/stage/102_64/database/SAP/SVRCUSTOM.RSP --> /tmp/.orainst_rsp.6246: Done
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be redhat-3, SuSE-9, SuSE-10, redhat-4, UnitedLinux-1.0, asianux-1 or asianux-2
Passed
All installer requirements met.
Preparing to launch Oracle Universal Installer from /tmp/OraInstall1912-09-24_09-47-39AM. Please wait ...oraecc@sap01:/oracle/stage/102_64/database/SAP> Error occurred during initialization of VM
java.lang.ExceptionInInitializerError
1、the sap's graph was normal.
2、when I installed SuSE, I chose the component of SAP and Oracle which contained some rpms,such as saplocales,orarun...
and in that time, it show the dependency conflict, and I chose ingore. (as I haved tried to choose one of them ,but then failed.)
pls someFriends help me.
BestRegards!Hi,
Have you checked the following notes:
Note 958253 - SUSE LINUX Enterprise Server 10: Installation notes
Note 1122387 - Linux: SAP Support in virtualized environments
Kind regards,
Mark -
Hello everyone,
I developed a Web Service prototype accessing remote EJB using the EJB
control with special syntax in the jndi-name attribute: @jws:ejb
home-jndi-name="t3://10.10.245.70:7131/AccountDelegatorEJB"
Everything works fine, but I get an error when I restrict access to my web
service with a declarative security model by implementing steps provided in
help doc:
- Define the web resource you wish to protect
- Define which security role is required to access the web resource
- Define which users are granted the required security role
- Configure WebLogic Server security for my web service(Compatibility
Security/Users)
I launch the service by entering the address in a web browser. When prompted
to accept the digital certificate, click Yes, when prompted for network
authentication information, enter username and password, navigate to the
Test Form tab of Test View, invoke the method by clicking the button and I
get the following exception:
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed for
name:t3://10.10.245.70:7131/AccountDelegatorEJB]</faultstring>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
lookup from jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed
for name:t3://10.10.245.70:7131/AccountDelegatorEJB] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64) </jwErrorDetail>
</detail>
</error>
I have a simple Hello method as well in my WebService (which is also
restricted) and it works fine, but remote EJB access doesn't. I tested my
prototype on Weblogic 7.2 and 8.1 platforms - same result.
Is that a bug or I am missing some additional configuration in order to get
that working. Has anyone seen similar behavior? Is there a known resolution?
Or a suggested way to work around the problem?
Thank you.
AndreAndre,
It would be best if this issue is handled as an Eval Support case. Please
BEA Customer Support at http://support.beasys.com along with the required
files, and request that an Eval support case be created for this issue.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Andre Shergin" <[email protected]> wrote in message
news:[email protected]...
Anurag,
I removed "t3", still get an error but a different one (Unable to create
InitialContext:null):
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi://secuser1:[email protected]:7131/AccountDelegatorEJB[Unable to
create InitialContext:null]</faultstring>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
lookup from
jndi://secuser1:[email protected]:7131/AccountDelegatorEJB[Unable to
create InitialContext:null] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetVisaHistoryTransactions.getVisaHistoryTxn(GetVisaHistoryTransactions
.jws:67) </jwErrorDetail>
</detail>
</error>
Note: inter-domain communication is configured properly. The Web Service to
remote EJB works fine without a declarative security.
Any other ideas?
Thank you for your help.
Andre
"Anurag" <[email protected]> wrote in message
news:[email protected]...
Andre,
It seems you are using the URL
jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB
whereas you should not be specifying the "t3:" protocol.
The URL should be like
jndi://secuser1:[email protected]:7131/AccountDelegatorEJB
Please do let me know if you see any issues with this.
Note that this will only allow you to access remote EJBs in the same WLS
domain. For accessing EJBs on another domain, you need to configure
inter-domain communication by
following a few simple steps as mentioned at
http://e-docs.bea.com/wls/docs81/ConsoleHelp/jta.html#1106135. This link has
been provided in the EJB Control Workshop documentation.
Regards,
Anurag
"Andre Shergin" <[email protected]> wrote in message
news:[email protected]...
Raj,
I tried that before, it didn't help. I got similar error message:
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB[Lookup
failed for
name:t3://secuser1:[email protected]:7131/AccountDelegatorEJB]</faultstr
ing>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
lookup from
jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB[Lookup
failed for
name:t3://secuser1:[email protected]:7131/AccountDelegatorEJB] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64) </jwErrorDetail>
</detail>
</error>
Anything else should I try?
P.S. AccountDelegatorEJB, the remote EJB my Web Service calls is NOTaccess
restricted.
I hope there is a solution.
Thanks,
Andre
"Raj Alagumalai" <[email protected]> wrote in message
news:[email protected]...
Andre,
Can you try using the following url with username and password
jndi://username:password@host:7001/my.resource.jndi.object ?
once you add webapp level security, the authenticated is the user who
invokes the EJB.
http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/controls/ejb/con
CreatingANewEJBControl.html?skipReload=true
has more info on using remote EJB's.
Hope this helps.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Alla Resnik" <[email protected]> wrote in message
news:[email protected]...
Hello everyone,
I developed a Web Service prototype accessing remote EJB using the EJB
control with special syntax in the jndi-name attribute: @jws:ejb
home-jndi-name="t3://10.10.245.70:7131/AccountDelegatorEJB"
Everything works fine, but I get an error when I restrict access to my
web
service with a declarative security model by implementing steps
provided
in
help doc:
- Define the web resource you wish to protect
- Define which security role is required to access the web resource
- Define which users are granted the required security role
- Configure WebLogic Server security for my web service(Compatibility
Security/Users)
I launch the service by entering the address in a web browser. Whenprompted
to accept the digital certificate, click Yes, when prompted for
network
authentication information, enter username and password, navigate tothe
Test Form tab of Test View, invoke the method by clicking the buttonand
I
get the following exception:
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed for
name:t3://10.10.245.70:7131/AccountDelegatorEJB]</faultstring>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during
JNDI
lookup from jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookupfailed
for name:t3://10.10.245.70:7131/AccountDelegatorEJB] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260)at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64)</jwErrorDetail>
</detail>
</error>
I have a simple Hello method as well in my WebService (which is also
restricted) and it works fine, but remote EJB access doesn't. I testedmy
prototype on Weblogic 7.2 and 8.1 platforms - same result.
Is that a bug or I am missing some additional configuration in order
to
get
that working. Has anyone seen similar behavior? Is there a knownresolution?
Or a suggested way to work around the problem?
Thank you.
Andre -
We are in the process of migrating from Weblogic 6.1 SP2 to SP5. We have an applet
that
subscribes to a JMS Topic. The applet is throwing the following exception with
SP5:
java.lang.ExceptionInInitializerError: java.security.AccessControlException: access
denied
(java.util.PropertyPermission weblogic.kernel.allowQueueThrottling read)
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
at java.lang.System.getProperty(Unknown Source)
at weblogic.kernel.Kernel.initAllowThrottleProp(Kernel.java:79)
at weblogic.kernel.Kernel.<clinit>(Kernel.java:54)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Unknown Source)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.fedex.efm.frontend.model.JMSMessageProcessor.<init>(JMSMessageProcessor.java:266)
at com.fedex.efm.frontend.view.EFMAbstractApplet.startMessageProcessor(EFMAbstractApplet.java:81)
at com.fedex.efm.frontend.view.EFMAbstractApplet.start(EFMAbstractApplet.java:187)
at com.fedex.efm.frontend.view.EFMApplet.start(EFMApplet.java:430)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Any ideas as to what I am missing?
Thanks,
RamPrasad,
It's one thing not to have to modify the security policy on the server,
but on a client and applets have even bigger restrictions this might
very well be the only way since the default applet restrictions would
not allow a lot of permissions granted by default for normal Java
applications.
Dejan
Prasad Peddada wrote:
Deyan D. Bektchiev wrote:
Ram,
You are missing a permission grant in your policy file and the
SecurityManager doesn't allow the code to read that property.
You have either configured a different security manager or have the
wrong file in use.
For applets this file might be in the user's home directory and named
.java.policy
you need to have the following line somethere in it:
grant {
permission java.util.PropertyPermission "*", "read,write";
Which will allow any applet to read and write any JVM property.
Look at Java permissions is you need more info:
http://java.sun.com/j2se/1.3/docs/guide/security/permissions.html
--dejan
Ram Gopal wrote:
We are in the process of migrating from Weblogic 6.1 SP2 to SP5. We
have an applet
that
subscribes to a JMS Topic. The applet is throwing the following
exception with
SP5:
java.lang.ExceptionInInitializerError:
java.security.AccessControlException: access
denied
(java.util.PropertyPermission weblogic.kernel.allowQueueThrottling
read) at java.security.AccessControlContext.checkPermission(Unknown
Source) at java.security.AccessController.checkPermission(Unknown
Source) at java.lang.SecurityManager.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPropertyAccess(Unknown Source) at
java.lang.System.getProperty(Unknown Source) at
weblogic.kernel.Kernel.initAllowThrottleProp(Kernel.java:79) at
weblogic.kernel.Kernel.<clinit>(Kernel.java:54) at
weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
at java.lang.Class.newInstance0(Native Method) at
java.lang.Class.newInstance(Unknown Source) at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at
javax.naming.InitialContext.init(Unknown Source) at
javax.naming.InitialContext.<init>(Unknown Source) at
com.fedex.efm.frontend.model.JMSMessageProcessor.<init>(JMSMessageProcessor.java:266)
at
com.fedex.efm.frontend.view.EFMAbstractApplet.startMessageProcessor(EFMAbstractApplet.java:81)
at
com.fedex.efm.frontend.view.EFMAbstractApplet.start(EFMAbstractApplet.java:187)
at com.fedex.efm.frontend.view.EFMApplet.start(EFMApplet.java:430)
at sun.applet.AppletPanel.run(Unknown Source) at
java.lang.Thread.run(Unknown Source)
Any ideas as to what I am missing?
Thanks,
Ram
This is a WLS bug. You shouldn't have to modify security policy.
Please approach support for a fix.
Cheers,
-- Prasad
Maybe you are looking for
-
MultiProvider design CMP Warnings
Hello, I'm trying to activate a MultiProvider using some infocubes including 0PA_C01 and 0PAOS_C01. When I check some warnings appears, among others: Check of MultiProvider ZM: Error messages from point of view of OLAP processor:
-
I'm not sure what's going on with Verizon's ordering system. I ordered two Iphone 6 Plus on 9/19. When I returned from the weekend, I decided to call and check status, and I was told that there was only one phone on my order. They had to cancel that
-
Help! "Disk can not be read from or written to" error
Hi, I just bought a couple of movies on itunes but when I try to sync them to iphone it stalls and I get the error "Attempt to copy to disk "my iphone" failed. The disk could not be read from or written to". Oddly though everything else except the vi
-
Hi ABAP Gurus, I have a problem with ALV subtotals and don't now how to solve it using ALV. I might have to go back to Classical reports if I cannot solve it. Here is the Problem : The tables BSET stores the Taxes info for the accounting documents. E
-
Need an adobe pdf with 2 content areas like a book
Dear all, maybe an easy question for you but I didn´t find a solution yet. I need a PDF like a book. Means Page 1 on the left side, Page 2 on the right side. On Next page: Page 3 on left, Page 4 on right side and so on. Thanks. Kind regards Frank