Cannot Start Portal Server.

Hi
I am using EP 7.0. I am not able to start portal server. From the log file I have found out the following details.
<b>Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.
     at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:78)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
     ... 7 more
Caused by: java.lang.ClassNotFoundException: com.sap.portals.jdbc.oracle.OracleDriver</b>
Any Suggestion where is the problem. The portal was working fine before stopping it.
Regards
Debasish

There is no clear documentation available to enable custom security but IBM info center has decent documentation for LDAP based security. I would say follow the steps mentioned for IBM directory and then modify the necessary configuration parameters for OID. This should solve your issues. For better help open a PMR with IBM to get necessary quick help.

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

Cannot start weblogic server anymore after conf. jena for oracle database

Hi,
My weblogic server 10.3.4.0 installed in oracle developer days in oralce linux guest was able to start before using the oracle user account. Following the seman. tech. dev. guide, I set up jena adapter for oracle in my guest linux system. Since the oracle user doesn't have permission to copy folders into the autodeploy directory in weblogic server, so I login as root to copy the joseki.war folder into the autodeploy directory. However, after that, I am not able to start the weblogic server console anymore using the oracle user account. Any suggestions will be much appreciated. Thanks a lot in advance.
Hong

Pl do not post duplicates - cannot start weblogic server anymore in oracle user after config. in root

Start Portal server

Hi,
I changed my WLS6.0 to 6.1 sp2 on WinNT. Starting install Portal 4.0, it went
through well. However, I couldnot start Portal server. Hereis the massege after
start Portal server (WLS is running) :
# Note: Server initialization may take several minutes.
# Please be patient.
<Jan 3, 2002 3:57:47 PM EST> <Info> <Security> <Getting boot password from user.
>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: try to access method weblogic/management/internal/
Helper.preloadMBeanInfos()V from class weblogic/management/Admin
at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Press any key to continue . . .
my WSL log file see attached file
Could you help me to finger out what's wrong.
thanks
tao
[weblogic.log]

I had the same problem on Solaris 2.8, the only way I could fix it was to backtrack
to WebLogic Server 6.1 w/ sp1 instead of sp2
Brian
"Stéphane Gamondes" <[email protected]> wrote:
>
>
Hi,
I don't have the answer to this error, but we had the same problem...
Switching back to WLS6.1 sp1 solved it though.
Stéphane
"Tao Huang" <[email protected]> wrote:
Hi,
I changed my WLS6.0 to 6.1 sp2 on WinNT. Starting install Portal 4.0,
it went
through well. However, I couldnot start Portal server. Hereis the massege
after
start Portal server (WLS is running) :
# Note: Server initialization may take several minutes.
# Please be patient.
<Jan 3, 2002 3:57:47 PM EST> <Info> <Security> <Getting boot password
from user.
>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: try to access method weblogic/management/internal/
Helper.preloadMBeanInfos()V from class weblogic/management/Admin
at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Press any key to continue . . .
my WSL log file see attached file
Could you help me to finger out what's wrong.
thanks
tao

Cannot start SQL Server Service (SQLEXPRESS).

Cannot start SQL Server (SQLEXPRESS). When i tried to start the SQL Server Services, the warning: This request failed or the service did not respond in a timely fashion. Consult the event log or other application error logs for details.
I opened the Event Viewer, Error is shown as : An error occurred in the Service Broker / Database Mirroring transport manager. Error: 9694, Stare 27.

Here is the ERRORLOG
2015-03-16 11:20:30.50 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2015-03-16 11:20:30.50 Server (c) Microsoft Corporation.
2015-03-16 11:20:30.50 Server All rights reserved.
2015-03-16 11:20:30.50 Server Server process ID is 6816.
2015-03-16 11:20:30.50 Server System Manufacturer: 'LENOVO', System Model: '20C5A01K00'.
2015-03-16 11:20:30.50 Server Authentication mode is MIXED.
2015-03-16 11:20:30.50 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-03-16 11:20:30.50 Server The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2015-03-16 11:20:30.50 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-03-16 11:20:30.50 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2015-03-16 11:20:30.64 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-03-16 11:20:30.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-16 11:20:30.64 Server Detected 7906 MB of RAM. This is an informational message; no user action is required.
2015-03-16 11:20:30.64 Server Using conventional memory in the memory manager.
2015-03-16 11:20:30.75 Server Error: 9694, Severity: 16, State: 27.
2015-03-16 11:20:30.75 Server Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
2015-03-16 11:20:30.75 Server Error: 9643, Severity: 16, State: 1.
2015-03-16 11:20:30.75 Server An error occurred in the Service Broker/Database Mirroring transport manager: Error: 9694, State: 27.
2015-03-16 11:20:30.75 Server Error: 9694, Severity: 16, State: 30.
2015-03-16 11:20:30.75 Server Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
2015-03-16 11:20:30.75 Server SQL Server Audit failed to record the SERVER SHUTDOWN action.

Solaris 10 x86 (gold) will not install - Cannot start X-Server

(Originally posted in the wrong forum. Oops)
Okay,. this is really stupid. I don't understand this one at all.
I cannot install Solaris x86 (gold - as in "non-beta") at all. I have tried both the ATI Rage 128 Pro and NVidia GeForce chipsets. Both cards are correctly detected; however, regardless of what selection or driver option I choose, the installation crashes immediately thereafter.
If I let the installation go on its own, it stops completely at the "Detecting additional network parameters" or whatever that particular error message is.
If I manually select the standard (non XF86) drivers of the card, black-on-yellow text complains about how it cannot detect the card (that it correctly identified) and that it cannot start the X server. It then improperly displays the text menu for language selection and stops.
If I manually select the XF86 drivers, it gets all of the way through to where I test the video mode and then just dies. No error message or anything.
{rant mode on}
Jesus, Sun! What the hell is going on? These are two INDUSTRY STANDARD video cards! These aren't some run-of-the-mill, no-name chipsets we're talking about! It's exactly because of idiotic driver issues like this that people laugh when given the choice between Solaris and Linux while looking for Windows alternatives for the desktop!
{rant mode off}
Sorry for the rant, but I've been complaining for years that issues like this are exactly why Windows has been allowed to dominate the desktop. Now here comes Linux which supports just about everything, and Sun still apparently has no clue about supporting desktops. I know , I know-- servers are Sun's strengths, but if Sun is going to try to get JDS onto the desktop, this is not the way to go about it.
Now that I've gotten that off my chest (I really needed that), does anyone know what needs to be done to get this to install properly and of course function properly thereafter without having to jump througha ton of hoops?

That's just what really bothers me about this!
Last week, I installed from the very same CDs onto an old Celeron 633 w/ 128 MB and ATI Rage video chipset just for giggles. Everything went beautifully except for the network. (Once again, Sun shows its pathetic weakness on drivers thus giving Linux a major edge.) The only video error that I got was remedied by switching to the standard driver from the XF86 driver. It ran like a champ afterwards except that it got confused on the network card and therefore prevented network connectivity.
So, this time I tried to install it on a Pentium 4 1.8 GHz w/ 512 MB RAM, and it's puking on me with same video chipset family (ATI Rage) as well as NVidia chipsets! Absolutely ridiculous!

Cannot start SQL Server Agent (Version 2014 enterprise core)?

The SQL Server Agent log file has the following information. I already set the firewall for inbound 1433.
2014-11-04 11:59:43 - ? [100] Microsoft SQLServerAgent version 12.0.2000.8 (X64 unicode retail build) : Process ID 6108
2014-11-04 11:59:43 - ? [495] The SQL Server Agent startup service account is ......
2014-11-04 11:59:43 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2014-11-04 11:59:43 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2014-11-04 11:59:43 - ! [298] SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider is installed and registered correctly. [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [298] SQLServer Error: 27, Client unable to establish connection [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to
allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2014-11-04 11:59:43 - ? [098] SQLServerAgent terminated (normally

Is this new SQL Server installation or originally it was working fine ?
Below message makes me think you might as well need to repair your installation
>SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider is installed and registered correctly. [SQLSTATE 08001]
Please see below link
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/d2a97cf4-54b2-40b7-836a-b9f146442855/unable-to-open-sql-server-logs?forum=sqlsetupandupgrade
Without errorlog it would be difficult to say why this happened but as errorlog says it has found registry inconsistent so repairing installation would help
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Cannot start managed server

Hi,
I cannot start the managed server and here MyServer.out
<Aug 6, 2011 11:40:42 PM> <INFO> <NodeManager> <Server output log file is 'C:\spl\Middleware\user_projects\domains\DWP\servers\MyServer\logs\MyServer.out'>
<Aug 6, 2011 11:40:43 PM PDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Aug 6, 2011 11:40:43 PM PDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Aug 6, 2011 11:40:44 PM PDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
C:\spl\Middleware\user_projects\domains\DWP\lib\sipactivator.jar>
<Aug 6, 2011 11:40:45 PM PDT> <Info> <Server> <BEA-002647> <The service plugin, com.oracle.core.sip.activator, was added from C:\spl\Middleware\user_projects\domains\DWP\lib\sipactivator.jar.>
<Aug 6, 2011 11:40:45 PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 19.1-b02 from Sun Microsystems Inc.>
<Aug 6, 2011 11:40:46 PM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Aug 6, 2011 11:40:47 PM PDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.ClassNotFoundException: com.bea.wcp.sip.management.descriptor.beans.SipServerBean>
<Aug 6, 2011 11:40:47 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Aug 6, 2011 11:40:47 PM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Aug 6, 2011 11:40:47 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Aug 6, 2011 11:40:48 PM> <FINEST> <NodeManager> <Waiting for the process to die: 6200>
<Aug 6, 2011 11:40:48 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Aug 6, 2011 11:40:48 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Please help. Thanks.

maybe this http://appsonlinedba.blogspot.com/2011/05/managed-server-failed-to-start-when.html can help

Sequence of scripts to start portal server

Hi All,
I installed Oracle 10G Release2 on Suse 9 (all components on the same machine). I checked the demo pages also all were working fine. But when i rebooted my machine, none of the service get up. I manully started the database, emctl, opmnctl processes but still i am unable to access the application.
Can anybody tell me which services we required to start to access the whole portal server. If you could provide me some kind of startup script which i can place in my init level, so that would be much better.
Thanks in advance.
Sunil Kumar

gday Sunil --
I'd try reposting this Portal question to either the Portal forum on OTN or the General Application Server forum. You're likely to get access to more Portal specific folks there.
cheers
-steve-

Workshop cannot start "localhost" server

Hi,
I'm using Workshop 10.3 (from Oracle Service Bus 10gR3) on a Windows XP machine.
I have to run my domains strictly on "localhost". I've edited the default OSB and Workshop domains (i.e. ${OSB_HOME}/osb_10.3/samples/domains/servicebus and ${OSB_HOME}/workshop_10.3/samples/domains/workshop) and defined a "<listen-address>" of "localhost". For example, the workshop domain's config.xml contains:
<server>
    <name>cgServer</name>
    <ssl>
      <name>cgServer</name>
      <enabled>true</enabled>
       <listen-port>7002</listen-port>
    </ssl>
    <listen-port>7001</listen-port>
    <listen-address>localhost</listen-address>
</server>
...When I start a server for either of the two domains from within the Workshop IDE, I get an error claiming that the server failed to start because it's occupied. For example, the OSB samples domain give the following error log:
!ENTRY com.bea.workshop.wls.core 1 2000 2010-03-31 14:04:19.114
!MESSAGE Server watcher[Oracle WebLogic Server v10.3 at localhost (OSB samples domain)]:running Weblogic detected, validating...
!ENTRY com.bea.workshop.wls.core 2 2 2010-03-31 14:04:19.192
!MESSAGE Unable to validate WebLogic domain.
Please make sure the running WebLogic instance is an Administration Server
!ENTRY com.bea.workshop.wls.core 4 4000 2010-03-31 14:04:19.630
!MESSAGE Another server (or another process) is running on the same TCP/IP port '7021'.
!ENTRY org.eclipse.wst.server.core 4 0 2010-03-31 14:04:19.661
!MESSAGE Server Oracle WebLogic Server v10.3 at localhost (OSB samples domain) failed to start.I can guarantee that there's nothing already running on port 7021/7022 (or 7001/7002 which is mentioned when I try to start the Workshop domain with the same failing result). If the server is not running I can see with "netstat" that nothing's using those ports and a telnet to either port will simply fail to connect to localhost.
In fact, the Workshop IDE simply thinks that the server process failed to start, when in fact it is running successfully. If I access (e.g. for OSB) http://localhost:7021/examplesWebApp/index.jsp I get the samples screen (in fact the browser is started on this address automatically) and can run the samples. I can also access the console by going to http://localhost:7021/console.
However, Workshop thinks the server is dead and I cannot publish/run projects on the server from within the IDE.
Any ideas why?

The problem is related to the fact that the server does not accept connections using the T3 protocol.
For more details, see Can't connect to administration server using "t3" protocol
It has not been resolved, but I have an SR pending with Oracle support.

Dbstart cannot start Oracle server

The command dbstart cannot start the Oracle 8ir2 (8.1.6) server. It only shows the message "Database "ORCL" warm started.", but the oracle instance did not start nor database was not mounted. I have updated the /etc/oratab file to put Y to my database.
But the command dbshut can shutdown the oracle server.
Any help!!
I am running Redhat 6.2. The hardware is Athlon K7-750, 256MB Ram, ASUS K7V M/B, Voodoo 3.

The program svrmgrl of Oracle 8ir2 shows JServer Release 8.1.6.0.0 instead of PL/SQL (Version|Release) 8.1.? in the screen. Thus, I edit the dbstart script to change the line
/PL\/SQL (Release|Version)/ {substr($3,1,3) ;
to
/JServer (Release|Version)/ {substr($3,1,3) ;
to solve this problem.
Ed Cheng

Cannot start protocol server agents

I cannot start several Ifs protocol servers: NbServerAgent, SmtpServerAgent, FtpServerAgent, WcpServerAgent and ImapServerAgent. They are "starting..." for a few minutes and then stop.
Although, I can start SmbServerAgent and CupServerAgent.
IfsProtocol.log file says that timers expire. For example, when I try to start FtpServerAgent...
FtpServerAgent: Timer timeouts remaining set to 4
FtpServerAgent: timer expired with internal
status of Starting...
FtpServerAgent: remaining timeouts reduced to 0
FtpServerAgent: timer expired with internal status of Starting...
FtpServerAgent: Starting external process has timed out
FtpServerAgent: Forcing process to exit
FtpServerAgent: Server Freed with internal status of Starting...
FtpServerAgent: Process Exit with internal status of Server Unregistered
FtpServerAgent: Signalling a restart (1)
FtpServerAgent: Exiting handle loop
FtpServerAgent.err Inputs received: 0; log thread exiting...
FtpServerAgent.out Inputs received: 0; log thread exiting...
FtpServerAgent: postRun
FtpServerAgent: stopping timer
FtpServerAgent: Start request
FtpServerAgent: passing credentials
FtpServerAgent: starting timer
... And finally:
FtpServerAgent: Too many restart failures; restart not attempted
Can anybody help me? Thanks in advance.

There is nothing special. For example, FtpServer.log says:
Tue Apr 17 16:32:20 CEST 2001
arg[0]: null
arg[1]: ManagerID=34693
arg[2]: "ServerName=FtpServer"
arg[3]: "parameterfile=/usr/app/oracle/product/8.1.7/ifs1.1/settings/FtpServer.def"
arg[4]: "outputfile=/usr/app/oracle/product/8.1.7/ifs1.1/log/FtpServer.log"
arg[5]: PassCredentials=true
Tue Apr 17 16:34:05 CEST 2001
arg[0]: null
arg[1]: ManagerID=34693
arg[2]: "ServerName=FtpServer"
arg[3]: "parameterfile=/usr/app/oracle/product/8.1.7/ifs1.1/settings/FtpServer.def"
arg[4]: "outputfile=/usr/app/oracle/product/8.1.7/ifs1.1/log/FtpServer.log"
arg[5]: PassCredentials=true
Tue Apr 17 16:35:45 CEST 2001
arg[0]: null
arg[1]: ManagerID=34693
arg[2]: "ServerName=FtpServer"
arg[3]: "parameterfile=/usr/app/oracle/product/8.1.7/ifs1.1/settings/FtpServer.def"
arg[4]: "outputfile=/usr/app/oracle/product/8.1.7/ifs1.1/log/FtpServer.log"
arg[5]: PassCredentials=true
Tue Apr 17 16:38:13 CEST 2001
arg[0]: null
arg[1]: ManagerID=34693
arg[2]: "ServerName=FtpServer"
arg[3]: "parameterfile=/usr/app/oracle/product/8.1.7/ifs1.1/settings/FtpServer.def"
arg[4]: "outputfile=/usr/app/oracle/product/8.1.7/ifs1.1/log/FtpServer.log"
arg[5]: PassCredentials=true
It keeps trying as long as the max number of restart failures permits.
With the same load conditions of the system, the number of protocols that can be started varies, though vmstat says that there is enough free memory (350 Mb) when I try it.
I tried to increase the initial and maximum jvm heap size with -ms and -mx, but it didn4t seem to have any effect. Is this correct?
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Luis:
What do you see in the ftp.log, smb.log, etc?<HR></BLOCKQUOTE>
null

Cannot start SQL-SERVER-AGENT

Hellow friends. I have made a software that uses SQL-SERVER database at back end.. I want to use
express version of SQL-SERVER so i downloaded SQL-SERVER-2008 R2.. But i could not start
SQL-SERVER agent.
Can i still share database over the NEWTWORK
without starting SQL-SERVER-AGENT???

IS it possible to share database over a LAN using SQL server Express 2008.??
Or do EXPRESS-VERSION of sql server does not allow us to do so. ?
I find both 'yes' and 'no' answers when i google this question. Please i am in need of specific answer.
Just because you can get answer from forum dont start flooding it with same question.Below thread has same question see my reply, and reply to below forum only
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/eae75c95-6e98-413e-9e1d-206d95d893bf/cannot-start-sqlserveragent?forum=sqltools
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Cannot start BI Server (nQSError: 15014)

Hello,
just migrated a Discoverer EUL with the migration tool and integrated the new rpd file into the NQSConfig.ini. When I tried to start the BI Server, I got an error:
"...Server start up failed: [nQSError: 15014] No subject area is available in the repository Star. Remove the repository from NQSConfig.ini and restart the server.."
Reverting back to the samplessales star in the "[ REPOSITORY ]" section lets me start the server again. So, apparently something is wrong with the generated rpd file. However, there was no error message, when I did the migration.
Any ideas appreciated.

Hi John,
with respect to the NQServer.log, I found the following error message:
"[14054] Unable to load subject area: NVC_2007.[nQSError: 15001] Could not load navigation space for subject area NVC_2007.
[nQSError: 42001] Missing repository object with ID=0:0."
Any idea how I can narrow down on the object mentioned? Object with ID=0.0 doesn't ring a bell...

Cannot start Managed Server- after creating a new domain

I created a new domain, I could start Admin Server but ,I am unable to start Managed Server.
My DB is up & running
at com.collaxa.cube.engine.CubeEngine.finalizeActivity(CubeEngine.java:2842)
at com.collaxa.cube.engine.CubeEngine.checkBlockConditions(CubeEngine.java:3557)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2490)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1133)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:219)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:327)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4350)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4282)
at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:713)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:545)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:654)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:355)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106)
at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:106)
at sun.reflect.GeneratedMethodAccessor840.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy245.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.java:396)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:82)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
at java.lang.Thread.run(Thread.java:619)
Caused By: com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'ReadInputDataSelect' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
DemoDBAdapter:ReadInputData [ ReadInputData_ptt::ReadInputDataSelect(ReadInputDataSelect_inputParameters,CustomerCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510
JCA Resource Adapter location error.
Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/>
The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/DemoConnection'.
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or
2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/DemoConnection. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR).
Please correct this and then restart the Application Server

Dear Anuj,
I created a connection pool in DB adapter with JNDI name "eis/DB/DemoConnection"? and then updated
BUT WHEN I SEE DB ADAPTER in deployments, the sate is New . It should be ACTIVE . right?
Again when I start Managed Server,although my soa_server is up and running, I get this error
However, I did not create any JMS for this domain.
<Aug 9, 2010 11:21:45 AM CDT> <Warning> <oracle.soa.adapter> <BEA-000000> <JMSAdapter HelloWorld JMSMessageConsumer_init: Retrying connection; attempt #5>
<Aug 9, 2010 11:21:45 AM CDT> <Warning> <oracle.soa.adapter> <BEA-000000> <JMSAdapter HelloWorld
BINDING.JCA-12135
ERRJMS_ERR_CR_QUEUE_CONS.
ERRJMS_ERR_CR_QUEUE_CONS.
Unable to create Queue consumer due to JMSException.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:620)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:913)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
... 8 more
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:87)
at weblogic.jms.dispatcher.Request.getResult(Request.java:52)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:1124)
at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
... 12 more
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:289)
at weblogic.jms.frontend.FEManager.invoke(FEManager.java:548)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:914)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:864)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:106)
... 2 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.backend.jms'. Resolved 'weblogic.jms.backend'; remaining name 'jms'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:287)
at weblogic.jms.frontend.FEManager.invoke(FEManager.java:548)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:913)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
... 2 more
>
<Aug 9, 2010 11:21:46 AM CDT> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<Aug 9, 2010 11:21:46 AM CDT> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.128.102:8001 was shutdown.>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on 127.0.0.1:8001 was shutdown.>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on 0:0:0:0:0:0:0:1:8001 was shutdown.>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on fe80:0:0:0:20c:29ff:fe81:998f:8001 was shutdown.>
INFO: JMSAdapter JmsResourceAdapter_endpointDeactivation: Deactivating endpoint Endpoint_1
[TopLink Info]: 2010.08.09 11:21:53.232--ServerSession(382132253)--deferred_session logout successful
[TopLink Info]: 2010.08.09 11:21:53.232--ServerSession(381072707)--tracking_session logout successful
<Aug 9, 2010 11:21:54 AM CDT> <Notice> <LoggingService> <BEA-320400> <The log file /u01/app/oracle/product/Middleware/user_projects/domains/base_domain4/servers/soa_server1/logs/soa_server1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Aug 9, 2010 11:21:54 AM CDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /u01/app/oracle/product/Middleware/user_projects/domains/base_domain4/servers/soa_server1/logs/soa_server1.log00021. Log messages will continue to be logged in /u01/app/oracle/product/Middleware/user_projects/domains/base_domain4/servers/soa_server1/logs/soa_server1.log.>
[oracle@OracleTest1 bin]$

Cannot Start Portal Server.

Similar Messages

Maybe you are looking for