WebLogic 10.3.6 logging health messages to stdout

Hello,
I have a 10.3.6 instance running with JRE 1.7.0_25-b15.
The server is sending health related info messages to stdout.
"com.bea.logging.BaseLogger log Info: XX% of the total memory in the server is free"
2 messages are logged at a time, but not on a consistent interval.
We send the stdout and stderr to a log file via the -Dweblogic.Stdout and -Dweblogic.Stderr properties. These messages are adding to the
log file size and frankly are an annoyance. Is there any additional settings/properties/filters needed to eliminate these messages?
These are the instance's settings with regard to logging:
- Minimum severity to log: Warning
- Log File Severity level: Warning
- Standard Out Severity level: Off
- Memory Buffer Severity level: Warning
- Redirect Stdout Logging: disabled
- Redirect Stderr Logging: disabled
- Logging implementation: JDK
Thanks in advance.

Similar Messages

Logging SOAP messages

I need help on how to use handlers in Weblogic Workshop web services. I have the following logging handler from the bea documentation site.
Now, if I want to log my SOAP messages on the server side, do I just need to put the annotation:
* @jws:handler operation="handler.ConsoleLoggingHandler"
at the top of my JWS file? If that is the case, I don't see any messages being logged. Any help will be greatly appreciated.
Thanks.
gtata
package handler;
import java.util.Iterator;
import javax.xml.rpc.handler.MessageContext;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import javax.xml.soap.SOAPElement;
// for readability, using weblogic API instead of javax.xml.rpc.handler.GenericHandler
// See http://edocs.beasys.com/wls/docs81/webserv/interceptors.html#1060763
import weblogic.webservice.GenericHandler;
* Purpose: Log all messages to the Server console
public class ConsoleLoggingHandler extends GenericHandler
* Handles incoming web service requests and outgoing callback requests
public boolean handleRequest(MessageContext mc)
logSoapMessage(mc, "handleRequest");
return true;
* Handles outgoing web service responses and incoming callback responses
public boolean handleResponse(MessageContext mc)
this.logSoapMessage(mc, "handleResponse");
return true;
* Handles SOAP Faults that may occur during message processing
public boolean handleFault(MessageContext mc)
this.logSoapMessage(mc, "handleFault");
return true;
* Log the message to the server console using System.out
protected void logSoapMessage(MessageContext mc, String eventType)
try
System.out.println("*****************************");
System.out.println("Event: "+eventType);
System.out.println("Endpoint Method: " + getMethodName(mc));
System.out.println("Soap message is: \n " +
com.bea.wlw.runtime.jws.soap.util.SAAJUtil.SOAPPart2String(
((SOAPMessageContext)mc).getMessage() ) + "\n");
System.out.println("*****************************");
catch( Exception e )
e.printStackTrace();
* Get the method Name from a SOAP Payload.
protected String getMethodName(MessageContext mc)
String operationName = null;
try
SOAPMessageContext messageContext = (SOAPMessageContext) mc;
// assume the operation name is the first element
// after SOAP:Body element
Iterator i = messageContext.
getMessage().getSOAPPart().getEnvelope().getBody().getChildElements();
while ( i.hasNext() )
Object obj = i.next();
if(obj instanceof SOAPElement)
SOAPElement e = (SOAPElement) obj;
operationName = e.getElementName().getLocalName();
break;
catch(Exception e)
e.printStackTrace();
return operationName;
}

You can use the logging and tracing functionality to write log statements anywhere in BPEL. refer http://wiki.open-esb.java.net/Wiki.jsp?page=LoggingFromWSBPELActivityInABusinessProcess . But you should keep in mind these are not soap messages that you log. They will be abstract WSDL message instances. If you want to log specifically the soap messages you need the support in HTTP-BC.
If you turn on logging you should see the line number of BPEL where it fails. That should give you some indication. I am not 100% sure, but in the logs, we should be logging the variable which was not initialized. I can't think of any other way to find out which variable caused this exception.
-Kiran Bhumana

Logging t3 messages

Hi,
Is there any way through which we can log t3 messages in weblogic?
Thanks

Hi,
Is there any way through which we can log t3 messages in weblogic?
Thanks

How to log the messages in program scheduled background

Hi all,
I have a program and it is to be scheduled to run in the background.
I want to log the messages within the program while running.
What could I do?
(The standard job log is not what I want)
Thanks.

Ignore my previous post. It is good that you posted this question, as I learnt something new. Try the code below.
Regarding help for why you require and why to go for application logs, refer this SAP Help
http://help.sap.com/saphelp_47x200/helpdata/en/2a/fa0223493111d182b70000e829fbfe/frameset.htm
DATA: ls_log TYPE bal_s_log.
DATA: p_log_handle TYPE balloghndl.
ls_log-extnumber = 'YMYTEST'.
ls_log-alprog = sy-repid.
CALL FUNCTION 'BAL_LOG_CREATE'
EXPORTING
    I_S_LOG                 = ls_log
IMPORTING
    E_LOG_HANDLE            = p_log_handle
EXCEPTIONS
    LOG_HEADER_INCONSISTENT = 1
    OTHERS                  = 2.
IF SY-SUBRC <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
data: l_s_msg TYPE bal_s_msg.
data: E_MSG_WAS_DISPLAYED type boolean.
data: E_MSG_WAS_LOGGED type boolean.
data: E_S_MSG_HANDLE type BALMSGHNDL.
l_s_msg-msgid = '00'.
l_s_msg-msgty = 'E'.
l_s_msg-msgno = '001'.
l_s_msg-msgv1 = 'This is a test message from 20130810'.
CALL FUNCTION 'BAL_LOG_MSG_ADD'
EXPORTING
    I_LOG_HANDLE              = p_log_handle
    I_S_MSG                   = l_s_msg
IMPORTING
   E_S_MSG_HANDLE            = E_S_MSG_HANDLE
   E_MSG_WAS_LOGGED          = E_MSG_WAS_LOGGED
   E_MSG_WAS_DISPLAYED       = E_MSG_WAS_DISPLAYED
EXCEPTIONS
   LOG_NOT_FOUND             = 1
   MSG_INCONSISTENT          = 2
   LOG_IS_FULL               = 3
   OTHERS                    = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
data: I_T_LOG_HANDLE type BAL_T_LOGH.
append p_log_handle to i_t_log_handle.
CALL FUNCTION 'BAL_DSP_LOG_DISPLAY'
EXPORTING
*   I_S_DISPLAY_PROFILE          =
    I_T_LOG_HANDLE               = i_t_log_handle
*   I_T_MSG_HANDLE               =
*   I_S_LOG_FILTER               =
*   I_S_MSG_FILTER               =
*   I_T_LOG_CONTEXT_FILTER       =
*   I_T_MSG_CONTEXT_FILTER       =
*   I_AMODAL                     = ' '
* IMPORTING
*   E_S_EXIT_COMMAND             =
EXCEPTIONS
   PROFILE_INCONSISTENT         = 1
   INTERNAL_ERROR               = 2
   NO_DATA_AVAILABLE            = 3
   NO_AUTHORITY                 = 4
   OTHERS                       = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Regards,
Subramanian V.

Developing the Wrapper class to log the message in XI server

Hi All,
We are trying to develop wrapper class on the SAP Logging API, in that I am unable to log the message in the log file(whose path is mentioned in the properties file).
We use this for storing when exception raised during message transformation due to certain error conditions...
Procedure:
My Wrapper class will take the parameters from Property file and store/log the message in the specified location,
This is working outside of XI environment
Please suggest how to make to work in XI environment
Also suggest do I need to do any configurations in SAP web As
Thanks,
venu.

HI,
With the above blog ref by Michal , see the below links also,
/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
/people/amjad-ali.khoja/blog/2005/12/16/slaw-a-new-logging-tracing-framework-for-xi
/people/amjad-ali.khoja/blog/2006/02/07/using-dom4j-in-xi--a-more-sophisticated-option-for-xml-processing-than-sap-xml-toolkit
Also my be useful..
/people/community.user/blog/2007/01/09/enterprise-soa-explorations-reflections-on-database-integration
/people/anne.tarnoruder/blog/2006/10/26/reusing-code-with-pdk-for-net
/people/piers.harding/blog/2006/05/18/ruby-on-rails-with-ajax
Regards
Chilla

How to log Synchornous Messages in XI

Hi,
how to log Synchornous Messages in XI ?

Michal has explained it clearly .....with screen shots
Check the below blog
The specified item was not found.
Thanks,
Karthik

Date format in log/error messages

Hi there,
Is there a way to change the date format in log/error messages in ttmesg.log & tterror.log files ?
In my log files, only the hour is specified but I wish I could get the day each single line has been logged.
Thanks in advance.
PS : I'm running TimesTen release 7.0.3 on a RedHat ES release 4

Yes, you just need to add the option -showdate into the ttendaemon.options file.
</p>
Please check out the section on Modifying informational messages in the Operations Guide.
</p>
Simon

OBIEE 10g UI shows logging in message while downloading a report.

Hi Experts,
We have a report on OBIEE Dashboard which show URLs (GO URLs) to download the report in .CSV format.
Most of the times, It works fine... However, sometimes the user clicks on the link, the report starts downloading but the page (on which the link was clicked) keeps showing Logging In message.
Has anyone faced this issue ever?
(We are using OBIEE 10.1.3.4.1 on Solaris)
Regards,
Vishal

Vishal,
It would be great if you can provide us the screen shot?
Thanks,

Logging Error Message in Console [Servlet Error]-[Cannot find FacesContex]

Hi,
I am using Web Application with JSF . but when i log in into the web appl everthing is fine but in back end i mean the console of RAD Tool having some logging Error message:
SRVE0026E: [Servlet Error]-[Cannot find FacesContext]: javax.servlet.jsp.JspException: Cannot find FacesContext
at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java(Compiled Code))
at com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java(Compiled Code))
at org.apache.jsp._index._jspService(_index.java:86)
at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java(Compiled Code))
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java(Compiled Code))
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java(Compiled Code))
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java(Compiled Code))
So could you please help me find out the solution for this :
While i am using the code in jsp page:
<%@taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@taglib uri="http://www.ibm.com/jsf/html_extended" prefix="hx"%>
<%@taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<TITLE>Web App
     <f:view>
          <h:outputText value="#{dataInfo.info}"/>
     </f:view>
</TITLE>
Suggest me the solution:
Regards,
Prabhat

This usually means that you call the JSF page the wrong way. Try something like http://hostname:port/servletcontextroot/faces/page.jspx
--olaf

Logging app messages into another file than server.log

Hello:
I'm working with Application Server Enterprise Edition 7 2004Q2 and I'd like logging application messages into another file than server.log.
I tried to set up a logging configuration file as
com.appname.handlers = java.util.logging.FileHandler
( where all packages in my application are named like com.appname.* )
and pass it as
-Djava.util.logging.config.file
But nothing happens. Indeed , no file is created.
I tried with
handlers = java.util.logging.FileHandler
and works fine but, obviusly, are wrote server messages too.
So, the problem is 'com.appname.handlers ' property, but I dont know why.
any workaround to perform this ?
what's wrong ?
Thanks in advance.
Best regards

Hi,
The samples are usaully in the samples directory of the appserver install dir. However, this might depend on the server install.
Anyway, samples can be downloaded from:
http://developers.sun.com/prodtech/appserver/reference/codesamples/index.html
This is a zip file with all the samples stuff
The actual code in there:
        // import for logging classes
        import java.util.logging.*;
        //Remove all handlers
        Handler[] h = logger.getHandlers();
        for (int i = 0; i < h.length; i++) {
            logger.removeHandler(h);
//Set it to its parent handler so that it gets NOT (by Robert) printed on the server log
// In the original sample this is set to true
logger.setUseParentHandlers(false);
The actual way of adding your own file log handler:
     // Create a file handler with a string as parameter for filename
      Handler fh = new FileHandler(<LOGFILENAME>);
       // Create a formatter to format the logger
       fh.setFormatter(new SimpleFormatter());
       // Add the handler to logger instance
       logger.addHandler(fh);See the javadocs for formatting stuff,
HTH Robert

Weblogic 6.1sp1 - Weblogic 6.1sp1 in different domain messaging bridge configuration

I'm trying to configure messaging bridge to send messages from WLS
          6.1sp1 to WLS 6.1sp1 in another domain and seems it doesn't work. I'm
          using following configuration, any idea?
          <MessagingBridge Name="BatchBridge"
          SourceDestination="BatchBridgeDestination" Started="true"
          TargetDestination="BatchBridgeSource" Targets="myserver"/>
          <BridgeDestination
          AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          Name="BatchBridgeSource"
          Properties="ConnectionURL=t3://localhost:7001;DestinationJNDIName=ngfs.batch.Queue;ConnectionFactoryJNDIName=jms.connection.BridgeConnectionFactoryXA"
          UserName="system" UserPassword="something"/>
          <BridgeDestination
          AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          Name="BatchBridgeDestination"
          Properties="ConnectionURL=t3://ngfsdev:8001;DestinationJNDIName=ngfs.batch.Test;ConnectionFactoryJNDIName=jms.connection.BridgeConnectionFactoryXA"
          UserName="system" UserPassword="something"/>


Are the two servers having the same name?
          Try not to use the same name for different WebLogic servers.
          Also It is not recommended that different JMS servers or
          different JMS stores use the same name, even if they
          are on different WebLogic servers.
          Try it.
          Dongbo
          Vyacheslav wrote:
          >
          > I tryed what you adviced to me and it finally started to work on one
          > server. When both ConnectionURL point to t3://localhost:7001 it is
          > working. That is a progress already.
          > But when I'm pointing it to remote server it gives me exception. What
          > coud be the reason?
          > Configuration now looks like following:
          >
          > <MessagingBridge Name="BatchBridge"
          > SourceDestination="BatchBridgeSource" Started="true"
          > TargetDestination="BatchBridgeDestination"
          > Targets="myserver"/>
          >
          > <BridgeDestination
          > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          > Name="BatchBridgeSource"
          > Properties="ConnectionURL=t3://localhost:7001;DestinationJNDI=ngfs.batch
          > .Queue;ConnectionFactoryJNDI=jms.connection.BridgeConnectionFactoryXA"
          > UserName="system" UserPassword="something"/>
          >
          > <BridgeDestination
          > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          > Name="BatchBridgeDestination"
          > Properties="ConnectionURL=t3://ngfsdev:8001;DestinationJNDI=ngfs.batch.Test;ConnectionFactoryJNDI=jms.connection.BridgeConnectionFactoryXA"
          > UserName="system" UserPassword="something"/>
          >
          > I don't understand why it cannot connect.
          >
          > I have created factory jms.connection.BridgeConnectionFactoryXA on
          > remote server.
          > I have created queue ngfs.batch.Test on remote server.
          > What is wrong?
          >
          > Server output:
          >
          > configured = jms.connection.BridgeConnectionFactoryXA ra's =
          > jms.connection.Brid
          > geConnectionFactoryXA
          > Lookup: cfJNDI = jms.connection.BridgeConnectionFactoryXA
          > Username = system password = <cut>
          > configured = jms.connection.BridgeConnectionFactoryXA ra's =
          > jms.connection.Brid
          > geConnectionFactoryXA
          > Lookup: cfJNDI = jms.connection.BridgeConnectionFactoryXA
          > Username = system password = <cut>
          > weblogic.jms.common.JMSException: Connection not found
          > at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManag
          > er.java:121)
          > at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.jav
          > a:503)
          > at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.ja
          > va:272)
          > at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:26
          > 1)
          > at weblogic.jms.client.JMSXAConnection.createXAQueueSession(JMSXAConnect
          > ion.java:67)
          > at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:2
          > 00)
          > at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnect
          > ion(JMSManagedConnectionFactory.java:200)
          > at weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
          > ctionPool.java:808)
          > at weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
          > ctionPool.java:1441)
          > at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
          > n(ConnectionPoolManager.java:154)
          > at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
          > ection(ConnectionManagerImpl.java:20)
          > at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMS
          > BaseConnectionFactory.java:157)
          > at weblogic.jms.bridge.internal.MessagingBridge.getConnections(Messaging
          > Bridge.java:543)
          > at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
          > java:677)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > <Jul 23, 2002 4:52:37 PM EDT> <Error> <Connector> <Error granting
          > connection req
          > uest.>
          >
          > "Dongbo Xiao" <[email protected]> wrote in message news:<[email protected]>...
          > > Having looked at your configuration again, I found an interesting thing,
          > > which may have caused the problem. Your bridge is configured to
          > > transfer messages from ngfs.batch.Test to ngfs.batch.Queue, while you
          > > expect to see it working in the reverse direction.
          > >
          > > Dongbo
          > >
          > > > > "Vyacheslav" <[email protected]> wrote in message
          > > > > news:[email protected]...
          > > > > > I'm trying to configure messaging bridge to send messages from WLS
          > > > > > 6.1sp1 to WLS 6.1sp1 in another domain and seems it doesn't work. I'm
          > > > > > using following configuration, any idea?
          > > > > >
          > > > > > <MessagingBridge Name="BatchBridge"
          > > > > > SourceDestination="BatchBridgeDestination" Started="true"
          > > > > > TargetDestination="BatchBridgeSource" Targets="myserver"/>
          > > > > >
          > > > > > <BridgeDestination
          > > > > > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          > > > > > Name="BatchBridgeSource"
          > > > > >
          > > > >
          > > Properties="ConnectionURL=t3://localhost:7001;DestinationJNDIName=ngfs.batch
          > > > >
          > > .Queue;ConnectionFactoryJNDIName=jms.connection.BridgeConnectionFactoryXA"
          > > > > > UserName="system" UserPassword="something"/>
          > > > > >
          > > > > > <BridgeDestination
          > > > > > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          > > > > > Name="BatchBridgeDestination"
          > > > > >
          > > > >
          > > Properties="ConnectionURL=t3://ngfsdev:8001;DestinationJNDIName=ngfs.batch.T
          > > > > est;ConnectionFactoryJNDIName=jms.connection.BridgeConnectionFactoryXA"
          > > > > > UserName="system" UserPassword="something"/>

Log a message when the buffer has been overwritten?

Is there a way to configure the IOS to log a message when my configured buffer is full and the oldest log entry gets overwritten?
Logging buffered 32768

endasil wrote:
I agree with baftos that a screen saver is a brilliant and simple way to handle this. I don't think for your purposes you need to use JNI though. This is how I would lay it out:
2 Programs:
-Listener
-ScreenSaver
The listener's only function is to continuously loop, (utilizing Thread.sleep() to not take up much in terms of resources) checking for the existence of some dummy file on your system, say C:\Temp\inactive. If the file doesn't exist, the program increments your study time by however long it's been since it last checked.
The screensaver is just a small native (you could do this in VB in just a few lines of code) app which blanks the screen, and exits on a mouse move or keyboard event. When the Screensaver starts, it creates C:\temp\inactive. When it exits, it deletes that file.
JNI would probably be more stable (for instance, if your screensaver is killed by forcibly killing the process, you'd be screwed), but it also has a learning curve. Using a dummy file, on the other hand, is an indirect but fairly simple way of passing messages between programs (another way is to ping a local port, I believe, which should also work).The file idea makes me think that this is a lot simpler. The screen saver writes the file like this:
Started: 10:00:25-blabla (whatever time date format)
Stopped: ...
Started: .......
Stopped:......
The Java program is run only when you want a report. A simple java application that grabs the file and does whatever it
wants with it.
Edited by: baftos on Dec 7, 2007 4:54 PM

I keep getting the "you've been logged out" message when I try to log in in Creative Cloud...

I keep getting the "you've been logged out" message when I try to log in in Creative Cloud...

Hi Luciana,
In addition to Jeff's suggestion, you may also refer to the threads below:
You've been signed out
"You've been signed out" error every time I try to sign into Creative Cloud desktop application.
How I fixed: You have been signed out problem in 2 minutes!
Regards,
Sheena

WLST redirect command does not log print messages

I am using redirect to log WLST messages in a logfile, while my WLST Jython script is running. However, I am using the print command to output various messages, but I am finding that these print messages are not in the logfile.
How do I get such messages in the "redirect logfile" ?

Hi, I have a similar situation.
I am exec the WLST code from within an application.
When using the WLST scripting, and trying to use the "print" statement for logging messages, we can see the message on the console, but the messages do not show up in our logfile (using java.util.logging.Logger).
For example, if my script has: print "test message"
This will apppear on the console output, but not in my logfile.
But other messages derived from the script are logged.
For example, if in the WLST script we call startEdit(), then the message "Starting an edit session..." will appear in both the console and logfile as expected.
Not sure why the print statement will not get directed to the logfile. Have tried both using statements in single quotes and double quotes, but it doesn't seem to make a difference.
Any idea how we can log from WLST to ensure our logs capture all messages?
I don't want to explicitly open the logfile as shown in your example, as its already open by the logger.

FMS server keeps logging this message "fiber pool full : 0 active" and crashes every few hours

Hello.
We have a live video streaming application running on Flash Media Server 4.5. It usually has about 50-80 concurrent clients connections - and at peaks it can sometimes reach 200-300.
The server log in the admin console keeps repeatedly logging this message:
fiber pool full : 0 active
I have no idea what this message means, and googling it returns 0 results.
Please, someone clarify what this message means...
Plus:
Every few hours the application in the flash server suddenly seem to stop responding - in a way that makes it seem (at least in the admin console) as though clients gets connected but never disconnect - and then the numbers of connecting clients seem to rapidly increase really fast to about 4000-5000 - and the server becomes unresponsive.
I don't know why it happens but - probably is related to that cryptic message mentioned above.
Please help.
Thanks,
Yuval.
Invoke LTD.

Hey Yuval, I am having the same issue on my server, it keeps showing me a wrong number of connected clients and on server logs the message "Fiber Pool Full: 0 active".
After I am on manage server and try to go back to application flash player stop responding and I need to close that tab and open again!
Does this happen to you?
Too bad I don`t have any solution to that, but if you find anything, it could be valuable for me as well, and vice versa.
Thanks.

WebLogic 10.3.6 logging health messages to stdout

Similar Messages

Maybe you are looking for