GeeCON Prague 2014*
The moose likes BEA/Weblogic and the fly likes Help Please...unable to start the managed server Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Help Please...unable to start the managed server" Watch "Help Please...unable to start the managed server" New topic
Author

Help Please...unable to start the managed server

deepa karkala
Ranch Hand

Joined: Jan 29, 2003
Posts: 62
Hi everyone,
When i ping my admin server, it is responding indicating that admin server is running :

C:\bea\wlserver6.1\config\mydomain>java -classpath c:\bea\wlserver6.1\lib\weblo
gic.jar weblogic.Admin -url T3://164.164.0.204:7001 PING
Sending 1 ping of 100 bytes.
RTT = ~40 milliseconds, or ~40 milliseconds/packet


But when i run weblogic.Admin utility to find out the available managed servers, i get the error:

C:\bea\wlserver6.1\config\mydomain>java -classpath c:\bea\wlserver6.1\lib\weblo
gic.jar weblogic.Admin -url 164.164.0.204:7001 -username system -password weblogic
-GET -type Server

javax.naming.CommunicationException: javax.naming.CommunicationException [Root e
xception is weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
Could not find MBean home using provided arguments:
java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: Failed t
o contact t3://164.164.0.204:7001.
Is there a server running at this address?



Finally i am unable to start the managed server (correctly given admin username and admin password)
and get the Security error :

Starting WebLogic Server ....
Connecting to http://164.164.0.204:7001...
<Nov 24, 2003 11:01:44 AM EST> <Error> <Configuration Management> <Error connect
ing to admin server and initializing admin home: admin URL: t3://164.164.0.204:700
1
javax.naming.AuthenticationException. Root exception is java.lang.SecurityExcep
tion: attempting to add an object which is not an instance of java.security.Prin
cipal to a Subject's Principal Set
at javax.security.auth.Subject$SecureSet.add(Subject.java:1098)
at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(Boot
ServicesStub.java:72)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesSt
ub.java:80)
at weblogic.security.acl.internal.Security.authenticate(Security.java:10
8)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
xtFactoryDelegate.java:461)

I would highly appreciate if any one help me on this issue.
Thanks.
george kenya
Greenhorn

Joined: Nov 24, 2003
Posts: 1
in fact i had posted this question a few days ago but that time i had not observed the input which i have given in today's question. (sorry).
deepa karkala
Ranch Hand

Joined: Jan 29, 2003
Posts: 62
Hi george, did you face the same problem and did you get any solution for this issue ?
thanks
deepa karkala
Ranch Hand

Joined: Jan 29, 2003
Posts: 62
Hi george, did you face the same problem and did you get any solution for this issue ?
thanks
Ashish Pagare
Ranch Hand

Joined: Oct 14, 2003
Posts: 101
What does admin and managed server logs says? I guess there must be something there, which can be of some help.
Are both the servers running on same box?
deepa karkala
Ranch Hand

Joined: Jan 29, 2003
Posts: 62
Hi Ashish,
yes, i am running both servers on same box (windows XP).
The managed server log says :
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException: attempting to add an object which is not an instance of java.security.Principal to a Subject's Principal Set
at javax.security.auth.Subject$SecureSet.add(Subject.java:1098)
at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(BootServicesStub.java:72)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:80)
at weblogic.security.acl.internal.Security.authenticate(Security.java:108)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:461)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:316)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:288)
at weblogic.jndi.Environment.getContext(Environment.java:155)
at weblogic.jndi.Environment.getInitialContext(Environment.java:138)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:951)
at weblogic.management.Admin.start(Admin.java:342)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:367)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
####
The admin log says :
java.io.InvalidClassException: javax.security.auth.Subject; Local class not compatible: stream classdesc serialVersionUID=-6842430708383393570 local class serialVersionUID=-8308522755600156056
at java.io.ObjectStreamClass.validateLocalClass(ObjectStreamClass.java:523)
at java.io.ObjectStreamClass.setClass(ObjectStreamClass.java:567)
at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:936)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at weblogic.rjvm.ClassTableEntry.readExternal(ClassTableEntry.java:29)
at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:581)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:638)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception creating response stream ] - with nested exception:
[java.io.InvalidClassException: javax.security.auth.Subject; Local class not compatible: stream classdesc serialVersionUID=-6842430708383393570 local class serialVersionUID=-8308522755600156056]
at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:581)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:638)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
I am unable to figure it out.
thank you.
deepa karkala
Ranch Hand

Joined: Jan 29, 2003
Posts: 62
Ashish, here is the latest error message from managed server log :

####<Nov 24, 2003 1:12:26 PM EST> <Emergency> <Server> <temp1> <appManaged> <main> <> <> <000000> <Unable to initialize the server: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: admin URL: t3://164.164.0.204:7001 - with nested exception:
[javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: attempting to add an object which is not an instance of java.security.Principal to a Subject's Principal Set]]
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException: attempting to add an object which is not an instance of java.security.Principal to a Subject's Principal Set
at javax.security.auth.Subject$SecureSet.add(Subject.java:1098)
at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(BootServicesStub.java:72)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:80)
at weblogic.security.acl.internal.Security.authenticate(Security.java:108)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:461)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:316)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:288)
at weblogic.jndi.Environment.getContext(Environment.java:155)
at weblogic.jndi.Environment.getInitialContext(Environment.java:138)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:951)
at weblogic.management.Admin.start(Admin.java:342)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:367)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: admin URL: t3://164.164.0.204:7001 - with nested exception:
[javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: attempting to add an object which is not an instance of java.security.Principal to a Subject's Principal Set]]
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:956)
at weblogic.management.Admin.start(Admin.java:342)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:367)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
'>
BTW, I am connected to the office network and obtained 164.164.0.204 as IP for my machine for my office DHCP server. This IP address i have assigned as listen address to my admin server. port is 7001.
For managed server, i assigned 127.0.0.1 as listen address to my managed server with port as 7001. ( i could not assign any virtual IP address because multihoming is not working in my windows XP professional).
Thank you.
 
GeeCON Prague 2014
 
subject: Help Please...unable to start the managed server