Managed server discovery problem
I'm running WL 6.0 sp1 on Solaris 2.7.
I have my admin server discover=true. I start this up, with all my other servers in the domain
down, and get a bunch of can't-find-server warnings, which is fine. But then I get a null ptr
exception and the server shuts down!
If I manually cleaned up running-managed-servers.xml, then my admin server runs again, but obviously
I do not want to manually maintain this file!
<Mar 15, 2001 10:26:58 AM PST> <Notice> <Management> <Starting discovery of Managed Server...>
<Mar 15, 2001 10:26:58 AM PST> <Info> <Management> <Managed Server discovery, for server app03
running at 10.1.3.41:10085>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.3.41:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.3.41:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDe
legate.java:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app03
running on listen address 10.1.3.41 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No server found
at T3://10.1.3.41:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <Management> <Managed Server discovery, for server app02
running at 10.1.3.40:10085>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.3.40:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.3.40:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app02
running on listen address 10.1.3.40 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No server found
at T3://10.1.3.40:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <Management> <Managed Server discovery, for server app01
running at 10.1.1.22:10085>
<Mar 15, 2001 10:27:00 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.1.22:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.1.22:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app01
running on listen address 10.1.1.22 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No server found
at T3://10.1.1.22:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Info> <Management> <Managed Server discovery, for server web01
running at 10.1.1.22:10081>
<Mar 15, 2001 10:27:07 AM PST> <Emergency> <Server> <Unable to initialize the server: 'Fatal
initialization exception
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:191)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:191)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
done
"Viresh Garg" <[email protected]> wrote in message news:[email protected]...
Can you please follow up with [email protected], so that we can create a formal bug for this.
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
Gene Chuang wrote:
I'm running WL 6.0 sp1 on Solaris 2.7.
I have my admin server discover=true. I start this up, with all my other servers in the domain
down, and get a bunch of can't-find-server warnings, which is fine. But then I get a null ptr
exception and the server shuts down!
If I manually cleaned up running-managed-servers.xml, then my admin server runs again, but
obviously
I do not want to manually maintain this file!
<Mar 15, 2001 10:26:58 AM PST> <Notice> <Management> <Starting discovery of Managed Server...>
<Mar 15, 2001 10:26:58 AM PST> <Info> <Management> <Managed Server discovery, for server app03
running at 10.1.3.41:10085>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.3.41:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.3.41:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDe
legate.java:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app03
running on listen address 10.1.3.41 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No serverfound
at T3://10.1.3.41:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <Management> <Managed Server discovery, for server app02
running at 10.1.3.40:10085>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.3.40:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.3.40:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app02
running on listen address 10.1.3.40 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No serverfound
at T3://10.1.3.40:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <Management> <Managed Server discovery, for server app01
running at 10.1.1.22:10085>
<Mar 15, 2001 10:27:00 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.1.22:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.1.22:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app01
running on listen address 10.1.1.22 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No serverfound
at T3://10.1.1.22:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Info> <Management> <Managed Server discovery, for server web01
running at 10.1.1.22:10081>
<Mar 15, 2001 10:27:07 AM PST> <Emergency> <Server> <Unable to initialize the server: 'Fatal
initialization exception
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:191)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:191)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Similar Messages
-
Manage Server Start Problem (weblogic.store.io.jdbc.JDBCStoreException)
I have a problem, when i start manage server.
Could you please help me about this problem?
Thanks
Orhan YENER
<Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "p13nJMSPersistenceStore" failed to open table "P13N_MESSAGING_WLStore".
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "p13nJMSPersistenceStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
weblogic.store.io.jdbc.JDBCStoreException: open failed
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSPersistenceStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Warning> <Store> <BEA-280076> <Database table "PF_PROLIFERATION_WLStore" for store "pfProliferationJMSStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102728280]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:57 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "pfProliferationJMSStore" in this server is not the owner of database table "PF_PROLIFERATION_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102748300]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=3276936988962983628:timestamp=1340102737578]".>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "pfProliferationJMSStore" failed to open table "PF_PROLIFERATION_WLStore".
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
weblogic.store.io.jdbc.JDBCStoreException: open failed
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "p13nJMSServer" due to weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist.
weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server p13nJMSServer: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
Truncated. see log file for complete stacktrace
Caused By: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
Truncated. see log file for complete stacktrace
Caused By: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'p13n-security-jms'.
weblogic.application.ModuleException: ERROR: Could not activate p13n-security-jms!p13n.security.RDBMSSecurityStoreTopic
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.backend.BETopicRuntimeDelegate.activate(BETopicRuntimeDelegate.java:100)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
Truncated. see log file for complete stacktrace
Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel p13nJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
at weblogic.messaging.kernel.internal.TopicImpl.activate(TopicImpl.java:97)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:627)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
Truncated. see log file for complete stacktrace
Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1696)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1872)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320400> <The log file /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log00054. Log messages will continue to be logged in /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log.>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerportal. Error - weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.jar.JarFile.<init>(JarFile.java:133)
at java.util.jar.JarFile.<init>(JarFile.java:97)
at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerportal' due to error weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.jar.JarFile.<init>(JarFile.java:133)
at java.util.jar.JarFile.<init>(JarFile.java:97)
at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerstaticweb. Error - weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerstaticweb' due to error weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
Truncated. see log file for complete stacktrace
>
>
<Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 19, 2012 1:46:13 PM EEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jun 19, 2012 1:46:14 PM EEST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 172.25.23.238:80 was shutdown.>It's the first couple of bits that are key here
<Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
It looks to me that your stores are incorrectly configured, targetted or or just simply messed up. First thing I would do here is check the configuration and targetting of the JDBC Stores and make sure that each JMS server is using it own store and database tables. You may find that it's a really simple thing like creating two sets of tables on the same database, but making sure that they have different prefixes ... -
Weblogic 8.1 managed server shuttdown problem
Hi Friends,
When we log in to Admin console and selecting servers in the left pane and right clicking a server instance and selecting start/stop server, it shows
start this server
resume this server
graceful shutdown of this server
force shutdown of this server
The problem is graceful shutdown of this server and force shutdown of this server links are not highliting for a perticular managed server and they are highlighting all remaining servers.
that means we are unable to shutdown the server from console. we are doing from command line.
can please respond where the problem is?
thanks for advance friends.
weblogic-adminHi,
I have been watching responses on this issue (that I have encountered too). I use IE6.0 and this does not happen always. I have seen it happen twice where the Graceful Shutdown and Forced Shutdown links are not highlighted for one managed server whereas for others it is highlighted. The only option then to shutdown/restart this is via the CLI. Please note that other times, these links are high-lighted for the same managed server that did not have these options high-lighted.
So I would like to know when and why this would happen?
Thanks.
Jay -
SOA managed server startup problem
Hi All,
I am facing an issue while starting the SOA Managed Server (soa_server1) using NodeManager.
Backgound:
I have setup a soa domain, started up NM and admin server using NM in solaris environemnt. All runs fine but when I start MS using NM for the first time it throws error. If I start the MS from the admin console it starts fine. The execution steps I have performed-
1. Started NodeManager - using script
2. Shutdown the NodeManager , changed the nodemanager.properties file to update parameter [startScriptEnabled=true] and start it again.
3. Started AS using NM [nmConnect(..) and nmStart('AdminServer')]
4. Enrolled the NM with the current machine [connect(..), nmEnroll(domain_dir, nodemanager_home)]
5. Copied the boot.properties to security/ dir of soa_server1
6. Started MS using NM - Throws error
Does it really mean I have to start the MS through admin console everytime I start MS first time in the machine? (I am working on automation on SOA env where everynight env wipes off and installs the SOA stack from scratch)
The soa-server1.out looks like:
<15-Mar-2012 10:26:41 o'clock GMT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<15-Mar-2012 10:26:41 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.1-b02 from Sun Microsystems Inc.>
<15-Mar-2012 10:26:42 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<15-Mar-2012 10:26:45 o'clock GMT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: Booting as admin server, but servername, soa_server1, does not match the admin server name, AdminServer
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:879)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
at weblogic.Server.main(Server.java:71)
>
<15-Mar-2012 10:26:45 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<15-Mar-2012 10:26:45 o'clock GMT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<15-Mar-2012 10:26:45 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<15-Mar-2012 10:26:45> <FINEST> <NodeManager> <Waiting for the process to die: 20518>
<15-Mar-2012 10:26:45> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<15-Mar-2012 10:26:45> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Please help with your expertise.
Apologies if I have missed any info or posted in wrong forum, if you need more feel free to shout.
Thanks in advance.
Cheers,
BhaskarHi,
I have implemented the above mentioned suggestions. But seems to have no luck. I had
1. Copied startup.properties to ${DOMAIN_HOME}/servers/soa_server1/data/nodemanager
2. Copied the boot.properties to ${DOMAIN_HOME}/servers/soa_server1/security
These did not added any value, so I though of passing the parameters at nmStart() as WLST object;
arg="Arguments=\" -Dweblogic.management.server=localhost:8001\"" (My AS and MS runs on same machine)
prps=makePropertiesObject(arg)
nmStart('soa_server1',props=prps)
This started throwing Boot Identity file not valid.
I changed my way.
1. Connected to Admin Server using WLST
connect (username, password)
2. Start MS
start('soa_server1')
Its working fine now and under NM control. Not sure what more NM demands when starting without AS.
Regards,
Bhaskar -
Admin Server and Managed server startup problem
Hi,
My weblogic server version is 11g and OS is Linux.
When i am trying to start the admin server a frer i created the domain i am getting following exceptions in the server log and server is shutting down.
FPR6 4008000000000000 (f: 0.000000, d: 3.000000e+00)
FPR7 4010000000000000 (f: 0.000000, d: 4.000000e+00)
FPR8 006f007300690078 (f: 6881400.000000, d: 1.379624e-306)
FPR9 0053006f0063006b (f: 6488171.000000, d: 4.228017e-307)
FPR10 00650074004d0075 (f: 5046389.000000, d: 9.346098e-307)
FPR11 0078006500720024 (f: 7471140.000000, d: 2.136208e-306)
FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR13 4068000000000000 (f: 0.000000, d: 1.920000e+02)
FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so
Module_base_address=0800000000003000
Target=2_40_20090409_033254_BHdSMr (AIX 5.3)
CPU=ppc64 (4 logical CPUs) (0x220000000 RAM)
- Stack Backtrace -
/usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so:0x000046F4 [0x00003000 +0x000016F4]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005F7088 [0x005AF000 +0x00048088]
/usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB8228 [0x00FAB000 +0x0000D228]
/usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB884C [0x00FAB000 +0x0000D84C]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EDE08 [0x005AF000 +0x0003EE08]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF600 [0x005AF000 +0x00040600]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF3A8 [0x005AF000 +0x000403A8]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EC1A0 [0x005AF000 +0x0003D1A0]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB5B4 [0x005AF000 +0x0000C5B4]
/usr/java6_64/jre/lib/ppc64/default/libj9prt24.so:0x0064C21C [0x00649000 +0x0000321C]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB4D0 [0x005AF000 +0x0000C4D0]
/usr/java6_64/jre/lib/ppc64/default/libj9thr24.so:0x006375F0 [0x00635000 +0x000025F0]
/usr/lib/libpthreads.a:0x005084F0 [0x00505000 +0x000034F0]
0x00000000
JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
JVMDUMP007I JVM Requesting System dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp'
JVMDUMP010I System dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp
JVMDUMP007I JVM Requesting Snap dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc'
UTE105: Error writing header to tracefile: /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
JVMDUMP010I Snap dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
JVMDUMP007I JVM Requesting Java dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt'
JVMDUMP012E Error in Java dump: /usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt
JVMDUMP013I Processed dump event "gpf", detail "".
After adding "<native-io-enabled>false</native-io-enabled>" in cofig.xml as shown below , i am able to start the admin server.
<server>
<name>AdminServer</name>
<native-io-enabled>false</native-io-enabled>
<listen-port>9595</listen-port>
<listen-address>10.10.15.16</listen-address>
</server>
i did the same thing for managed servers to start the server.
My Question is:
Are we missing any configurations/settings while creating domain?
Is there any other option to start the server without adding <native-io-enabled>false</native-io-enabled>?
Regards,
NagaHi,
my managed server heap size properties are
-XX:PermSize=256m -XX:MaxPermSize=256m -Xms256M -Xmx512M
But the error with Admin server also and we are not providing any heap size properties to admin server. Becuase while creating the domain, i haven't got any
option to set the heap size for Admin server. Am i required to set heap size properties in Admin server by following this path "Summary of Servers >AdminServer->Server start->"Arguements"?
Sorry, i am not able to find activity.log. Can you please tell me the location where i can find acivity.log. If i am not wrong, are you taling about serverOut.log? If that is serverOut.log, please tell me which log you require? is it admin server or managed server? -
9i Enterprise Management Server License problem
9i database standard edition can use Enterprise Managament Server?
Enterprise Management Server can send a alert e-mail then some tablespace have large than the setting size.Questions like this should be addressed to your Oracle sales representative. No one here can give you a reliable answer,which passes into law. In general Management Packs require Enterprise Edition.
Werner -
Fabric manager Server discovery issue
Hi,
I installed Fabric manager server and trying to discover a fabric.
after entering the user and password for the SNMP v3 I am getting SNMP timeout.
the user is configured on the switch and "snmp-server host" was created for the fabric manager server
in order to receive traps (using port 1163).
in the snmp-log i am getting an error about a timeout but no other information besides:
no SNMP/TCP support.
(I am attaching the log...)
does anyone knows what can I do?
Thanks!Looked at your log. you may have firewall in between. There are many connections timeout using TCP/UDP. Talk to you network team. snmpv2/v3 need to be allowed.
2011.07.11 16:21:16 WARN [snmp.tcp] connect timed out
java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Sour
2011.07.11 16:21:16 ERROR [snmp.udp] request sending error: <16:21:11 10.5.125.250, 1836974547 GET u=null >
com.cisco.dcbu.lib.snmp.SnmpException: send PDU: no SNMP/TCP support. connect timed out
at com.cisco.dcbu.lib.snmp.SnmpSession.writePDU(SnmpSession.java:709) -
Oracle OVM 3.1 Manager Server Discovery WARNING Message.
I am getting this warning trying to run [ Discover Servers ] in my OVM Manager. Can someone help figure out what is that I am missing here.
[root@ovmserver1 log]#
[root@ovmserver1 log]# cat ovs-agent.log
[2011-11-23 09:05:09 18587] DEBUG (OVSCommons:123) discover_server: ()
[2011-11-23 09:05:09 18587] WARNING (host:443) cannot get core api version: [Errno 2] No such file or directory: '/usr/lib/python2.4/site-packages/version.properties'
[2011-11-23 09:05:09 18587] DEBUG (OVSCommons:131) discover_server: call completed.
[2011-11-23 09:05:11 18623] DEBUG (OVSCommons:123) discover_hardware: ()
[2011-11-23 09:05:12 18623] DEBUG (OVSCommons:131) discover_hardware: call completed.
[root@ovmserver1 log]#
[root@ovmserver1 log]#
ThanksThis is fine, it will go away once the manager takes ownership of the server...
-
Deployment problem in managed server environment
I have a problem deploying a connector as a .rar-file. The file contains the two deployment
descriptors and a .jar-file containing the connector classes. If I deploy the connector
in a non-managed server (for instance the admin server), there is not a problem at
all. But if I deploy the connector to a server that is managed I get an exception
indicating that the resource manager could not find my javax.resource.spi.ManagedConnectionFactory
implementation.
If I put the .jar-file containing my connector implementation classes into the system
classpath when booting the managed server, the problem is solved. The problem is
that I don't want this .jar-file in the system classpath.
Is this a known bug with any workarounds?
Environment:
Windows 2000
WLS 6.1 SP 3
JDK 1.3.1
Hi Leif,
I believe that there is a patch that resolves this problem. Could you please ask
BEA Support for the 6.1 SP2 patch called CR078437_61sp2.jar. You would need to
put this .jar on the front of your WLS classpath. This patch was created for 6.1
SP2 but I believe should work for SP3 as well.
Deb
>As I wrote:
>WLS 6.1 SP 3
>
>"Jim Gish" <[email protected]> wrote:
>>What version (including service pack number) of Weblogic Server are
>you
>>using?
>>
>>"Leif Kristian Vadseth" <[email protected]> wrote in message
>>news:[email protected]...
>>>
>>> I have a problem deploying a connector as a .rar-file. The file contains
>>the two deployment
>>> descriptors and a .jar-file containing the connector classes. If I
>>deploy
>>the connector
>>> in a non-managed server (for instance the admin server), there is
>not
>>a
>>problem at
>>> all. But if I deploy the connector to a server that is managed I get
>>an
>>exception
>>> indicating that the resource manager could not find my
>>javax.resource.spi.ManagedConnectionFactory
>>> implementation.
>>>
>>> If I put the .jar-file containing my connector implementation classes
>>into
>>the system
>>> classpath when booting the managed server, the problem is solved.
>The
>>problem is
>>> that I don't want this .jar-file in the system classpath.
>>>
>>> Is this a known bug with any workarounds?
>>>
>>> Environment:
>>> Windows 2000
>>> WLS 6.1 SP 3
>>> JDK 1.3.1
>>>
>>
>>
>
-
Problem with Managed Server pointing to a different JDK
Hi,
My Adminserver is pointing to JDK 1.7 which is shown in the startup, but my managed servers are pointing to a different 1.6_43 . We are running into Java version mismatch problem while deploying our application built with jdk 1.7 onto these managed servers . How do i change the version of my managed server ?
Thanks
SamHi Sam,
You generally only have to change it in two places.
DOMAIN_HOME/bin/setDomainEnv.sh and MW_HOME/wlserver_12.1/common/bin/commEnv.sh
See examples below.
If you are on Linux you can quickly fix it. For example:
cd /u01/app/oracle/product/fmw
find . -type f -exec sed -i "s/\/u01\/app\/oracle\/product\/jdk1.6.0_39/\/u01\/app\/oracle\/product\/java_current/g" {} \;
It is a good idea to make a softlink to your Java installation, then you will not have this problem in the future. If you are on Windows you can use a symlink.
Linux example:
ln -s /u01/app/oracle/product/jdk1.7.0_25 /u01/app/oracle/product/java_current
Windows example:
mklink /d D:\oracle\product\java_current D:\oracle\product\jrockit-jdk1.6.0_26-R28.1.4-4.0.1
setDomainEnv.sh
/u01/app/oracle/domains/eksudv/bin/setDomainEnv.sh
if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
JAVA_HOME="${BEA_JAVA_HOME}"
export JAVA_HOME
else
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
JAVA_HOME="${SUN_JAVA_HOME}"
export JAVA_HOME
else
JAVA_VENDOR="Sun"
export JAVA_VENDOR
JAVA_HOME="/u01/app/oracle/product/java_current"
export JAVA_HOME
fi
fi
commEnv.sh
/u01/app/oracle/product/fmw/wlserver_12.1/common/bin/commEnv.sh
# 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="/u01/app/oracle/product/java_current"
# Set up JAVA VENDOR, possible values are
#Oracle, HP, IBM, Sun ...
JAVA_VENDOR=Sun
# PRODUCTION_MODE, default to the development mode
PRODUCTION_MODE=""
fi
Regards Peter
http://theheat.dk -
Problem with JMS migration when using Ctrl+C to stop the managed server in cluster
Hi,
I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
uses JMS as a asynchrous communication. We have MDB which listens to these JMS
messages.
If something is being processed on Managed Server 1 and while the request is in
process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
After this, i go to admin console and migrate teh JTA and JMS. After this, i am
expecting other running Managed Server should restart the incomplete transaction.
But this is not happening. The Managed Serve2 doesn't process the requst.
But when i restart teh MAnaged SErver 1 again, it takes up the same request and
processes it.
Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
Please note that the same thing is working fine when i stop the server using Admin
console(Normal shutdown OR forced shutdown).
Any comments in this regards are apprecciated.
Thanks,
Naresh
Hi,
I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
uses JMS as a asynchrous communication. We have MDB which listens to these JMS
messages.
If something is being processed on Managed Server 1 and while the request is in
process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
After this, i go to admin console and migrate teh JTA and JMS. After this, i am
expecting other running Managed Server should restart the incomplete transaction.
But this is not happening. The Managed Serve2 doesn't process the requst.
But when i restart teh MAnaged SErver 1 again, it takes up the same request and
processes it.
Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
Please note that the same thing is working fine when i stop the server using Admin
console(Normal shutdown OR forced shutdown).
Any comments in this regards are apprecciated.
Thanks,
Naresh
-
Problem installing Oracle Identity Manager Server 9.1
Hello,
I try to install oracle identity Manager Server 9.1, but I'm having a problem.
Oracle identity manager 9.03 is already installed with jboss-4.0.3SP1 and j2sdk1.4.2_15
and oracle 10.2.0
So I follow these steps to clean out the db:
1. Drop tablespace: drop tablespace oimtbs including contents;
2. Drop user: drop user oimuser cascade;
and ran prepare_xl_db.bat as instructed. No errors in the log.
I ran the DiagonasticDashboard : the db setup was fine.
When I ran the installer "setup_server.exe", i haved this message :
Folowing Error occured during schema creation
Error encountered while loading database script
E:\OIM_Install\OIM9100\installServer\Xellerate/db/oracle/xell.sql
Please contact your DBA!
maximum key length (1478) exceeded
Does anybody have any idea what this error is about ?
Thanks.Index IDX_LKV_LKV_ENCODED on Table LKV (Column :- LKV_ENCODED - VARCHAR2(3000)) is failing on 2k block size. Though all the Indexes are working fine with the 4k block size.
But OIM Dev team recommends to create the 8k block size for the Index storage.
Because the blocksize affects the number of keys within each index node, it follows that the blocksize will have an effect on the structure of the index tree. All else being equal, large blocksizes will have more keys, resulting in a flatter index than the same index created in a 2k tablespace. A large blocksize will also reduce the number of consistent gets during index access, improving performance for scattered reads access.
HOW TO CREATE THE INDEXES IN LARGER BLOCKSIZE TABLESPACE
In the existing database:-
Create a tablespace with the 8k blocksize, For Example
First,
Set the system cache size for that particular db block size
sql> alter system set db_8k_cache_size=100M;
sql> CREATE TABLESPACE db_8k_tablespace DATAFILE 'C:/oracle/product/10.2.0/oradata/8k_file.dbf' SIZE 100M BLOCKSIZE 8192;
Then
Reorganize the Index using command:-
sql> Alter Index <Index_Name> Rebuild tablespace <Tablespace_Name>
Regards,
Neeraj Goel -
I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
I have to remove the management installation first. And that's not gonna happen.
I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
Control Panel. And this can NOT be the most healthy way of getting through the setup.
I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
Any of you have tips as to how I can get rid of the agents more gracefully?Hi
Thanks for the replay guys!
None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
days.
Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment. -
Problems starting Managed Server on WL6.0 Solaris
Hi,
I installed a WL6.0 on Solaris 8. Everythings works fine.
I careated a Domain and an additional Server wich is located at a
different machine. As is start this managed server on the other machine
it complains with the following error message:
<Aug 30, 2001 12:41:18 PM CEST> <Info> <Security> <Getting boot password
from user.>
Enter password to boot WebLogic server:weblogic
Starting WebLogic Server ....
Connecting to http://sol23:7001...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: paros not
found
weblogic.management.configuration.ConfigurationException: paros not
found
at
weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
at weblogic.management.Admin.initialize(Admin.java:287)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
In the access-Log of the Admin-Server the following line appears
my IP - - [30/Aug/2001:12:41:13 +0200] "GET
/wl_management_internal2/Bootstrap HTTP/1.0" 404 0
So my question: Where does this "wl_management_internal2" Application
come from?
Do I have to install some special things when I start an Admin-Server?
thanks
Falko Zurell . Webmaster
Pixelpark AG . http://www.pixelpark.com
Rotherstrasse 8 . 10245 Berlin . Germany
phone: + 49 30 5058 - 1963 . fax: -1600Hi Falko,
This is not a problem. when you want to add a new managed server to the
admin server, you need to use weblogic console to create that server in the
admin server first, then start the managed server with that name to connect
to the admin server. That is like you have to let the admin server know
there is such a server, then let it join to the Admin server. you can do
that by using the admin console, from left panel, click on Servers -->
"Create a new server" and name it to be "paros", specify the port and IP.
and hit "create". then start the managed server.
Thanks
Yu
"Falko Zurell" <[email protected]> wrote in message
news:[email protected]...
Hi,
I installed a WL6.0 on Solaris 8. Everythings works fine.
I careated a Domain and an additional Server wich is located at a
different machine. As is start this managed server on the other machine
it complains with the following error message:
<Aug 30, 2001 12:41:18 PM CEST> <Info> <Security> <Getting boot password
from user.>
Enter password to boot WebLogic server:weblogic
Starting WebLogic Server ....
Connecting to http://sol23:7001...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: paros not
found
weblogic.management.configuration.ConfigurationException: paros not
found
at
weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
at weblogic.management.Admin.initialize(Admin.java:287)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
>
In the access-Log of the Admin-Server the following line appears
my IP - - [30/Aug/2001:12:41:13 +0200] "GET
/wl_management_internal2/Bootstrap HTTP/1.0" 404 0
So my question: Where does this "wl_management_internal2" Application
come from?
Do I have to install some special things when I start an Admin-Server?
thanks
Falko Zurell . Webmaster
Pixelpark AG . http://www.pixelpark.com
Rotherstrasse 8 . 10245 Berlin . Germany
phone: + 49 30 5058 - 1963 . fax: -1600 -
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 .......
Maybe you are looking for
-
I'm currently on Sky HD but I'm cancelling it as the majority of programmes I watch are on freeview. I signed up online for BT Sports back in May but I've changed my mind & don't wish to go ahead with it anymore. How do you cancel this before the sea
-
Default profit center for banks account
Friends, Can we get the profit center as default in the bank account ? How ?Please tell me the config steps! Regards HK
-
I need to display only subtotals in the ALV and not the details.
Hi, I have an ALV report . I have totals and subtotals in the same with details. My requirement is to have only subtotals and totals in my output. I do not want the details of all the items. I want only the subtotals row. Pls advice on this.
-
Hi! For some of our users whenever they export Viewer reports to Excel, they loose the filter options that available in the original Discoverer Viewer reports. However, for others such as myself this works fine. Is there a configuaration option somew
-
Router use for Ethernet hand off
Hello everyone, we are trying to squeeze every ounce of life out of our hardware. Adding bandwidth to our network to accommodate social networking traffic. We are about to order a 200 meg Ethernet circuit with a T3 backup. We have two 3662s. My quest