Stopping BEA managed server
Is there a way of stopping a weblogic (8.1SP3) managed server, running in production mode, without providing a username & passowrd on the CLI (or thru a script)?
regards,
Vishal
Are you using a custom script or <domain>/bin/stopManagedWebLogic.sh ?
The msg you've informed seems to be an error that happens when you try to start a managed server that is trying to use a port that is already in use.
Similar Messages
-
Problem with JMS migration when using Ctrl+C to stop the managed server in cluster
Hi,
I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
uses JMS as a asynchrous communication. We have MDB which listens to these JMS
messages.
If something is being processed on Managed Server 1 and while the request is in
process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
After this, i go to admin console and migrate teh JTA and JMS. After this, i am
expecting other running Managed Server should restart the incomplete transaction.
But this is not happening. The Managed Serve2 doesn't process the requst.
But when i restart teh MAnaged SErver 1 again, it takes up the same request and
processes it.
Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
Please note that the same thing is working fine when i stop the server using Admin
console(Normal shutdown OR forced shutdown).
Any comments in this regards are apprecciated.
Thanks,
Naresh
Hi,
I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
uses JMS as a asynchrous communication. We have MDB which listens to these JMS
messages.
If something is being processed on Managed Server 1 and while the request is in
process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
After this, i go to admin console and migrate teh JTA and JMS. After this, i am
expecting other running Managed Server should restart the incomplete transaction.
But this is not happening. The Managed Serve2 doesn't process the requst.
But when i restart teh MAnaged SErver 1 again, it takes up the same request and
processes it.
Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
Please note that the same thing is working fine when i stop the server using Admin
console(Normal shutdown OR forced shutdown).
Any comments in this regards are apprecciated.
Thanks,
Naresh
-
Java.rmi.server.ExportException: while stopping weblogic Managed server
Hello,
I am getting the below error while I try to stop the weblogic managed server from the stop script in the server. I am able to do it thru the console.
the weblogic version is 9.23.
-server -Xms1536m -Xmx1536m
Stopping Weblogic Server...
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9990; nested exception is:
java.net.BindException: Address already in use
I am a newbie , so anyone could help me figure out the things I need to check so that I can troubleshoot the issue?
thanks in advance.Are you using a custom script or <domain>/bin/stopManagedWebLogic.sh ?
The msg you've informed seems to be an error that happens when you try to start a managed server that is trying to use a port that is already in use. -
Stopping Managed Server took hours
Hi all,
I have an issue stopping the one of our managed servers (say MNG_SVR_1). It took almost 5 hrs to stop. There was no issue stopping another managed server.
In the managed server logs, I could see the following messages;
>
####<Jul 5, 2010 5:08:02 AM XXX> <Error> <Cluster> <XXXX10> <MNG_SVR_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1278364082350> <BEA-000110> <Multicast socket receive error: java.lang.ClassNotFoundException: com.bea.p13n.cache.internal.system.CacheClusterMessage: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
java.lang.ClassNotFoundException: com.bea.p13n.cache.internal.system.CacheClusterMessage: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:218)
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:85)
at weblogic.common.internal.WLObjectInputStream.resolveClass(WLObjectInputStream.java:61)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.common.internal.WLObjectInputStream.readObjectWL(WLObjectInputStream.java:98)
at weblogic.cluster.MulticastReceiver.getNextMessage(MulticastReceiver.java:259)
at weblogic.cluster.MulticastReceiver.dispatch(MulticastReceiver.java:109)
at weblogic.cluster.MulticastManager.run(MulticastManager.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
I didn't have such issues previously. So, I am seeking some experts' advices on what went wrong.
Thanks in advance,
StephenHow was the managed server tried to be brought down. Forceful or Graceful? In case of a graceful shutdown, the managed server would be brought down only after all the active requests are processed and completed. Moreover, there's something unusual that is seen in the logs that you pasted. Is some application component deployed on only one managed server of the cluster as the logs suggest??Few logs lines previous and after to the one that you have pasted would be giving more pointers...
-
Managed server is not starting with MSI mode
Managed server not starting with MSI mode even though we enabled the managed server independence mode
Started the admin server and managed server first time enabled the MSI mode.
Restarted all admin and Managed server.
We have tested the following scenarios
scenarios1: Stopped the Admin server and restarted the Managed server with MSI mode it comes up.
scenarios2:Admin server is running but not able to connect to the managed server
In this scenario
we have removed the Network cable and restarted the managed server its throwing ldap error.
<Aug 14, 2010 1:58:32 PM SGT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
netscape.ldap.LDAPException: failed to connect to server ldap://sgppsr00383:16827 (91)
at netscape.ldap.LDAPConnSetupMgr.connectServer(LDAPConnSetupMgr.java:515)
at netscape.ldap.LDAPConnSetupMgr.openSerial(LDAPConnSetupMgr.java:435) at netscape.ldap.LDAPConnSetupMgr.connect(LDAPConnSetupMgr.java:274)
at netscape.ldap.LDAPConnSetupMgr.openConnection(LDAPConnSetupMgr.java:199)
at netscape.ldap.LDAPConnThread.connect(LDAPConnThread.java:109)
at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:1083) at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:954)
at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:781)
at weblogic.ldap.EmbeddedLDAPConnection.getAndInitDelegate(EmbeddedLDAPConnection.java:2031)
at weblogic.ldap.EmbeddedLDAPConnection.add(EmbeddedLDAPConnection.java:1065) at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.addEntry(DefaultCredentialMapperLDAPHelper.java:537)
at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.createOrgUnit(DefaultCredentialMapperLDAPHelper.java:432)
at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.verifyHierarchy(DefaultCredentialMapperLDAPHelper.java:407)
at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.<init>(DefaultCredentialMapperLDAPHelper.java:146) at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:112)
at weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340) at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461) at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854) at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
- with nested exception:
Managed server looking for ldap configuration from admin server.
I have checked the all configuration file same on both managed server and admin server.
Please let me know How to recover the managed server in this scenario.
Edited by: user10773210 on Aug 16, 2010 11:55 PM
Edited by: user10773210 on Aug 17, 2010 2:38 AMthanks for the reply....
the managed server is pointing to jrokit_160_22_D1.1.1-3 jdk....the server has enough ram also...while running the managed server showing status 'STARTING' for long period of time...and the admin server health goes 'Warning' because of threadpool....when we stop the managed server then adminserver health becomes ok... -
Managed server is not starting....
hi friends,
we have four node weblogic 10.3.5 clustered deployment of oim 11.1.1.5 ....previously everything was working fine....two of the oim managed server is not starting and throwing following error.... two are working fine and all other 4 soa servers also running fine...
####<May 20, 2012 3:43:18 PM AST> <Warning> <RMI> <server2> <WLS_OIM2> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1337517798416> <BEA-080004> <An error was thrown by rmi server: weblogic.server.RemoteLifeCycleOperationsImpl.forceShutdown()
java.lang.ExceptionInInitializerError.
java.lang.ExceptionInInitializerError
at weblogic.wsee.runtime.JMSStoreRoutableIDMapper.shutdown(JMSStoreRoutableIDMapper.java:478)
at weblogic.wsee.runtime.WebServicesRuntime.shutdown(WebServicesRuntime.java:146)
at weblogic.wsee.runtime.WseeService.haltService(WseeService.java:60)
at weblogic.server.ServiceActivator.halt(ServiceActivator.java:113)
at weblogic.t3.srvr.ServerServicesManager.haltInternal(ServerServicesManager.java:504)
at weblogic.t3.srvr.ServerServicesManager.halt(ServerServicesManager.java:336)
at weblogic.t3.srvr.T3Srvr.shutdown(T3Srvr.java:1120)
at weblogic.t3.srvr.T3Srvr.forceShutdown(T3Srvr.java:1024)
at weblogic.t3.srvr.ServerRuntime.forceShutdown(ServerRuntime.java:351)
at weblogic.server.RemoteLifeCycleOperationsImpl.forceShutdown(RemoteLifeCycleOperationsImpl.java:57)
at weblogic.server.RemoteLifeCycleOperationsImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.lang.IllegalStateException: Shutdown in progress
at java.lang.ApplicationShutdownHooks.add(ApplicationShutdownHooks.java:39)
at java.lang.Runtime.addShutdownHook(Runtime.java:193)
at weblogic.wsee.persistence.LogicalStore.<clinit>(LogicalStore.java:192)
at weblogic.wsee.runtime.JMSStoreRoutableIDMapper.shutdown(JMSStoreRoutableIDMapper.java:478)
at weblogic.wsee.runtime.WebServicesRuntime.shutdown(WebServicesRuntime.java:146)
at weblogic.wsee.runtime.WseeService.haltService(WseeService.java:61)
at weblogic.server.ServiceActivator.halt(ServiceActivator.java:114)
at weblogic.t3.srvr.ServerServicesManager.haltInternal(ServerServicesManager.java:504)
at weblogic.t3.srvr.ServerServicesManager.halt(ServerServicesManager.java:336)
at weblogic.t3.srvr.T3Srvr.shutdown(T3Srvr.java:1120)
at weblogic.t3.srvr.T3Srvr.forceShutdown(T3Srvr.java:1025)
at weblogic.t3.srvr.ServerRuntime.forceShutdown(ServerRuntime.java:351)
at weblogic.server.RemoteLifeCycleOperationsImpl.forceShutdown(RemoteLifeCycleOperationsImpl.java:59)
at weblogic.server.RemoteLifeCycleOperationsImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:668)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:523)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:119)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Regards
jdevthanks for the reply....
the managed server is pointing to jrokit_160_22_D1.1.1-3 jdk....the server has enough ram also...while running the managed server showing status 'STARTING' for long period of time...and the admin server health goes 'Warning' because of threadpool....when we stop the managed server then adminserver health becomes ok... -
Hello All,
My question concerns stopping a managed server once it has been installed and
started as an NT Service. What we want to do is to shutdown our server at night
in order to do database backups. Once we have our managed server running as a
managed service we can issue a stop service command. It looks like that shuts
down the server, but it looks like it does it very abruptly. Is this an OK method
for shutting down a managed server? The reason we're doing this is so that we
can have the command issued automatically by our database server. Is there some
other automated method which we can use for shutting down the server? What are
other people doing for a problem like this where backups are done at night?
Thanks In Advance,
RichThe WebLogic docs describe how to shut down a server from the command line:
http://edocs.bea.com/wls/docs61/adminguide/startstop.html#1028914
This is perhaps more gentle than stopping the service.
"Rich Llaca" <[email protected]> wrote:
>
Hello All,
My question concerns stopping a managed server once it has been installed
and
started as an NT Service. What we want to do is to shutdown our server
at night
in order to do database backups. Once we have our managed server running
as a
managed service we can issue a stop service command. It looks like that
shuts
down the server, but it looks like it does it very abruptly. Is this
an OK method
for shutting down a managed server? The reason we're doing this is so
that we
can have the command issued automatically by our database server. Is
there some
other automated method which we can use for shutting down the server?
What are
other people doing for a problem like this where backups are done at
night?
Thanks In Advance,
Rich -
Passing arguments to Managed Server ServerStart when using Node Manager
Below is the procedure to pass arguments to Managed Server serverstart tab when using Node Manager to start and stop the Managed Server instance
For passing the JVM arguments we will have to use "-server" which is hotspot and then pass the arguments
for eg: "-server -Xms2048m -Xmx2048m -verbosegc"
For adding jar's to the classpath you will have to add weblogic.jar and weblogic_sp.jar from WL_HOME/server/lib directory as well along with the custom jar (In some cases we can ignore weblogic_sp.jar, just adding weblogic.jar will do).
for eg: "\home\user\debug.jar;\home\user\bea\wlserver_10.3\server\lib\weblogic.jar;\home\user\bea\wlserver_10.3\server\lib\weblogic_sp.jar;"
- - TarunHi,
To me, if you don't wanna use the NodeManager, you won't be able to start your managed servers with WLST.
I guess the only ways are :
* through the console / WLST using the NodeManager
* using the startManagedWebLogic.[cmd/sh]
Regards -
Starting Managed Server from Administration Console
Hi
I am new for SOA and fusion. Can anyone share the brief steps that are needed to start/stop a Managed Server from Admin Console.
I did a fresh install on RHEL5 and configure a domain. i was able to start the services from script which are created when creating a domain.
But when i assigned a Managed Server to a Node Manager and try starting the Managed server. It does not start and in the log i can see exceptions like below
Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
java.lang.ClassNotFoundException
Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
java.lang.ClassNotFoundException
I start the services in below order
Weblogic Server
node Manager
and
soa_server
Thanks
Hariyou must set to true the StartScriptEnabled property in nodemanager.properties
-
Weblogic Installation gets managed server of old installation
Hi. In my CentOS I had a weblogic 10.3.3.0 with three managed servers, then I unistalled it, delete the folder of installation manually for the files that the uninstaller didn't erase and then I installed again weblogic (jdevstudio11113install.bin) with new managed servers and when I want to start them up it tells me that it doesn't exist that the only ones that exist are the old ones I had in the previous installation. So I assume they are in a hidden file that I had to remove or update with new managed servers, which sounds strange because that should be deleted during uninstall process. Anyway any hint would be highly appreciated. Greetings.
From what I understand about your problem you have a domain - Admin server running on one physical machine and Managed server running on another physical machine, when stopping the Managed server its getting hung at suspending state, which in turn is causing Admin server slow down in response or hang.
Please confirm on this how are you stopping and starting your managed server
make sure that you do not use localhost when creating domains which spread across more than one physical machine.
Make sure that your Adminserver & Managed server have address as hostname's of physical server instead of Localhost
You should be starting / stopping Managed server something like this
startManagedWeblogic.sh -url t3://AdminserverHostName:PortNo <servername>
stopManagedWeblogic.sh -url t3://AdminserverHostName:PortNo <servername>
Let me know if you still have the problem.
Weblogic Consultant -
Managed Server not populating while installation in SOA server detail
I am facing an issue in installation of AIA. In the screen SOA server detail, managed server is not populating in dropdown option. I have installed Weblogic middle ware fusion in which admin server and managed server is running. Both are configured for by own machine and clustering is not done
I want to know these things.
1) Is there any problem with weblogic installation or configuration. Managed server and admin server is running fine
2) Do i need to configure node management to map admin server and managed server in fusion middleware?
3) Is there any compatibility mode issue? I am running the setup as administrator in window 7 OS for 32bit windows
Please help me in resolving this issue.
ThanksCheck for the following in your target soa server:
1. SOA components are correctly deployed.
2. soa-infra deployment is running and healthy.
3. node manager is able to start and stop the managed server properly. -
Restarting AdminServer without shutting down Managed Server
Using Weblogic 10.3.5 on OEL v8
To clear some old stats I need to bounce the Admin Server running on port 7001. Would I have to stop the Managed server as well (my applications) for this? Or can I bounce Admin Server without stopping my application?
Thanks.809364 wrote:
Which stats you want to reset. is it specific to your application-runtime statistic data running on managed server.
You need to restart your managed server in case of stats belonging to the application or from the managed server.JDBC Data Source - Failure to Reconnect count . -
Errors of BEA-101147 during shutdown if a managed server form a cluster
Hi there,
We have a cluster with two machines running one managed server on each. Acces to these servers is made with mod_wl.so on Apache. The problem we´re having is: when I shutdown one of the managed servers it seems to undeploy the web application before stopping serving requests. Issuing thus the following error message on the log:
<br>
####<05/10/2004 08h19min43s BRT> <Debug> <HTTP> <calipso> <calipsoFOCC> <ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <<b>BEA-101147</b>> <HttpServer(20184735,null default ctx,calipsoFOCC) Found no context for "/externo/portal/pop/sendData.jsp". This request does not match the context path for any installed Web applications, and there is no default Web application configured.>
<br>
The effect for the end user is that he receives 404 errors. Even tought the session is being replicated to the other server. <br>
I´m running WLS Premium 8.1SP2.. If anyone has a clue on this I would be very greateful.<br>
Regards,<br>
Renato MoutinhoHi,
You didn't mention what WLS release you are using. There is a known problem with 8.1sp2 and 8.1sp3. You should open a case with BEA Support and reference change request number CR185885.
Jane -
NotEditorException while restarting and stopping managed server
Hi guys/gals,
I am using JDK 1.4 for weblogic 9.2. I have created two managed servers, but while restarting or stopping them, I am facing following exception. because of this exception, application that is deployed is not getting exploded.
While starting the managed server.
<May 26, 2008 3:22:57 PM IST> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.management.mbeanservers.edit.NotEditorException:
at weblogic.management.mbeanservers.edit.internal.ConfigurationManagerMBeanImpl.getUnactivatedChanges(ConfigurationManagerMBeanImpl.java:292)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.management.jmx.modelmbean.WLSModelMBean.getAttribute(WLSModelMBean.java:499)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttribute(DynamicMetaDataImpl.java:96)
at com.sun.jmx.mbeanserver.MetaDataImpl.getAttribute(MetaDataImpl.java:181)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:638)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:659)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:281)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$5.run(AuthenticatedSubjectInterceptor.java:192)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.getAttribute(AuthenticatedSubjectInterceptor.java:190)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:269)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1385)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:597)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_920_WLStub.getAttribute(Unknown Source)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:854)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:175)
at weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:503)
Caused by: weblogic.management.provider.EditNotEditorException: Not edit lock owner
at weblogic.management.provider.internal.EditAccessImpl.checkEditLock(EditAccessImpl.java:1405)
at weblogic.management.provider.internal.EditAccessImpl.getUnactivatedChanges(EditAccessImpl.java:949)
at weblogic.management.mbeanservers.edit.internal.ConfigurationManagerMBeanImpl.getUnactivatedChanges(ConfigurationManagerMBeanImpl.java:283)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.management.jmx.modelmbean.WLSModelMBean.getAttribute(WLSModelMBean.java:499)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttribute(DynamicMetaDataImpl.java:96)
at com.sun.jmx.mbeanserver.MetaDataImpl.getAttribute(MetaDataImpl.java:181)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:638)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:659)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:281)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$5.run(AuthenticatedSubjectInterceptor.java:192)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.getAttribute(AuthenticatedSubjectInterceptor.java:190)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:269)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1385)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:597)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_920_WLStub.getAttribute(Unknown Source)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:854)
And while stopping the servers, exception trace is as follows,
<Console encountered the following error weblogic.management.mbeanservers.edit.NotEditorException:
at weblogic.management.mbeanservers.edit.internal.ConfigurationManagerMBeanImpl.getUnactivatedChanges(ConfigurationManagerMBeanImpl.java:292)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.management.jmx.modelmbean.WLSModelMBean.getAttribute(WLSModelMBean.java:499)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttribute(DynamicMetaDataImpl.java:96)
at com.sun.jmx.mbeanserver.MetaDataImpl.getAttribute(MetaDataImpl.java:181)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:638)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:659)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:281)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$5.run(AuthenticatedSubjectInterceptor.java:192)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.getAttribute(AuthenticatedSubjectInterceptor.java:190)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:269)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1385)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:597)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_920_WLStub.getAttribute(Unknown Source)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:854)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:175)
at weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:503)
at weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:380)
Caused by: weblogic.management.provider.EditNotEditorException: Not edit lock owner
at weblogic.management.provider.internal.EditAccessImpl.checkEditLock(EditAccessImpl.java:1405)
at weblogic.management.provider.internal.EditAccessImpl.getUnactivatedChanges(EditAccessImpl.java:949)
at weblogic.management.mbeanservers.edit.internal.ConfigurationManagerMBeanImpl.getUnactivatedChanges(ConfigurationManagerMBeanImpl.java:283)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.management.jmx.modelmbean.WLSModelMBean.getAttribute(WLSModelMBean.java:499)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttribute(DynamicMetaDataImpl.java:96)
at com.sun.jmx.mbeanserver.MetaDataImpl.getAttribute(MetaDataImpl.java:181)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:638)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:659)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:281)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$5.run(AuthenticatedSubjectInterceptor.java:192)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.getAttribute(AuthenticatedSubjectInterceptor.java:190)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:269)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1385)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:597)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_920_WLStub.getAttribute(Unknown Source)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:854)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:175)
weblogic.server.ServerLifecycleException: Can not get to the relevant ServerRuntimeMBean
at weblogic.server.ServerLifeCycleRuntime$ShutdownRequest.run(ServerLifeCycleRuntime.java:484)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Please let me know about the configuration under which you had faced such problems or solutions if possible.
Thanks in advance,
Rahul Gandhi.I would use the console and release the edit lock to see if that clears
up the problem.
Rahul Gandhi wrote:
Hi guys/gals,
I am using JDK 1.4 for weblogic 9.2. I have created two managed servers, but while restarting or stopping them, I am facing following exception. because of this exception, application that is deployed is not getting exploded.
While starting the managed server.
<May 26, 2008 3:22:57 PM IST> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.management.mbeanservers.edit.NotEditorException:
at weblogic.management.mbeanservers.edit.internal.ConfigurationManagerMBeanImpl.getUnactivatedChanges(ConfigurationManagerMBeanImpl.java:292)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.management.jmx.modelmbean.WLSModelMBean.getAttribute(WLSModelMBean.java:499)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttribute(DynamicMetaDataImpl.java:96)
at com.sun.jmx.mbeanserver.MetaDataImpl.getAttribute(MetaDataImpl.java:181)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:638)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:659)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:281)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$5.run(AuthenticatedSubjectInterceptor.java:192)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.getAttribute(AuthenticatedSubjectInterceptor.java:190)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:269)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1385)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:597)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_920_WLStub.getAttribute(Unknown Source)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:854)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:175)
at weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:503)
Caused by: weblogic.management.provider.EditNotEditorException: Not edit lock owner
at weblogic.management.provider.internal.EditAccessImpl.checkEditLock(EditAccessImpl.java:1405)
at weblogic.management.provider.internal.EditAccessImpl.getUnactivatedChanges(EditAccessImpl.java:949)
at weblogic.management.mbeanservers.edit.internal.ConfigurationManagerMBeanImpl.getUnactivatedChanges(ConfigurationManagerMBeanImpl.java:283)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.management.jmx.modelmbean.WLSModelMBean.getAttribute(WLSModelMBean.java:499)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttribute(DynamicMetaDataImpl.java:96)
at com.sun.jmx.mbeanserver.MetaDataImpl.getAttribute(MetaDataImpl.java:181)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:638)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:659)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:281)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$5.run(AuthenticatedSubjectInterceptor.java:192)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.getAttribute(AuthenticatedSubjectInterceptor.java:190)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:269)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1385)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:597)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_920_WLStub.getAttribute(Unknown Source)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:854)
And while stopping the servers, exception trace is as follows,
<Console encountered the following error weblogic.management.mbeanservers.edit.NotEditorException:
at weblogic.management.mbeanservers.edit.internal.ConfigurationManagerMBeanImpl.getUnactivatedChanges(ConfigurationManagerMBeanImpl.java:292)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.management.jmx.modelmbean.WLSModelMBean.getAttribute(WLSModelMBean.java:499)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttribute(DynamicMetaDataImpl.java:96)
at com.sun.jmx.mbeanserver.MetaDataImpl.getAttribute(MetaDataImpl.java:181)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:638)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:659)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:281)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$5.run(AuthenticatedSubjectInterceptor.java:192)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.getAttribute(AuthenticatedSubjectInterceptor.java:190)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:269)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1385)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:597)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_920_WLStub.getAttribute(Unknown Source)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:854)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:175)
at weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:503)
at weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:380)
Caused by: weblogic.management.provider.EditNotEditorException: Not edit lock owner
at weblogic.management.provider.internal.EditAccessImpl.checkEditLock(EditAccessImpl.java:1405)
at weblogic.management.provider.internal.EditAccessImpl.getUnactivatedChanges(EditAccessImpl.java:949)
at weblogic.management.mbeanservers.edit.internal.ConfigurationManagerMBeanImpl.getUnactivatedChanges(ConfigurationManagerMBeanImpl.java:283)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.management.jmx.modelmbean.WLSModelMBean.getAttribute(WLSModelMBean.java:499)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttribute(DynamicMetaDataImpl.java:96)
at com.sun.jmx.mbeanserver.MetaDataImpl.getAttribute(MetaDataImpl.java:181)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:638)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:659)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:112)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:281)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$5.run(AuthenticatedSubjectInterceptor.java:192)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.getAttribute(AuthenticatedSubjectInterceptor.java:190)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:269)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1385)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:597)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_920_WLStub.getAttribute(Unknown Source)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:854)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:175)
weblogic.server.ServerLifecycleException: Can not get to the relevant ServerRuntimeMBean
at weblogic.server.ServerLifeCycleRuntime$ShutdownRequest.run(ServerLifeCycleRuntime.java:484)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Please let me know about the configuration under which you had faced such problems or solutions if possible.
Thanks in advance,
Rahul Gandhi. -
Error While Starting the Weblogic Managed server- BEA-160001
Hi,
While starting the managed server (10.3.4) below exception occurs. Help me on why the error occurs.
<Error> <J2EE> <BEA-160001> <Error deploying Internal Application: weblogic.application.ModuleException: [HTTP:101216]Servlet: "CoordinatorPortTypeServlethttp" failed to preload on startup in Web application: "wls-wsat.war".
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
Caused by: java.lang.IllegalArgumentException: com.sun.xml.messaging.saaj.soap.LocalStrings != com.sun.xml.internal.messaging.saaj.soap.LocalStrings
at java.util.logging.Logger.getLogger(Logger.java:314)
at com.sun.xml.internal.messaging.saaj.soap.SAAJMetaFactoryImpl.<clinit>(SAAJMetaFactoryImpl.java:41)
.Hi,
There are two workaround for this issue.
1) Without disabling wls-wsat application:
Here are the steps:
Add jar saaj-impl-1.3.jar to weblogic classpath
Start weblogic using java options:
-Djavax.xml.soap.MessageFactory=com.sun.xml.messaging.saaj.soap.MessageFactoryImpl
-Djavax.xml.soap.SOAPFactory=com.sun.xml.messaging.saaj.soap.SOAPFactoryImpl
-Djavax.xml.soap.MetaFactory=com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl
2) If wls-wsat is not required:
This is the setting to disable wls-wsat:
-Dweblogic.wsee.wstx.wsat.deployed=false
It is mentioned here in the doc
http://docs.oracle.com/cd/E21764_01/web.1111/e13734/cluster.htm
Regards,
Kal
Maybe you are looking for
-
Help! I have a question about colors. I'm working on a number of files in which one of the colors have technically changed, however the name of the color has to stay the same. I open a previous file, with the old color (a spot color), and open up a n
-
Dynamically populating a combo box in Forms
I am having a hard time figuring out how to dynamically populate a combo box at run time. Could someone give me any ideas? thanks, Robin
-
Dock adapter capability with 4th generation ipod?
Hello, I have just bought the new 5G iPod and i noticed that it came with a dock adapter, but i was wondering if i could use my old 4G ipod dock to charge the 5G with the adapter. This would result in saving me buying a brand new dock. Thanks alot fo
-
Hi.. Could anyone pls share me link to download book in pdf of CCNP Security Study guide.
-
Finding a folders parent folder
How can you find out what a folders parent folder is ? The view WWSBR_ALL_FOLDERS has the folder information (id, name etc.) but doesn't have anything to indicate what the parent folder is. This view runs off the table WWV_USER_CORNERS which contains