Root management server stops alerting frequently

Hi All,
I have a Root management server running SCOM 2007 R2 CU4. All the roles are in the same RMS server (RMS, SQL, Webconsole).
Suddenly once in a day our alerting stops and even after we see the scom services are running and the management server is in a healthy state. We restart the services SDK, Healthservice, System center management configuration. Still we do not get the alerts.
We need to fully reboot the RMS and it works fine in a day. Same issue continues and we reboot it once in a day.
Any idea what is the issue. We cannot afford rebooting this daily.
We had installed few security patches on the RMS. We got them uninstalled but still the same issue.
Analysed the event logs and found few logs.
Lot of Event is 2115 events.
Event id 26380 - The System Center Operations Manager SDK Service failed due to an unhandled exception. 
The service will attempt to restart. Exception:
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at Bid.TraceError(String fmtPrintfW, Object a1, Object a2)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments executeArguments, RetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader sqlDataReader, SqlConnection sqlConnection, IList`1 prologEpilogList, RetryPolicy retryPolicy)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid id, Int32 count)
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid readerId, Int32 count)
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid readerId, Int32 count)
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid readerId, Int32 count)
   at SyncInvokeGetObjectsFromReader(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
   at System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(RequestContext request, Boolean cleanThread, OperationContext currentOperationContext)
   at System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(RequestContext request, OperationContext currentOperationContext)
   at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)
   at System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
   at System.ServiceModel.AsyncResult.Complete(Boolean completedSynchronously)
   at System.ServiceModel.Channels.FramingDuplexSessionChannel.TryReceiveAsyncResult.OnReceive(IAsyncResult result)
   at System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
   at System.ServiceModel.AsyncResult.Complete(Boolean completedSynchronously)
   at System.ServiceModel.Channels.SynchronizedMessageSource.SynchronizedAsyncResult`1.CompleteWithUnlock(Boolean synchronous, Exception exception)
   at System.ServiceModel.Channels.SynchronizedMessageSource.ReceiveAsyncResult.OnReceiveComplete(Object state)
   at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)
   at System.ServiceModel.Channels.StreamConnection.OnRead(IAsyncResult result)
   at System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
   at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
   at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
   at System.Net.Security.NegotiateStream.ProcessFrameBody(Int32 readBytes, Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.NegotiateStream.ReadCallback(AsyncProtocolRequest asyncRequest)
   at System.Net.FixedSizeReader.CheckCompletionBeforeNextRead(Int32 bytes)
   at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)
   at System.ServiceModel.AsyncResult.Complete(Boolean completedSynchronously)
   at System.ServiceModel.Channels.ConnectionStream.ReadAsyncResult.OnAsyncReadComplete(Object state)
   at System.ServiceModel.Channels.SocketConnection.FinishRead()
   at System.ServiceModel.Channels.SocketConnection.AsyncReadCallback(Boolean haveResult, Int32 error, Int32 bytesRead)
   at System.ServiceModel.Diagnostics.Utility.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
Event id 1103 - Summary: 28 rule(s)/monitor(s) failed and got unloaded, 0 of them reached the failure limit that prevents automatic reload. Management group "My Management Group". This is summary only event, please see other events
with descriptions of unloaded rule(s)/monitor(s).
Event id: 26319
The description for Event ID 26319 from source OpsMgr SDK Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Connect uuid:6856a52d-56c3-4aa2-92e3-2ca16e644c12;id=1 The creator of this fault did not specify a Reason. System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.SdkServiceNotInitializedException]: The creator of this fault did not specify
a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.SdkServiceNotInitializedException: Sdk Service has not yet initialized. Please retry).
The handle is invalid
The description for Event ID 26319 from source OpsMgr SDK Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Connect
uuid:6856a52d-56c3-4aa2-92e3-2ca16e644c12;id=2
The creator of this fault did not specify a Reason.
System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.SdkServiceNotInitializedException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.SdkServiceNotInitializedException:
Sdk Service has not yet initialized. Please retry).
The handle is invalid
Event id: 1103
The description for Event ID 1103 from source HealthService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Name of my management group
1
0
The handle is invalid
Event id 29104 - OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening because the Root OpsMgr Health Service is not running.
Event id : 4000 - A monitoring host is unresponsive or has crashed.  The status code for the host failure was 2164195371.
Event id 4503 - A module reported an error 0x8007000E from a callback which was running as part of rule "_44E9A997_6A02_4298_8430_8E01952AB6F3_.RaiseAlert" running for instance "Root managementserver FQDN" with id:"{6C3444C3-3990-BB5A-F25E-289D8F427570}"
in management group "My Management Group".
==================================
Can anyone help us.

Hi,
How to troubleshoot Event ID 2115 in Operations Manager
http://support2.microsoft.com/kb/2681388
SCOM 2007 R2 - SDK Service Exception with Event ID's 27000, 26371, 26338, 26380, 26319
http://social.technet.microsoft.com/Forums/systemcenter/en-US/93977ed8-ff95-49d0-bc85-42217526c5b0/scom-2007-r2-sdk-service-exception-with-event-ids-27000-26371-26338-26380-26319?forum=operationsmanagergeneral
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

  • My root management server goes to grayed state frequently

    Hi All,
    I have a strange issue with my SCOM 2007 R2 CU4.
    My management server grayes out frequently and when i check the operations manager console it throws me these two errors. Can anyone give me a solution for this.
    Note:  The following information was gathered when the operation was attempted.  The information may appear cryptic but provides context for the error.  The application will continue to run.
    Microsoft.EnterpriseManagement.Common.UnknownAuthorizationStoreException: Unable to perform the operation because of authorization store errors. ---> System.Runtime.InteropServices.COMException (0x800705AA): Insufficient system resources exist to complete
    the requested service. (Exception from HRESULT: 0x800705AA)
       at Microsoft.Interop.Security.AzRoles.IAzApplication2.InitializeClientContextFromToken(UInt64 ullTokenHandle, Object varReserved)
       at Microsoft.EnterpriseManagement.Mom.Sdk.Authorization.AzManHelper.AccessCheck(String accessCheckContext, Int32[] operationIds, IntPtr hToken, String stringSid, Int32[] accessCheckReturnCodes, List`1[] accessCheckScopes)
       --- End of inner exception stack trace ---
       at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex)
       at Microsoft.EnterpriseManagement.DataAbstractionLayer.InstanceSpaceOperations.GetMonitoringObjectByMonitoringObjectIds(List`1 monitoringObjectIds, String languageCode, MonitoringObjectMode monitoringObjectMode)
       at Microsoft.EnterpriseManagement.ManagementGroup.GetPartialMonitoringObjects(ICollection`1 ids)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.TaskPaneContext.GetManagedEntities(ICollection`1 items)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.TaskPaneContext.UpdateContextJob(Object sender, ConsoleJobEventArgs args)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)
    System.Runtime.InteropServices.COMException (0x800705AA): Insufficient system resources exist to complete the requested service. (Exception from HRESULT: 0x800705AA)
       at Microsoft.Interop.Security.AzRoles.IAzApplication2.InitializeClientContextFromToken(UInt64 ullTokenHandle, Object varReserved)
       at Microsoft.EnterpriseManagement.Mom.Sdk.Authorization.AzManHelper.AccessCheck(String accessCheckContext, Int32[] operationIds, IntPtr hToken, String stringSid, Int32[] accessCheckReturnCodes, List`1[] accessCheckScopes)
    ====================================================================================
    Note:  The following information was gathered when the operation was attempted.  The information may appear cryptic but provides context for the error.  The application will continue to run.
    Microsoft.Mom.Isam.IsamOutOfMemoryException: Out of Memory (-1011)
       at Microsoft.Mom.Isam.?A0x5359b89f.HandleError(Int32 err)
       at Microsoft.Mom.Isam.EseInterop.JetGetIndexInfo(JET_SESID sesid, JET_DBID dbid, String table, String index)
       at Microsoft.Mom.Isam.IndexCollection.get_Item(String indexName)
       at Microsoft.Mom.Isam.Cursor.get_CurrentIndexDefinition()
       at Microsoft.Mom.Isam.Cursor.MakeKey(Key key, Boolean end)
       at Microsoft.Mom.Isam.Cursor.GotoKey(Key key)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.EseCursor.Find(Object[] values)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.MPImageCache.RetrieveImageIdFromCache(CacheTable classToImageMapTable, ManagementPackElementImageKey imageKey, Guid& imageId)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.MPImageCache.GetImageCore(CacheSession session, ManagementGroup managementGroup, ManagementPackElementImageKey imageKey, Guid& imageId)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.MPImageCache.GetImageJob(Object sender, ConsoleJobEventArgs jobArgs)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)
    Screenshot of the error:
    Also i restarted the health service and the health service fails to start below is the screenshot of that.
    Analysed the event logs and found the below:
    Event id 29104 - OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening because the Root OpsMgr Health Service is not running.
    Event id : 4000 - A monitoring host is unresponsive or has crashed.  The status code for the host failure was 2164195371.
    Event id 4503 - A module reported an error 0x8007000E from a callback which was running as part of rule "_44E9A997_6A02_4298_8430_8E01952AB6F3_.RaiseAlert" running for instance "Root managementserver FQDN" with
    id:"{6C3444C3-3990-BB5A-F25E-289D8F427570}" in management group "CINSCOM".
    Event id - 21044 - The OpsMgr Connector cannot uncompress package, received from IP XXXXXXXXXXXX
    Event id 1103 - Summary: 28 rule(s)/monitor(s) failed and got unloaded, 0 of them reached the failure limit that prevents automatic reload. Management group "CINSCOM". This is summary only event, please see other events
    with descriptions of unloaded rule(s)/monitor(s).
    26380 - The System Center Operations Manager SDK Service failed due to an unhandled exception.  
    The service will attempt to restart. 
    Exception: 
    System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
       at Bid.TraceError(String fmtPrintfW, Object a1, Object a2)
       at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments executeArguments, RetryPolicy retryPolicy, GenericExecute`1 genericExecute)
       at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader sqlDataReader, SqlConnection sqlConnection, IList`1 prologEpilogList, RetryPolicy retryPolicy)
       at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
       at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid id, Int32 count)
       at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid readerId, Int32 count)
       at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid readerId, Int32 count)
       at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid readerId, Int32 count)
       at SyncInvokeGetObjectsFromReader(Object , Object[] , Object[] )
       at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
       at System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(RequestContext request, Boolean cleanThread, OperationContext currentOperationContext)
       at System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(RequestContext request, OperationContext currentOperationContext)
       at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)
       at System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
       at System.ServiceModel.AsyncResult.Complete(Boolean completedSynchronously)
       at System.ServiceModel.Channels.FramingDuplexSessionChannel.TryReceiveAsyncResult.OnReceive(IAsyncResult result)
       at System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
       at System.ServiceModel.AsyncResult.Complete(Boolean completedSynchronously)
       at System.ServiceModel.Channels.SynchronizedMessageSource.SynchronizedAsyncResult`1.CompleteWithUnlock(Boolean synchronous, Exception exception)
       at System.ServiceModel.Channels.SynchronizedMessageSource.ReceiveAsyncResult.OnReceiveComplete(Object state)
       at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)
       at System.ServiceModel.Channels.StreamConnection.OnRead(IAsyncResult result)
       at System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
       at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
       at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
       at System.Net.Security.NegotiateStream.ProcessFrameBody(Int32 readBytes, Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.NegotiateStream.ReadCallback(AsyncProtocolRequest asyncRequest)
       at System.Net.FixedSizeReader.CheckCompletionBeforeNextRead(Int32 bytes)
       at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)
       at System.ServiceModel.AsyncResult.Complete(Boolean completedSynchronously)
       at System.ServiceModel.Channels.ConnectionStream.ReadAsyncResult.OnAsyncReadComplete(Object state)
       at System.ServiceModel.Channels.SocketConnection.FinishRead()
       at System.ServiceModel.Channels.SocketConnection.AsyncReadCallback(Boolean haveResult, Int32 error, Int32 bytesRead)
       at System.ServiceModel.Diagnostics.Utility.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)
       at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
    ======================================================
    Below is the configuration of the server:
    Windows server 2008 r2 enterprise (Without SP1)
    SQL server standard edition 2008.
    Intel Xeon 2.6 Ghz (2 Processors) Totally 8 cores.
    12GB Physical memory (Always 95 - 98% used)
    427 agents being monitored (Exchange 2010, Blackberry etc)
    All the roles (SCOM, RMS, SQL all are in the same box)
    Can anyone please help.
    Gautam.75801

    Did you install some software before this issue appeared? If yes, you need to uninstall it because May be there is conflict software.
    Also for event 29104, you can refer below links
    http://blog.tyang.org/2011/09/30/event-id-29104-on-scom-rms-cluster/
    http://support.microsoft.com/kb/946417/en-us
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • Identifying the Root Management Server in Operations Manager 2012

    Hello,
    I want to replace my primary management server.
    Do i need to do the following steps if i have SCOM 2012??
    https://technet.microsoft.com/en-us/library/cc540401.aspx?f=255&MSPPError=-2147217396
    Promote a management server to a root management server role
    Configure the reporting server with the name of the new root management server.
    Configure the Web console with the name of the new root management server.
    Set ENABLE_BROKER to 1 if needed
    Thanks!
    TechNet

    Hello,
    I am not sure i understand how it works.
    The SQL server and the Application server are at the same domain (no firewalls) but not on the same server.
    The reporting are installed on the SQL server.
    We only have one domain admin account that is running on "data warehouse report deployment account"
    At the reporting configuration manager, it's the correct report link.
    At the reporting server i can see that at the :"c:\ProgramFiles\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer" there is a file
    called "reportserver", inside this file i can see the FQDN of my primary SCOM Server under "Security" and "Authentication" sections.
    Is that why the reporting URL doesn't work when the primary server is down?
    Remember - i set the RMS emulator to a different server.
    If i need to change that manually then the first Q i have ask is relevant also for SCOM 2012.
    Thanks.
    TechNet

  • SCOM 2007 R2 Root Management server showing Not Monitored State in Ops Mgr Console

    Hello Experts,
    In my Prod SCOM 2007 R2 environment RMS server state is "Not Monitored", But we are receiving alerts with limitation. By mistakenly I put Maintenance Mode while rebooting RMS server due to slow performance of the server.
    Can anybody help me to revert back to the RMS Health state ?

    We can identify the Performance Signature Data Collection Rules in this example by executing the following SQL Query. This query should be executed in SQL Management Studio against the Operations Manager database.
    -- Return all Performance Signature Collection Rules
    Use OperationsManager
    select 
    managementpack.mpname, 
    rules.rulename
    from performancesignature with (nolock)
    inner join rules with (nolock)
    on rules.ruleid = performancesignature.learningruleid
    inner join managementpack with(nolock)
    on rules.managementpackid = managementpack.managementpackid
    group by managementpack.mpname, rules.rulename
    order by managementpack.mpname, rules.rulename
    This query will return all Performance Signature Collection Rules and their respective Management Pack name. A column is returned for Management Pack name and Rule name.
    The following Performance Monitor Counters on a Management Server will provide information concerning Database and Data Warehouse write action insertion batch size and time. If the batch size is growing larger, for example the default batch size is 5000 items,
    this indicates either the Management Server is slow inserting the data to the Database or Data Warehouse, or is receiving a burst of Data Items from the Agents or Gateway Servers. 
    · OpsMgr DB Write Action Modules(*)\Avg. Batch Size 
    · OpsMgr DB Write Action Modules(*)\Avg. Processing Time 
    · OpsMgr DW Writer Module(*)\Avg. Batch Processing Time, ms 
    · OpsMgr DW Writer Module(*)\Avg. Batch Size 
    From the Database and Data Warehouse write action account Average Processing Time counter, we can understand how long it takes on average to write a batch of data to the Database and Data Warehouse. Depending upon the amount of time it takes to write a batch
    of data to the Database, this may present an opportunity for tuning. 
    Event ID 2115 A Bind Data Source in Management Group
    http://blogs.technet.com/b/kevinholman/archive/2008/04/21/event-id-2115-a-bind-data-source-in-management-group.aspx
    Niki Han
    TechNet Community Support

  • DI Server stops responding frequently

    Hi all,
      We are using the DI Server on one of  our client for providing the ecommerce solution. Initially it works fine and after sometime, the DI Server stops responding and i need to restart the DI Server and it works fine again.
    What we have done is :
    1) Login using DI Server
    2) Query to the SAP B1 to do the business work.
    3) Logout
    I also noticed that the simultaneous ecommerce  user is below 100. Our DI Server Licence is 8.
    Any help will be great support for this work
    Regards,
    Bikal Ghimire

    We are facing this problem too!, it's strange actually I found about 3 threads about the DI Server and nothing answered and i have the same problem with them
    http://scn.sap.com/thread/3219386 I need answer for this please or any document could be helpful
    http://scn.sap.com/thread/3179798 also this once some times it happen with us too!
    Thanks in advance

  • JMX Connectivity has been discontinued with the managed server

    Dear all,
    I am getting following msg in my weblogic 11g manage server and admin server.
    Namage Server Log
    ####<Nov 22, 2010 2:15:39 PM IST> <Warning> <Log Management> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415539687> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
    Admin Server Log
    ####<Nov 22, 2010 2:13:35 PM IST> <Info> <JMX> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415415015> <BEA-149507> <JMX Connectivity has been discontinued with the managed server NewTradeServer.>
    ####<Nov 22, 2010 2:13:35 PM IST> <Info> <Server> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415415015> <BEA-002634> <The server "NewTradeServer" disconnected from this server.>
    ####<Nov 22, 2010 2:51:32 PM IST> <Info> <Server> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417692374> <BEA-002635> <The server "NewTradeServer" connected to this server.>
    During this time my admin server in running, i can able to loggin to admin server console,
    Problem which i am faceing is that, i am not able to see the server status of that particular
    manage server, i am not able to see the any sub tabs statistic in Monitoring TAB of manage server, and after 1/2 and hours the manage server stop responding, then i restart the manage server and after that every thing work fine..
    any one have the solution for this error????///
    Regds
    Amar Shaw

    Kindly fing the log for the server problem time.
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.177.97.179:21,557 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 117.206.128.110:1,069 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 203.123.173.169:50,920 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.180.84.228:50,902 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 120.61.132.164:1,297 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.166.48.41:21,631 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 125.22.34.38:39,481 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 113.193.25.104:52,294 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.122:18,934 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 115.241.80.244:24,575 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 196.15.16.20:38,791 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 202.65.136.252:4,055 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 80.239.242.168:46,777 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 110.227.109.138:64,362 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.93.223.187:1,046 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 114.30.77.228:50,110 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.164.238.6:1,935 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 192.20.251.68:41,430 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 195.189.142.85:51,932 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 180.150.250.17:3,974 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 82.178.3.115:11,545 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 125.21.153.192:7,902 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.177.2.33:50,437 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 117.201.90.244:5,725 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 220.227.95.145:17,067 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 115.248.137.70:33,786 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.121:6,260 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.93.55.98:6,387 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.162.145.253:1,603 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 80.239.242.168:46,443 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 120.61.132.164:1,298 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 121.243.135.163:2,342 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.202.130.167:1,451 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 204.194.141.28:15,387 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 180.215.198.169:2,108 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 180.150.250.17:40,204 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.168.80:1,044 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.241.82.55:50,090 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.134.134:1,079 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.162.69.77:4,185 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 155.56.68.217:60,708 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 121.245.188.43:1,262 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 125.17.188.19:45,490 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.165.58.249:49,239 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 61.17.215.126:4,085 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 124.125.27.11:2,992 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.121:7,639 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 61.246.47.199:2,426 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.169.70.18:14,392 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:42,408 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.197.237.98:51,852 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.163.89.69:64,984 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 192.20.246.168:13,547 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:37,198 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:39,842 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.202.130.167:1,450 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.90.72.203:3,972 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 155.56.68.217:58,671 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.168.80:1,043 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.163.163.25:1,957 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 115.240.50.203:1,059 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 203.197.42.2:34,187 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 203.124.135.246:21,650 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 93.186.23.240:11,235 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.133:4,215 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.161.99.67:20,466 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <WebLogicServer> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576578> <BEA-000000> <WebLogic Server "NewTradeServer" version:
    WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Notice> <Log Management> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576703> <BEA-170019> <The server log file D:\BEA11G\user_projects\domains\IndiabullsWLS\servers\NewTradeServer\logs\NewTrade_%yyyy%_%MM%_%dd%_%hh%_%mm%.log is opened. All server side log events will be written to this file.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Log Management> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576718> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Diagnostics> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576812> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "http" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "https" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <RJVM> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576937> <BEA-000570> <Network Configuration for Channel "NewTradeServer"
    Listen Address          172.17.1.134:80
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <RJVM> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576937> <BEA-000570> <Network Configuration for Channel "NewTradeServer"
    Listen Address          172.17.1.134:443 (SSL)
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576968> <BEA-002609> <Channel Service initialized.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576999> <BEA-000406> <NTSocketMuxer was built on Jan 24 2006 20:40:35
    >
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577078> <BEA-000436> <Allocating 4 reader threads.>
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577078> <BEA-000446> <Native IO Enabled.>
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <IIOP> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577281> <BEA-002014> <IIOP subsystem enabled.>
    ####<Nov 22, 2010 2:49:38 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417578718> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Nov 22, 2010 2:49:38 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417578796> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_KNcrxQIcWPsGUMqWWNL3mWV+Tkc=>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417579203> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417579390> <BEA-000000> <Parsing class "com.bea.common.security.store.data.Top".>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Securit

  • Management server alerts

    Has anyone seen this before? If so, how do you resolve it?
    The System Center Management Health Service DC026218-94F0-1BDC-1FC1-BB7BD4A0A70D running on host managementserver1.domain and serving management group with id {5F201AB2-4B10-7FCC-C716-B2361102248D} is not healthy. System Center Management Health
    Service is unable to process or load configuration.
    I'm also getting another alert saying:
    The System Center Management Health Service DC026218-94F0-1BDC-1FC1-BB7BD4A0A70D running on host managementserver1.domain and serving management group with id {5F201AB2-4B10-7FCC-C716-B2361102248D} is not healthy. Some system rules failed to load.
    According to the product knowledge section of the alert, it suggests repairing the agent, however, because it's a management server, they don't have agents but rather inbuilt ones. 
    Any ideas would be highly appreciated.
    Thanks, David.

    I've seen this before and I managed to resolve it by clearing the Health Service State cache on the management server in question. If the underlying issue is due to outdated configuration, this can force the server to refresh the correct configuration. If
    the underlying issue is different, this is still a good troubleshooting step to see whether or not the issue continues.
    To clear the cache, first stop the Health Service (Microsoft Monitoring Agent) service on the management server. Next, navigate to the application's install folder (for example, "C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server").
    Open the sub-folder "Health Service State" and delete all of the contents. Finally, restart the Health Service. The management server will re-download the configuration from the database and repopulate the Health Service State folder.
    Hopefully that helps!

  • I am getting a service start and stop alert while doing the windows server updates.

    HI
    I am getting a service start and stop alert while doing the windows server updates. Services are wmiApSrv , WPDBusEnum. Can you please help me to under stand why i am getting the service start and stop alert.
    Thanks & Regards
    Abhilash K Joy

    Hi,
    The WMI Performance Adapter (wmiApSrv) service provides performance library information from Windows Management Instrumentation (WMI) providers to clients on the network. This service only runs when Performance Data Helper is activated.
    This service is installed by default and its startup type is Manual. When started in the default configuration it will log on using the Local System account.
    You can try troubleshooting the issue using Clean Boot to check if the issue is related to third-party software.
    How to perform a clean boot in Windows
    http://support.microsoft.com/kb/929135/en-us
    Best Regards,
    Mandy
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • 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
              

  • How to stop and start Managed Server using weblogicServer

    Hi
    We are new.
    We have 2 managed servers and an Admin Server.
    We're trying to use the command line to stop/start our Managed Server.
    Could someone share examples on how one could write the command line that's similar to the WLS console Server Start tab ?
    We have a couple of classpaths and a bunch a arguments;
    When we tried to start one of the managed server it defaults to use some other settings as opposed to the ones in Server Start tab.
    What did we do wrong ?
    Thanks

    Hi,
    Follow the below links,each n every links have various methods and example for starting and stopping of Weblogic services
    We have 2 managed servers and an Admin Server.
    We're trying to use the command line to stop/start our Managed Server.http://docs.oracle.com/cd/E15523_01/core.1111/e10105/start.htm#CIHBIGCD
    We have a couple of classpaths and a bunch a arguments;http://docs.oracle.com/cd/E13222_01/wls/docs90/admin_ref/weblogicServer.html#frequently_used_optional_arguments
    http://docs.oracle.com/cd/E13222_01/wls/docs90/admin_ref/weblogicServer.html#1008628
    Regards
    Fabian

  • Stop managed server without node manager and admin server

    What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
    (I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
    (The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
    UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
    Edited by: user12163080 on Jun 24, 2010 4:40 AM

    Hai,
    I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
    "The start command starts Managed Servers or clusters in a domain using Node Manager.
    To use the start command, WLST must be connected to a running Administration Server.
    To start Managed Servers without requiring a running Administration Server, use the
    nmStart command with WLST connected to Node Manager."
    "You shut down a server to which WLST is connected by entering the shutdown command
    without any arguments.
    When connected to a Managed Server instance, you only use the shutdown command to shut
    down the Managed Server instance to which WLST is connected; you cannot shut down another
    server while connected to a Managed Server instance.
    WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
    Server, Node Manager must be running.
    In the event of an error, the command returns"
    They are two option if you are using adminserver then we can stop the any Managed server.
    The option is if you are using the nodemanager without admin server we can stop the any Managed server.
    The last final solution to kill the particular Managed server pid.
    Regards,
    S.vinoth babu

  • Health Service Heartbeat Failure Alert for Generated when one Management Server Down,

    Hi,
    I have Two Management Server, every one manage about 100 server, when one Management Server goes down unexpected, I receive 100 Alert for 100 Server Health Service Heartbeat Failure.
    My Question, why when the Management Server down, it send that all Managed agent Health Service Heartbeat Failure?
    Is there a way to change this?

    SCOM 2012 agent will autofailover when primary server is down. You can check the failover management server by using the following powershell cmdlet:
    #Verify Failover for Agents reporting to MS1
    $Agents = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq 'MS1.DOMAIN.COM'}
    $Agents | sort | foreach {
    Write-Host "";
    "Agent :: " + $_.Name;
    "--Primary MS :: " + ($_.GetPrimaryManagementServer()).ComputerName;
    $failoverServers = $_.getFailoverManagementServers();
    foreach ($managementServer in $failoverServers) {
    "--Failover MS :: " + ($managementServer.ComputerName);
    Write-Host "";
    http://www.systemcentercentral.com/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr/

  • Server stop problem with node manager

    Hi ,
    I get this error often when I try to stop a managed server via the nodemanager
    from the admin console or from the weblogic.Admin command. The server does not
    stop and it goes into an unknown state and I have to do a force shutdown
    [java] Error: [Could not execute command shutdown for server xxx via the N e Manager
    - reason: [__COMMAND_EXCEPTION__Request: failed to execute command ' utdown' on
    server 'xxx - reason: '[Unable to send shutdown request to server.> ].]
    [java] Start server side stack trace: [java] weblogic.nodemanager.NodeManagerException:
    [Could not execute comman shutdown for server xxx via the Node Manager - reason:
    [__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' on server 'xxx
    - reason: '[Unable o send shutdown request to server.]'> ].] [java] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
    gerRuntime.java:472) [java] at weblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
    time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method) [java]
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(D amicMBeanImpl.java:732)
    [java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicM anImpl.java:714)
    [java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1557)
    [java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1525)
    [java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

    Hi Anil,
    A little more information might be helpful. Which version are you talking
    about ? What is the server state when you issue the command ? Is the server
    very busy. Are you able to get the server state from the nodemanager when
    the server is running ? Are you able to communicate from admin server ->
    nodemanager <-> managed server ?
    cheers,
    gaurav.
    "Anil Jacob" <[email protected]> wrote in message
    news:3fb16b7c$[email protected]..
    >
    Hi ,
    I get this error often when I try to stop a managed server via thenodemanager
    from the admin console or from the weblogic.Admin command. The server doesnot
    stop and it goes into an unknown state and I have to do a force shutdown
    [java] Error: [Could not execute command shutdown for server xxx via the N
    e Manager> - reason: [__COMMAND_EXCEPTION__Request: failed to execute command 'utdown' on> server 'xxx - reason: '[Unable to send shutdown request to server.> .]
    [java] Start server side stack trace: [java]weblogic.nodemanager.NodeManagerException:
    [Could not execute comman shutdown for server xxx via the Node Manager -
    reason:> [__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' onserver 'xxx> - reason: '[Unable o send shutdown request to server.'> ].] [java] atweblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
    gerRuntime.java:472) [java] atweblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
    time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method)[java]
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DamicMBeanImpl.java:732)
    [java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicManImpl.java:714)
    [java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1557)
    [java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1525)
    [java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

  • 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.

  • OIM Managed server is frequently reaching maximum data sources count

    Hi All,
    We are using OIM 11.1.1.3.0 , Weblogic Version 10.3.3,database 11.2.0.1 for one of our client bank . Recently we encountered a problem that my oim managed server is being overloaded ,when we check the error i see data sources reaching maximum count . We have increased the maximum count to 500 and still we are facing the same issue . We also find out dead-locks in the alert log . Now,i dont understand why data sources consumption is too high .
    Please let us know your valuable inputs on the specific areas where we can check this .
    Regards,
    Nag.

    Nag,
    You don't need the developer to understand what code is causing the issue. You can analyse these issues using JRockit Mission Control, check these:
    1-http://itnaf.org/2012/06/24/jrockit-flight-recorder-into-oim-environment/
    2-http://itnaf.org/2012/08/26/jrockit-flight-recorder-analysis-into-oam-11g-environment/
    I hope this helps,
    Thiago Leoncio.

Maybe you are looking for

  • Shopping cart approval

    Hi Experts, We have following scenario to be implemented: Item based approval is being used for approval of shopping cart. The approvers are determined in BADI. The approver for a line item is taken as the owner of cost center which is assigned to th

  • Cant get Itunes and ItunesU to sync

    I have just downloaded the new ItunesU app on my Ipad, but cant get it to sync with Itunes on my macmini. The Ipad is upto date software wise and I have tried deleting the app and reinstalling it but to no avail. When I sync to the mac mini it does n

  • Bug between JRockit and X11 forwarding via ssh

    I have encountered what appears to be a bug in the interaction of JRockit with X11 ssh forwarding. When running any Java GUI application on a remote machine using X11 forwarding via ssh, a variety of problems occur. For example: --- cut here --- % mi

  • [SOLVED] Gnome 2.26 upgrade. Seg faults during upgrade.

    Hello. I have an huge problem... Yesterday I've tried to update my ArchLinux and I've got seg faults from gconf during the upgrade and my gnome won't start. Nautilus, gnome-settings-daemon, etc... All of them with seg faults. Anyone with the same pro

  • My ipod won't connect to the internet but my friends ipod will and it's on an open network

    What should i do btw it's a 4th gen