[Fwd: Starting Managed server problem ......]
Forwarding to the security news group...
-------- Original Message --------
Subject: Starting Managed server problem ......
Date: 1 Jun 2004 23:02:53 -0700
From: Sameer <barsatkiraat2001>
Newsgroups: weblogic.developer.interest.management
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and
installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one
unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager
and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482>
<BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. Check
the peer to determine why it rejected the certificate chain (trusted CA
configuration, hostname verification). SSL debug tracing may be required
to determine the exact reason the certificate was rejected.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504>
<Certificate chain received from PortalQA - 10.12.10.94 failed hostname
verification check. Certificate contained AdminQA but check expected
PortalQA>
The WebLogic Server did not start up properly.
Exception raised:
'weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038>
<The node manager is unable to monitor this server. Could not create an
SSL connection to the node manager. Reason :
[Security:090504]Certificate chain received from PortalQA - 10.12.10.94
failed hostname verification check. Certificate contained AdminQA but
check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due to
faulty SSL configuration, this server is unable to establish a
connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer>
<BEA-000342> <Unable to initialize the server:
weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.>
If some one can help me, I do appreciate in all due respect.
Sameer.
Hello Satya/All,
I'm also experiencing the exact problem you are facing. It would be great if
somebody could help in this regard at the earliest.
Thanks, senthil
Satya Ghattu <[email protected]> wrote:
Forwarding to the security news group...
-------- Original Message --------
Subject: Starting Managed server problem ......
Date: 1 Jun 2004 23:02:53 -0700
From: Sameer <barsatkiraat2001>
Newsgroups: weblogic.developer.interest.management
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and
installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one
unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager
and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482>
<BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. Check
the peer to determine why it rejected the certificate chain (trusted
CA
configuration, hostname verification). SSL debug tracing may be required
to determine the exact reason the certificate was rejected.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504>
<Certificate chain received from PortalQA - 10.12.10.94 failed hostname
verification check. Certificate contained AdminQA but check expected
PortalQA>
The WebLogic Server did not start up properly.
Exception raised:
'weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038>
<The node manager is unable to monitor this server. Could not create
an
SSL connection to the node manager. Reason :
[Security:090504]Certificate chain received from PortalQA - 10.12.10.94
failed hostname verification check. Certificate contained AdminQA but
check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due
to
faulty SSL configuration, this server is unable to establish a
connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer>
<BEA-000342> <Unable to initialize the server:
weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.>
If some one can help me, I do appreciate in all due respect.
Sameer.
Similar Messages
-
Starting Managed server problem ......
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504> <Certificate chain received from PortalQA - 10.12.10.94 failed hostname verification check. Certificate contained AdminQA but check expected PortalQA>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : [Security:090504]Certificate chain received from PortalQA - 10.12.10.94 failed hostname verification check. Certificate contained AdminQA but check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
If some one can help me, I do appreciate in all due respect.
Sameer.Hello,
NodeManager requires proper SSL configuration. Are you sure you are using the right certificates?
Try running AS with following option
-Dweblogic.security.SSL.ignoreHostnameVerification=true
Ali -
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 -
Problem in starting managed server
hi all,
i have configure a admin server and 3 managed server. after i startup the
admin server and node manager , i start managed server in admin console, but
got a list of errors as follows:
####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
<kernel identity> <> <160037> <J2EE service initializing>
####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
<myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
server: Fatal initialization exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Cannot intialize Resource Manager Connection Factory resources because could
not get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Factory resources because could not
get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
at
weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at
weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
i have checked that rmiregistry is up and 1099 port is listening. Does
anyone know why ?
thank you very much
regrds
andhi all,
i have configure a admin server and 3 managed server. after i startup the
admin server and node manager , i start managed server in admin console, but
got a list of errors as follows:
####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
<kernel identity> <> <160037> <J2EE service initializing>
####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
<myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
server: Fatal initialization exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Cannot intialize Resource Manager Connection Factory resources because could
not get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Factory resources because could not
get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
at
weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at
weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
i have checked that rmiregistry is up and 1099 port is listening. Does
anyone know why ?
thank you very much
regrds
and -
Problem with starting managed server
In a domain , I have one admin server and one managed server. When im trying to start managed server , the message says,
Message icon - Warning For server Server-0, the Node Manager associated with machine Machine-0 is not reachable.
Message icon - Warning 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.
Already i started the node manager , i checked with node manager's log files, and I found these error in log files,
<Jul 30, 2010 12:54:32 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Can any one help me to troubleshoot this.Hi Jose,
To Disable SSL communication for NodeManager do the following:
<b><font color=maroon>Step1).</font></b> Open the *"nodeManager.properties"* file from *<WL_HOME>\common\nodemenager* (Example Location : C:\bea103\wlserver_10.3\common\nodemanager ) directory and change the value of SecureListener property to false:
SecureListener=false
<b><font color=maroon>Step2).</font></b> Login to AdminConsole and then
AdminConsoleHome--->Machines --><Your_MachineName> (Click here)--->NodeManager (Tab)---> Select the type as "Plain" from the combo box (by default it will be SSL)
<b><font color=maroon>Step3).</font></b> Restart the NodeManager ....better if you follow Step4) as well...
<b><font color=maroon>Step4).</font></b> Please Enroll your NodeManager as described in the Step8) of the following Link: http://weblogic-wonders.com/weblogic/2010/04/28/weblogic-clustering-in-remote-boxes/
Thanks
Jay SenSharma -
Error while starting manages server
Hi All.
M facing problem while starting managed server, this might be related to sip server as i see this in the error log. when i click on the sip server tab in the console then io see below error :-
+++++++++
Error opening /ext-jsp/sipserver/ConfigGeneralForm.jsp.
The source of this error is:
javax.servlet.ServletException: weblogic.servlet.jsp.CompilationException: Failed to compile JSP /ext-jsp/sipserver/ConfigGeneralForm.jsp
Exception occurred while processing '/bea/wls/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_internal/consoleapp/jxhze9/console-ext/sipserver-console-ext/ext-jsp/sipserver/ConfigGeneralForm.jsp'java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:67)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:152)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:717)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:377)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.compile(Compiler.java:422)
at weblogic.jsp.internal.java.JDTJavaCompiler.generateByteCode(JDTJavaCompiler.java:104)
at weblogic.jsp.internal.java.JavaSourceFile._codeGen(JavaSourceFile.java:211)
at weblogic.jsp.internal.java.JavaSourceFile.codeGen(JavaSourceFile.java:201)
at weblogic.jsp.internal.ProxySourceFile.compileGeneratedFiles(ProxySourceFile.java:310)
at weblogic.jsp.internal.ProxySourceFile.codeGen(ProxySourceFile.java:248)
at weblogic.jsp.internal.SourceFile.codeGen(SourceFile.java:327)
at weblogic.jsp.internal.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:599)
at weblogic.jsp.internal.client.Job.performJob(Job.java:83)
at weblogic.jsp.internal.client.ThreadPool$WorkerThread.run(ThreadPool.java:217)
Caused by: weblogic.servlet.jsp.CompilationException: Failed to compile JSP /ext-jsp/sipserver/ConfigGeneralForm.jsp
Exception occurred while processing '/bea/wls/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_internal/consoleapp/jxhze9/console-ext/sipserver-console-ext/ext-jsp/sipserver/ConfigGeneralForm.jsp'java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:67)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:152)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:717)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:377)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.compile(Compiler.java:422)
at weblogic.jsp.internal.java.JDTJavaCompiler.generateByteCode(JDTJavaCompiler.java:104)
at weblogic.jsp.internal.java.JavaSourceFile._codeGen(JavaSourceFile.java:211)
at weblogic.jsp.internal.java.JavaSourceFile.codeGen(JavaSourceFile.java:201)
at weblogic.jsp.internal.ProxySourceFile.compileGeneratedFiles(ProxySourceFile.java:310)
at weblogic.jsp.internal.ProxySourceFile.codeGen(ProxySourceFile.java:248)
at weblogic.jsp.internal.SourceFile.codeGen(SourceFile.java:327)
at weblogic.jsp.internal.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:599)
at weblogic.jsp.internal.client.Job.performJob(Job.java:83)
at weblogic.jsp.internal.client.ThreadPool$WorkerThread.run(ThreadPool.java:217)
at weblogic.servlet.jsp.JavelinxJSPStub.reportCompilationErrorIfNeccessary(JavelinxJSPStub.java:226)
at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:162)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:256)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
... 184 more
++++++++
Below is the config.xml file i am using :-
<?xml version="1.0" encoding="UTF-8"?>
<domain xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd" xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<name>base_domain</name>
<domain-version>10.3.4.0</domain-version>
<security-configuration xmlns:xacml="http://xmlns.oracle.com/weblogic/security/xacml" xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator">
<name>base_domain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"/>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xsi:type="xacml:xacml-role-mapperType"/>
<sec:authorizer xsi:type="xacml:xacml-authorizerType"/>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"/>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"/>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"/>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}Ax9F8YRCZJqRRoPcjJxTwS03NgNAJSUjUcQ0vMJybMfkxNKN3YZCRsR+jEQrT/n3/KU4Kn5WXqCILWifqYRDlmnGGryHuNEEK83B/FCoBb1h8T47+ML1pULyyNpGPaFq</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{AES}G0nkKdRHqwIqNXGqn7lArIXG1SfKKdkWwTOyZ4SmkwE=</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<self-tuning-thread-pool-size-min>15</self-tuning-thread-pool-size-min>
<socket-readers>2</socket-readers>
<ssl>
<name>AdminServer</name>
<enabled>true</enabled>
</ssl>
<machine>Machine_1</machine>
<listen-address/>
<network-access-point>
<name>sip</name>
<protocol>sip</protocol>
<listen-port>5060</listen-port>
<public-port>5060</public-port>
<http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>
<outbound-enabled>true</outbound-enabled>
</network-access-point>
<network-access-point>
<name>sips</name>
<protocol>sips</protocol>
<listen-port>5061</listen-port>
<public-port>5061</public-port>
<http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>
<outbound-enabled>true</outbound-enabled>
</network-access-point>
</server>
<server>
<name>M1</name>
<ssl>
<name>M1</name>
<enabled>true</enabled>
<listen-port>7503</listen-port>
</ssl>
<machine>Machine_1</machine>
<listen-port>7003</listen-port>
<listen-address/>
<web-service>
<name>M1</name>
<web-service-persistence>
<name>M1</name>
<web-service-logical-store>
<name>WseeStore</name>
<persistence-strategy>LOCAL_ACCESS_ONLY</persistence-strategy>
<request-buffering-queue-jndi-name>weblogic.wsee.BufferedRequestQueue</request-buffering-queue-jndi-name>
<response-buffering-queue-jndi-name>weblogic.wsee.BufferedResponseQueue</response-buffering-queue-jndi-name>
</web-service-logical-store>
</web-service-persistence>
</web-service>
</server>
<server>
<name>M2</name>
<ssl>
<name>M2</name>
<enabled>true</enabled>
<listen-port>7504</listen-port>
</ssl>
<machine>Machine_1</machine>
<listen-port>7004</listen-port>
<listen-address/>
<web-service>
<name>M2</name>
<web-service-persistence>
<name>M2</name>
<web-service-logical-store>
<name>WseeStore</name>
<persistence-strategy>LOCAL_ACCESS_ONLY</persistence-strategy>
<request-buffering-queue-jndi-name>weblogic.wsee.BufferedRequestQueue</request-buffering-queue-jndi-name>
<response-buffering-queue-jndi-name>weblogic.wsee.BufferedResponseQueue</response-buffering-queue-jndi-name>
</web-service-logical-store>
</web-service-persistence>
</web-service>
</server>
<embedded-ldap>
<name>base_domain</name>
<credential-encrypted>{AES}vWDbFLBCN+g/5kGlFyC+Qp8NUIevNXYQEJYBVgoM2BaXRBIGnLy+rHfLzGrQT5JG</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.4.0</configuration-version>
<machine xsi:type="unix-machineType">
<name>Machine_1</name>
<node-manager>
<name>Machine_1</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
<jms-server>
<name>WseeJmsServer_auto_2</name>
<target>M1</target>
<persistent-store>WseeFileStore_auto_2</persistent-store>
</jms-server>
<jms-server>
<name>WseeJmsServer_auto_3</name>
<target>M2</target>
<persistent-store>WseeFileStore_auto_3</persistent-store>
</jms-server>
<jms-server>
<name>WseeJaxwsJmsServer_auto_2</name>
<target>M1</target>
<persistent-store>WseeJaxwsFileStore_auto_2</persistent-store>
</jms-server>
<jms-server>
<name>WseeJaxwsJmsServer_auto_3</name>
<target>M2</target>
<persistent-store>WseeJaxwsFileStore_auto_3</persistent-store>
</jms-server>
<self-tuning>
<fair-share-request-class>
<name>wlss.transport.fsrc</name>
<target>M1,M2</target>
<fair-share>50</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.timer.fsrc</name>
<target>M1,M2</target>
<fair-share>100</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.tracing.fsrc</name>
<target>M1,M2</target>
<fair-share>50</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.connect.fsrc</name>
<target>M1,M2</target>
<fair-share>1000</fair-share>
</fair-share-request-class>
<min-threads-constraint>
<name>wlss.tracing.minthreads</name>
<target>M1,M2</target>
<count>1</count>
</min-threads-constraint>
<min-threads-constraint>
<name>wlss.connect.minthreads</name>
<target>M1,M2</target>
<count>1</count>
</min-threads-constraint>
<max-threads-constraint>
<name>wlss.timer.maxthreads</name>
<target>M1,M2</target>
<count>16</count>
<connection-pool-name/>
</max-threads-constraint>
<max-threads-constraint>
<name>wlss.tracing.maxthreads</name>
<target>M1,M2</target>
<count>1</count>
<connection-pool-name/>
</max-threads-constraint>
<capacity>
<name>wlss.transport.capacity</name>
<target>M1,M2</target>
<count>400</count>
</capacity>
<capacity>
<name>wlss.timer.capacity</name>
<target>M1,M2</target>
<count>256</count>
</capacity>
<work-manager>
<name>wlss.transport</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.transport.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<capacity>wlss.transport.capacity</capacity>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.timer</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.timer.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<max-threads-constraint>wlss.timer.maxthreads</max-threads-constraint>
<capacity>wlss.timer.capacity</capacity>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.tracing.domain</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.tracing.fsrc</fair-share-request-class>
<min-threads-constraint>wlss.tracing.minthreads</min-threads-constraint>
<max-threads-constraint>wlss.tracing.maxthreads</max-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.tracing.local</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.tracing.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<min-threads-constraint>wlss.tracing.minthreads</min-threads-constraint>
<max-threads-constraint>wlss.tracing.maxthreads</max-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.connect</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.connect.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<min-threads-constraint>wlss.connect.minthreads</min-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>weblogic.wsee.mdb.DispatchPolicy</name>
<target>M1,M2</target>
</work-manager>
<work-manager>
<name>weblogic.wsee.jaxws.mdb.DispatchPolicy</name>
<target>M1, M2</target>
</work-manager>
</self-tuning>
<file-store>
<name>WseeFileStore_auto_2</name>
<directory>WseeFileStore_auto_2</directory>
<target>M1</target>
</file-store>
<file-store>
<name>WseeFileStore_auto_3</name>
<directory>WseeFileStore_auto_3</directory>
<target>M2</target>
</file-store>
<file-store>
<name>WseeJaxwsFileStore_auto_2</name>
<directory>WseeJaxwsFileStore_auto_2</directory>
<target>M1</target>
</file-store>
<file-store>
<name>WseeJaxwsFileStore_auto_3</name>
<directory>WseeJaxwsFileStore_auto_3</directory>
<target>M2</target>
</file-store>
<file-store>
<name>WseeFileStore</name>
<directory>WseeFileStore</directory>
<target>AdminServer</target>
</file-store>
<jms-system-resource>
<name>WseeJmsModule</name>
<target>M1,M2</target>
<sub-deployment>
<name>WseeJmsServer9127702</name>
<target>WseeJmsServer_auto_2</target>
</sub-deployment>
<sub-deployment>
<name>WseeJmsServer20604610</name>
<target>WseeJmsServer_auto_3</target>
</sub-deployment>
<descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>WseeJaxwsJmsModule</name>
<target>M1,M2</target>
<sub-deployment>
<name>WseeJaxwsJmsServer31278546</name>
<target>WseeJaxwsJmsServer_auto_2</target>
</sub-deployment>
<sub-deployment>
<name>WseeJaxwsJmsServer7750867</name>
<target>WseeJaxwsJmsServer_auto_3</target>
</sub-deployment>
<descriptor-file-name>jms/wseejaxwsjmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<custom-resource>
<name>sipserver</name>
<target>M1,M2</target>
<descriptor-file-name>custom/sipserver.xml</descriptor-file-name>
<resource-class>com.bea.wcp.sip.management.descriptor.resource.SipServerResource</resource-class>
<descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.SipServerBean</descriptor-bean-class>
</custom-resource>
<admin-server-name>AdminServer</admin-server-name>
<saf-agent>
<name>ReliableWseeSAFAgent</name>
<target>AdminServer</target>
<store>WseeFileStore</store>
</saf-agent>
<saf-agent>
<name>ReliableWseeJaxwsSAFAgent_M1</name>
<target>M1</target>
<store>WseeJaxwsFileStore_auto_2</store>
</saf-agent>
<saf-agent>
<name>ReliableWseeJaxwsSAFAgent_M2</name>
<target>M2</target>
<store>WseeJaxwsFileStore_auto_3</store>
</saf-agent>
</domain>
Can someone please helpme here..I tried same and facing below error whenever i click on any tab over the console :-
Error opening /jsp/core/server/ServersControlTable.jsp
The source of this error is:
java.lang.OutOfMemoryError: PermGen space
++++++++
below is the MEm_ARGS in commEnv.sh :-
# This script is used to set up a common environment for starting WebLogic
# Server, as well as WebLogic development.
# It sets the following variables:
# BEA_HOME - The home directory of all your BEA installation.
# MW_HOME - The home directory of all your Oracle installation.
# WL_HOME - The root directory of the BEA installation.
# COHERENCE_HOME - The root directory of the COHERENCE installation.
# ANT_HOME - The Ant Home directory.
# ANT_CONTRIB - The Ant contrib directory
# JAVA_HOME - Location of the version of Java used to start WebLogic
# Server. See the Oracle Fusion Middleware Supported System Configurations page
# (http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html) for an
# up-to-date list of supported JVMs on your platform.
# JAVA_VENDOR - Vendor of the JVM (i.e. BEA, HP, IBM, Sun, etc.)
# JAVA_USE_64BIT - Indicates if JVM uses 64 bit operations
# PATH - JDK and WebLogic directories will be added to the system
# path.
# WEBLOGIC_CLASSPATH - Classpath required to start WebLogic Server.
# FMWCONFIG_CLASSPATH - Classpath required to start config tools such as WLST, config wizard, pack, and unpack..
# FMWLAUNCH_CLASSPATH - Additional classpath needed for WLST start script
# LD_LIBRARY_PATH, LIBPATH and SHLIB_PATH
# - To locate native libraries.
# JAVA_VM - The java arg specifying the VM to run. (e.g.
# -server, -hotspot, etc.)
# MEM_ARGS - The variable to override the standard memory arguments
# passed to java.
# CLASSPATHSEP - CLASSPATH delimiter.
# PATHSEP - Path delimiter.
# DERBY_HOME - Derby home directory.
# DERBY_TOOLS - Derby tools jar.
# DERBY_CLASSPATH - Classpath needed to start Derby.
# DERBY_CLIENT_CLASSPATH
# - Derby client classpath.
# PRODUCTION_MODE - Indicates if the Server will be started in PRODUCTION_MODE
# PATCH_CLASSPATH - WebLogic system classpath patch
# PATCH_LIBPATH - Library path used for patches
# PATCH_PATH - Path used for patches
# WEBLOGIC_EXTENSION_DIRS - Extension dirs for WebLogic classpath patch
# It exports the following function:
# trapSIGINT - Get actual Derby PID when running in MKSNT environment;
# trap SIGINT to make sure Derby will also be stopped.
# resetFd - Reset the number of open file descriptors to 1024.
# jDriver for Oracle users: This script assumes that native libraries required
# for jDriver for Oracle have been installed in the proper location and that
# your os specific library path variable (i.e. LD_LIBRARY_PATH/solaris,
# SHLIB_PATH/hpux, etc...) has been set appropriately. Also note that this
# script defaults to the oci920_8 version of the shared libraries. If this is
# not the version you need, please adjust the library path variable
# accordingly.
# sub functions
# limit the number of open file descriptors
resetFd() {
if [ ! -n "`uname -s |grep -i cygwin || uname -s |grep -i windows_nt || \
uname -s |grep -i HP-UX`" ]
then
ofiles=`ulimit -S -n`
maxfiles=`ulimit -H -n`
if [ "$?" = "0" -a `expr ${maxfiles} : '[0-9][0-9]*$'` -eq 0 -a `expr ${ofiles} : '[0-9][0-9]*$'` -eq 0 ]; then
ulimit -n 4096
else
if [ "$?" = "0" -a `uname -s` = "SunOS" -a `expr ${maxfiles} : '[0-9][0-9]*$'` -eq 0 ]; then
if [ ${ofiles} -lt 65536 ]; then
ulimit -H -n 65536
else
ulimit -H -n ${ofiles}
fi
fi
fi
fi
# Get actual Derby process when running in MKS/NT environment;
# Trap SIGINT
# input:
# DERBY_PID -- Derby server process id.
# output:
# DERBY_PID -- Actual Derby pid in MKS/NT environment.
trapSIGINT() {
# With MKS, the pid of $! dosen't show up correctly.
# It starts a shell process to launch whatever commands it calls.
if [ `uname -s` = "Windows_NT" ]; then
DERBY_PID=`ps -eo pid,ppid |
awk -v DERBY_PID=${DERBY_PID} '$2 == DERBY_PID {print $1}'`
POINTBASE_PID=`ps -eo pid,ppid |
awk -v POINTBASE_PID=${POINTBASE_PID} '$2 == POINTBASE_PID {print $1}'`
fi
# Kill Derby on interrupt from this script (^C)
trap 'if [ "${DERBY_PID}" != "" ]; then
kill -9 ${DERBY_PID}
unset DERBY_PID
fi' 2
trap 'if [ "${POINTBASE_PID}" != "" ]; then
kill -9 ${POINTBASE_PID}
unset POINTBASE_PID
fi' 2
# end of sub functions
# Set up BEA Home
BEA_HOME="/bea/wls"
# Set up Middleware Home
MW_HOME="/bea/wls"
# Set up WebLogic Home
WL_HOME="/bea/wls/wlserver_10.3"
# Set up COHERENCE Home
COHERENCE_HOME="/bea/wls/coherence_3.6"
# Set up Common Modules Directory
MODULES_DIR="/bea/wls/modules"
# Set up Common Features Directory
FEATURES_DIR="/bea/wls/modules/features"
# Set up Ant Home
ANT_HOME="${MODULES_DIR}/org.apache.ant_1.7.1"
# Set up Ant contrib
ANT_CONTRIB="${MODULES_DIR}/net.sf.antcontrib_1.1.0.0_1-0b2"
# Setup SUN_ARCH_DATA_MODEL
SUN_ARCH_DATA_MODEL="32"
#JAVA_USE_64BIT, true if JVM uses 64 bit operations
JAVA_USE_64BIT=false
# Reset JAVA_HOME, JAVA_VENDOR and PRODUCTION_MODE unless JAVA_HOME
# and JAVA_VENDOR are pre-defined.
if [ -z "${JAVA_HOME}" -o -z "${JAVA_VENDOR}" ]; then
# Set up JAVA HOME
JAVA_HOME="/usr/jdk/instances/jdk1.7.0_05"
# Set up JAVA VENDOR, possible values are
#Oracle, HP, IBM, Sun ...
JAVA_VENDOR=Oracle
# PRODUCTION_MODE, default to the development mode
PRODUCTION_MODE=""
fi
export BEA_HOME MW_HOME WL_HOME MODULES_DIR FEATURES_DIR COHERENCE_HOME ANT_HOME ANT_CONTRIB JAVA_HOME JAVA_VENDOR PRODUCTION_MODE JAVA_USE_64BIT
# Set up JVM options base on value of JAVA_VENDOR
if [ "$PRODUCTION_MODE" = "true" ]; then
case $JAVA_VENDOR in
Oracle)
JAVA_VM=-server
MEM_ARGS="-Xms128m -Xmx256m"
HP)
JAVA_VM=-server
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
IBM)
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
Sun)
JAVA_VM=-server
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
Apple)
JAVA_VM=-server
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
esac
else
case $JAVA_VENDOR in
Oracle)
JAVA_VM=-server
MEM_ARGS="-Xms128m -Xmx256m"
-Xms512m -Xmx512m -XX:MaxPermSize=256m
JAVA_OPTIONS="${JAVA_OPTIONS} -Xverify:none"
HP)
JAVA_VM=-client
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
IBM)
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
Sun)
JAVA_VM=-client
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
JAVA_OPTIONS="${JAVA_OPTIONS} -Xverify:none"
Apple)
JAVA_VM=-client
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
esac
fi
export JAVA_VM MEM_ARGS JAVA_OPTIONS
# Set the classpath separator
case `uname -s` in
Windows_NT*)
CLASSPATHSEP=\;
PATHSEP=\;
CYGWIN*)
CLASSPATHSEP=\;
esac
if [ "${CLASSPATHSEP}" = "" ]; then
CLASSPATHSEP=:
fi
if [ "${PATHSEP}" = "" ]; then
PATHSEP=:
fi
export PATHSEP CLASSPATHSEP
# Set-up patch related class path, extension dirs, library path and path options
if [ -f "${WL_HOME}/common/bin/setPatchEnv.sh" ]; then
. "${WL_HOME}"/common/bin/setPatchEnv.sh
fi
# Figure out how to load java native libraries, also add -d64 for hpux and solaris 64 bit arch.
case `uname -s` in
AIX)
if [ -n "${LIBPATH}" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LIBPATH=${LIBPATH}:${WL_HOME}/server/native/aix/ppc64
else
LIBPATH=${LIBPATH}:${WL_HOME}/server/native/aix/ppc
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LIBPATH=${WL_HOME}/server/native/aix/ppc64
else
LIBPATH=${WL_HOME}/server/native/aix/ppc
fi
fi
LIBPATH=${PATCH_LIBPATH}:${LIBPATH}
export LIBPATH
HP-UX)
arch=`uname -m`
if [ "${arch}" = "ia64" ]; then
if [ -n "${SHLIB_PATH}" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/IPF64:${WL_HOME}/server/native/hpux11/IPF64/oci920_8
else
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/IPF32:${WL_HOME}/server/native/hpux11/IPF32/oci920_8
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${WL_HOME}/server/native/hpux11/IPF64:${WL_HOME}/server/native/hpux11/IPF64/oci920_8
else
SHLIB_PATH=${WL_HOME}/server/native/hpux11/IPF32:${WL_HOME}/server/native/hpux11/IPF32/oci920_8
fi
fi
else
if [ -n "${SHLIB_PATH}" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/PA_RISC64:${WL_HOME}/server/native/hpux11/PA_RISC64/oci920_8
else
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/PA_RISC:${WL_HOME}/server/native/hpux11/PA_RISC/oci920_8
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${WL_HOME}/server/native/hpux11/PA_RISC64:${WL_HOME}/server/native/hpux11/PA_RISC64/oci920_8
else
SHLIB_PATH=${WL_HOME}/server/native/hpux11/PA_RISC:${WL_HOME}/server/native/hpux11/PA_RISC/oci920_8
fi
fi
fi
SHLIB_PATH=${PATCH_LIBPATH}:${SHLIB_PATH}
export SHLIB_PATH
if [ "${JAVA_USE_64BIT}" = "true" ] && [ "${JAVA_VENDOR}" != "Oracle" ]
then
JVM_D64="-d64"
export JVM_D64
JAVA_VM="${JAVA_VM} ${JVM_D64}"
export JAVA_VM
fi
LINUX|Linux)
arch=`uname -m`
if [ -n "${LD_LIBRARY_PATH}" ]; then
if [ "${arch}" = "ia64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/ia64:${WL_HOME}/server/native/linux/ia64/oci920_8
else
if [ "${arch}" = "x86_64" -a "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/${arch}:${WL_HOME}/server/native/linux/${arch}/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/${arch}:${WLSS_HOME}/server/native/linux/${arch}/oci920_8
fi
else
if [ "${arch}" = "s390x" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/s390x
else
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/i686:${WL_HOME}/server/native/linux/i686/oci920_8
fi
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/i686:${WLSS_HOME}/server/native/linux/i686/oci920_8
fi
fi
fi
else
if [ "${arch}" = "ia64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/ia64:${WL_HOME}/server/native/linux/ia64/oci920_8
else
if [ "${arch}" = "x86_64" -a "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/linux/${arch}:${WL_HOME}/server/native/linux/${arch}/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/${arch}:${WLSS_HOME}/server/native/linux/${arch}/oci920_8
fi
else
if [ "${arch}" = "s390x" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/linux/s390x
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/linux/i686:${WL_HOME}/server/native/linux/i686/oci920_8
fi
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/i686:${WLSS_HOME}/server/native/linux/i686/oci920_8
fi
fi
fi
fi
LD_LIBRARY_PATH=${PATCH_LIBPATH}:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
OSF1)
if [ -n "${LD_LIBRARY_PATH}" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/tru64unix
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/tru64unix
fi
LD_LIBRARY_PATH=${PATCH_LIBPATH}:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
SunOS)
arch=`uname -m`
if [ -n "${LD_LIBRARY_PATH}" ]; then
if [ "${arch}" = "i86pc" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/x64
else
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/x86
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/sparc64:${WL_HOME}/server/native/solaris/sparc64/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc64:${WLSS_HOME}/server/native/solaris/sparc64/oci920_8
fi
else
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/sparc:${WL_HOME}/server/native/solaris/sparc/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc:${WLSS_HOME}/server/native/solaris/sparc/oci920_8
fi
fi
fi
else
if [ "${arch}" = "i86pc" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/x64
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/x86
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/sparc64:${WL_HOME}/server/native/solaris/sparc64/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc64:${WLSS_HOME}/server/native/solaris/sparc64/oci920_8
fi
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/sparc:${WL_HOME}/server/native/solaris/sparc/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc:${WLSS_HOME}/server/native/solaris/sparc/oci920_8
fi
fi
fi
fi
LD_LIBRARY_PATH=${PATCH_LIBPATH}:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
if [ "${JAVA_USE_64BIT}" = "true" ] && [ "${JAVA_VENDOR}" != "Oracle" ]
then
JVM_D64="-d64"
export JVM_D64
JAVA_VM="${JAVA_VM} ${JVM_D64}"
export JAVA_VM
fi
Darwin)
if [ -n "${DYLD_LIBRARY_PATH}" ]; then
DYLD_LIBRARY_PATH=${DYLD_LIBRARY_PATH}:${WL_HOME}/server/native/macosx
else
DYLD_LIBRARY_PATH=${WL_HOME}/server/native/macosx
fi
DYLD_LIBRARY_PATH=${PATCH_LIBPATH}:${DYLD_LIBRARY_PATH}
export DYLD_LIBRARY_PATH
Windows_NT*) ;;
CYGWIN*) ;;
echo "$0: Don't know how to set the shared library path for `uname -s`. "
esac
# set up WebLogic Server's class path
WEBLOGIC_CLASSPATH="${JAVA_HOME}/lib/tools.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic.jar${CLASSPATHSEP}${FEATURES_DIR}/weblogic.server.modules_10.3.4.0.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${ANT_HOME}/lib/ant-all.jar${CLASSPATHSEP}${ANT_CONTRIB}/lib/ant-contrib.jar"
export WEBLOGIC_CLASSPATH
# set up config tools class path
FMWCONFIG_CLASSPATH="${JAVA_HOME}/lib/tools.jar${CLASSPATHSEP}${BEA_HOME}/utils/config/10.3/config-launch.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic.jar${CLASSPATHSEP}${FEATURES_DIR}/weblogic.server.modules_10.3.4.0.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${ANT_HOME}/lib/ant-all.jar${CLASSPATHSEP}${ANT_CONTRIB}/lib/ant-contrib.jar"
export FMWCONFIG_CLASSPATH
FMWLAUNCH_CLASSPATH="${BEA_HOME}/utils/config/10.3/config-launch.jar"
export FMWLAUNCH_CLASSPATH
if [ "${PATCH_CLASSPATH}" != "" ] ; then
WEBLOGIC_CLASSPATH="${PATCH_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH}"
export WEBLOGIC_CLASSPATH
FMWCONFIG_CLASSPATH="${PATCH_CLASSPATH}${CLASSPATHSEP}${FMWCONFIG_CLASSPATH}"
export FMWCONFIG_CLASSPATH
fi
if [ "$SIP_ENABLED" = "true" ]; then
# set up SIP classpath
SIP_CLASSPATH="${WLSS_HOME}/server/lib/weblogic_sip.jar"
# add to WLS class path
WEBLOGIC_CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${SIP_CLASSPATH}"
export WEBLOGIC_CLASSPATH
FMWCONFIG_CLASSPATH="${FMWCONFIG_CLASSPATH}${CLASSPATHSEP}${SIP_CLASSPATH}"
export FMWCONFIG_CLASSPATH
fi
# DERBY configuration
DERBY_HOME="${WL_HOME}/common/derby"
DERBY_CLIENT_CLASSPATH="${DERBY_HOME}/lib/derbyclient.jar"
DERBY_CLASSPATH="${CLASSPATHSEP}${DERBY_HOME}/lib/derbynet.jar${CLASSPATHSEP}${DERBY_CLIENT_CLASSPATH}"
DERBY_TOOLS="${DERBY_HOME}/lib/derbytools.jar"
DERBY_SYSTEM_HOME=${WL_HOME}/common/derby/demo/databases
DERBY_OPTS="-Dderby.system.home=$DERBY_SYSTEM_HOME"
if [ "${DERBY_PRE_CLASSPATH}" != "" ] ; then
DERBY_CLASSPATH="${DERBY_PRE_CLASSPATH}${CLASSPATHSEP}${DERBY_CLASSPATH}"
fi
if [ "${DERBY_POST_CLASSPATH}" != "" ] ; then
DERBY_CLASSPATH="${DERBY_CLASSPATH}${CLASSPATHSEP}${DERBY_POST_CLASSPATH}"
fi
export DERBY_HOME DERBY_CLASSPATH DERBY_TOOLS DERBY_SYSTEM_HOME DERBY_OPTS
if [ -d "${WL_HOME}/common/eval/pointbase" ]
then
# PointBase configuration
POINTBASE_HOME="${WL_HOME}/common/eval/pointbase"
POINTBASE_CLIENT_CLASSPATH="${POINTBASE_HOME}/lib/pbclient57.jar"
POINTBASE_CLASSPATH="${CLASSPATHSEP}${POINTBASE_HOME}/lib/pbembedded57.jar${CLASSPATHSEP}${POINTBASE_CLIENT_CLASSPATH}"
POINTBASE_TOOLS="${POINTBASE_HOME}/lib/pbtools57.jar"
if [ "${POINTBASE_PRE_CLASSPATH}" != "" ] ; then
POINTBASE_CLASSPATH="${POINTBASE_PRE_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}"
fi
if [ "${POINTBASE_POST_CLASSPATH}" != "" ] ; then
POINTBASE_CLASSPATH="${POINTBASE_CLASSPATH}${CLASSPATHSEP}${POINTBASE_POST_CLASSPATH}"
fi
export POINTBASE_HOME POINTBASE_CLASSPATH POINTBASE_TOOLS
fi
# Set up PATH
if [ `uname -s` = "CYGWIN32/NT" ]; then
# If we are on an old version of Cygnus we need to turn <letter>:/ in the path
# to //<letter>/
WL_HOME_CYGWIN=`echo $WL_HOME | sed 's#\([a-zA-Z]\):#//\1#g'`
ANT_HOME_CYGWIN=`echo $ANT_HOME | sed 's#\([a-zA-Z]\):#//\1#g'`
ANT_CONTRIB_CYGWIN=`echo $ANT_CONTRIB | sed 's#\([a-zA-Z]\):#//\1#g'`
JAVA_HOME_CYGWIN=`echo $JAVA_HOME | sed 's#\([a-zA-Z]\):#//\1#g'`
PATCH_PATH_CYGWIN=`echo $PATCH_PATH | sed 's#\([a-zA-Z]\):#//\1#g'`
WL_USE_X86DLL=
WL_USE_IA64DLL=
WL_USE_AMD64DLL=
if [ "${WL_USE_IA64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64/oci920_8"
fi
if [ "${WL_USE_X86DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32/oci920_8"
fi
if [ "${WL_USE_AMD64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64/oci920_8"
fi
else
if [ -n "`uname -s |grep -i cygwin_`" ]; then
# If we are on an new version of Cygnus we need to turn <letter>:/ in
# the path to /cygdrive/<letter>/
CYGDRIVE=`mount -ps | tail -1 | awk '{print $1}' | sed -e 's%/$%%'`
WL_HOME_CYGWIN=`echo $WL_HOME | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
ANT_HOME_CYGWIN=`echo $ANT_HOME | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
PATCH_PATH_CYGWIN=`echo $PATCH_PATH | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
JAVA_HOME_CYGWIN=`echo $JAVA_HOME | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
WL_USE_X86DLL=
WL_USE_IA64DLL=
WL_USE_AMD64DLL=
if [ "${WL_USE_IA64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64/oci920_8"
fi
if [ "${WL_USE_X86DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32/oci920_8"
fi
if [ "${WL_USE_AMD64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64/oci920_8"
fi
else
# set PATH for other shell environments
PATH="${WL_HOME}/server/bin${PATHSEP}${ANT_HOME}/bin${PATHSEP}${JAVA_HOME}/jre/bin${PATHSEP}${JAVA_HOME}/bin${PATHSEP}${PATH}"
# On Windows, include WebLogic jDriver in PATH
if [ -n "`uname -s |grep -i windows_nt`" ]; then
WL_USE_X86DLL=
WL_USE_IA64DLL=
WL_USE_AMD64DLL=
if [ "${WL_USE_IA64DLL}" = "true" ]; then
PATH="${PATCH_PATH}${PATHSEP}${WL_HOME}/server/native/win/64${PATHSEP}${PATH}${PATHSEP}${WL_HOME}/server/native/win/64/oci920_8"
fi
if [ "${WL_USE_AMD64DLL}" = "true" ]; then
PATH="${PATCH_PATH}${PATHSEP}${WL_HOME}/server/native/win/x64${PATHSEP}${PATH}${PATHSEP}${WL_HOME}/server/native/win/x64/oci920_8"
fi
if [ "${WL_USE_X86DLL}" = "true" ]; then
PATH="${PATCH_PATH}${PATHSEP}${WL_HOME}/server/native/win/32${PATHSEP}${PATH}${PATHSEP}${WL_HOME}/server/native/win/32/oci920_8"
fi
fi
fi
fi
export PATH
resetFd
=======
my system is not on production mode and using oracle java. please suggest -
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 ServerDear 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]$ -
Facing error in starting managed server from nodemanager
Hi All,
I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
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]
Starting WLS with line:
D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_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=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
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]
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
<11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
Can anyone please tell me what could be the issue. It is really urgent. Please help!!Hi Roshni,
It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
3. Save and close the file.
4. Restart the Node Manager
If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
Thanks,
Scott (PITSS)
http://pitss.com/us -
Getting error while starting Managed Server
Hi All,
I configured Custered environment in Weblogic 9.2 to use in ALSB.
While starting managed server i am getting error :
<Critical> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666363188> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:941)
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)
>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000365> <Server state changed to FAILED>
####<Feb 3, 2009 6:36:04 PM IST> <Error> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364594> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Feb 3, 2009 6:36:04 PM IST> <Info> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364891> <BEA-000236> <Stopping execute threads.>
Can anybody pls guide me to solve this erro.
Thanks,
KartheekThis statement should be prominently displayed in this and all similar forums, but the best advice I can give anyone here is that if you're struggling with a problem for several DAYS, not to mention weeks, and the only resource you've used is this forum, you should file a support request with Oracle right now. That is one of the most important skills you will need to use WebLogic effectively.
-
Getting error while starting Managed server configured in ALSB(ClusteredEnv
Hi All,
I configured Custered environment in Weblogic 9.2 to use in ALSB.
While starting managed server i am getting error :
<Critical> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666363188> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:941)
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)
>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000365> <Server state changed to FAILED>
####<Feb 3, 2009 6:36:04 PM IST> <Error> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364594> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Feb 3, 2009 6:36:04 PM IST> <Info> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364891> <BEA-000236> <Stopping execute threads.>
Can anybody pls guide me to solve this erro.
Thanks,
KartheekYou probably changed your system password in the console?
Look for your boot.properties file in the following location:
[domain]\servers\[server]\security
change the following line:
password={3DES}Ytm72Oh4zE0bsptrYn13Xw==
to:
password=mynewpassword
WebLogic Server will encrypt the password on the next boot, and your problem should be resolved. -
Error start managed server from admin console in SSL mode
I have configured Admin server, managed servers and node manager on the same physical server and commonly using a single SSL sertificate.
There is no problem to start node manager, admin server and managed server individually. But if I try to start managed server from the admin console then I am getting the following errors.
<Feb 22, 2005 11:02:26 AM CST> <Info> <[email protected]:6666> <Starting Server peoplesoft::PIA1 ...>
<Feb 22, 2005 11:02:26 AM CST> <Info> <NodeManager@xxxxxxxxxx:6666> <BaseProcessControl: saving process id of Weblogic Managed server 'PIA1', pid: 285390>
<Feb 22, 2005 11:02:35 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://xxxxxxxx:admin_server_portnumber to check if there exists a running admin server at this URL.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch 8 CR174605 for PeopleSoft 09/09/2004 18:11:35
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<Feb 22, 2005 11:02:37 AM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://xxxxxxxxx.org:Admin_server_portnumber to retrieve the initial configuration.>
<Feb 22, 2005 11:02:45 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xxxx/webserv/peoplesoft/PIA1/PIA1.log is opened. All server side log events will be written to this file.>
<Feb 22, 2005 11:03:01 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Feb 22, 2005 11:03:01 AM CST> <Warning> <Security> <BEA-090066> <Problem handling boot identity. The following exception was generated: java.lang.NullPointerException>
<Feb 22, 2005 11:03:10 AM CST> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
<Feb 22, 2005 11:03:10 AM CST> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : null>
<Feb 22, 2005 11:03:10 AM CST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
I am running everything on IBM UNIX server.
I appriciate your help.
Thanks & regards,
Laxman.Hi
From the admin console ... Are you able to check the status of Node Manager ?
If yes ... please check the SSL configuration of managed servers ...
Check the domain administration port also.
Jin -
Errors Starting Managed Server
Hai all!
I Have 1 Admin server A and One Managed Server M.
1)I Started Admin server A.
2)It starts fine promitng Clustering services are started
3)Now i starts Managed Server M.
4)When starting M it gives error Application defaultwebAppA cannot be deployed
into server M.
5)At the same time in console of Admin A error message prints out reading Unable
to deploy defaultWebAppB into Server A.
What may be the problem?
Can u Pls drive out of the problem?
TIA
Rgds
Manohar
[att1.html]
-
Error starting managed server with JRockit VM
I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
option on. The OS is NT. Any clues , please ?
exception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
D:\i252\services>runtxnserver
JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
Garbage Collector, started.
[JRockit] Starting Management Server on port 7090
Starting WebLogic Server ....
Connecting to http://ocncat2:7991...
<May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on fd:
4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
35c4a
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
tected attempting to connect to admin server at http://ocncat2:7991 during i
alization of managed server ( null:7551 ). The reported error was: < java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) > This condition generally results when the managed and
n servers are using the same listen address and port.>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize th
rver: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException:
.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack traceI found the solution . The reason for this is that JRockit's High Performance Thread
System uses asynchrounous I/O "under the hood". Weblogic's Native I/O is also asynchronous.
The two asynchronous I/O systems clash and the result is the error you see.
There are two ways around this problem. Either disable JRockit's High Performance
Thread System (or thinthreads) by using the -Xnativethreads command line flag, or
disable Weblogic's Native I/O.
For Weblogic 6.0 and higher, edit the config.xml file. Find the line saying NativeIOEnabled="true"
and change this to NativeIOEnabled="false".
For Weblogic 5.1 you edit the file weblogic.properties and change the line weblogic.system.nativeIO.enable=true
to
weblogic.system.nativeIO.enable=false
"Manoj jayadevan" <[email protected]> wrote:
>
I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
option on. The OS is NT. Any clues , please ?
exception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
D:\i252\services>runtxnserver
JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
Garbage Collector, started.
[JRockit] Starting Management Server on port 7090
Starting WebLogic Server ....
Connecting to http://ocncat2:7991...
<May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on
fd:
4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
35c4a
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
tected attempting to connect to admin server at http://ocncat2:7991 during
i
alization of managed server ( null:7551 ). The reported error was: < java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) > This condition generally results when the managed
and
n servers are using the same listen address and port.>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize
th
rver: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException:
.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace -
Fatal initialization exception occurs when starting Managed Server
Hi all,
First I configured a Adminisistration server and started it. After that I added
a another server as ManagedServer.These two points to the same Weblogic server.
When I try to start Managed server by running the script, it gave me following
error. _______________________________
<Jun 25, 2001 5:25:11 PM GMT+06:00> <Emergency> <Server> <Unable to initialize
the server: 'Fatal initialization exception Throwable: java.lang.IllegalAccessError:
java.security.acl.NotOwnerException java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91) at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183) at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116) at
weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:444)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:287)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:259)
at weblogic.jndi.Environment.getContext(Environment.java:135) at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:891) at weblogic.management.Admin.start(Admin.java:305)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35) ______________________________________________
I suspect reason for this might be weblogic.policy file. There you need to edit
some lines replacing the location of the directory in which you installed WebLogic
Server. I did this but still error occurs.
Do u have any idea why above error occurs and if it is due to the weblogic.policy
file entry please tell me how it correctly done.
I am using WL60(sp2)in Win NT,
My installed dir: E:\bea\wlserver6.0\
Thanks NalikaHi
(It was me and Berit that sent the original question).
After some experimentation we saw that the managed server did get
some configuration from the admin server, so the problem was in
there somewhere.
I had added an (empty) cluster and machine to the admin server, just
to test adding. When I removed them everything worked fine afterward.
So it was some kind of configuration error from our side, but we never
did find out what it was.
I guess the lesson is to only define things when you really need them :-)
Regards
Mikael
Timothy Fry wrote:
We're getting the same problem, but on Solaris 2.7.
Did you get a solution from bea yet?
Tim
"Berit Bylund" <[email protected]> wrote in message
news:[email protected]..
Hello
We are trying to start a managed server (under the examples
domain, NT 4.0, WLS 6.0 Beta 2)
We start the managed server with the parameter
-Dweblogic.management.server=http://127.0.0.1:7001 -
Error in Starting Managed Server
Hi,
I have installed Oracle webcenter Portal 11g on my local machine.
Started admin server successfully
url: http://localhost:7001/console
When i tried starting Managed server WC_Spaces,WC_Portlet,WC_Collaboration & WC_Utilities.
Am getting error as "<BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied"
Whole error log copied below.
####<28 Oct, 2013 4:46:41 PM IST> <Critical> <Security> <BDC4B-D-5PKRWQ1> <WC_Spaces> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1382959001849> <BEA-090403> <Authentication for user weblogic denied>
####<28 Oct, 2013 4:46:41 PM IST> <Critical> <WebLogicServer> <BDC4B-D-5PKRWQ1> <WC_Spaces> <main> <<WLS Kernel>> <> <> <1382959001850> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
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.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
at $Proxy36.login(Unknown Source)
at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
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.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
at $Proxy54.authenticate(Unknown Source)
at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:338)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:930)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Any one has come accross this kind of issue.
Thanks,
ARHi ,
This is just to confirm , when you started AdminServer for first time , did you create boot.properties file yourself ? . Second are you able to log in to Admin Console using the same username/pwd ? Also are you able to start manage servers from AdminServer console ?
Thanks
Maybe you are looking for
-
Itunes incompatibility with windows vista
Itunes versions 7.1 and 7.2 do not work with windows vista correctly. Both versions interfere with uploading the DVD drive when booting up the computer. The DVD drive can not start. Is there a solution for this?
-
Disable RightClick on PDF in Browser using API methods ?
How to use adobe acrobat API method/events to capture function keydown effectively disabling rightclick menu in Reader in browser? Question: can anyone illustrate how to disable menu right click ? ive seen methods/events in the acrobat api that look
-
HTTPS certificate problem on MPLS
/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tableau Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0c
-
How to check two internal table fields
Hi all, I need to check two internal table fields are equal or not means which statement i can use. Not internal table ,table contents i need to check i.e it1-pernr = it2-pernr. like this if i put loop it'll check one table field for one loop. if i p
-
Hi Experts, Have a basic question, if every transaction in SAP can be accessed with ITS without any new development why is that we need build BSP or Webdynpro pages? I am sure there are some drawbacks of ITS but I was not able to find out more deta