Acl.NotOwnerException when starting managed server
I have installed the evaluation version of WL 6.0 and sp1 on Solaris and can run
applications
using the administration server.
I created a new server with the WL console, and then tried to start it as a managed
server,
but I get a java.security.acl.notOwnerException. I start the admin server and
the managed
server using the same user account. When prompted for the boot password, I use
the same
password to start each server.
Is there anything I can change in my setup to get around this problem?
This is the trace of the error:
startManagedWebLogic.sh myserver2 http://localhost:7501
p1= myserver2
p2= http://localhost:7501
LD_LIBRARY_PATH=/private/weblogic/weblogic6.0/wlserver6.0/lib/solaris
<Mar 29, 2001 2:31:16 PM PST> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:systempswd
Starting WebLogic Server ....
Connecting to http://localhost:7501...
log file: /private/weblogic/weblogic6.0/wlserver6.0/./myserver2.log
<Mar 29, 2001 2:31:26 PM PST> <Info> <Logging> <Only log messages of severity
"Error" or worse will be displayed in this window. This can be changed at Admin
Console> mydomain> Servers> myserver2> Logging> General> Stdout severity threshold>
<Mar 29, 2001 2:31:26 PM PST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Thanks in advance for any help.
Joan
Hi Joan
Go to the Managedserver Confiuration and give the Correct listen Port and SSL.I hope this will help you.
Nagesh Rao
Joan Silverman wrote:
I have installed the evaluation version of WL 6.0 and sp1 on Solaris and can run
applications
using the administration server.
I created a new server with the WL console, and then tried to start it as a managed
server,
but I get a java.security.acl.notOwnerException. I start the admin server and
the managed
server using the same user account. When prompted for the boot password, I use
the same
password to start each server.
Is there anything I can change in my setup to get around this problem?
This is the trace of the error:
startManagedWebLogic.sh myserver2 http://localhost:7501
p1= myserver2
p2= http://localhost:7501
LD_LIBRARY_PATH=/private/weblogic/weblogic6.0/wlserver6.0/lib/solaris
<Mar 29, 2001 2:31:16 PM PST> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:systempswd
Starting WebLogic Server ....
Connecting to http://localhost:7501...
log file: /private/weblogic/weblogic6.0/wlserver6.0/./myserver2.log
<Mar 29, 2001 2:31:26 PM PST> <Info> <Logging> <Only log messages of severity
"Error" or worse will be displayed in this window. This can be changed at Admin
Console> mydomain> Servers> myserver2> Logging> General> Stdout severity threshold>
<Mar 29, 2001 2:31:26 PM PST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Thanks in advance for any help.
Joan
Similar Messages
-
Fatal initialization exception occurs when starting Managed Server
Hi all,
First I configured a Adminisistration server and started it. After that I added
a another server as ManagedServer.These two points to the same Weblogic server.
When I try to start Managed server by running the script, it gave me following
error. _______________________________
<Jun 25, 2001 5:25:11 PM GMT+06:00> <Emergency> <Server> <Unable to initialize
the server: 'Fatal initialization exception Throwable: java.lang.IllegalAccessError:
java.security.acl.NotOwnerException java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91) at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183) at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116) at
weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:444)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:287)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:259)
at weblogic.jndi.Environment.getContext(Environment.java:135) at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:891) at weblogic.management.Admin.start(Admin.java:305)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35) ______________________________________________
I suspect reason for this might be weblogic.policy file. There you need to edit
some lines replacing the location of the directory in which you installed WebLogic
Server. I did this but still error occurs.
Do u have any idea why above error occurs and if it is due to the weblogic.policy
file entry please tell me how it correctly done.
I am using WL60(sp2)in Win NT,
My installed dir: E:\bea\wlserver6.0\
Thanks NalikaHi
(It was me and Berit that sent the original question).
After some experimentation we saw that the managed server did get
some configuration from the admin server, so the problem was in
there somewhere.
I had added an (empty) cluster and machine to the admin server, just
to test adding. When I removed them everything worked fine afterward.
So it was some kind of configuration error from our side, but we never
did find out what it was.
I guess the lesson is to only define things when you really need them :-)
Regards
Mikael
Timothy Fry wrote:
We're getting the same problem, but on Solaris 2.7.
Did you get a solution from bea yet?
Tim
"Berit Bylund" <[email protected]> wrote in message
news:[email protected]..
Hello
We are trying to start a managed server (under the examples
domain, NT 4.0, WLS 6.0 Beta 2)
We start the managed server with the parameter
-Dweblogic.management.server=http://127.0.0.1:7001 -
Error when starting managed server
Hi,
I have a setup with a admin-server and a managed server. Everything
worked fine, until one day, an exception started occurring in the logs
when starting the managed server.
The setup is:
- WLS6.1SP2
- Solaris 8, SPARC
The exception is:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
I've taken a look in the admin-servers JNDI-tree, and it is correct,
it only has "weblogic.transaction.resources", and is missing the
unresolved "atserver1" part.
Why is it suddenly referencing this, and what can/should I do about
it.
The server seems to be running even with this exception.
Full stack trace at managed server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '81
52308822087678327S:192.168.26.196:[7551,7551,7552,7552,7551,7552,-1]:atdomain:atserver1',
oid: '9', implementation: 'weblogic.jndi.interna
l.RootNamingNode@6fb3d6''
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:887)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy6.list(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:153)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(ServerCoordinatorDescriptor.java:1008)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoordinatorDescriptor.java:944)
at weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCoordinatorDescriptor.java:936)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Full server stack trace in admin server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid: '-60698
70668923812357S:192.168.26.196:[7441,7441,7442,7442,7441,7442,-1]:atdomain:atadmin',
oid: '267', implementation: 'weblogic.management.inte
rnal.AdminMBeanHomeImpl@46cc9c''
javax.management.InstanceNotFoundException:
atdomain:Location=atserver1,Name=atserver1,Type=ServerRuntime
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:116)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help appreciated!
Regards, PerHi Per
I have problems in creating managed server in the default mydomain .Do i need
to configure a new machine if the managed server and admin server are going to be
in the same machine.
I created a new machine that has the following parameters
listen address :localhost
Listen port :7001
As the next step i created a server with the machine name pointing to new one, when
i tried to start this as a managed server it gives an Error
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException: java
.security.acl.NotOwnerException - with nested exception:
[java.lang.IllegalAccessError: java.security.acl.NotOwnerException]
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:12
5)
could you please help me on creating a managed server
thanks in advance
karthik
[email protected] (Per Olesen) wrote:
Hi,
I have a setup with a admin-server and a managed server. Everything
worked fine, until one day, an exception started occurring in the logs
when starting the managed server.
The setup is:
- WLS6.1SP2
- Solaris 8, SPARC
The exception is:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
I've taken a look in the admin-servers JNDI-tree, and it is correct,
it only has "weblogic.transaction.resources", and is missing the
unresolved "atserver1" part.
Why is it suddenly referencing this, and what can/should I do about
it.
The server seems to be running even with this exception.
Full stack trace at managed server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '81
52308822087678327S:192.168.26.196:[7551,7551,7552,7552,7551,7552,-1]:atdomain:atserver1',
oid: '9', implementation: 'weblogic.jndi.interna
l.RootNamingNode@6fb3d6''
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:887)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy6.list(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:153)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(ServerCoordinatorDescriptor.java:1008)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoordinatorDescriptor.java:944)
at weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCoordinatorDescriptor.java:936)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Full server stack trace in admin server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid: '-60698
70668923812357S:192.168.26.196:[7441,7441,7442,7442,7441,7442,-1]:atdomain:atadmin',
oid: '267', implementation: 'weblogic.management.inte
rnal.AdminMBeanHomeImpl@46cc9c''
javax.management.InstanceNotFoundException:
atdomain:Location=atserver1,Name=atserver1,Type=ServerRuntime
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:116)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help appreciated!
Regards, Per -
ClassNotFoundException When Starting Managed Server with NodeManager
Hi Experts,
ENV:
Weblogic Server 10.3.3
Webcenter 11.1.1.3
My managed server can be brought up correctly by stopManagedWebLogic.sh <ManagedServerName>. But when trying to start them up, app on that server can not run correctly, and node manager log complained that below classes are not found:
oracle.jrf.wls.JRFStartup
oracle.security.jps.wls.JpsWlsStartupClass
oracle.core.ojdl.weblogic.ODLConfiguration
oracle.jrf.AppContextStartup
oracle.ias.cache.Startup
oracle.dms.wls.DMSStartup
My Nodemanager is setup following instructions in OBE.Administering Managed Servers by Using the Node Manager(http://www.oracle.com/technology/obe/fusion_middleware/wls103/installconfig/admin_mngd_srvr/admin_ms_using_nm.htm#t4). Output javaclaspath of setWLSEnv.sh has been copy&pasted to admin console->server->..->Server start->classpath
Thanks,
ToddTrying setting the property StartScriptEnabled=true instead of false.
You can change this in the nodemanager.properties file (usually located in the directory <middleware-home>/wlserver_10.3/common/nodemanager)
The classes are set in the startscripts, such as setDomainEnv, which is called by startWebLogic.
The latter script is set by default in the nodemanager.properties file, through the property StartScriptName=startWebLogic.cmd. -
Error when starting managed server Message Too Long
Hi,
I'm trying to setup clustering with WLS6.1sp2.
I use the jdk include with wls
2 servers in the cluster OS=AIX
1 Adminserver running on Solaris 8
When I start a managed server on one of the clustered machines
I see the following error.
Starting Cluster Service ....
<Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread listening
on port 7001, ip address 10.160.3.74>
<Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast message:
java.io.IOException: Message too long
java.io.IOException: Message too long
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
at java.net.DatagramSocket.send(DatagramSocket.java:341)
at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
Code))
at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
>
<Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast messages
(cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
<Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic Managed
Server "s01ap007" for domain "axa" running in Production Mode>
Also deploying doesn't seem to succeed could this be coused by this error
I hope someone can help me.
Best regards,
Peter Van der Goten
Because I found the answer via Mr. yunyee who also had this problem on an AIX machine
I will post this also here.
The problem was that the upd_sendspace variable was set on
a mutch to low value (9126) or something in this range
It had to be set on 32769.
this was done with no -o udp_sendspace=32769
Best regards,
Peter
"Peter Van der Goten" <[email protected]> wrote:
>
>Hi,
>I'm trying to setup clustering with WLS6.1sp2.
>I use the jdk include with wls
>2 servers in the cluster OS=AIX
>1 Adminserver running on Solaris 8
>
>When I start a managed server on one of the clustered machines
>I see the following error.
>Starting Cluster Service ....
><Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread
>listening
>on port 7001, ip address 10.160.3.74>
><Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast
>message:
>java.io.IOException: Message too long
>java.io.IOException: Message too long
> at java.net.PlainDatagramSocketImpl.send(Native Method)
> at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
> at java.net.DatagramSocket.send(DatagramSocket.java:341)
> at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
> at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
> at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
>Code))
> at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
> at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
> at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
> at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
> at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
> at weblogic.Server.main(Server.java:35)
>>
><Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast
>messages
>(cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
><Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic
>Managed
>Server "s01ap007" for domain "axa" running in Production Mode>
>
>Also deploying doesn't seem to succeed could this be coused by this error
>
>I hope someone can help me.
>Best regards,
>Peter Van der Goten
>
-
Getting error when starting managed server from administration server
When i start one of my managed server in the cluster i get the following error
The WebLogic Server did not start up properly.
Exception raised: java.lang.ArrayIndexOutOfBoundsException
java.lang.ArrayIndexOutOfBoundsException
at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
at com.bea.utils.misc.Process.validate(Process.java:1231)
at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:278)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:335)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Please tell if somebody know it
Do you have any other products from BEA other than WLS?
I can't seem to find the following (com/bea/utils/misc) from WLS source
line ?
Kumar
Ritesh Kapoor wrote:
> When i start one of my managed server in the cluster i get the following error
> The WebLogic Server did not start up properly.
> Exception raised: java.lang.ArrayIndexOutOfBoundsException
> java.lang.ArrayIndexOutOfBoundsException
> at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
> at com.bea.utils.misc.Process.validate(Process.java:1231)
> at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
> at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
> at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:278)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:335)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
> at weblogic.Server.main(Server.java:35)
> Reason: Fatal initialization exception
>
> Please tell if somebody know it
>
>
-
Authentication for user weblogic denied problem when starting managed serve
Hi All,
I have a strange situation here. I installed WLS and SOA and BAM servers. Initially I could start both WLS and SOA.
Later I changed some files (possibly startManagedWebLogic.sh or deleted soa_server1/data/ldap/ or AdminServer/security/boot.properties), but later I remember I changed them back. I am now seeing that my WLS is starting up fine, but SOA is not. I am always getting the error:
<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
>
I tried to go to admin console to change/verify the password for weblogic user, and then put plaintext password in AdminServer/security/boot.properties, then restart Adminserver. But I still cannot start SOA server.
Could you please let me know how to resolve this issue? I do want to save my environment at this point. Many thanks.Hi,
My understanding is admin user server is coming up fine but when you try to bring the soa_server1(managed instance) is not coming up due the below mentioned exception.
If not please correct me.
I have a few query, please give me comment on this.
1) Admin and managed instances are running on the same box or different
2) Did you try to reset the password from console or using weblogic.security command
3) Did you cleared the soa_server1 temp directory(server/soa_server1/*)
Solution-1 (If Domain running on different box)
=============================
1) Copy the DefaultAuthenticatorInit.ldift file from Domain_dir/Security/ to Remote machine - Domain_dir/Security/
Note- Remote machine - take a backup of DefaultAuthenticatorInit file.
2) Remote machine- rename or take a backup of ldap directory and boot.properties file
/servers/soa_server1/ldap
/servers/soa_server1/security/boot.properties.
3) Now try to brought up the soa_server1.It will prompt you the username and password.
Please let me know.
Thanks,
Rajkumar -
Server start arguments ignored when starting managed server
Hi
We have configured a bunch of arguments for the managed server through the Admin Console in the Server->Start Arguments
However those arguments are not picked up when we are starting the managed server.
We are using a shell script to start the managed server using the weblogic.Admin class functionality.
If the arguments are set in the JAVA_OPTIONS of setDomainEnv.sh, then they are picked up when starting the managed server.
The nodemanager is configured with startScriptEnabled=true and startscript set to startWeblogic.sh.
This is the scenario in Weblogic 10.0.0.
Can anybody please explain why the arguments are not picked up?
We tried the same arguments in Weblogic 10.2 and the arguments are picked up even if they are not configured in setDomainEnv.sh
Is the difference in behavior because of the difference in versions?
Edited by: user1030647 on Aug 29, 2010 12:26 AMThanks Jay for the immediate responses.
The thing I am worried about is it seems the behavior in Weblogic 10.0.2 seems to be in consistent with the behavior in Weblogic 10.0.0.
In Weblogic 10.0.2, even if the JAVA_OPTIONS in setDomainEnv.sh do not include the paramaters that are set in "Server Start->Arguments", when starting the managed servers, they are picked up as can be seen from the managed server log files.
However, in Weblogic 10.0.0, it seems that these options are not picked up when they are configured in "Server Start->Arguments". Only when they are configured in setDomainEnv.sh are they picked up.
Do you have any info which points to this discrepancy? -
HANDSHAKE_FAILURE problem when starting managed server via NOdeManager
hi all, i am trying to start a managed server using nodeManager, but i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command start for
server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
to negotiate an acceptable set of security parameters.. Please ensure that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try to start
the managed server via adminserver console, i got the exception mentioned in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver, and
nodemanager is supposed to run at localhost:5555 (and indeed it does, because
ihave started it successfully).
thanx in advance and regards marcoMarco.
Sorry, this is not a solution to your problem but i am trying to solve the same
problem for a week now.
I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
same error. I know that the default certificate installed provides a hostname
verification of weblogic.com. I turned the hostname verification off, i put in
the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
error when starting the managed server. I went ahead and created my own certificate
for machine called mallik, created my own passphrase, created a new keystore,
made the admin server view the keystore, used the same certificate for both the
admin server and the node manager. It still fails with the same error. I went
ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
totally confused now what needs to be done.
My nodeManger.hosts looks like this:
mallik 10.100.10.130
managedServer1 10.100.10.130
managedServer2 10.100.10.13
Below is the startNodeManager.cmd.
@echo off
@rem *************************************************************************
@rem This script can be used to start the WebLogic NodeManager
@rem
@rem This script sets the following variables before starting the NodeManager:
@rem
@rem WL_HOME - The root directory of your WebLogic installation.
@rem NODEMGR_HOME - The home directory for this NodeManager instance.
@rem JAVA_HOME - Location of the version of Java used to start WebLogic
@rem Server. This variable must point to the root directory of
@rem a JDK installation and will be set for you by the
@rem installer. See the WebLogic platform support page
@rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
list of
@rem supported JVMs on Windows NT.
@rem PATH - Adds the JDK and WebLogic directories to the system path.
@rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
@rem JAVA_OPTIONS - Java command-line options for running the server. (These
@rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
@rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
@rem -client, etc.)
@rem MEM_ARGS - The variable to override the standard memory arguments
@rem passed to java
@rem
@rem *************************************************************************
SETLOCAL
set WL_HOME=C:\bea7.0\weblogic700
set NODEMGR_HOME=%WL_HOME%\common\nodemanager
set JAVA_HOME=C:\bea7.0\jdk131_06
Call %WL_HOME%\common\bin\commEnv.cmd
@rem If NODEMGR_HOME does not exist, create it
:checkNodeManagerHome
if exist %NODEMGR_HOME% goto checkJava
echo.
echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
mkdir %NODEMGR_HOME%
@rem Check that java is where we expect it to be
:checkJava
if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
echo The JDK wasn't found in directory %JAVA_HOME%.
echo Please edit this script so that the JAVA_HOME
echo variable points to the location of your JDK.
goto finish
:runNodeManager
if not "%JAVA_VM%" == "" goto noResetJavaVM
rem set JAVA_VM=-hotspot
set JAVA_VM=%COMM_VM%
:noResetJavaVM
if not "%MEM_ARGS%" == "" goto noResetMemArgs
set MEM_ARGS=-Xms32m -Xmx200m
:noResetMemArgs
@echo on
set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
cd %NODEMGR_HOME%
#"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
"-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
"-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
"-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
"-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
goto finish
:finish
ENDLOCAL
I would appreciate if anybody can help me.
Mallik.
"Marco" <[email protected]> wrote:
>
hi all, i am trying to start a managed server using nodeManager, but
i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command
start for
server managedServer via the Node Manager - reason: [CommandInvoker:
Failed to
send command: 'online to server 'managedServer' to NodeManager at host:
'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
was unable
to negotiate an acceptable set of security parameters.. Please ensure
that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
-Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost
and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try
to start
the managed server via adminserver console, i got the exception mentioned
in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver,
and
nodemanager is supposed to run at localhost:5555 (and indeed it does,
because
ihave started it successfully).
thanx in advance and regards marco -
InvalidClassException when starting managed server
Hi,
I just created a new managed server from the admin console, but it won't start. Regardless whether I try to start it via the admin console (using NodeManager) or a start script (startManagedWebLogic.sh), it fails with a complaint about an InvalidClassException. For example:
<24.05.2006 15:07:57 CEST> <Info> <NodeManager@localhost:5555> <Starting Server mydomain::VemaQuickServer ...>
<24.05.2006 15:07:57 CEST> <Info> <NodeManager@localhost:5555> <BaseProcessControl: saving process id of WebLogic Managed server 'VemaQuickServer', pid: 21452>
<24.05.2006 15.08 Uhr CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_06-b05 from Sun Microsystems Inc.>
<24.05.2006 15.08 Uhr CEST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://192.168.1.202:9001 to check if there exists a running admin server at this URL.>
<24.05.2006 15.08 Uhr CEST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<24.05.2006 15.08 Uhr CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 >
<24.05.2006 15.08 Uhr CEST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://192.168.1.202:9001 to retrieve the initial configuration.>
<24.05.2006 15.08 Uhr CEST> <Error> <Configuration Management> <BEA-150001> <An error occurred while connecting to the admin server to bootstrap through URL: http://192.168.1.202:9001/wl_management_internal2/Bootstrap, user: system
java.io.InvalidClassException: javax.management.ObjectName; local class incompatible: stream classdesc serialVersionUID = -5467795090068647408, local class serialVersionUID = 1081892073854801359
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:519)>
Any ideas what is going on ?
Regards
HeikoWLS 8.1 does not support JDK 5.
You will need to upgrade to WLS 9.x to use JDK 5.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/ -
JMX error when starting managed server
One of our production managed servers has suddenly encountered an error when try to start it via the Admin console.
No changes have been made recently that I am aware of. The port number for the node manager is available and the log files states that it has started successfully.
Message: The requested operation is not exposed through JMX in this context: start
Stack Trace: java.lang.RuntimeException: The requested operation is not exposed through JMX in this context: start at weblogic.management.jmx.ExceptionMapper.matchJMXException(ExceptionMapper.java:87) at weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:547) at weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:380) at $Proxy105.start(Unknown Source) at com.bea.console.actions.core.server.lifecycle.Lifecycle.finish(Lifecycle.java:719) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64) at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:184) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:261) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133) at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106) at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225) at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199) at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47) at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: javax.management.ReflectionException at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:205) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222) at javax.management.remote.rmi.RMIConnectionImpl_1033_WLStub.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:993) at weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:544) ... 92 more Caused by: java.lang.NoSuchMethodException: start() for com.bea:Name=cieaeq03-z1,Type=ServerLifeCycleRuntime at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:395) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:349) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447) at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:268) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447) at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447) at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:444) at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:323) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:663) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:661) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:654) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174) ... 96 moreHi,
Am getting the error while starting the manage servers.The weblogic server is 10g.If anyone has any details please share, Appreciate any help.
Error Details :
The requested operation is not exposed through JMX in this context: start
Stack Trace: java.lang.RuntimeException: The requested operation is not exposed through JMX in this context: start at weblogic.management.jmx.ExceptionMapper.matchJMXException(ExceptionMapper.java:87) at weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:547) at weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:380) at $Proxy104.start(Unknown Source) at com.bea.console.actions.core.server.lifecycle.Lifecycle.finish(Lifecycle.java:719) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64) at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:184) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:261) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133) at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106) at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225) at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199) at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47) at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: javax.management.ReflectionException at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:205) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222) at javax.management.remote.rmi.RMIConnectionImpl_1033_WLStub.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:993) at weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:544) ... 92 more Caused by: java.lang.NoSuchMethodException: start() for com.bea:Name=GOLF_Server1,Type=ServerLifeCycleRuntime at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:395) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:349) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447) at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:268) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447) at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447) at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:444) at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:323) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:663) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:661) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:654) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174) ... 96 more
帖子经 user8858768编辑过
Thanks,
Smita
帖子经 user8858768编辑过 -
Security exception when trying to start Managed Server
Hi all,
First I configured a Adminisistration server and started it. After that I added
a another server as ManagedServer.These two points to the same Weblogic server.
When I try to start Managed server by running the script, it gave me following
error.
<Jun 25, 2001 5:25:11 PM GMT+06:00> <Emergency> <Server> <Unable to initialize
the server: 'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:444)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:287)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:259)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:891)
at weblogic.management.Admin.start(Admin.java:305)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
I suspect reason for this might be weblogic.policy file. There you need to edit
some lines replacing the location of the directory in which you installed WebLogic
Server. I did this but still error occurs.
Do u have any idea why above error occurs and if it is due to the weblogic.policy
file entry please tell me how it correctly done.
I am using WL60(sp2)in Win NT,
My installed dir: E:\bea\wlserver6.0\
Thanks
NalikaI don't believe that you can use the same server definitions for both an admin server and a managed server. So, you'll need to create a second server that is your managed server with a different name or
just run with the admin server.
Paul
On 25 Jun 2001 04:43:22 -0800, "Nalika" <[email protected]> wrote:
>
Hi all,
First I configured a Adminisistration server and started it. After that I added
a another server as ManagedServer.These two points to the same Weblogic server.
When I try to start Managed server by running the script, it gave me following
error.
<Jun 25, 2001 5:25:11 PM GMT+06:00> <Emergency> <Server> <Unable to initialize
the server: 'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:444)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:287)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:259)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:891)
at weblogic.management.Admin.start(Admin.java:305)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
I suspect reason for this might be weblogic.policy file. There you need to edit
some lines replacing the location of the directory in which you installed WebLogic
Server. I did this but still error occurs.
Do u have any idea why above error occurs and if it is due to the weblogic.policy
file entry please tell me how it correctly done.
I am using WL60(sp2)in Win NT,
My installed dir: E:\bea\wlserver6.0\
Thanks
Nalika -
WLST - error when i start managed server using nmstart() command.
i am receiving an error when start the managed server using nmstart(). Please advise.
Do I have add any parameter to nodemanager.properties file?
Thankyou
pasted below is the error message i am receiving when i start managed server.
Starting server hssclient ...This Exception occured at Thu Mar 19 10:30:02 EDT 2
009.
java.lang.IllegalArgumentException: Invalid host name: Null or empty
at weblogic.nodemanager.client.NMClient.checkNullOrEmpty(NMClient.java:7
2)
at weblogic.nodemanager.client.NMClient.setHost(NMClient.java:79)
at weblogic.nodemanager.mbean.NodeManagerRuntime.getNMClient(NodeManager
Runtime.java:527)
at weblogic.nodemanager.mbean.NodeManagerRuntime.getNMClient(NodeManager
Runtime.java:565)
at weblogic.nodemanager.mbean.NodeManagerRuntime.start(NodeManagerRuntim
e.java:188)
at weblogic.server.ServerLifeCycleRuntime.startServer(ServerLifeCycleRun
time.java:439)
at weblogic.server.ServerLifeCycleRuntime.start(ServerLifeCycleRuntime.j
ava:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean
.java:428)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImp
l.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBea
nServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:248)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.
run(WLSMBeanServerInterceptorBase.java:443)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.inv
oke(WLSMBeanServerInterceptorBase.java:441)
at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterce
ptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:63)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.
run(WLSMBeanServerInterceptorBase.java:443)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.inv
oke(WLSMBeanServerInterceptorBase.java:441)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(
SecurityInterceptor.java:426)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
ptor$10$1.run(AuthenticatedSubjectInterceptor.java:582)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
ptor$10.run(AuthenticatedSubjectInterceptor.java:580)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
ptor.invoke(AuthenticatedSubjectInterceptor.java:573)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanSer
ver.java:310)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnecti
onImpl.java:1410)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectio
nImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run
(RMIConnectionImpl.java:1247)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(R
MIConnectionImpl.java:1350)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImp
l.java:784)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown S
ource)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:553)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:443)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:439)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:6
1)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicSer
verRef.java:983)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)Hi I am getting below exception, is nmStart only start AdminServer ????
There are 1 nested errors:
weblogic.management.ManagementException: Booting as admin server, but servername, MS1, 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:803)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:493)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
>
<Feb 10, 2010 1:45:17 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Feb 10, 2010 1:45:17 PM UTC> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Feb 10, 2010 1:45:17 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Feb 10, 2010 1:45:17 PM> <FINEST> <NodeManager> <Waiting for the process to die: 8275>
<Feb 10, 2010 1:45:17 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Feb 10, 2010 1:45:17 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
~ -
Authentication Error while starting managed server ...
Hi everyone,
is there anyone to help me in avoiding the SecurityException while starting managed
server in a cluster. Weblogic version is 6.1.
I have started the admin server in a cluster and is running fine. Also cluster
is started successfully.
When I start managed server appManaged (which is also included in the cluster),
I get the following error:
Starting WebLogic Server ....
Connecting to http://appadmn:7001...
<Nov 20, 2003 11:05:56 AM EST> <Error> <Configuration Management> <Error connect
ing to admin server and initializing admin home: admin URL: t3://appadmin:7001
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)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:316)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.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)
The start script for managed server appManaged is :
%JAVA_HOME%\bin\java -hotspot -ms64m -ms64m -classpath %CLASSPATH% -Dweblogic.Domain=mydomain
-Dweblogic.management.server=appadmin:7001 -Dweblogic.Name=appManaged -Dbea.home=%BEA_HOME%
-Dweblogic.management.username=system -Dweblogic.management.password=weblogic
-Dweblogic.ProductionModeEnabled=%STARTMODE% -Djava.security.auth.login.config==%
BEA_HOME%\wlserver6.1\lib\compat.config -Djava.security.policy==%BEA_HOME%\wlserver6.1\lib\weblogic.policy
-Dweblogic.management.discover=false weblogic.Server
thanks.
I could see calling to setDomainEnv.cmd script:
*@REM Call setDomainEnv here.*
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
set SAVE_CLASSPATH=%CLASSPATH%
But in my environment I do not see these variable set to any, JAVA_HOME, DERBY_CLASSPATH, JAVA_OPTIONS, CLASS_PATH.
This might be the issue? Or anything else? -
Help Please !!! Authentication error while starting managed server
Hi everyone,
is there anyone to help me in avoiding the SecurityException while starting managed
server in a cluster. Weblogic version is 6.1.
I have started the admin server in a cluster and is running fine. Also cluster
is started successfully.
When I start managed server appManaged (which is also included in the cluster),
I get the following error:
Starting WebLogic Server ....
Connecting to http://appadmn:7001...
<Nov 20, 2003 11:05:56 AM EST> <Error> <Configuration Management> <Error connect
ing to admin server and initializing admin home: admin URL: t3://appadmin:7001
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)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:316)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.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)
The start script for managed server appManaged is :
%JAVA_HOME%\bin\java -hotspot -ms64m -ms64m -classpath %CLASSPATH% -Dweblogic.Domain=mydomain
-Dweblogic.management.server=appadmin:7001 -Dweblogic.Name=appManaged -Dbea.home=%BEA_HOME%
-Dweblogic.management.username=system -Dweblogic.management.password=weblogic
-Dweblogic.ProductionModeEnabled=%STARTMODE% -Djava.security.auth.login.config==%
BEA_HOME%\wlserver6.1\lib\compat.config -Djava.security.policy==%BEA_HOME%\wlserver6.1\lib\weblogic.policy
-Dweblogic.management.discover=false weblogic.Server
thanks.I could see calling to setDomainEnv.cmd script:
*@REM Call setDomainEnv here.*
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
set SAVE_CLASSPATH=%CLASSPATH%
But in my environment I do not see these variable set to any, JAVA_HOME, DERBY_CLASSPATH, JAVA_OPTIONS, CLASS_PATH.
This might be the issue? Or anything else?
Maybe you are looking for
-
How can I reflash firmware on 2008 Macbook 4,1?
It looks as though the firmware that was installed after updating my Macbook 4,1 to 10.6.8 fried my Macbook. I can only assume that something went wrong with the update, as the Macbook was working fine up till then. 10.6.8 seemed to install fine. I r
-
Dear all, My user has posted fallowing entry (KZ) KZ 001 50 1000 911000012 ICICI -Moti-134-Out 47,770.00- 002 29B 1000 100116 KETAN ENTERPRISE 18,489.00 003 29B 1000 100116 KETAN ENTERPRISE 2,310.88 004 29B 1000 100116 KETAN ENTERPRISE 23,973.00 005
-
How to maintain cover artwork when importing from media library
Hello, I would need some help on a small, but pretty annoying issue I keep experiencing. I manage my music with iTunes 11, i.e. I use my personal library to rip my CDs to iTunes. Often cover art of albums does not appear automatically, which I then m
-
Function module/BAPI for Pgi creation
hi all, any standard function module/ BAPI for create PGI. i know BAPI_OUTB_DELIVERY_CONFIRM_DEC, suppose if we are using PGI reverse not possibul. regards
-
Itunes account canceled by Itunes
Account was cancelled by itunes due to fruadulent use. Need to find out how to transfer purchases to my new itunes account