Axis2 dumping Debug msgs in Weblogic logs

Hi,
I have axis2 with weblogic 10.3.6 and the weblogic logs are dumping a lot of axis debug messages like below.
213215 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG org.apache.axis2.transport.TransportUtils username: oss.eai, client id: 3270976000000, API user: true, database: myhost, Server: myhost.acc.com - Found RequestResponseTransport returning isResponseWritten()
213215 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG org.apache.axis2.transport.TransportUtils username: oss.eai, client id: 3270976000000, API user: true, database: myhost, Server: myhost.acc.com - Exiting deleteAttachments()
213221 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG org.apache.axis2.transport.TransportUtils username: oss.eai, client id: 3270976000000, API user: true, database: myhost, Server: myhost.acc.com - Exiting deleteAttachments()
Inorder to get rid of these debug messages I tried the below in vain
JVM arguments: -Dlog4j.debug=true -Dweblogic.log.StdoutSeverity="Info" -Dweblogic.log.LoggerSeverity="Warning" -Dweblogic.log.LoggerSeverityProperties="org.apache.axis2=Warning;EJB=Info" -Dlog4j.properties=/oss/tgi/bea/user_projects/domains/mydomain/config/log4j.properties"
log4j.properties has been given the below entries:
log4j.category.org.apache.commons.httpclient=INFO
log4j.category.org.apache.commons=INFO
log4j.category.org.apache.commons.digester=INFO
log4j.category.org.apache.commons.httpclient=INFO
log4j.category.org.apache.axis=INFO
log4j.category.org.apache.struts=ERROR
I also tried suppressing the Axis2 Debug messages in the weblogic logs by configuring filtering like below:
Domain ->LogFilters->here I added log filter as AxisLogFilter Expression is (MESSAGE != 'Exiting deleteAttachments()')
Added this log filter to the weblogic server under logging tab.
Below are more expressions that I tried.
(MESSAGE != '%Exiting deleteAttachments%')
NOT(MESSAGE = 'Exiting deleteAttachments')
NOT(MESSAGE LIKE 'Exiting deleteAttachments')
NOT(MESSAGE = '%Exiting deleteAttachments%')
NOT(MESSAGE LIKE '%Exiting deleteAttachments%')
All these does not seem to help.
Can you please suggest ?

Similar Messages

Can I change where WL dumps weblogic.log?

Hi,
I believe WL always writes wl.log to the subdir defined by
weblogic.system.home... can I specify a different directory for logging?
This is important for us in the context of clustering and shared file
system, because we want WL to log to a local dir instead of the shared file
system (for performance reasons), and yet in order to clustering to work
under 5.1, I had to set weblogic.system.home to a directory under the shared
file system!
Gene

Yes this bug will be fixed in service pack 2.
          Prasad
          Gene Chuang wrote:
          > I posted in the env group as well, but the only reason why I need to change
          > the location of the weblogic.log is because of the 5.1 unable to cluster ejb
          > due to tmp_deployments bug... If this bug can be solved, I have no reason
          > to change where weblogic.log gets dumped!
          >
          > Gene
          >
          > "Prasad Peddada" <[email protected]> wrote in message
          > news:[email protected]..
          > > You should post this in environment newsgroup.
          > >
          > > Thanks
          > > Prasad
          > >
          > > Gene Chuang wrote:
          > >
          > > > Hi,
          > > >
          > > > I believe WL always writes wl.log to the subdir defined by
          > > > weblogic.system.home... can I specify a different directory for
          > logging?
          > > > This is important for us in the context of clustering and shared file
          > > > system, because we want WL to log to a local dir instead of the shared
          > file
          > > > system (for performance reasons), and yet in order to clustering to work
          > > > under 5.1, I had to set weblogic.system.home to a directory under the
          > shared
          > > > file system!
          > > >
          > > > Gene
          > >

Weblogic.log formatting

I have 2 weblogic servers running.
one on my W2K laptop and an AS400
When a nosuchmethod error is logged on my W2K webserver
I get the method name.
When the same error is generated on my AS400 webserver it does not.
Is there a way to get it to show up in the AS400 weblogic.log
thanks in advance
Mickey

"Beth" <[email protected]> wrote:
Hi,
I'm trying to find out some more info on the weblogic.log:
1) I see that there is a weblogic.system.maxLogFileSize property
in the weblogic.properties file which will rotate the log based on size.
Are we limited to size only? Is there any way to rotate the log file
based on a new day?This is available for access log...(for HTTP)
not sure for weblogic.log
>
2) Is there any way to specify exactly how many rotations you want?
For example if I only want to keep the last three weblogic.log files-
if there are already three on the system, overwrite the oldest one.
3) I am looking for more information on LogOutputStream, but haven't
been able to locate the doc on the web site. Any idea where I might find
it?
4) I assume by using LogOutputStream and log() that the server is taking
care of synchronizing multiple calls to the log file?I dont think logging is synchronised.
for me it makes sense.
>
5) During development I will be using calls such as log.debug() but when
I'm
ready for production I don't want those log messages in the log file. Is
there
any kind of switch to tell the logging mechanism to ignore certains types of
log
messages? Or does one have to do something specific to the code to ignore
those messages when the time comes?check out weblogic.system.discardOutAndErr=true
but i am not sure this will help..
>
Thanks in advance,
Beth

Weblogic.log questions

Hi,
I'm trying to find out some more info on the weblogic.log:
1) I see that there is a weblogic.system.maxLogFileSize property
in the weblogic.properties file which will rotate the log based on size.
Are we limited to size only? Is there any way to rotate the log file
based on a new day?
2) Is there any way to specify exactly how many rotations you want?
For example if I only want to keep the last three weblogic.log files-
if there are already three on the system, overwrite the oldest one.
3) I am looking for more information on LogOutputStream, but haven't
been able to locate the doc on the web site. Any idea where I might find
it?
4) I assume by using LogOutputStream and log() that the server is taking
care of synchronizing multiple calls to the log file?
5) During development I will be using calls such as log.debug() but when
I'm
ready for production I don't want those log messages in the log file. Is
there
any kind of switch to tell the logging mechanism to ignore certains types of
log
messages? Or does one have to do something specific to the code to ignore
those messages when the time comes?
Thanks in advance,
Beth

"Beth" <[email protected]> wrote:
Hi,
I'm trying to find out some more info on the weblogic.log:
1) I see that there is a weblogic.system.maxLogFileSize property
in the weblogic.properties file which will rotate the log based on size.
Are we limited to size only? Is there any way to rotate the log file
based on a new day?This is available for access log...(for HTTP)
not sure for weblogic.log
>
2) Is there any way to specify exactly how many rotations you want?
For example if I only want to keep the last three weblogic.log files-
if there are already three on the system, overwrite the oldest one.
3) I am looking for more information on LogOutputStream, but haven't
been able to locate the doc on the web site. Any idea where I might find
it?
4) I assume by using LogOutputStream and log() that the server is taking
care of synchronizing multiple calls to the log file?I dont think logging is synchronised.
for me it makes sense.
>
5) During development I will be using calls such as log.debug() but when
I'm
ready for production I don't want those log messages in the log file. Is
there
any kind of switch to tell the logging mechanism to ignore certains types of
log
messages? Or does one have to do something specific to the code to ignore
those messages when the time comes?check out weblogic.system.discardOutAndErr=true
but i am not sure this will help..
>
Thanks in advance,
Beth

Pb with weblogic.log

To debug our application, we inserted many System.out.println() in our
servlets/jsp. The problem is that, whereas they appear in the
weblogic-launch-window, they don't in the weblogic.log file. Is there a
property to change in order to get these messages?

I am also lookign which log file "System.out.println's" are going to. Please give details as to what we need to do to see these messages and which log file to go to.

Weblogic.log error levels

I am trying to find some more information on the different error levels that are logged to weblogic.log. Does anyone know if the levels are described anywhere?

Or see weblogic.logging.Severities @
http://e-docs/wls/docs60/javadocs/index.html
Brad Stone <[email protected]> wrote in message
news:[email protected]...
WebLogic uses the following severities, in order of criticality:
Emergency The server is in an unusable state. This should only be used to
designate severe system failures or panics.
Alert A particular service is in an unusable state. Other parts of the
system continue to function. Automatic recovery is not possible and the
immediate attention of the administrator is required to resolve theproblem.
>
Critical A system/service level error has occurred. The system is ableto
recover, perhaps with a momentary loss or permanent degradation ofservice.
>
Notice A particularly important warning or informational message.
Messages, such as notification of successful recovery from a failure,which
is of particular importance to an administrator monitoring the server.
Error A user level error has occurred. The system is able to handle the
error with no interruption and limited degradation in service. Make this
severity less 'severe' than NOTICE.
Warning A warning message. A suspicious operation or configuration which
doesn't affect the normal operation of the server.
Informational An informational message. Used for the logging of normal
operations for later examination.
Debug A debug message. Should be output only when the server isconfigured
in a debug mode. May contain detailed information about operations or the
state of the server.
"Beth" <[email protected]> wrote in message
news:[email protected]...
I never found anything in the documentation. But if you are using
LogOutputStream, there is the following:
- emergency
- alert
- critical
- error
- notice
- warning
- info
- debug
All take parameters of either just a String or a String and Throwable.
I don't know of a way to tell Weblogic just to log certain levels andignore
others so when you are done debugging you don't log any of the debug
messages to the log file.
This can be found by doing a
javap weblogic.logging.LogOutputStream
Hope this is what you are looking for.
"Jennifer Edwards" <[email protected]> wrote in message
news:[email protected]...
I am trying to find some more information on the different error
levels
that are logged to weblogic.log. Does anyone know if the levels are
described anywhere?

Logging to weblogic.log

hi
i need couple of clarifications with regard to implementation of logging with
weblogic.
a) Is logging implemented using JMS? ( Is logging asynchronous?)
b) I am wondering if i can use logging api into some helper classes that wouldn't
be run in weblogic server. If weblogic server is a pre-requisite, then i will
not be able to use this logging api in these classes.
Thanks
Rob Woollen <[email protected]> wrote:
From server-side code (ie servlets or EJB). do
LogServiceDef log = T3Services.getT3Services().log();
to get the log, and then you can use log.inform(), log.debug, or
log.error as appropriate.
See
http://www.weblogic.com/docs45/classdocs/weblogic.common.LogServicesDef.html
-- Rob
Rob Woollen
Software Engineer
BEA WebLogic
[email protected]
Vinny Carpenter wrote:
Hi there. I have a cluster of WebLogic 4.5.1 servers running under
Solaris 2.6. My application consists of two EJB's and a couple of
servlets as front end. As part of the application logging process,I
output certain text using System.out.println and System.err.printlnthat
are typically displayed on the console.
How can I redirect those messages to the machine's weblogic.log file??
Is there a logging mechanism that will allow me to do that?? thanks
--Vinny

WLS Locks on weblogic/logging/ConsoleHandler

Hi all,
i have an ADF/ADF Faces application installed on Oracle WLS 10.3.3.0
The Application Server is installed on Windows Server 2003 Service Pack 2.
The problem is that some times a locks over the weblogic/logging/ConsoleHandler is happened and Server Hangs on it, because
all threads are getting blocked when they trying to use the Logger.
Example from thread dump:
The thread which holds the lock:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 prio=1 alive, in native, daemon
at jrockit/io/FileNativeIO.writeBytesPinned(Ljava/io/FileDescriptor;[BIIZ)V(Native Method)
at jrockit/io/FileNativeIO.writeBytes(FileNativeIO.java:52)
at java/io/FileOutputStream.writeBytes([BII)V(FileOutputStream.java)
at java/io/FileOutputStream.write(FileOutputStream.java:260)
at java/io/BufferedOutputStream.write(BufferedOutputStream.java:105)
^-- Holding lock: java/io/BufferedOutputStream@0x0000000026643F90[thin lock]
at java/io/PrintStream.write(PrintStream.java:430)
^-- Holding lock: java/io/PrintStream@0x000000002678AFF8[thin lock]
at sun/nio/cs/StreamEncoder.writeBytes(StreamEncoder.java:202)
at sun/nio/cs/StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
at sun/nio/cs/StreamEncoder.implFlush(StreamEncoder.java:276)
at sun/nio/cs/StreamEncoder.flush(StreamEncoder.java:122)
^-- Holding lock: java/io/OutputStreamWriter@0x00000000264C6408[thin lock]
at java/io/OutputStreamWriter.flush(OutputStreamWriter.java:212)
at java/util/logging/StreamHandler.flush(StreamHandler.java:225)
^-- Holding lock: weblogic/logging/ConsoleHandler@0x00000000264C5EE0[recursive]
at weblogic/logging/ConsoleHandler.publish(ConsoleHandler.java:90)
^-- Holding lock: weblogic/logging/ConsoleHandler@0x00000000264C5EE0[fat lock]
at java/util/logging/Logger.log(Logger.java:458)
at com/bea/logging/BaseLogger.log(BaseLogger.java:51)
at weblogic/logging/WLLogger.log(WLLogger.java:40)
at com/bea/logging/LoggingService.log(LoggingService.java:251)
at weblogic/jdbc/JDBCLogger.logTestFailed(JDBCLogger.java:856)
at weblogic/jdbc/common/internal/ConnectionEnv.testInternal(ConnectionEnv.java:876)[optimized]
at weblogic/jdbc/common/internal/ConnectionEnv.test(ConnectionEnv.java:756)[inlined]
at weblogic/jdbc/common/internal/ConnectionEnv.test(ConnectionEnv.java:495)[optimized]
at weblogic/common/resourcepool/ResourcePoolImpl.testResource(ResourcePoolImpl.java:2345)[inlined]
at weblogic/common/resourcepool/ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1657)[inlined]
at weblogic/common/resourcepool/ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1564)[inlined]
at weblogic/common/resourcepool/ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1553)[inlined]
at weblogic/common/resourcepool/ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:2001)[optimized]
at weblogic/common/resourcepool/ResourcePoolImpl.access$900(ResourcePoolImpl.java:40)[inlined]
at weblogic/common/resourcepool/ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2433)[optimized]
at weblogic/timers/internal/TimerImpl.run(TimerImpl.java:273)[optimized]
at weblogic/work/SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)[optimized]
at weblogic/work/ExecuteThread.execute(ExecuteThread.java:201)[optimized]
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
Blocked lock chains
===================
Chain 2:
"[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" id=22 idx=0x6c tid=5484 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 3:
"[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" id=51 idx=0xcc tid=6836 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 4:
"[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" id=53 idx=0xd4 tid=6228 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 5:
"[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" id=81 idx=0x144 tid=2840 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 6:
"[STUCK] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" id=82 idx=0x148 tid=5168 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 7:
"[STUCK] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" id=83 idx=0x14c tid=6728 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 8:
"[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" id=84 idx=0x150 tid=4596 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 9:
"[STUCK] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" id=85 idx=0x154 tid=6924 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 10:
"[STUCK] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'" id=86 idx=0x158 tid=2172 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 11:
"[STUCK] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'" id=87 idx=0x15c tid=4340 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 12:
"[STUCK] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" id=88 idx=0x160 tid=3156 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 13:
"[STUCK] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" id=89 idx=0x164 tid=7100 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 14:
"[STUCK] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'" id=90 idx=0x168 tid=5968 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 15:
"[STUCK] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'" id=91 idx=0x16c tid=4620 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 16:
"[STUCK] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'" id=92 idx=0x170 tid=7008 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 17:
Can somebody help with this ?
Thanks in advance,
Krasimir

Hi all,
i have an ADF/ADF Faces application installed on Oracle WLS 10.3.3.0
The Application Server is installed on Windows Server 2003 Service Pack 2.
The problem is that some times a locks over the weblogic/logging/ConsoleHandler is happened and Server Hangs on it, because
all threads are getting blocked when they trying to use the Logger.
Example from thread dump:
The thread which holds the lock:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 prio=1 alive, in native, daemon
at jrockit/io/FileNativeIO.writeBytesPinned(Ljava/io/FileDescriptor;[BIIZ)V(Native Method)
at jrockit/io/FileNativeIO.writeBytes(FileNativeIO.java:52)
at java/io/FileOutputStream.writeBytes([BII)V(FileOutputStream.java)
at java/io/FileOutputStream.write(FileOutputStream.java:260)
at java/io/BufferedOutputStream.write(BufferedOutputStream.java:105)
^-- Holding lock: java/io/BufferedOutputStream@0x0000000026643F90[thin lock]
at java/io/PrintStream.write(PrintStream.java:430)
^-- Holding lock: java/io/PrintStream@0x000000002678AFF8[thin lock]
at sun/nio/cs/StreamEncoder.writeBytes(StreamEncoder.java:202)
at sun/nio/cs/StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
at sun/nio/cs/StreamEncoder.implFlush(StreamEncoder.java:276)
at sun/nio/cs/StreamEncoder.flush(StreamEncoder.java:122)
^-- Holding lock: java/io/OutputStreamWriter@0x00000000264C6408[thin lock]
at java/io/OutputStreamWriter.flush(OutputStreamWriter.java:212)
at java/util/logging/StreamHandler.flush(StreamHandler.java:225)
^-- Holding lock: weblogic/logging/ConsoleHandler@0x00000000264C5EE0[recursive]
at weblogic/logging/ConsoleHandler.publish(ConsoleHandler.java:90)
^-- Holding lock: weblogic/logging/ConsoleHandler@0x00000000264C5EE0[fat lock]
at java/util/logging/Logger.log(Logger.java:458)
at com/bea/logging/BaseLogger.log(BaseLogger.java:51)
at weblogic/logging/WLLogger.log(WLLogger.java:40)
at com/bea/logging/LoggingService.log(LoggingService.java:251)
at weblogic/jdbc/JDBCLogger.logTestFailed(JDBCLogger.java:856)
at weblogic/jdbc/common/internal/ConnectionEnv.testInternal(ConnectionEnv.java:876)[optimized]
at weblogic/jdbc/common/internal/ConnectionEnv.test(ConnectionEnv.java:756)[inlined]
at weblogic/jdbc/common/internal/ConnectionEnv.test(ConnectionEnv.java:495)[optimized]
at weblogic/common/resourcepool/ResourcePoolImpl.testResource(ResourcePoolImpl.java:2345)[inlined]
at weblogic/common/resourcepool/ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1657)[inlined]
at weblogic/common/resourcepool/ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1564)[inlined]
at weblogic/common/resourcepool/ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1553)[inlined]
at weblogic/common/resourcepool/ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:2001)[optimized]
at weblogic/common/resourcepool/ResourcePoolImpl.access$900(ResourcePoolImpl.java:40)[inlined]
at weblogic/common/resourcepool/ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2433)[optimized]
at weblogic/timers/internal/TimerImpl.run(TimerImpl.java:273)[optimized]
at weblogic/work/SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)[optimized]
at weblogic/work/ExecuteThread.execute(ExecuteThread.java:201)[optimized]
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
Blocked lock chains
===================
Chain 2:
"[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" id=22 idx=0x6c tid=5484 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 3:
"[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" id=51 idx=0xcc tid=6836 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 4:
"[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" id=53 idx=0xd4 tid=6228 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 5:
"[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" id=81 idx=0x144 tid=2840 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 6:
"[STUCK] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" id=82 idx=0x148 tid=5168 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 7:
"[STUCK] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" id=83 idx=0x14c tid=6728 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 8:
"[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" id=84 idx=0x150 tid=4596 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 9:
"[STUCK] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" id=85 idx=0x154 tid=6924 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 10:
"[STUCK] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'" id=86 idx=0x158 tid=2172 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 11:
"[STUCK] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'" id=87 idx=0x15c tid=4340 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 12:
"[STUCK] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" id=88 idx=0x160 tid=3156 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 13:
"[STUCK] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" id=89 idx=0x164 tid=7100 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 14:
"[STUCK] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'" id=90 idx=0x168 tid=5968 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 15:
"[STUCK] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'" id=91 idx=0x16c tid=4620 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 16:
"[STUCK] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'" id=92 idx=0x170 tid=7008 waiting for weblogic/logging/ConsoleHandler@0x00000000264C5EE0 held by:
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=52 idx=0xd0 tid=3152 in chain 1
Chain 17:
Can somebody help with this ?
Thanks in advance,
Krasimir

WebLogic logging services, SMTPHandler project

I wrote an SMTPHandler for java.util.logging
The SMTPHandler is similar to Log4j's SMTPAppender.
The SMTPHandler code is open source (Apache Public License)
If you are using Weblogic's Logging Services, I'd like to get feedback
from you.
I'd like to know if the SMTPHandler works for you in your
Weblogic 8.1 environment.
http://smtphandler.sourceforge.net/
http://edocs.bea.com/wls/docs81/logging/

Can you debug print the LogFactory.getFactory().getClass().getName() to stdout and see what class is being initialized as the LogFactory? You can try to set the commons logging property on the command line of the server with the -Dorg.apache.commons.logging.LogFactory=weblogic.logging.commons.LogFactoryImpl and see if this helps. When Commons Logging is initialized with the WebLogic Commons Log factory implementation you should see Commons log messages being directed to the Server logs.

Re: Pb with weblogic.log

The mechanism to do this is:
http://www.weblogic.com/docs51/classdocs/javadocs/weblogic/common/LogService
sDef.html
Unfortunately, it was mistakenly deprecated in version 5.1.0. We are on
undeprecating it as a service pack No. 2 (I believe is the correct number)
for version 5.1.
It should work fine in version 4.5.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
UAI <[email protected]> wrote in message
news:8g0g2e$c1a$[email protected]..
To debug our application, we inserted many System.out.println() in our
servlets/jsp. The problem is that, whereas they appear in the
weblogic-launch-window, they don't in the weblogic.log file. Is there a
property to change in order to get these messages?

I am also lookign which log file "System.out.println's" are going to. Please give details as to what we need to do to see these messages and which log file to go to.

Weblogic logging to syslog?

Hi All.
I have a setup in which:
- applications deployed in weblogic send logs to weblogic;
- components of weblogic (domain, admin server, managed servers) log to proper files (default logging).
I would like to connect logging to syslog server. Is it possible? As I have read it is possible to log from applications with log4j (on weblogic level with domain_root/lib/log4j.xml or log4j.properties) if they send logs to weblogic server. But is it possible to log from weblogic components to log4j and through it to syslog?
There is much info on the web and I'm quite confused. Thanks for all help.
Best regards,
Rafal.

Basically syslog configuration is very easy with logging host x.x.x.x. But more options that you need to be aware of.
1)Router# configure terminal--Enters global configuration mode.
2)Router(config)# service timestamps type datetime [msec] [localtime] [show-timezone]--Instructs the system to timestamp syslog messages;
3)Router(config)#logging host--Tells the syslog server by IP address or host name; multiple servers also can be specified.
4)Router(config)# logging trap level--severity level. The possible values for level are as follows:Use the debug level with caution, because it can generate a large amount of syslog traffic in a busy network
Emergency-0
Alert-1
Critical-2
Error- 3
Warning- 4
Notice- 5
Informational- 6
Debug- 7
Router# show logging--Showslogging configuration.

Overhead in weblogic logging

Does anyone have an info on the performance overhead of logging within
weblogic (6.1 sp2). There doesn't seem to be a way to turn down the
logging to weblogic.log from info to something like error or warning
level. I thought the StdoutSeverityLevel parameter would do that but it
only controls what is written to standard out not the weblogic.log.
Also, should the access log be enabled in production systems? Since it
writes a line to the log for every http hit, I was wondering what kind
of performance overhead that might make.
Kirk

FYI: The LogToStdOut option only applies to the console output, not the
weblogic.log file.
Nils
Pamal wrote:
>
Hi,
You can turn off complete logging by unchecking the Log to Stdout in WebLogic
administration console. Or the same can be achieved by giving the following in
config.xml
<WebServer DefaultWebApp=""
LogFileName="./config/petstore/logs/access.log"
LoggingEnabled="false" Name=""/>
You can also set the level of logging to Info, Debug etc
Regards,
Pamal
Rob Woollen <[email protected]> wrote:
I don't believe there's any current way to limit what gets written to
the
weblogic.log.
Writes to the access.log are buffered internally in the server so their
performance impact shouldn't be too big.
FWIW, I'd recommend that you run performance tests on your application
first and
then consider turning off logging only if it has a significant impact.
-- Rob
Kirk Everett wrote:
I totally agree and was only thinking about doing this in a productionenv. I
just wanted to know if you could (or should) turn off the access.logand the
weblogic.log. Is there even a way to turn down what gets put in the
weblogic.log?
Kirk
Cameron Purdy wrote:
Logging can be expensive, but only consider this once you have a
stable
application. Usually the application-level (not server-level) loggingis the
prime culprit, and you can reduce this with clever use of the deletekey in
source code files. You can also redirect stdout and stderr to nuland you
can turn off logging options once you are sure that things are stable.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you shouldbe!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Kirk Everett" <[email protected]> wrote in message
news:[email protected]...
Does anyone have an info on the performance overhead of logging
within
weblogic (6.1 sp2). There doesn't seem to be a way to turn downthe
logging to weblogic.log from info to something like error or warning
level. I thought the StdoutSeverityLevel parameter would do thatbut it
only controls what is written to standard out not the weblogic.log.
Also, should the access log be enabled in production systems? Sinceit
writes a line to the log for every http hit, I was wondering whatkind
of performance overhead that might make.
Kirk
============================
[email protected]

Logging in weblogic personalization server (weblogic.log)

Hello,
I have been searching through the newsgroups trying to find an
appropriate way to log messages to the weblogic.log from a class.
However, I am more confused than ever. I can't locate a jar file
containing some definition for the T3Services class ... can someone
please help?
thanks in advance!
Neelam Checknita ; ~ )

Something like this
import weblogic.common.T3Services;
T3Services.getT3Services().log().debug("This will go in the log");
T3Services.getT3Services().log().info("This will go in the log");
T3Services.getT3Services().log().warning("This will go in the log");
T3Services.getT3Services().log().security("This will go in the log");
T3Services.getT3Services().log().error("This will go in the log",
Exception);
Neelam Checknita wrote:
Hello,
I have been searching through the newsgroups trying to find an
appropriate way to log messages to the weblogic.log from a class.
However, I am more confused than ever. I can't locate a jar file
containing some definition for the T3Services class ... can someone
please help?
thanks in advance!
Neelam Checknita ; ~ )[chris.jolley.vcf]

Weblogic logging implementation

Hi experts,
I m trying to implement org.apache.commons.logging.Log implementation. I copied 2 lib jars into domainhome/lib folder acc to http://docs.oracle.com/cd/E21764_01/web.1111/e13739/config_logs.htm#i1014785. If i use System.setProperty(LogFactory.FACTORY_PROPERTY, "weblogic.logging.commons.LogFactoryImpl"); before creating logger instance (by using LogFactory.getFactory().getInstance(this.getClass());) it works. But i do not want to use setProperty on every class by this way. So i manipulated my setDomainEnv.cmd (see below plz) as adding -Dweblogic.logging.commons.LogFactoryImpl=org.apache.commons.logging.LogFactory argument, i have not faced any exception when i start weblogic by that way but it does not writeout any log.
Plz help me that what i missed?
Thx in advance
Brgds
sertDomainEnv.cmd
set EXTRA_JAVA_PROPERTIES=-Dweblogic.logging.commons.LogFactoryImpl=org.apache.commons.logging.LogFactory %EXTRA_JAVA_PROPERTIES%
MainManagerBean.class
@Stateless(name="MainManager", mappedName = "MainManager")
@TransactionManagement(TransactionManagementType.CONTAINER)
@Interceptors(value = { PerformanceMonitor.class, ProfileInterceptor.class })
public class MainManagerBean implements MainManager, MainManagerLocal
    private Log logger =LogFactory.getFactory().getInstance(this.getClass());
    @PersistenceContext(unitName = "EJBModel")
    private EntityManager manager;
    @Resource
    SessionContext ctx;
    @PostConstruct
    public void initialized()
        //System.setProperty(LogFactory.FACTORY_PROPERTY, "weblogic.logging.commons.LogFactoryImpl");
        // logger= LogFactory.getFactory().getInstance(this.getClass());
        logger.debug("MainManagerBean is initialized");
        logger.info("MainManagerBean is initialized");
        logger.trace("MainManagerBean is initialized");

You have to make sure the commons-logging library is in the system classpath (with the logging implemenation it is using, for example log4j)
To this end you can edit the commEnv file (which is located in the $WL_HOME/common/bin directory) for example,
WEBLOGIC_CLASSPATH="${JAVA_HOME}/lib/tools.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic.jar${CLASSPATHSEP}${FEATURES_DIR}/weblogic.server.modules_12.1.1.0.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${ANT_HOME}/lib/ant-all.jar${CLASSPATHSEP}${ANT_CONTRIB}/lib/ant-contrib.jar${CLASSPATHSEP}${WL_HOME}/common/deployable-libraries/log4j-1.2.13.jar${CLASSPATHSEP}${WL_HOME}/common/deployable-libraries/commons-logging-1.1.1.jar"
More information is provided here http://middlewaremagic.com/weblogic/?p=6725 (at the end of the post)

How to write to weblogic.log from JSP ?

It is possible to write some messages to weblogic.log from JSP?


Use weblogic.logging.LogOutputStream class to log messages into
          weblogic.log file.
          javap on weblogic.logging.LogOutputStream
          for e.g
          <%@ page import="weblogic.logging.*" %>
          <%
          LogOutputStream los = new LogOutputStream("TEST");
          los.error("Writing into Log file");
          %>
          Hope this helps.
          --kumar allamraju
          Mikhail Ershov wrote:
          > It is possible to write some messages to weblogic.log from JSP?

Axis2 dumping Debug msgs in Weblogic logs

Similar Messages

Maybe you are looking for