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

Similar Messages

Disabling logging to weblogic.log during startup of WLS

Hello,
Does anybody know how to disable logging to the weblogic.log file during startup
of WLS (v5.1.0).
Specifically I would like to hide parameters such as username and password that
show up as clear text for example when a database pool is created.
Thanks,
Murtaza.

Hi under WLS5.1.0, you can not do it.
thanks
Yu
Murtaza Sonaseth <[email protected]> wrote in message
news:3b5c729e$[email protected]..
>
Hello,
Does anybody know how to disable logging to the weblogic.log file duringstartup
of WLS (v5.1.0).
Specifically I would like to hide parameters such as username and passwordthat
show up as clear text for example when a database pool is created.
Thanks,
Murtaza.

How to use weblogic.logging classes in 6.0

Hi,
We developed a number of logging classes under 5.1. One used
weblogic.logging.LogOutputStream to write messages out to the log. This
code no longer works under WLS 6.0. Everything compiles and runs but I
don't see any of our messages in any of the log files. Judging from the 6.0
JavaDoc, it looks like LogOutputStream is no longer supported. So I
switched over to using NonCatalogLogger. Same results - no output in the
logs.
What am I missing?
Thanks.
-brian

My coding error. weblogic.logging.* classes work just fine in 6.0 (he said
sheepishly)!
-b
"Brian J. Levine" <[email protected]> wrote in message
news:[email protected]..
Hi,
We developed a number of logging classes under 5.1. One used
weblogic.logging.LogOutputStream to write messages out to the log. This
code no longer works under WLS 6.0. Everything compiles and runs but I
don't see any of our messages in any of the log files. Judging from the6.0
JavaDoc, it looks like LogOutputStream is no longer supported. So I
switched over to using NonCatalogLogger. Same results - no output in the
logs.
What am I missing?
Thanks.
-brian

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?

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.

Using weblogic.logging.NonCatalogLogger

I am getting an exception whenever i try to use the NonCatalogLogger.info(string,
throwable). It's a null pointer exception which is caused as the constructor of
the NonCatalogLogger seems to be returning a null object.
How do you appropriately construct a NonCatalogLogger object
weblogic.logging.NonCatalogLogger

this seems wierd ? i don't see how this constructor can return null ?
are you seeing any error in the server error log.
"Prakash M" <[email protected]> wrote in message
news:3ad216ac$[email protected]..
>
I actually changed this to a valid subsystem name; EJB; however i am stillgetting
the same exception. What can cause this ?
I am trying to use the logging API within the server instance; i.e.currently
i am trying to use it within a Message Driven Bean
Prakash
"Prakash M" <[email protected]> wrote:
My constructor is returning a null; this is caused since i do not have
a valid
subsytem name. How do i create a user-defined subsystem within WLS 6.0
Prakash
"Sanjeev Chopra" <[email protected]> wrote:
There is only 1 constructor, which takes a subsystem name (string).
This can be created only within a T3Client.
Is the constructor throwing an exception ? (if yes pls post your
stacktrace)
OR is it silently returning null.
"Prakash M" <[email protected]> wrote in message
news:3ace4899$[email protected]..
I am getting an exception whenever i try to use theNonCatalogLogger.info(string,
throwable). It's a null pointer exception which is caused as theconstructor of
the NonCatalogLogger seems to be returning a null object.
How do you appropriately construct a NonCatalogLogger object
weblogic.logging.NonCatalogLogger

Weblogic.log

Hi,
          I am using weblogic5.1. I use System.out.println() to output messages to Weblogic console. But I cannot see these messages in weblogic.log. If I start weblogic as Windows service, since there is no weblogic console, I cannot see any messages outputed using System.out.print(). Is there any way to configure such that I can direct System.out.println() messages to weblogic.log, or any other file so I can view these messages.
          Thanks a lot.
          Zhe


[email protected] wrote:
          > I would want to think so to,
          > But I guess Weblogic grabs the Out variable first (and make a private copy
          > for itself ...?)
          Strange - I thought it does this to redirect all System.out.println's to it's
          log, but looking at the System.out in the debugger shows that it's the same
          one System.initializeSystemClass() created.
          > Dimitri do you know of any "undocumented" JDK property to set the standard
          > op stream ...other than
          > java xxx > mylog.txt ?
          Nop. I guess you can get clever and do it as a part of the 1.4 logging initialization
          (called by System.initializeSystemClass()).
          > peace,
          > _NR
          > "Dimitri I. Rakitine" <[email protected]> wrote in message
          > news:[email protected]...
          >> [email protected] wrote:
          >> > Hmmm..tough call.. A cheap way would be to set
          >>
          >> > System.setOut(PrintStream out) to some file or something... before the
          > first
          >>
          >> I thought that WebLogic does it by itself, doesn't it?
          >>
          >> > System.out.printX() gets called...
          >>
          >> > peace,
          >> > -NR
          >>
          >>
          >>
          >>
          >>
          >>
          >>
          >>
          >>
          >> > "Zhe Liu" <[email protected]> wrote in message
          >> > news:[email protected]...
          >> >>
          >> >> Thank you very much for you reply.
          >> >>
          >> >> Does that mean I have to use the LogServicesDef to replace all
          > System.out
          >> > in my
          >> >> code? I am wondering whether there is a way to see the System.out
          > messages
          >> > without
          >> >> changing code, say, just change the configuration or
          > weblogic.properties.
          >> > I have
          >> >> many JSP pages and I am encounting a problem that weblogic will die by
          >> > itsself
          >> >> in production. But I have no idea which page may cause the problem. It
          >> > will be
          >> >> very helpful if I can see all the messages sending to System.out. But
          > it
          >> > is difficult
          >> >> to change all source code in a short time.
          >> >>
          >> >> Zhe
          >> >>
          >> >> <[email protected]> wrote:
          >> >> >As far as I remember there is a way to do that in WLS 5.1 ,using the
          >> >> >LogServicesDef and I am not sure if they were deprecated !!
          >> >> >
          >> >> >http://www.weblogic.com/docs51/classdocs/API_t3.html#services
          >> >> >
          >> >> >and
          >> >> >
          >> >> >http://www.weblogic.com/docs51/classdocs/API_servlet.html
          >> >> >
          >> >> >T3ServicesDef t3s = T3Services.getT3Services();String consoleEnabled
          >> >> >=
          >> >> >t3s.config().getProperty("weblogic.system.enableConsole");String
          > logmsg
          >> >> >=
          >> >> >"bla set to " + bla + " at " + new
          >> >> >java.util.Date();LogServicesDef logger = t3s.log();logger.log(logmsg);
          >> >> >"Zhe Liu" <[email protected]> wrote in message
          >> >> >news:[email protected]...
          >> >> >> Hi,
          >> >> >>
          >> >> >> I am using weblogic5.1. I use System.out.println() to output
          > messages
          >> >> >to
          >> >> >Weblogic console. But I cannot see these messages in weblogic.log. If
          >> >> >I
          >> >> >start weblogic as Windows service, since there is no weblogic console,
          >> >> >I
          >> >> >cannot see any messages outputed using System.out.print(). Is there
          > any
          >> >> >way
          >> >> >to configure such that I can direct System.out.println() messages to
          >> >> >weblogic.log, or any other file so I can view these messages.
          >> >> >>
          >> >> >> Thanks a lot.
          >> >> >>
          >> >> >> Zhe
          >> >> >
          >> >> >
          >> >>
          >>
          >>
          Dimitri

Rolling of weblogic.log

WLS 5.1 SP5
Solaris 5.6
JDK 1.2.2_005a
I can see in the docs the weblogic.properties for rolling of access.log,
but there is nothing about rolling of weblogic.log. I specifically need
this as my web-app will write messages on here (via ServletContext.log()
) for the admins to read and watch out for.
Specifically, I would like to have a weblogic.log file rolled per day
(at 12 midnight).

Oh, access.log also does not rotate.
"Jesus M. Salvo Jr." wrote:
>
Rolling of weblogic.log does not seem to be working with the following
properties:
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
weblogic.httpd.logRotationType=date
weblogic.httpd.logRotationPeriodMins=5
weblogic.httpd.logRotationBeginTime=09-28-2000-11:30:00
... and I restarted WLS at 11:29:00, but several minutes have passed (45
minutes) now, but is not rotating. In fact, it still continues to append
to the existing weblogic.log
Having mentioned the above, I found an alternative solution. I'll post
it on a separate discussion thread.
"Jesus M. Salvo Jr." wrote:
WLS 5.1 SP5
Solaris 5.6
JDK 1.2.2_005a
I can see in the docs the weblogic.properties for rolling of access.log,
but there is nothing about rolling of weblogic.log. I specifically need
this as my web-app will write messages on here (via ServletContext.log()
) for the admins to read and watch out for.
Specifically, I would like to have a weblogic.log file rolled per day
(at 12 midnight).

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?

Error in weblogic.log using weblogic 6.1

I have this error in my weblogic.log file. I do not know the reason for the
error. What is the error about?
####<Oct 7, 2002 1:23:34 PM PDT> <Error> <Management> <hewlett-yf9yyzb>
<myserver> <ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'>
<system> <> <140001> <Error getting attribute EJBName.MethodName on MBean
mydomain:Application=test,AssemblyDescriptor=AssemblyDescriptor-4,ContainerT
ransaction=ContainerTransaction-4,EJBComponent=sempire_bc,EJBDescriptor=EJBD
escriptor-4,EJBJar=EJBJar-9,Location=myserver,Name=Method-12,Type=Method.
Method: null>
javax.management.AttributeNotFoundException: EJBName.MethodName
at
weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBean
Impl.java:1643)
at
weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
java:502)
at
weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
java:477)
at
com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:118
3)
at
com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:115
3)
at
weblogic.management.internal.MBeanProxy.getOneAttribute(MBeanProxy.java:283)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:199)
at $Proxy77.getAttribute(Unknown Source)
at
weblogic.management.console.utils.MBeans.getDisplayNameFor(MBeans.java:705)
at
weblogic.management.console.utils.ConsoleComparator.compare(ConsoleComparato
r.java:83)
at java.util.Arrays.mergeSort(Arrays.java:1176)
at java.util.Arrays.sort(Arrays.java:1123)
at java.util.Collections.sort(Collections.java:116)
at weblogic.management.console.utils.MBeans.sort(MBeans.java:1101)
at
weblogic.management.console.tags.DeclareBeanSetTag.doStartTag(DeclareBeanSet
Tag.java:96)
at
weblogic.management.console.webapp._ejb._ejb20.__nav._jspService(__nav.java:
4606)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:482)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:308)
at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:116)
at
weblogic.management.console.webapp._ejb.__nav._jspService(__nav.java:177)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:242)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java
:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServl
et.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2546)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Ronak Parekh

It looks like an error/bug in the deployment descriptor editor in the
console.
-- Rob
Ronak Parekh wrote:
I have this error in my weblogic.log file. I do not know the reason for the
error. What is the error about?
####<Oct 7, 2002 1:23:34 PM PDT> <Error> <Management> <hewlett-yf9yyzb>
<myserver> <ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'>
<system> <> <140001> <Error getting attribute EJBName.MethodName on MBean
mydomain:Application=test,AssemblyDescriptor=AssemblyDescriptor-4,ContainerT
ransaction=ContainerTransaction-4,EJBComponent=sempire_bc,EJBDescriptor=EJBD
escriptor-4,EJBJar=EJBJar-9,Location=myserver,Name=Method-12,Type=Method.
Method: null>
javax.management.AttributeNotFoundException: EJBName.MethodName
at
weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBean
Impl.java:1643)
at
weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
java:502)
at
weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
java:477)
at
com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:118
3)
at
com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:115
3)
at
weblogic.management.internal.MBeanProxy.getOneAttribute(MBeanProxy.java:283)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:199)
at $Proxy77.getAttribute(Unknown Source)
at
weblogic.management.console.utils.MBeans.getDisplayNameFor(MBeans.java:705)
at
weblogic.management.console.utils.ConsoleComparator.compare(ConsoleComparato
r.java:83)
at java.util.Arrays.mergeSort(Arrays.java:1176)
at java.util.Arrays.sort(Arrays.java:1123)
at java.util.Collections.sort(Collections.java:116)
at weblogic.management.console.utils.MBeans.sort(MBeans.java:1101)
at
weblogic.management.console.tags.DeclareBeanSetTag.doStartTag(DeclareBeanSet
Tag.java:96)
at
weblogic.management.console.webapp._ejb._ejb20.__nav._jspService(__nav.java:
4606)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:482)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:308)
at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:116)
at
weblogic.management.console.webapp._ejb.__nav._jspService(__nav.java:177)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:242)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java
:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServl
et.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2546)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Ronak Parekh

Providing developers with access to WebLogic logs

Hi all,
I keep getting asked by developers for access to WebLogic logs in restricted test environments. But due to security policies, I can't just create an account for them. In one of my previous roles we just gave developers access to a WeLogic monitor account (read-only), but I find the WebLogic admin console is not user friendly for viewing logs.
To overcome this, I created a really simple WebLogic app that lets the developers access all logs files on the managed servers.
I've blogged a quick how-to here for anyone interested in doing the same: [http://connectionserver.blogspot.com/2009/05/listing-directories-simple-weblogic.html|http://connectionserver.blogspot.com/2009/05/listing-directories-simple-weblogic.html]
Hope it helps someone :)
P.S. Perhaps someone could modify it to restrict access to certain roles.
-Mr Jones.

You may run into incompatible class versions issue. Basically you have altogehter 2 different JVMs. One for EJBs (utility framework as you defiined using 1.3). Another JVM is weblogic server using JDK 1.6 where you have Client to remotely access those EJBs methods. Going back, when you generate the client stubs and skeletons, and refer them on your client side, did you ran into any issues like with incompatible class versions.
Goud

How to view weblogic log files from a browser

Hi,
I am running WebLogic Server 7.03 on Solaris 8.
I have one Admin and multiple Managed servers running.
Each creates its own log file.
Is there anyway I can access this log files from the browser ?
In Apache, you can create a link from htdocs dir to the logs dir
and then view the log files from the browser. Is there a similar
mechanism in Weblogic server.
A quick response is well appreciated.
Thanks in advance.
-Anil Varma

If you are on a unix system you can do something similar by making an open
directory webapp with symbolic links to the weblogic log directories. I suggest
that you protect that webapp with administration access only.
Sam
Anil Varma wrote:
Hi,
I am running WebLogic Server 7.03 on Solaris 8.
I have one Admin and multiple Managed servers running.
Each creates its own log file.
Is there anyway I can access this log files from the browser ?
In Apache, you can create a link from htdocs dir to the logs dir
and then view the log files from the browser. Is there a similar
mechanism in Weblogic server.
A quick response is well appreciated.
Thanks in advance.
-Anil Varma

Unwanted stack trace in weblogic.log for thrown JSP Exceptions

We are throwing a JSP exception within a custom tag when data validation
          errors occur; the errorPage for the JSP page is then invoked to show the
          appropriate errors. However, in the weblogic.log, a stack trace is shown
          indicating the exception (example below). We do not want this stack track
          shown unless there is a real "error" in our system vs. invoking the
          errorPage to show "application" errors. Is there any way to supress this,
          as we are not explicitly causing this to happen. It appears to be a
          weblogic feature. This causes us problems in finding true system errors
          that might be occurring due to these non-problems showing up in the
          weblogic.log.
          Thanks for the help.
          John Bauer
          Wed Dec 20 15:34:49 EST 2000:<E> <ServletContext-General> exception raised
          on '/test/test.jsp'
          javax.servlet.ServletException: runtime failure in custom tag 'testtag'
          at jsp_servlet._test._test._jspService(_test.java:89)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :124)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:
          60)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:
          07)
          at
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
          Manager
          java:251)
          at
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
          at
          weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
          Code)


The design of the data entry pages is such that the error page is the same
          page as the data entry page, and a validation JSP tag validates the data and
          if it finds a problem, it will set some variables and throw a JSP exception
          to redisplay the page. Unfortunately, we are forced to live with this
          design. Are you aware of any mechanism to suppress the automatic logging of
          thrown JSP exceptions in the weblogic log?
          Thanks,
          JDB
          Cameron Purdy <[email protected]> wrote in message
          news:[email protected]...
          > Exception handling for custom tags is very poorly handled right now. For
          > one thing, WL hides the actual exception.
          >
          > However, the way that you are doing this seems very odd. The error page
          is
          > for server errors, not user typos.
          >
          > Peace,
          >
          > --
          > Cameron Purdy
          > Tangosol, Inc.
          > http://www.tangosol.com
          > +1.617.623.5782
          > WebLogic Consulting Available
          >
          >
          > "John Bauer" <[email protected]> wrote in message
          > news:[email protected]...
          > > We are throwing a JSP exception within a custom tag when data validation
          > > errors occur; the errorPage for the JSP page is then invoked to show the
          > > appropriate errors. However, in the weblogic.log, a stack trace is
          shown
          > > indicating the exception (example below). We do not want this stack
          track
          > > shown unless there is a real "error" in our system vs. invoking the
          > > errorPage to show "application" errors. Is there any way to supress
          this,
          > > as we are not explicitly causing this to happen. It appears to be a
          > > weblogic feature. This causes us problems in finding true system errors
          > > that might be occurring due to these non-problems showing up in the
          > > weblogic.log.
          > >
          > > Thanks for the help.
          > > John Bauer
          > >
          > > Wed Dec 20 15:34:49 EST 2000:<E> <ServletContext-General> exception
          raised
          > > on '/test/test.jsp'
          > > javax.servlet.ServletException: runtime failure in custom tag 'testtag'
          > > at jsp_servlet._test._test._jspService(_test.java:89)
          > > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          > > at
          > >
          >
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          > > :124)
          > > at
          > >
          >
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          > > l.java:
          > > 60)
          > > at
          > >
          >
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          > > l.java:
          > > 07)
          > > at
          > >
          >
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
          > > Manager
          > > java:251)
          > > at
          > >
          >
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
          > > at
          > > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
          > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
          Compiled
          > > Code)
          > >
          > >
          >
          >

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

G5 locks up when logging out and other concern

This has become a problem over the past year. I know that it is an old single processor, first of the Power Macs, legacy machine and OS. I have gone through all various check system/disk evolutions with Apple and TechTool Utilities.
Also, when I have a software glitch, I can never get the Send To Apple report to "send". I get a message that reads something along the line of 'not being able to connect to Apple'. Why, the legacy problem again? If so, I am suprized that I get iTunes and Safari updates.

I don't think it has anything to do with it being a "legacy" Mac. I have a Power Mac G5, running Leopard, and it runs quite well.
Locking up when logging out is usually caused by a process that is running and the OS is not able to quit it. It may be related to an app, or it may be a background process. If you restart (or log out and log in) and then immediately log out, does it lock up?
As a test, you can try creating a new user account in System Preferences Accounts pane. Log out of your usual account and log in to the new account. Do some things you normally do, then try logging out. Does it lock up?

WLS Locks on weblogic/logging/ConsoleHandler

Similar Messages

Maybe you are looking for