Getting JMS Exception while starting the managed servers

Hi ,
I have Savvion BPM tool hosted on WebLogic server 10.3 version.Before the manage servers coming to Running state its throwing the below mention warning message.Can anybody help me to identify what could be the reason the managed server the below exceptions.
Thanks in advance...
<Jun 19, 2012 3:54:32 AM EDT> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server sbmejb2.>
<Jun 19, 2012 3:54:33 AM EDT> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server sbmejb2.>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
*<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLServiceMDB is unable to connect to the J*
MS destination: jms/BLAdminTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster addres
s "sbmejb1,sbmejb2">
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCacheSyncMDB is unable to connect to the
JMS destination: jms/BLCacheSyncTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLSessionMDB is unable to connect to the J
MS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.177.16.126:16103 for pr
otocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "sbmejb1" for domain "sb
m76" running in Production Mode>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLBizStoreMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCheckDueMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLEmailMDB is unable to connect to the JMS
destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLResumeWSMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MConsoleServiceMDB is unable to connect to
the JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EPServiceMDB is unable to connect to the J
MS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:42 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EventReaderBean is unable to connect to th
e JMS destination: jms/BPAdminTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

Hi Rohit,
Thanks for your response..
Below is the BLAdminTopic configuration.Please let me know if you need any further info.
Topic:BLAdminTopic
Type:Distributed Topic
JNDI:jms/BLAdminTopic
Sub Deployment :N/A
Target:N/A
BLAdminTopic@jmsnode1BL Topic jms/BLAdminTopic@jmsnode1BL BLAdminTopic@jmsnode1BL jmsnode1BL
BLAdminTopic@jmsnode2BL Topic jms/BLAdminTopic@jmsnode2BL BLAdminTopic@jmsnode2BL jmsnode2BL
Regards,
Jyotiranjan

Similar Messages

Empty initial replica exception while starting up managed servers

Hi,
I am doing what should be a fairly straight forward installtion/configuration of the weblogic portal 10.3.2.
I have installed the portal, created a new domain with one admin server and two managed servers in it. I also have a cluster on which I have both my managed servers and finally I have a machine on which I have all the 3 of my servers.
I am able to successfully startup the nodemanager and then the admin server. But when I try to start up the managed servers from the admin console, I get this exception -
####<Feb 11, 2011 12:39:37 PM IST> <Critical> <WebLogicServer> <XXXXXXXX> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1297408177691> <BEA-000386> <Server subsystem failed. Reason: weblogic.ldap.EmbeddedLDAPException: Empty initial replica
weblogic.ldap.EmbeddedLDAPException: Empty initial replica
     at weblogic.ldap.EmbeddedLDAP.getInitialReplicaFromAdminServer(EmbeddedLDAP.java:1301)
     at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:221)
     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)
Any idea what could be the reason for this?
Regards,
Kunal
Edited by: kunal. on Feb 11, 2011 1:34 AM

Hi,
anybody got any solution to this?
Regards,
Kunal

General enquiry regarding starting the managed servers in weblogic

Hi,
Is there any sequence do we need to follow while bringing up the managed server? like in our set up we do have SOA,OSB & BAM managed servers.
So during maintainance activities, we have to start in sequence like SOA(managed server1),OSB(managed server 2) then BAM(managed server3).
In case if we change the above mentioned order the servers are not coming up.
So, we would like to know what might be cause & is there a sequence do we need to go thru to start the servers? if Yes, please give us the justification.
Thanks,
Sudhir.

In order to diagnostic the problem, you should post the error you're getting when trying to start the managed servers on a different order. Also, which mservers exactly are causing you problems?
Regards,
Franco.

Unable to start the Managed servers OIM and SOA after starting the Weblogic

Hi,
We are unable to start the any manager servers after starting the weblogic Admin Server.
We are getting the below error after trying to start the OIM or SOA managed servers.
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use
We have also cross verified that the port 5555 is listening after starting the weblogic Admin server.
Please help us to start the managed servers in the weblogic 10.3.5.
Thanks.

We are getting the below errors after starting the Admin server and Managed servers.
Admin Server:
<Jan 11, 2012 7:15:06 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Jan 11, 2012 7:16:02 AM EST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>
Managed Server:
Starting WLS with line:
/opt/jdk1.6.0_27/bin/java -client -Xms1024m -Xmx4096m -XX:PermSize=512m -XX:MaxPermSize=1024m -Dweblogic.Name=oim_server1 -Djava.security.policy=/ama/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/ama/Oracle/Middleware/wlserver_10.3 -Dwls.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dcommon.components.home=/ama/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Djrockit.optfile=/ama/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/servers/oim_server1 -Doracle.domain.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/carml -Digf.arisidstack.home=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/servers/oim_server1/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/ama/Oracle/Middleware/Oracle_IDM1/server/loginmodule/wls,/ama/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/ama/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -DXL.HomeDir=/ama/Oracle/Middleware/Oracle_IDM1/server -Djava.security.auth.login.config=/ama/Oracle/Middleware/Oracle_IDM1/server/config/authwl.conf -Dorg.owasp.esapi.resources=/ama/Oracle/Middleware/Oracle_IDM1/server/apps/oim.ear/APP-INF/classes -da:org.apache.xmlbeans... -Dsoa.archives.dir=/ama/Oracle/Middleware/Oracle_SOA1/soa -Dsoa.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dsoa.instance.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -Dem.oracle.home=/ama/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dums.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://127.0.0.1:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/ama/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/ama/Oracle/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use
We have to find out why the port 5555 is in listening mode after starting the Admin server.

Error while starting the managed server using nodemanager

HI ,
I am getting the below error while starting the managed server from the Admin console. All the serverstart and the node manager proeprties looks fine.
Below is the error in the managed server log,
startWebLogic.sh: grep: not found
startWebLogic.sh: uname: not found
startWebLogic.sh: test: argument expected
can you help me to solve the problem please. i am using weblogic 10.3.3
thanks
Arun

I think you've changed and added some lines into your startWebLogic.sh script. Can you put your script here?

Error while starting the managed server

Hi,
While starting the managed server i get ClassNotFoundException for the following files.
oracle.as.jmx.framework.wls.spi.StartupListener - jmxframework.jar
oracle.security.jps.wls.JpsWlsStartupClass - jps-wls.jar
oracle.security.audit.ajl.loader.JEEAuditLoader
oracle.dms.wls.DMSStartup - dms.jar
oracle.core.ojdl.weblogic.ODLConfiguration - odl2.jar
oracle.ias.cache.Startup -
oracle.mds.lcm.weblogic.WLLifecycleListener
oracle.dms.wls.DMSServletFilter
When checked I found jars related to above classes in BEAHOME/jdeveloper/modules folder.
are the jars also present some where in weblogic related folders.
Also "wsil-wls" and "dms" applications are not properly deployed in the ManagedServer.
When I am trying to deploy another application in managed server i get DMSServletFilter ClassNotFoundException.
I tried to add the above jars from jdeveloper folder to the POST_CLASSPATH in setDomainEnv.sh but i still get the same ClassNotFOundException while deploying.
Which config file should i update?
Thank You.

I think you've changed and added some lines into your startWebLogic.sh script. Can you put your script here?

BEA-423442-Exception while starting the client classifications file poller

While Weblogic 10.3.2 server is started, below error is displayed in console. Please provide if any solution for this.
<netuix> <BEA-423442> <Exception while starting the client classifications file poller: [java.lang.AbstractMethodError]
java.lang.AbstractMethodError
at com.bea.netuix.xml.util.DomToolkit.parse(DomToolkit.java:166)
at com.bea.netuix.xml.util.JDomToolkit.build(JDomToolkit.java:45)
at com.bea.netuix.client.repository.ClassifierRepository.getDocumentFromInputStream(ClassifierRepository.java:339)
at com.bea.netuix.client.repository.ClassifierRepository.createRepositoryFromInputStream(ClassifierRepository.java:326)
at com.bea.netuix.client.ClientClassifierImpl.<init>(ClientClassifierImpl.java:103)
Truncated. see log file for complete stacktrace

Hi Angel,
Please see the following doc for instructions on starting an OMS.
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/emctl.htm#BABFEEAJ
Regards,
- Loc

Exception while starting the weblogic10.0 server : getTransactionSupport

We are in process of migrating the application from weblogic8 to weblogic10.0. we are facing some problem while starting the weblogic server, continously getting the exception like
####<31-Dec-2008 10:36:19 o'clock GMT> <Error> <<MessagingBridge> <blx25ao01> <aadev100-01><STANDBY ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)> <WLS Kernel> <1230719779233> <BEA-200044> <The following exception has occurred:
java.lang.AbstractMethodError: getTransactionSupport
at weblogic.jms.bridge.internal.MessagingBridge.startInternal(MessagingBridge.java:615)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1030)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
Our application is using the JMS with MQ Queue to send and receive the message. but messages are not flown fron MQ Queue to JMS server..
Please guide me on this..as we are in critical stage of implementation phase.

You need to open a support case at support.bea.com or 888.232.7878 for urgent issues.

Cannot start the managed servers because of this error.

Hi,
I installed weblogic 10.3.6 and created admin and managed servers and node manager. I am able to startup and shutdown the admin and managed servers using the node managers but when i try to start/shutdown the managed servers from the command prompt using startManagedWeblogic.cmd, i get this error:
<Apr 27, 2012 3:42:57 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
java.net.UnknownHostException: XXXXXX.XXXX.XXXX : 7152
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:849)
at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1202)
at java.net.InetAddress.getAllByName0(InetAddress.java:1153)
at java.net.InetAddress.getAllByName(InetAddress.java:1083)
at java.net.InetAddress.getAllByName(InetAddress.java:1019)
at java.net.InetAddress.getByName(InetAddress.java:969)
at weblogic.rjvm.JVMID.setLocalID(JVMID.java:238)
at weblogic.rjvm.RJVMService.setJVMID(RJVMService.java:48)
at weblogic.rjvm.RJVMService.start(RJVMService.java:30)
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)
>
The WebLogic Server encountered a critical failure
Reason: Assertion violated
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize
class weblogic.protocol.ServerIdentityManager$Initializer
at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIden
tityManager.java:64)
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:173)
at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(S
erverLifeCycleRuntime.java:1078)
at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:429)
at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:415)
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:206)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:482)
at weblogic.Server.main(Server.java:71)
Can anybody help me out with this. I am stuck here.
Thanks,
Robert
Edited by: Robert J on Apr 27, 2012 12:57 PM

try using flag -Djava.net.preferIPv4Stack=true within the startManagedWeblogic.cmd file to start the managed server with the command prompt.
Thanks,
Sandeep

Errors while starting the manager server

Hi
I have created a manager server under weblogic 6.1 with sp2.
I am trying to start the managed server using the command file provided by weblogic. And I am getting the following exceptions.... The Admin server is up and running.
Configuration for the managed server
Name: MngdServer
Machine: None
ListenPort: 9001
ListenAddress: <null>
External DNSName: <null>
The exception I am getting is ....
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:201)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:261)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:121)
at weblogic.net.http.HttpClient.New(HttpClient.java:156)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:111)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:283)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1019)
at weblogic.management.Admin.initialize(Admin.java:326)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
>
The WebLogic Server did not start up properly.
Exception raised:
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'localhost', port: '9001'
at weblogic.net.http.HttpClient.openServer(HttpClient.java:210)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:261)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:121)
at weblogic.net.http.HttpClient.New(HttpClient.java:156)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:111)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:283)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1019)
at weblogic.management.Admin.initialize(Admin.java:326)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: connecting to http://localhost:9001/wl_management_internal2/Bootstr
ap - with nested exception:
[java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'localhost', port: '9001']
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1110)
at weblogic.management.Admin.initialize(Admin.java:326)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
***************************************************************************

startManagedWebLogic.cmd MngdServer
http://localhost:9001
You should give the url for the admin server and name of the managed server as arguments for this command. you seem like giving the url for the managed server.
this command needs url for the admin server so that it can connect to that admin server and add this managed server to that domain.
Good luck

While Starting the Managed server using node manager

The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328874> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328874> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Notice> <Security> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Nov 24, 2010 11:12:08 AM IST> <Info> <WebLogicServer> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000a> <1290577328890> <BEA-000307> <Exportable key maximum lifespan set to 500 uses.>
####<Nov 24, 2010 11:12:22 AM IST> <Error> <NodeManager> <HYDHTC99264D> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <147c637c707a0ee8:-6a0778d9:12c7c6421ea:-7fd5-000000000000000d> <1290577342764> <BEA-300048> <Unable to start the server soa_server1 : Exception while starting server 'soa_server1'>
And the state of server is "FAILED_NOT_RESTARTABLE". Please help me in this
Regards
Veena

The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.> You may configure custom Identity and Trust in weblogic. It is not recommended to use Demo Trsut and Demo Identity for environments higher to Dev. -
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13707/identity_trust.htm#i1202182
Regards,
Anuj

Problems while starting the Managed Server through Node Manager..

When I was trying to start a Managed Server using the Nodemanager , I am getting the following error :
NodeManager not configured to receive commands from host : emis-develop
I have the "nodemanager.hosts" file under the directory "c:\bea\wlserver6.1\config" and even while invoking the script for the startnodemanager , I am indicating this in the script ! Any ideas for this problem ??

The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.> You may configure custom Identity and Trust in weblogic. It is not recommended to use Demo Trsut and Demo Identity for environments higher to Dev. -
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13707/identity_trust.htm#i1202182
Regards,
Anuj

Problem while starting the managed server

Hi
We have following configuration :-
We have 2 physical sesrvers :-
Server1 and Server2 in Sun Cluster running Solaris 10.
We also have Oracle DB server 9.2.0.8 in RAC mode, one instance each on Server1 & Server2.
Server 1 :-
cluster1 :- 1 Managed Server running
Server 2 :-
cluster2 :- 1 Managed Server running
we are getting following error in admin server log :-
<Error> <NodeManager> <BEA-300034> <Could not execute command "kill" for server "cluster1" using the node manager. Reason: Connection refused. Couldn't connect to NodeManager. Check that it is running at localhost:5556.>
Recently we have enabled the Connection Filter.
also getting following info in logs :-
<Notice> <Socket> <BEA-000445> <Connection rejected, filter blocked Socket[addr=192.193.164.8,port=53666,localport=8001], weblogic.security.net.FilterException: [Security:090220]rule 16>
<Notice> <Socket> <BEA-000445> <Connection rejected, filter blocked Socket[addr=163.37.174.126,port=58284,localport=8002], weblogic.security.net.FilterException: [Security:090220]rule 17>
Is it because of any misconfiguration in Connection filter ?
Or filter is not allowing the request for ipaddress and port of Managed Server in cluster1
Thanks in advance .. :)

Thanks for the information.
Node Manager is not used.
I found problem in Connection filter.
169.187.186.76 - address ManagedServer1
169.187.186.77- address Managed server2
169.187.186.51 :- Admin Server (8001 is http and 8002 is https)
Tunneling is enable for Managed Server
Please help me understanding below things is there any ambiguity in this rules :-
In the script to stop Managed server we are using t3 protocol like : t3://ip:port but its not allowing t3 protocol .whereas t3 protocol is no where denied in rules.
If I use https to issue request still not working
<connection-filter>weblogic.security.net.ConnectionFilterImpl</connection-filter>
<connection-filter-rule>127.0.0.1 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.0.129 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.1.1 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.59 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.51 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.76 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>192.168.10.4 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.4.1 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.77 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.60 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.0.130 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.1.2 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>192.168.10.5 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.4.2 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>ocs1.in.citicorp.com 169.187.186.51 8002 allow https</connection-filter-rule>
<connection-filter-rule>* 169.187.186.51 8001 deny</connection-filter-rule>
<connection-filter-rule>* 169.187.186.51 8002 deny</connection-filter-rule>
Thanks in Advance .......

JCAPS6 - Exception While starting the application

Hi,
I created a simple File to File using JCAPS 6. I deployed it successfully. When the application is starting it is giving the below error. Has anyone faced this kind of exception?
java.lang.Exception: SunJavaSystemApplicationServer12:
At least one operation failed
     at com.stc.codegen.driver.module.DeploymentDeployAction$DeploymentProgressListener.handleProgressEvent(DeploymentDeployAction.java:1640)
     at com.stc.deployment.framework.impl.DefaultProgressObjectManager.notify(DefaultProgressObjectManager.java:327)
     at com.stc.deployment.framework.impl.DefaultProgressObjectManager.handleProgressEvent(DefaultProgressObjectManager.java:298)
     at com.sun.enterprise.deployapi.ProgressObjectSink.handleProgressEvent(ProgressObjectSink.java:193)
     at com.sun.enterprise.deployapi.ProgressObjectImpl.fireProgressEvent(ProgressObjectImpl.java:393)
     at com.sun.enterprise.deployapi.ProgressObjectImpl.fireProgressEvent(ProgressObjectImpl.java:429)
     at com.sun.enterprise.deployapi.ProgressObjectImpl.setupForAbnormalExit(ProgressObjectImpl.java:527)
     at com.sun.enterprise.deployapi.ProgressObjectImpl.checkStatusAndAddStage(ProgressObjectImpl.java:569)
     at com.sun.enterprise.deployment.client.ChangeStateAction.run(ChangeStateAction.java:120)
     at java.lang.Thread.run(Thread.java:595)
Thanks
Rupesh

You need to open a support case at support.bea.com or 888.232.7878 for urgent issues.

Exception while starting Managed Server

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


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

Getting JMS Exception while starting the managed servers

Similar Messages

Maybe you are looking for