Exception in starting WLS_Portlet Server through console

Hi All
I have been working on Oracle WebCenter v11.1.3.1 and have successfully installed Weblogic Server and Webcenter.
When I try to restart the server I see all the instances except for WLS_Portlet instance.
Below is the error log from nodemanager console
INFO: Server output log file is 'D:\ramchow\Softwares\Oracle\Middleware\user_pro
jects\domains\fmw_domain\servers\WLS_Portlet\logs\WLS_Portlet.out'
*<Jun 17, 2010 6:52:25 PM> <INFO> <fmw_domain> <WLS_Portlet> <Server failed durin*
g startup so will not be restarted>
Jun 17, 2010 6:52:25 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
*<Jun 17, 2010 6:52:25 PM> <WARNING> <Exception while starting server 'WLS_Portle*
t'>
java.io.IOException: Server failed to start up. See server output log for more d
etails.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:33
*1)*
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Jun 17, 2010 6:52:25 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'WLS_Portlet'
java.io.IOException: Server failed to start up. See server output log for more d
etails.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:33
*1)*
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
I tried to check everything thing but could not succeed in starting the the portal instance.
Your help would be highly appreciated. Anybody can reach me at +91 9717003417
regards
Ramesh

You probably want to post this in the WebCenter Framework forum:
WebCenter Portal
Brad

Similar Messages

  • A lot of problem for an error: Cannot start Managed Server through NM

    Hi, all. Thank for coming here.
    My main problem is cannot start Manager server through Node Manager. I've configured with the same way on my friend's network and It's works but It's wrong with mine.
    my weblogic domain:
    Machine 1: Administration Server + 1 Managed server
    Machine 2: 1 Managed server
    all of these servers communicate through SSL protocol. When I try to start Managed Server on remote machine:
    output from console which was invoked startWebLogic.sh
    +<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    +<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'MS01'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    And this is MS01 log:
    starting weblogic with Java version:
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    +JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]+
    The application has requested the JVM to exit with an fatal error from JNI. Error message:
    JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    Starting WLS with line:
    +/opt/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin/java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=MS01 -Djava.security.policy=/opt/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.ReverseDNSAllowed=false -Xrs -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/opt/Oracle/Middleware/wlserver_10.3 -Dwls.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.1.35:7001 -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/opt/Oracle/Middleware/patch_wls1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/patch_wlp1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/wlportal_10.3/p13n/lib/system:/opt/Oracle/Middleware/wlportal_10.3/light-portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/lib/system:/opt/Oracle/Middleware/wlportal_10.3/analytics/lib/system:/opt/Oracle/Middleware/wlportal_10.3/apps/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/deprecated/lib/system:/opt/Oracle/Middleware/wlportal_10.3/content-mgmt/lib/system -Dweblogic.alternateTypesDirectory=/opt/Oracle/Middleware/wlportal_10.3/portal/lib/security weblogic.Server+
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    +JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]+
    The application has requested the JVM to exit with an fatal error from JNI. Error message:
    JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    Stopping PointBase server...
    PointBase server stopped.
    And this is output from console which node manager runs on:
    +<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    +<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'MS01'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    I tried to start Managed server some times again, but I face up to strange issue, this is output from console which Admin Server runs on (these exception messages throws continuously):
    +<Sep 9, 2010 12:42:53 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceNeverXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:57 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "p13nDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceAlwaysXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    I can ensure that all of these connection pool has configured to run on 9093 port already. Then I view the DOMAIN_NAME/pointbase.log, it said:
    Unable to start the server. start server error: java.net.BindException: Address already in use
    I cannot understand what's run on pointbase address ?
    All of these error make me angry, because I've configured with the same way on other system and It's work. I've spent all of week to fix these bug, but I'm having nothing :((
    Please help me.

    Thank Jay SenSharma.
    I've looked for these JAVA_OPTION values you said, but I cant found them. That value is content of JAVA_DEBUG option, not JAVA_OPTION. In my situation, JAVA_DEBUG=" " (it's not set by default).
    Please re-view my error log:
    Node Manager output:
    +<Sep 9, 2010 11:32:44 PM> <WARNING> <Exception while starting server 'MS01'>+
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    Sep 9, 2010 11:32:44 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'MS01'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    Managed server MS01's log:
    +<Sep 9, 2010 11:45:05 PM> <INFO> <NodeManager> <Server output log file is '/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.out'>+
    +<Sep 9, 2010 11:45:07 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>+
    +<Sep 9, 2010 11:45:09 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 9216172 Tue Jan 12 02:07:27 PST 2010+
    WebLogic Server 10.3.2.0  Tue Oct 20 12:16:15 PDT 2009 1267925 >
    +<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - Invalid xsi:type qname: 'wsrp:wsrp-identity-asserterType' in element realm@http://xmlns.oracle.com/weblogic/domain>+
    +<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - /opt/Oracle/Middleware/user_projects/domains/devdomain/<unknown>:11:9: error: failed to load java type corresponding to t=wsrp-identity-asserterType@http://www.bea.com/ns/wlp/90/security/wsrp>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320400> <The log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log00002. Log messages will continue to be logged in /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log.>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log is opened. All server side log events will be written to this file.>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details..+
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".  See the nested exception for details.
    +     at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)+
    +     at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".  See the nested exception for details.
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
    +     at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
    +     at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".  See the nested exception for details.
    +     at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:95)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
    +     at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: java.lang.RuntimeException: There were errors initializing your configuration: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal store error> org.apache.openjpa.util.StoreException: com.pointbase.jdbc.jdbcUniversalDriver
    +     at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:123)+
    +     at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.createConnectionFactory(JDBCConfigurationImpl.java:776)+
    +     at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:683)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
    +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
    +     at java.lang.reflect.Method.invoke(Method.java:597)+
    +     at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:288)+
    +     at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
    +     at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
    +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
    +     at java.lang.reflect.Method.invoke(Method.java:597)+
    +     at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)+
    +     at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
    +     at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
    +     at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
    +     at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
    +     at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:300)+
    +     at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)+
    +     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)+
    +     at weblogic.security.SecurityService.start(SecurityService.java:141)+
    +     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
    +     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)+
    +     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)+
    Caused by: java.lang.ClassNotFoundException: com.pointbase.jdbc.jdbcUniversalDriver
    +     at java.lang.Class.forName0(Native Method)+
    +     at java.lang.Class.forName(Class.java:169)+
    +     at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:85)+
    +     ... 38 more+
    +     at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:302)+
    +     at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
    +     at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
    +     Truncated. see log file for complete stacktrace+
    +>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:+
    There are 1 nested errors:
    +weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)+
    +     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)+
    +     at weblogic.security.SecurityService.start(SecurityService.java:141)+
    +     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
    +     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)+
    +     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)+
    +>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>+
    +<Sep 9, 2010 11:45:17 PM> <FINEST> <NodeManager> <Waiting for the process to die: 16443>+
    +<Sep 9, 2010 11:45:17 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>+
    +<Sep 9, 2010 11:45:18 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>+
    ps:
    I've come your weblog and found alot of tips for debugging WebLogic Server exceptions. It's really helpful. Thanks.
    Edited by: Doubt_Man on Sep 10, 2010 10:49 AM
    Edited by: Doubt_Man on Sep 10, 2010 3:54 PM

  • Adding patch jar file while starting Managed Server through Node Manager

    Hi,
    I am using Weblogic Express 10.0 on Linux env, Jrockit JVM.
    I have a patch jar file from BEA, I added it to Weblogic start script, when I start the Managed server by using startManagedWeblogic.sh script, I can see that patch jar file is added to classpath when I grep for Java process.(ps -ef | grep -i java).
    But when I start the Managed server through NodeManager and grep for java process, I dont see the patch jar file added to classpath of Managed server process which is started.
    Can someone let me know if I have to add the patch jar file somewhere else along with Weblogic start script if starting Managed server through Node Manager?
    Weblogic Consultant

    Thanks for your response.
    I found another way to do this.
    Edit nodemanager.properties file and set StartScriptEnabled=true (By default it is false), and then restart the Node Manager process.
    Enabling this setting to true will enable the NodeManager process to use startManagedWeblogic.sh script while starting the managed server, all the added jar files, memory settings will be taken from start script of Weblogic
    Weblogic Consultant

  • Error starting managed server through admin console

    Hey,
    I am trying to start the managed server through the admin console, but it gives fails and give errors in the log, below mention is the log file details:
    ####<2007-dec-18 kl 14:05 CET> <Error> <Security> <SESO-ODX251909> <ManagedServer_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1197983149062> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:469)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:342)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
         at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:115)
         at weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    ####<2007-dec-18 kl 14:05 CET> <Critical> <WebLogicServer> <SESO-ODX251909> <ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1197983149109> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:898)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    I am using weblogic server 9.2 on windows. Node manager is working fine. i have tried installing weblogic server several times but it gives the same error each time i start a managed server. Kindly help.
    Regards,
    Alka

    Can you start a managed server from the command line?
    <Alka Parveen> wrote in message news:[email protected]...
    Hey,
    I am trying to start the managed server through the admin console, but it
    gives fails and give errors in the log, below mention is the log file
    details:
    ####<2007-dec-18 kl 14:05 CET> <Error> <Security> <SESO-ODX251909>
    <ManagedServer_1> <[ACTIVE] ExecuteThread: '0' for queue:
    'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
    <1197983149062> <BEA-090870> <The realm "myrealm" failed to be loaded:
    weblogic.security.service.SecurityServiceException:
    com.bea.common.engine.ServiceInitializationException:
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    weblogic.security.service.SecurityServiceException:
    com.bea.common.engine.ServiceInitializationException:
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:469)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    com.bea.common.engine.ServiceInitializationException:
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:342)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
    at
    com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    at
    weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:115)
    at
    weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
    at
    com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
    at
    com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    ####<2007-dec-18 kl 14:05 CET> <Critical> <WebLogicServer> <SESO-ODX251909>
    <ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1197983149109>
    <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException:
    [Security:090399]Security Services Unavailable
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:898)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    I am using weblogic server 9.2 on windows. Node manager is working fine. i
    have tried installing weblogic server several times but it gives the same
    error each time i start a managed server. Kindly help.
    Regards,
    Alka

  • Unable to start SOA server through Node Manager

    Hi All,
    I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
    I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
    Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
    Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
    I am getting an error while trying to start soa server with nmStart() command, below is the error message...
    "Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
    I executed the dumpStack() command, and i am getting the output as "No stack trace available"
    If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
    I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
    I followed some of the blogs like...
    http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
    http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
    Experts, please give your advice.
    Many Thanks,
    N

    Hi Narsing,
    I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
    Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
    As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
    Regards,
    Neeraj Sehgal
    Hi Neeraj,
    I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
    I have made sure the property StartScriptEnabled= true.
    I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to      FAILED_NOT_RESTARTABLE status.
    If i see the log messages in the nodemanager.log, this is the below message...
    <Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
    <Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
    <Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)
    The log message in the soa_server1.out file is as below...
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
    <Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
    Many Thanks.

  • Exception in starting managed server

    I am using WLS6.0 and have the exception when starting a newly created managed server.
    The admin server console prompted the attached exception messages. It seems compliant
    about security?
    If someone know what's wrong, please share with me.
    Thanks in advance!
    <Feb 8, 2001 12:01:21 PM CST> <Critical> <Log Management> <Unable to contact managed
    server - unitTest, at 202.45.228.90:8003. Domain logfile will not contain m
    essages from this server.
    java.lang.IllegalArgumentException: Invalid user name or password
    at weblogic.management.logging.DomainLogHandler.getMBeanHome(DomainLogHandler.java:281)
    at weblogic.management.logging.DomainLogHandler.subscribeToServer(DomainLogHandler.java:243)
    at weblogic.management.logging.DomainLogHandler.registerToMe(DomainLogHandler.java:183)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:559)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:545)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBeanServerImpl_WLSkel.java:382)
    at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
    at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
    at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:103)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >

    Yes, I started both admin and managed server with 'system' user with password typed
    in password.ini file.
    I used the default NT script startWeblogic.cmd and startManagedWeblogic.cmd to start
    them.
    Command prompt 1: startWeblogic.cmd
    Command prompt 2: startManagedWeblogic.cmd newServer http://localhost:7001
    The exception message goes to admin server's console while no error message goes
    to the managed server's console.
    "Sanjeev Chopra" <[email protected]> wrote:
    Are you starting both managed and admin server with as the 'system' user
    Is the system password password provided to both servers same ?
    Please post your startup commands for both the servers.
    kf cheung <[email protected]> wrote in message
    news:[email protected]...
    I am using WLS6.0 and have the exception when starting a newly createdmanaged server.
    The admin server console prompted the attached exception messages. Itseems compliant
    about security?
    If someone know what's wrong, please share with me.
    Thanks in advance!
    <Feb 8, 2001 12:01:21 PM CST> <Critical> <Log Management> <Unable tocontact managed
    server - unitTest, at 202.45.228.90:8003. Domain logfile will not containm
    essages from this server.
    java.lang.IllegalArgumentException: Invalid user name or password
    atweblogic.management.logging.DomainLogHandler.getMBeanHome(DomainLogHandler.j
    ava:281)
    atweblogic.management.logging.DomainLogHandler.subscribeToServer(DomainLogHand
    ler.java:243)
    atweblogic.management.logging.DomainLogHandler.registerToMe(DomainLogHandler.j
    ava:183)
    at java.lang.reflect.Method.invoke(Native Method)
    atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    ..java:559)
    atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    45)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    atweblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBean
    ServerImpl_WLSkel.java:382)
    atweblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
    atweblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
    atweblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.
    java:103)
    atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    7)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >

  • Starting WebLogic Server using Console

    This is a simple question. I am trying to start the WebLogic Server
    using the WebLogic Console. It seems to be starting the wrong WebLogic
    server.
    When I monitor the log information in the console I see it starts the
    server with a 32ms and a 32mx whereas in my startWebLogic.sh script I
    have specified 128ms and 128mx. How do I make my startconsole.sh script
    read the correct startWebLogic.sh script ? This is on solaris.
    When I ran the script startWebLogic.sh it was able to start up
    completely.
    Thanks.

    Ted,
    Thanks for the reply. Just another question on this-I have added a lot of jar files to the
    WEBLOGICCLASSPATH in my startWebLogic.sh script. I presume since I am starting the server using the
    console I need to add this information(the WEBLOGICCLASSPATH variable) to the startConsole.sh script
    and try running the server again.
    Currently its reporting that its unable to find the server classes which I wrote.
    Aswin.
    Ted Dyer wrote:
    Aswin,
    Sorry for the confusion. When you start the server in the console, you get a dialog window. There
    is a button labled "Advanced..." Click on that and set the "Java Heap (MB)" to 128. That will do
    what you want it to.
    Ted
    Aswin Dinakar <[email protected]> wrote:
    Ted,
    I guess I was not clear on my problem. When I start the weblogic server using the
    weblogic console it doesnt seem to be running the startweblogic.sh script. It seems to be
    running another version of the startweblogic.sh script which I dont know where its getting
    from.
    Aswin.
    Ted Dyer wrote:
    Aswin,
    Did you edit your startConsole.sh? The last line in that file should set your ms and mx.
    It should say something like:
    $JAVA -ms16m -mx48m -classpath $JAVACLASSPATH weblogic.Console
    Changing the ms and mx values here should have the affect you're looking for.
    Ted
    Aswin Dinakar <[email protected]> wrote:
    This is a simple question. I am trying to start the WebLogic Server
    using the WebLogic Console. It seems to be starting the wrong WebLogic
    server.
    When I monitor the log information in the console I see it starts the
    server with a 32ms and a 32mx whereas in my startWebLogic.sh script I
    have specified 128ms and 128mx. How do I make my startconsole.sh script
    read the correct startWebLogic.sh script ? This is on solaris.
    When I ran the script startWebLogic.sh it was able to start up
    completely.
    Thanks.

  • Access Exception after starting Managed Server

    After Starting the managed server in our one of the domains we are getting this
    following exception.Actually we are using JCA Adapters(Clarify and MQ).So after
    starting servers it is trying to access these adapters and corresponding application
    views.
    Exception class: weblogic.management.NoAccessRuntimeException
    Access not allowed for subject: principals=[admin], on ResourceType: AppViewDeployment
    Action: execute, Target: undeployApplicationView
    weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
    principals=[admin], on ResourceType: AppViewDeployment Action: execute, Target:
    undeployApplicationView
         at weblogic.management.internal.Helper$IsAccessAllowedPrivilegeAction.run(Helper.java:2034)
         at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
         at weblogic.management.internal.Helper.isAccessAllowed(Helper.java:1865)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:949)
         at com.bea.wlai.client.bean.DeployManagerBean.undeployApplicationView(Unknown
    Source)
         at com.bea.wlai.client.bean.DeployManagerBean_qam0jv_EOImpl.undeployApplicationView(DeployManagerBean_qam0jv_EOImpl.java:210)
         at com.bea.wlai.client.bean.DeployManagerBean_qam0jv_EOImpl_WLSkel.invoke(Unknown
    Source)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at com.bea.wlai.client.bean.DeployManagerBean_qam0jv_EOImpl_WLStub.undeployApplicationView(Unknown
    Source)
         at com.bea.adapter.web.AbstractDesignTimeRequestHandler.undepappvw(Unknown
    Source)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.bea.web.ControllerServlet.processRequest(ControllerServlet.java:356)
         at com.bea.web.ControllerServlet.doAction(ControllerServlet.java:282)
         at com.bea.web.ControllerServlet.doPost(ControllerServlet.java:175)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5445)
         at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3105)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2588)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:215)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:191)
    Thanks and regds
    Sudarsan M

              One not so good solution I ever used is to remove the managed server and reinstall/configure
              it.
              "Victor" <[email protected]> wrote:
              >
              >
              >
              >Hi,
              >
              >I am getting 'Connection Refused' exception while starting the Managed
              >Server.Attached
              >log has the complete trace. It was working fine till few days back and
              >I havent
              >changed any configuration.
              >
              >I will be thankful to you if anyone gives me a clue to trace for the
              >solution
              >on this.
              >
              >Regards,
              

  • Start managed server from console?

    If I try to start a new weblogic 10.3 managed server from the console then i get this error:
    "The server myserver does not have a machine associated with it.
    All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed."
    Starting the same managed server from the dos prompt "bin/startManagedServer.bat myserver" works, so why is the weblogic console not working?

    Hi,
    To start any managed servers from Admin Console you need to have a Machine associated with that Managed server and have to start nodemanager, then only you can start a managed server from console.
    Following are the steps:
    1) Create a Managed Server (MS-1)
    2) Create a Machines (MachineA)
    3) In the above created MachineA add the MS-1 which can be done from the below console path
    Console Path:
    Machines --> MachineA --> Configuration [Tab] --> Servers [Sub-Tab]
    4) Now start nodemanager using the startNodeManager.sh script which can be found in the below path
    Path:
    wlserver_10.3/server/bin/
    5) Now you can try to start your MS-1 using the Admin Console.
    Note: If you still cannot start the your managed servers then would suggest you to have a look at the below post
    Topic: NodeManager is not reachable
    http://middlewaremagic.com/weblogic/?p=5205
    Topic: Common NodeManager Issues in WebLogic
    http://middlewaremagic.com/weblogic/?p=2887
    Regards,
    Ravish Mody

  • Exception while starting Managed Server

              Hi,
              I am getting 'Connection Refused' exception while starting the Managed Server.Attached
              log has the complete trace. It was working fine till few days back and I havent
              changed any configuration.
              I will be thankful to you if anyone gives me a clue to trace for the solution
              on this.
              Regards,
              [Document.txt]
              

              One not so good solution I ever used is to remove the managed server and reinstall/configure
              it.
              "Victor" <[email protected]> wrote:
              >
              >
              >
              >Hi,
              >
              >I am getting 'Connection Refused' exception while starting the Managed
              >Server.Attached
              >log has the complete trace. It was working fine till few days back and
              >I havent
              >changed any configuration.
              >
              >I will be thankful to you if anyone gives me a clue to trace for the
              >solution
              >on this.
              >
              >Regards,
              

  • Algorithm 'AES' has expired  exception while starting UCM server

    Hi,
    I am using Oracle UCM11g. While starting UCM server i am getting following exception.
    Error encountered encrypting the field 'JdbcPassword' with scope 'system'. The decryption key for category 'db' and encoding type 'AES' is missing. [ Details ]
    An error has occurred. The stack trace below shows more information.
    !csEncryptPasswordError,JdbcPassword,system!csDecryptKeyMissing,db,AES
    intradoc.data.DataException: !csDecryptKeyMissing,db,AES
    at intradoc.conversion.SecurityObjects.decryptWithFlags(SecurityObjects.java:350)
    at intradoc.conversion.SecurityObjects.decrypt(SecurityObjects.java:292)
    at intradoc.conversion.SecurityObjects.updatePassword(SecurityObjects.java:1132)
    at intradoc.conversion.SecurityObjects.updateExpiredPasswords(SecurityObjects.java:1036)
    at intradoc.conversion.CryptoPasswordUtils.updateExpiredPasswords(CryptoPasswordUtils.java:275)
    at intradoc.server.IdcSystemLoader.managePasswords(IdcSystemLoader.java:3125)
    at intradoc.server.IdcSystemLoader.finishInit(IdcSystemLoader.java:397)
    at intradoc.server.IdcSystemLoader.init(IdcSystemLoader.java:336)
    at intradoc.server.IdcServerManager.init(IdcServerManager.java:120)
    at intradoc.idcwls.IdcServletRequestUtils.initializeServer(IdcServletRequestUtils.java:624)
    at intradoc.idcwls.IdcServletRequestUtils.initializeServer(IdcServletRequestUtils.java:455)
    at intradoc.idcwls.IdcIntegrateWrapper.initializeServer(IdcIntegrateWrapper.java:102)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at idcservlet.common.IdcMethodHolder.invokeMethod(IdcMethodHolder.java:87)
    at idcservlet.common.ClassHelperUtils.executeMethodEx(ClassHelperUtils.java:305)
    at idcservlet.common.ClassHelperUtils.executeMethodWithArgs(ClassHelperUtils.java:278)
    at idcservlet.ServletUtils.initializeContentServer(ServletUtils.java:1242)
    at idcservlet.ServletUtils.startAndConfigureServer(ServletUtils.java:542)
    at idcservlet.ServletUtils.initializeAllServers(ServletUtils.java:455)
    at idcservlet.IdcFilter.initContentServer(IdcFilter.java:132)
    at idcservlet.IdcFilter.init(IdcFilter.java:124)
    at weblogic.servlet.internal.FilterManager$FilterInitAction.run(FilterManager.java:332)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.FilterManager.loadFilter(FilterManager.java:98)
    at weblogic.servlet.internal.FilterManager.preloadFilters(FilterManager.java:59)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1876)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Can anybody please tell me how to resole this problem.
    Thanks and regards,
    Nitin Anande

    Hi,
    Please find the following entries of config.cfg and intradoc.cfg.
    Config.cfg
    +<?cfg jcharset="Cp1252"?>+
    +#Server System Properties+
    IDC_Name=N60906016200
    IdcProductName=idccs
    InstanceMenuLabel=N60906016200
    InstanceDescription=Instance N60906016200
    SocketHostAddressSecurityFilter=127.0.0.1|0:0:0:0:0:0:0:1
    +#Database Variables+
    DatabaseType=other
    JdbcDriver=
    JdbcUser=
    JdbcPassword=managed
    JdbcPasswordEncoding=managed
    DatabasePreserveCase=0
    SystemDatabase:DataSource=CSDS
    SystemDatabase:UseDataSource=true
    +#Internet Variables+
    HttpServerAddress=N609060:16200
    MailServer=mail
    SysAdminAddress=[email protected]
    HttpRelativeWebRoot=/cs/
    UseSSL=No
    +#General Option Variables+
    IsAutoNumber=Yes
    AutoNumberPrefix=N6090601620
    +#Additional Variables+
    registerStartMenuActions=1
    FileEncoding=UTF8
    WebServer=javaAppServer
    IntradocServerPort=4444
    intradoc.cfg
    +<?cfg jcharset="Cp1252"?>+
    +#Server System Properties+
    IDC_Id=UCM_server1
    +#Server Directory Variables+
    IdcHomeDir=C:/APPS/oracle/MIDDLE~1/Oracle_ECM1/ucm/idc/
    AppServerHome=C:/APPS/oracle/MIDDLE~1/WLSERV~1.3/
    DomainHome=C:/APPS/oracle/MIDDLE~1/USER_P~1/domains/ecm_domain/
    FmwDomainConfigDir=C:/APPS/oracle/MIDDLE~1/USER_P~1/domains/ecm_domain/config/fmwconfig/
    AppServerJavaHome=C:/APPS/oracle/MIDDLE~1/JDK160~1/jre/
    AppServerJavaUse64Bit=false
    IntradocDir=C:/APPS/oracle/MIDDLE~1/USER_P~1/domains/ecm_domain/ucm/cs/
    VaultDir=C:/APPS/oracle/MIDDLE~1/USER_P~1/domains/ecm_domain/ucm/cs/vault/
    WeblayoutDir=C:/APPS/oracle/MIDDLE~1/USER_P~1/domains/ecm_domain/ucm/cs/weblayout/
    Thanks a lot.

  • Unable to Start MDM Server through MDM Console

    Dear All,
    We have issue to start MDM through MDM Console , MDM instance is up and running SAP console.
    I have already mounted MDM Server but its show MDM is not started , we are try to start manualy while right clicking.
    It shows below error .
    error starting 'sap1024.sap.xxx.com (MDM Server)'
    Call to SAPWebServiceStartInstance failed with error .A connection attempt failed because the connected party did not properly respond after a period of time , or established connecton failed bacause connected host has failed to respond.
    Kindly suggest to resolve the above issue in MDM.
    thanks

    Closing the thread , same thread post in MDM .

  • Starting J2EE server in console mode

    Hello Everyone,
    I have just installed WAS 640 SP3 J2EE only on AIX5.2 unix server. J2ee server starts and stops without any problem. I can even see the J2EE engine through the web.
    Administrator user is locked because of the wrong password entries. I am trying to follow OSS note : 669848, it explains how to unlock Administrator user for SP3 systems which requires to stop the Java instance and start it console mode by jlaunch. when I run the following command after setting the LIBPATH to /usr/sap/NWS/JC00/j2ee/os_libs, but it never put me the console mode.
    "jlaunch -file=/usr/sap/NWS/JC00/j2ee/cluster/instance.properties -nodeName=ID1693850 pf=/usr/sap/NWS/SYS/profile/NWS_JC00_cgunx130 -traceFile=tracefile3.log -startMode=console".
    tracefile3.log shows the following error message at the end.
    Fri Dec 17 17:44:25 2004
    ERROR => DlLoadLib: dlopen()= No such file or directory -> DLENOACCESS (2,No
    such file or directory) [dlux_mt.c    310]
    ERROR => Can't load VM shared library (libjvm.a) (rc=-2) [jhvmxx_mt.c  1380]
    ERROR => Cannot load DLL for Java VM [jlnchxxi_mt. 527]
    I use java 1.4.1
    cgunx130:nwsadm 22> java -version
    java version "1.4.1"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1)
    Classic VM (build 1.4.1, J2RE 1.4.1 IBM AIX 5L for PowerPC (64 bit JVM) build caix641411-20040301 (JIT enabled: jitc))
    Could you please help me to UNLOCK the Administrator user.
    Thanks,
    Tuncay

    Please, can u put how do you resolve the problem, i've the same situation.
    eulerss

  • How to start managed server from console?

    Hi,
    After several unsuccesful attempts to start a managed server from admin console,
    which starts fine by script and stops by console, can somebody please mail me
    what to enter in the "remote start" tab!
    The documentation is very uncertain if the path have to be absolute or not. It
    seems to be a problem with the classpath.
    thanks in advance
    Kai

    The ServerStart element should look like below (WLS6.1sp1+). Using absolute
    path is definitely OK. Please provide us more info if you still have this
    problem such as files under WL_HOME\NodeManagerLogs\<mgr'ed servername>
    especially config and <mgr'ed server name>_error.log
    <ServerStart Arguments="-mx64m -ms64m" BeaHome="d:\bea"
    ClassPath="d:\bea\load1;d:\bea\load1\lib\weblogic_sp.jar;d:\bea\load1\lib\we
    blogic.jar"
    Name="Server-1005280911753"
    OutputFile="d:\bea\load1\config\NodeManagerClientLogs\managed1\startserver_1
    005280991998.log"
    RootDirectory="d:\bea\load1"
    SecurityPolicyFile="d:/bea/load1/lib/weblogic.policy"/>
    "Kai" <[email protected]> wrote in message news:3bea490f$[email protected]..
    >
    Hi,
    After several unsuccesful attempts to start a managed server from adminconsole,
    which starts fine by script and stops by console, can somebody please mailme
    what to enter in the "remote start" tab!
    The documentation is very uncertain if the path have to be absolute ornot. It
    seems to be a problem with the classpath.
    thanks in advance
    Kai

  • License file missing exception while starting managed server

    Hi,
    I am trying to start a managed server on the same machine as the adminstration
    server. There are no problems starting the admin server but when we try to start
    the managed server , we get a "Missing License File" exception. The license file
    is valid for clustering also.
    Thanks In Advance
    Amit

    umm..make sure license.bea is in classpath
    make sure license.bea in Dbea.home of your startmangedscript.cmd
    "amit" <[email protected]> wrote in message
    news:3c605c10$[email protected]..
    >
    Hi,
    I am trying to start a managed server on the same machine as theadminstration
    server. There are no problems starting the admin server but when we try tostart
    the managed server , we get a "Missing License File" exception. Thelicense file
    is valid for clustering also.
    Thanks In Advance
    Amit

Maybe you are looking for