Weblogic Health status goes to "Warning"

Hello All,
I am working in a company in which we receive thousands of requests per day, when there are peek times, some of our weblogic servers reports the health status as "warning", we are using clustering and load balancing, i have searched for possible solutions on the internet but they all indicates the tuning of weblogic e.g increasing the time interval, stuck thread count etc etc.....
is there any solid solution available to this problem, means which could really solve this, i tried many of these but unable to solve the problem, every day to solve the problem i have to bounce back "restart the weblogic instance", so please help me in this problem so that i do not have to restart my weblogic server instance again and again.
your help is highly appreciated.
P.s: we are using weblogic 10.3.5
Regards.
Mansoor.

Hi,
Some of the information which i can access is given below (this task is assigned to me but i am not weblogic admin)
- we are using jrocket.
-weblogic is 32 bit.
A snapshot of server log is given below
[memory ][Mon Nov 26 14:46:12 2012][07144] Running with 32 bit heap and compressed references.
[memory ][Mon Nov 26 14:46:12 2012][07144] GC mode: Static, strategy: Generational Concurrent Mark & Sweep
[memory ][Mon Nov 26 14:46:12 2012][07144] heap size: 1536000K, maximal heap size: 1536000K, nursery size: 384000K
[memory ][Mon Nov 26 14:46:12 2012][07144] <s>-<end>: GC <before>K-><after>K (<heap>K), <pause> ms
[memory ][Mon Nov 26 14:46:12 2012][07144] <s/start> - start time of collection (seconds since jvm start)
[memory ][Mon Nov 26 14:46:12 2012][07144] <end> - end time of collection (seconds since jvm start)
[memory ][Mon Nov 26 14:46:12 2012][07144] <before> - memory used by objects before collection (KB)
[memory ][Mon Nov 26 14:46:12 2012][07144] <after> - memory used by objects after collection (KB)
[memory ][Mon Nov 26 14:46:12 2012][07144] <heap> - size of heap after collection (KB)
[memory ][Mon Nov 26 14:46:12 2012][07144] <pause> - total sum of pauses during collection (milliseconds)
[memory ][Mon Nov 26 14:46:12 2012][07144] run with -Xverbose:gcpause to see individual pauses
[JRockit] Management server started on port 57032, ssl=false, authenticate=false.
[memory ][Mon Nov 26 14:46:19 2012][07144] 6.891: parallel nursery GC 432860K->161756K (1536000K), 56.218 ms
[memory ][Mon Nov 26 14:47:14 2012][07144] 62.086: parallel nursery GC 480873K->201412K (1536000K), 35.692 ms
[memory ][Wed Nov 28 07:51:50 2012][07144] 147933.627-147938.089: GC 1281600K->1276830K (1536000K), sum of pauses 557.423 ms
[memory ][Wed Nov 28 07:51:55 2012][07144] 147938.168-147942.452: GC 1280000K->1276826K (1536000K), sum of pauses 41.780 ms
[memory ][Wed Nov 28 07:52:07 2012][07144] 147942.533-147954.871: GC 1286400K->1276836K (1536000K), sum of pauses 8197.144 ms
[memory ][Wed Nov 28 07:52:07 2012][07144] Throwing OutOfMemory: allocLargeObjectOrArray - Object size: 16777232, Num elements: 4194304
[memory ][Wed Nov 28 07:52:10 2012][07144] 147954.956-147957.579: GC 1283200K->757041K (1536000K), sum of pauses 340.881 ms
[memory ][Wed Nov 28 07:52:12 2012][07144] Changing GC strategy to Generational Concurrent Mark & Sweep
[memory ][Wed Nov 28 07:52:13 2012][07144] 147957.659-147960.479: GC 760241K->861430K (1536000K), sum of pauses 488.982 ms
[memory ][Wed Nov 28 07:52:16 2012][07144] 147960.566-147963.376: GC 863268K->761200K (1536000K), sum of pauses 366.075 ms
[memory ][Wed Nov 28 07:53:09 2012][07144] 148013.685-148016.781: GC 813168K->920501K (1536000K), sum of pauses 773.052 ms
[memory ][Wed Nov 28 08:06:33 2012][07144] 148820.343: parallel nursery GC 1168533K->1018744K (1536000K), 893.296 ms
[memory ][Wed Nov 28 08:06:34 2012][07144] 148821.616: parallel nursery GC 1377488K->1201126K (1536000K), 503.901 ms
[memory ][Wed Nov 28 08:06:35 2012][07144] 148822.326: parallel nursery GC 1489509K->1536000K (1536000K), 408.912 ms
[memory ][Wed Nov 28 08:06:38 2012][07144] Changing GC strategy to Generational Concurrent Mark, Parallel Sweep
[memory ][Wed Nov 28 08:06:39 2012][07144] 148821.258-148826.868: GC 1052344K->1281600K (1536000K), sum of pauses 1236.701 ms
[memory ][Wed Nov 28 08:06:44 2012][07144] 148826.964-148831.537: GC 1433600K->1393957K (1536000K), sum of pauses 1067.819 ms
[memory ][Wed Nov 28 08:06:48 2012][07144] 148831.627-148835.880: GC 1536000K->1483200K (1536000K), sum of pauses 819.866 ms
[memory ][Wed Nov 28 08:06:52 2012][07144] 148835.958-148840.043: GC 1502400K->1428227K (1536000K), sum of pauses 696.051 ms
[memory ][Wed Nov 28 08:06:58 2012][07144] 148840.121-148845.840: GC 1428227K->1421591K (1536000K), sum of pauses 2038.479 ms
[memory ][Wed Nov 28 08:07:12 2012][07144] 148845.919-148859.476: GC 1422400K->1297787K (1536000K), sum of pauses 9836.237 ms
[memory ][Wed Nov 28 08:07:12 2012][07144] Throwing OutOfMemory: allocLargeObjectOrArray - Object size: 353040, Num elements: 88256
[memory ][Wed Nov 28 08:07:13 2012][07144] 148859.555-148861.120: GC 1302400K->665578K (1536000K), sum of pauses 226.632 ms
[memory ][Wed Nov 28 08:07:13 2012][07144] Changing GC strategy to Generational Concurrent Mark & Sweep
[memory ][Wed Nov 28 08:07:14 2012][07144] 148861.199-148861.419: GC 680200K->157010K (1536000K), sum of pauses 137.983 ms
[memory ][Wed Nov 28 12:19:20 2012][07144] 163987.323: parallel nursery GC 449982K->141655K (1536000K), 60.356 ms
[memory ][Wed Nov 28 16:17:21 2012][07144] 178268.807: parallel nursery GC 450605K->163172K (1536000K), 67.881 ms
[memory ][Wed Nov 28 19:57:51 2012][07144] 191498.731: parallel nursery GC 451275K->163737K (1536000K), 54.393 ms
A snapshot of managed server thread dump is given below
2012/11/28 05:08:49.762 INFO <(DBProcessor.java:158)> [1149165250] -
Execution Time: 4.014
2012/11/28 05:10:06.928 INFO <(ARInvoiceWebservice.java:81)> [1149165250] -
Inquiry Webservice overall request execution time: 4821.064
2012/11/28 05:10:30.652 INFO <(SOAPHandler.java:116)> [1149165250] -
******** soapMessage in fault ******** SOAPMessageImpl[SOAPPartImpl[SOAPEnvelopeImpl[nullSOAPBody[<env:Fault><faultcode>env:Server</faultcode><faultstring>Exception during processing: java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 65552, Num elements: 16384 (see Fault Detail for stacktrace)</faultstring><detail><bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 65552, Num elements: 16384
     at weblogic.utils.collections.CircularQueue.expandQueue(CircularQueue.java:90)
     at weblogic.utils.collections.CircularQueue.add(CircularQueue.java:108)
     at weblogic.xml.babel.stream.XMLInputStreamBase.add(XMLInputStreamBase.java:151)
     at weblogic.xml.babel.adapters.DOMAdapter.adaptNamespace(DOMAdapter.java:107)
     at weblogic.xml.babel.adapters.DOMAdapter.adaptAttribute(DOMAdapter.java:127)
     at weblogic.xml.babel.adapters.DOMAdapter.adaptElement(DOMAdapter.java:158)
     at weblogic.xml.babel.adapters.DOMAdapter.adapt(DOMAdapter.java:71)
     at weblogic.xml.babel.adapters.DOMAdapter.recurseChildren(DOMAdapter.java:197)
     at weblogic.xml.babel.adapters.DOMAdapter.adaptElement(DOMAdapter.java:161)
     at weblogic.xml.babel.adapters.DOMAdapter.adapt(DOMAdapter.java:71)
     at weblogic.xml.babel.adapters.DOMAdapter.recurseChildren(DOMAdapter.java:197)
     at weblogic.xml.babel.adapters.DOMAdapter.adaptElement(DOMAdapter.java:161)
     at weblogic.xml.babel.adapters.DOMAdapter.adapt(DOMAdapter.java:71)
     at weblogic.xml.babel.adapters.DOMAdapter.recurseChildren(DOMAdapter.java:197)
     at weblogic.xml.babel.adapters.DOMAdapter.adaptElement(DOMAdapter.java:161)
     at weblogic.xml.babel.adapters.DOMAdapter.adapt(DOMAdapter.java:71)
     at weblogic.xml.babel.adapters.DOMAdapter.adaptDocument(DOMAdapter.java:96)
     at weblogic.xml.babel.adapters.DOMAdapter.adapt(DOMAdapter.java:64)
     at weblogic.xml.babel.stream.DOMInputStream.open(DOMInputStream.java:53)
     at weblogic.xml.babel.stream.XMLInputStreamFactoryImpl.newInputStream(XMLInputStreamFactoryImpl.java:95)
     at weblogic.xml.schema.binding.internal.builtin.DocumentCodec.serialize(DocumentCodec.java:53)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:192)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:178)
     at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:335)
     at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:304)
     at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:651)
     at weblogic.webservice.core.handler.InvokeHandler.handleRequest(InvokeHandler.java:151)
     at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:144)
     at weblogic.webservice.core.DefaultOperation.process(DefaultOperation.java:551)
     at weblogic.webservice.server.Dispatcher.process(Dispatcher.java:204)
     at weblogic.webservice.server.Dispatcher.doDispatch(Dispatcher.java:175)
     at weblogic.webservice.server.Dispatcher.dispatch(Dispatcher.java:97)
     at weblogic.webservice.server.WebServiceManager.dispatch(WebServiceManager.java:102)
     at weblogic.webservice.server.servlet.WebServiceServlet.serverSideInvoke(WebServiceServlet.java:321)
     at weblogic.webservice.server.servlet.ServletBase.doPost(ServletBase.java:454)
     at weblogic.webservice.server.servlet.WebServiceServlet.doPost(WebServiceServlet.java:293)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
</bea_fault:stacktrace></detail></env:Fault>]]]]
2012/11/28 05:22:07.188 INFO <(SOAPHandler.java:116)> [2145221434] -
******** soapMessage in fault ******** SOAPMessageImpl[SOAPPartImpl[SOAPEnvelopeImpl[nullSOAPBody[<env:Fault><faultcode>env:Server</faultcode><faultstring>Exception during processing: java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 235368, Num elements: 58837 (see Fault Detail for stacktrace)</faultstring><detail><bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 235368, Num elements: 58837
     at java.util.Arrays.copyOf(Arrays.java:2760)
     at java.util.Arrays.copyOf(Arrays.java:2734)
     at java.util.ArrayList.ensureCapacity(ArrayList.java:167)
     at java.util.ArrayList.add(ArrayList.java:351)
     at weblogic.xml.xmlnode.XMLNode.addChild(XMLNode.java:479)
     at weblogic.xml.xmlnode.XMLNode.addChild(XMLNode.java:435)
     at weblogic.xml.xmlnode.XMLNode.addChild(XMLNode.java:514)
     at weblogic.xml.xmlnode.XMLNodeWriter.write(XMLNodeWriter.java:55)
     at weblogic.xml.xmlnode.XMLNodeWriter.write(XMLNodeWriter.java:105)
     at weblogic.xml.babel.stream.XMLOutputStreamBase.writeXMLEvent(XMLOutputStreamBase.java:77)
     at weblogic.xml.babel.stream.XMLOutputStreamBase.write(XMLOutputStreamBase.java:99)
     at weblogic.xml.babel.stream.XMLOutputStreamBase.flush(XMLOutputStreamBase.java:208)
     at weblogic.xml.babel.stream.XMLOutputStreamBase.flush(XMLOutputStreamBase.java:215)
     at weblogic.xml.babel.stream.XMLOutputStreamBase.addXMLEvent(XMLOutputStreamBase.java:125)
     at weblogic.xml.babel.stream.XMLOutputStreamBase.add(XMLOutputStreamBase.java:173)
     at weblogic.xml.schema.binding.internal.builtin.DocumentCodec.serialize(DocumentCodec.java:71)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:192)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:178)
     at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:335)
     at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:304)
     at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:651)
     at weblogic.webservice.core.handler.InvokeHandler.handleRequest(InvokeHandler.java:151)
     at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:144)
     at weblogic.webservice.core.DefaultOperation.process(DefaultOperation.java:551)
     at weblogic.webservice.server.Dispatcher.process(Dispatcher.java:204)
     at weblogic.webservice.server.Dispatcher.doDispatch(Dispatcher.java:175)
     at weblogic.webservice.server.Dispatcher.dispatch(Dispatcher.java:97)
     at weblogic.webservice.server.WebServiceManager.dispatch(WebServiceManager.java:102)
     at weblogic.webservice.server.servlet.WebServiceServlet.serverSideInvoke(WebServiceServlet.java:321)
     at weblogic.webservice.server.servlet.ServletBase.doPost(ServletBase.java:454)
     at weblogic.webservice.server.servlet.WebServiceServlet.doPost(WebServiceServlet.java:293)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
</bea_fault:stacktrace></detail></env:Fault>]]]]
Ps: " Do you consider that maximizing the heap space will solve the problem definetly??"
Hope you will understand and will sugest a better solution.
your help is highly appreciated.
Regards.
Mansoor.

Similar Messages

How to determine weblogic health status column when it is in NOT OK via wlst?

Dear Legends,
Is there a command to determine weblogic managed or admin servers HEALTH COLUMN Status? Because some times in STATE Column it would be RUNNING and in HEALTH Column it would be in "NOT OK" or the OK will not be visible.
Thanks,
Karthik

Just in case others have the same question, I have determined that the CLI tools can be used to query the file services without any apparent detrimental effects while using our leopard server 10.5.3 in a workgroup configuration. Hence the names of AFP users can be determined from the command line by:
sudo serveradmin command afp:command = getConnectedUsers | grep name
and the smb users can be found with:
sudo serveradmin command smb:command = getConnectedUsers | grep name
Hope that helps
-csl

Managed server not showing health status on AdminServer

Hello - we are running into a situation where, in the admin console some nodes do not show a Health status. Most of the other nodes show "OK".
Weblogic Version: 12c
OS : RedHat Enterprise 6.0
Drilling down to figure this out, we attach using WLST to the node itself, goto the serverRuntim() section to look at the status, we we see the following:
wls:/domain/serverConfig> serverRuntime()
Location changed to serverRuntime tree. This is a read-only tree with ServerRuntimeMBean as the root.
For more help, use help(serverRuntime)
wls:/domain/serverRuntime> ls()
dr-- ApplicationRuntimes
dr-- AsyncReplicationRuntime
dr-- WseeWsrmRuntime
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 704, in ls
File "<iostream>", line 1847, in raiseWLSTException
WLSTException: Error occured while performing ls : Error while retrieving attribute names and values : javax.management.RuntimeMBeanException: MBean getAttribute failed: java.lang.IllegalStateException: Admin server identity is unavailable. The managed server may not be connected to the admin server
Use dumpStack() to view the full stacktrace
wls:/domain/serverRuntime>
When connecting to other nodes on the same machine, we see lots of great information. This tells me that the node is unable to talk to the Admin server correctly. Yet, stopping and starting the node from the admin server works fine (and is out current way to resolve the issue).
Ideas on where to look for the underlying cause of this problem?
Or how to force the node to attempt to reconnect to the Admin server?
Thanks.

Hi,
It could be if server came out of cluster due to issue with cluster and connection between admin server and managed server broke. At such stage even if server is healthy, it will not present in admin server or will be shown as failed.
To start with did you first checked if your server is UP and taking request. This you can achieve by doing any of the below,
1. PING test to managed server. It will show if there are any packet loss.
2. Check server access log to confirm if it is serving request in the runtime.
3. "telnet" to the ip:port pair and also check if process id is alive.
Also check server logs for cluster error. If server is healthy but not presented in admin console, then only restarting the server will re-create communication between admin server and managed server which will then display correct status on console. And if server itself is down, go for server restart.
Thanks,
Ranjan

Group Policy SYSVOL replication + health status

Is there a way for me to programmatically check the health status of a specific GPO in SYSVOL across all Domain Controllers?
How do I force a "Good" copy of a GPO to all other DC's?

Hi,
>>How do I force a "Good" copy of a GPO to all other DC's?
As Alex suggested, we can do a non-authoritative restore for Sysvol on un-healthy domain controllers to make them sync their Sysvol from a healthy one.
Regarding how to perform non-authoritative restore for Sysvol, this depends on what replication mechanism we use for replicating Sysvol.
If Sysvol is replicated by FRS, we can follow the procedure described in the following article to do a non-authoritative restore.
Using the BurFlags registry key to reinitialize File Replication Service replica sets
http://support.microsoft.com/kb/290762?wa=wsignin1.0
If Sysvol is replicated by DFSR, we can follow the procedure described in the following article to do a non-authoritative restore.
How to force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)
http://support.microsoft.com/kb/2218556
>>Is there a way for me to programmatically check the health status of a specific GPO in SYSVOL across all Domain Controllers?
We can check event logs in Event Viewer on domain controllers. If something goes wrong with Sysvol replication, error events will be logged under Applications and Services Logs\FRS or DFSR Replication.
Best regards,
Frank Shen
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]

Report is going in warning r12

Hi expert,
many times my users complain me all reports is going in warning. in this case i check the manager if the all manager are active and the manager's actual and target are different. i down all manager and after down all manager completely run the cmclean.sql script. and up the manager.
the issue is solved.
but many times i watch managers are working well and actual and target are same. till all reports are going in warning. in the same case i repeat the same way to solve the problem.
i want to know is there any permanent solution for this error or any other method to solve this type of problem in daily cases.
this type of issue raised on my production database..
also plz suggest me how can i tune my ebs r12 production database?????????
thanks & regards
pritesh ranjan

Hi,
many time when i down the manager all manager are down successfully but some time FNDLIBR (internal manager) not down after wait longtime (15-20 min)
Some time in the sense, are you able to figure out the instances this would occur or is it randomly.
How are you finding the FNDLIBR run? Is it through: ps -ef | grep FNDLIBR
If yes, I suggest you to give some time as the process kill take some time plus as long as your shutdown script ends up with a value '0' (zero), you are good.
then i kill the FNDLIBR manger in test instance and then start the manager and the test server work well.
Assuming you have shutdown the Application (which will include CM most importantly to our subject), and still if it hangs you may use the force kill option from OS. Since you have already performed the appropriate way of shutting down. But I also suggest you run the "Apps shutdown script" again.
i want to know can i kill FNDLIBR manager when it is not going to down after wait (15-20 min) in production instance. if i do such type of activity in production instance is it leave any bad impact on production instance.
In addition to my comments above, I suggest you to check for CM log files and also check the below note to be on safe side:
Concurrent Processing - CCM.sql Diagnostic Script to Diagnose Common Concurrent Manager Issues (Doc ID 171855.1)
Thanks &
Best Regards,

IPod frozen than working... how to check it's health status?

A friend of mine gave me a 20GB classic iPod, it was supposed to be broken, took it home, connected to the usb cable and the icon to get to service it showed up, nothing else to do, no way to access diagnostics, nothing nothing nothing.
Now, connected again to my old Dual MDD it mounted on the desktop and seems to work, what and how do I check its health status?
It would turn very useful for me to have this thing to work so much that I already thought, in case it was the disc, to change it but now how do I get to make sure it doesn't fail again?
Could it be a battery problem?
thanks all for your attention
Giovanni
<Edited by Host>

BTW, I did SMC and PRAM reset and it was the same in Lion when I bought the MBPR. It was working for days until I started noticing disconnect and reconnect iPhone 4S.

Weblogic domain status always down from Fusion Middleware Console

Hi Guys
Weblogic domain status always down from Fusion Middleware Console but however my Webdomain is Up and running.
At another level, I have the same problem with applications status. These applications are Up and running but visible status down too.
Platform: AIX 5.3 TL8
Weblogic Server: 10.3.2
Fusion Middleware Controle: 11.1.1.2.0
Any idea ?
bests regards
Denis Jeanneret

Hi,
I have similar setup and the WebTier component shows as down.
After some research I have come to the conclusion that some files have been missed in the EM packaging with the Web Center and OHS components.
Am following up with iAS development on this issue..
Check
http://<adminHost>:<adminPort>/dms
Click on Aggregate Metrics > scroll down to opmn_response and opmn_response_component. See if the instance is registered.
In my case, the opmn_response does not have the componentname in it but opmn_response_component seems to be fine.
Regards
Kotti

TD100 VMWare ESXi 3.5 U4 RAID health status

Hi,
i am using a TD100 (6429) with an 8k RAID adapter with VMWare ESXi 3.5 U4. The system is working fine with one exception:
I can not monitor the health status of my 8k RAID. It wont show up on the health status page in the VM client. Therefore the only way to check the status would be to look at the front lights of the server itself. That does not seem to be a good solution since it is out of sight in the server room.
In the VM forums i just found that some kind of CIM would be needed.
Is there any way to resolve this issue?

welcome to the forum!
the following document should help in using VMWare with IBM Director and ServeRAID Manager:
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101047
ThinkStation C20
ThinkPad X1C · X220 · X60T · s30 · 600

Windows Operating System Health Status Not Monitoring

Hi, I have installed SCOM agent to all my servers (Picture attached) and found some windows server not report health status and also i have already Installed Windows server Monitoring pack
I have run below list troubleshooting step but no luck on this
1. Flush agent cash and try refresh the agent
2. remove agent and wait for 3 days and install agent again
3. remove agent clear registry, re installed
but the result is same, even scom server itself windows health services show as not monitored,
Could anyone help on this
<< picture attached >>

Hi,
Did you import the below management pack for Winddows Server Operating System?
https://www.microsoft.com/en-hk/download/details.aspx?id=9296
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

KT4AV-L (MSI 6712-080) Need "PC Health Status" Port Map...or?

I run Linux exclusively and would like to get ahold of any technical information that would allow me to poll the "PC Health Status" information (Voltages, temps fan speed, etc.) from a Linux Desktop or Command Line environment.
So far I have found nothing to get me started. Does anyone have suggestions as to where I might look further?

Looks like somebody in Japan already beat me to the punch:
http://freshmeat.net/projects/xmbmon/

How to get rid of the weblogic.kernel.Default errors and warning?

Hi there,
When i'm running my application deployed on WLS8.1 SP3 and the application is running fine, but the following error and warnings were thrown.
2004-08-05 11:26:30,453 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] ERROR com.bea.wlw.runtime.core.util.Config - Failed to obtain connection to datasource=cgDataSource, using generic DB properties
<Aug 5, 2004 11:26:30 AM SGT> <Error> <WLW> <000000> <Failed to obtain connection to datasource=cgDataSource, using generic DB properties>
2004-08-05 11:27:12,281 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.default.elementattributes
2004-08-05 11:27:12,282 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.default.elementattributes', using defaults.
2004-08-05 11:27:12,308 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.system.groupIdCache.elementattributes
2004-08-05 11:27:12,308 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.system.groupIdCache.elementattributes', using defaults.
2004-08-05 11:27:12,386 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.region.CodeTableCache.elementattributes
2004-08-05 11:27:12,386 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.region.CodeTableCache.elementattributes', using defaults.
2004-08-05 11:27:13,527 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN com.bea.wlw.netui.script.el.NetUIReadVariableResolver - Could not create a ContextFactory for type "com.bea.netuix.servlets.script.PortalVariableResolver$PortalContextFactory" because the ContextFactory implementation class could not be found.
May i know why this is so? How to get rid of these error and warnings?
Thanks
Derek
Message was edited by derekchan at Aug 4, 2004 8:41 PM
Message was edited by derekchan at Aug 4, 2004 8:42 PM

you didnt seem to have configured the datasource / connection pool / database control with proper db properties
you should check your configuration to see if you have done it right and then you should check your application and the properties settings in the controls to ensure they are right.

Plug in Seagate USB drive and status goes from green to yellow

This is somewhat different from what others have posted.
When I plug in or turn on my Seagate 160 gig drive on the base station USB, the status light switches to yellow and no more wireless. The disk works when direct connected to the iMac. Epson printer works fine in the base station USB.
Anybody have these symptoms?
Rick

It is formatted FAT32 and works fine on my PC (I recently jumped ship to Mac) and connected to the iMac.
I don't understand your final comment. Once the disk goes 'ready', the wireless is down and I can no longer access the base station. If I turn the Seagate off, the light goes green again in about 5 seconds.
To anticipate: no, I have not yet attempted to 'talk' to the base via hard wired ethernet. That is, I have not seen any error text.

Idoc failed with status 51 for Warning/Information messages

Hi All,
We are trying to create some Sales Orders with the help of Idocs. We are facing some problem as mentioned below.
1.There are some warning messages/information messages written in standard Sales Order User Exit USEREXIT_SAVE_DOCUMENT_PREPARE
2.As soon as the Idoc processing reaches any of these messages, it considers them as ERROR message and Idoc fails with the status as 51 which is not expected.
3.Also, I see that the Sales Order is saved with the data that has been passed in the Idoc.
Is this the standard behavior ?? (Or) Is there any EDI related configuration setting which can be used to suppress these kind of messages in Idoc Processing ??
Any help on this would be highly appreciated.
Thanks,
Babu Kilari

if your IDOC has status 51 then it is not posted, hence your sales order cannot be created from this IDOC. of course this error behaviour can be originated by the user exit.
please read OSS note Note 747631 - Some tips when testing idoc_input_orders

Needed Message ID for Weblogic SHUTDOWN Status

Hi
We have our OBIEE11g Platform running in Windows platform.
We have the Weblogic Admin & Managed Services as windows Services
My Agenda is to monitor the the Weblogic Admin/managed services startup/stop based on messageID.
Successfully enabled the WL Diagnostics Module(watch/notification) to trigger an email for the Message ID <BEA-000360> "<Server started in RUNNING mode>" ,
but i could not able to find the relevant Message_ID for the SHUTDOWN status or Stopping mode, please let me know what would be the appropriate similar to the above ?
Will this "<BEA-000396> <Server shutdown has been requested by weblogic> can act as the correct messageID for shutdown?
Thanks

Hi
I reckon a good monitoring would be BEA-000365, then you would be aware of any server's status changes.
Cheers,
Vlad
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question.

Weblog server restart goes idle

i am trying weblogic admin server in unix box.
but the process goes idle after the below line on the console.
<May 3, 2012 2:51:43 PM BST> <Notice> <Management> <BEA-140005> <Loading domain configuration from configuration repository at /wls_domains/flwhl/flwhldA/./config.xml.>
clueless.
pls reply, if any idea....

Hi,
I need some information regarding the following
points.
Assuming that a JMS Provider goes down (server
restart) Config: TIBCO (Provider) client on Weblogic
1> Does a MessageProducer explicitly need to invoke a
method on the Connection for the ExceptionListener to
be notified?I suppose it is the responsibilit of JMS provider.So i believe it is automatically notified by the provider.
a) If yes, then why is a Listener required, coz the
e method invocation itself will raise a JMS Exception
that canTrue..It is not necessary to have a listener.If you dont have listener,you will realise that the connection is staled when you invoke a method on the connection.So you dont know at wht point of program you will get this exception.U need to protect the whole message producing blcok with a failover logic.If u register a listener you can do that at one place
     be caught and handled (re-connection)
b) If no, is it required for the re-connection code
e to be on a separate thread than the one that
implements the
     Listener Not necessary
2> For re-connection, is the complete cycle
InitContext - ConnectionFactory - Connection required
or a partial one works?It depends on the point of failure,if you fault tolerent architecture with multiple naming servers to retrieve JMS admin objects and multiple jms brokers,you can do the whole process with other set of details.
a) I checked it on a Weblogic 6.1 queue and found
d that although the same ConnectionFactory can be
used, the Queue
     required a JNDI lookup.I am not sure.
3> Lastly, if a cache of administered objects
(ConnectionFactory, Destination) is maintained (Using
a ServiceLocator),
is there any way to find out if the server on
on which these objects are configured is alive,
or is the Connection creation process the only way
way to ascertain this?I dont think there is any other way except knowing with a naming exception
>
Thanks in Advance
Anshu.

Weblogic Health status goes to "Warning"

Similar Messages

Maybe you are looking for