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.

Similar Messages

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.

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

Integration of Commons Logging framework with Weblogic

Hi,
We are trying to use Apache commons logging framework and trying to publish log mesages in Weblogic so that messages can be seen through console and all the Logging configurations can be managed from Admin console. I tried using the below steps:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/logging/config_logs.html#using_commons
But these does not seems to be working for User defined handlers. I am able to see the logs in the default odl-handler file but not able to log the messages through the handlers defined by me.
Can anyone help me on this.
Regards,
Anuj

Hi,
We are able to see reports through Workspace. We are facing problem after
integrating Hyperion Interactive Reporting with Weblogic Portal. we are able to see the sections like Query,Report,Results but we are not able to see the content after selecting any one of the section mentioned above.
System Configuration:
Hyperion Interactive Reporting 9.3.1
App Server: Weblogic server 9.2
Web Server: Apache 2.0.52
Database: Oracle 9.0.1.
Operating System: Windows 2003 with SP1
Browser: I.E 6.0
With Workspace everything is working fine. After Integration we are facing problem.
Regards,
S.Suresh.

Logging with Weblogic 10.3

Hello,
I am wondering how to manipulate the server logging with WebLogic 10.3. I get an error while deploying and I need further information for the packages concerning the named queries and for that I need to turn up the log level for this packages. Do I need to manipulate the config/logging.xml or which file?
Thank you

If you are deploying via the WebLogic admin console, here's the reference to configure logging level:
Administration Console Online Help - [View and configure logs|http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/logging/ConfigureAndViewLogs.html]
If deploying from command line, try including the -debug flag?
(weblogic.Deployer Command-Line Reference - [Common Arguments|http://download.oracle.com/docs/cd/E12840_01/wls/docs103/deployment/wldeployer.html#wp1010461])

What's wrong with the weblogic.log file?

Currently we got a problem and don't know what it means -
our weblogic.log file grows very fast by generating huge amount of logs like:
####<Feb 18, 2003 10:29:13 AM CST> <Info> <DGCserver> <awhq7232.whq.ual.com> <ECSserver>
<ExecuteThread: '13' for queue: 'default'> <> <> <000000> <Tried to renew lease
on lost reference: '1160'>
I counted and found that weblogic.log adds in at least 50 such logs per minute
and its size imcreases about 20M per day. But the application still work normally.
Could you experts help us on the following questions:
- Why WebLogic Container generates so many "Info" kind of logs?
- Could we config the WebLogic Server to avoid such "Info" kind of logs being
written into weblogic.log file?
Thank you very much!
Bill Yuan

It is harmless - it means that by the time server got to process lease
renewal message object is already gone.
You may want to check with support - I think there was a fix which supressed
this message.
Bill Yuan <[email protected]> wrote:
Currently we got a problem and don't know what it means -
our weblogic.log file grows very fast by generating huge amount of logs like:
####<Feb 18, 2003 10:29:13 AM CST> <Info> <DGCserver> <awhq7232.whq.ual.com> <ECSserver>
<ExecuteThread: '13' for queue: 'default'> <> <> <000000> <Tried to renew lease
on lost reference: '1160'>
I counted and found that weblogic.log adds in at least 50 such logs per minute
and its size imcreases about 20M per day. But the application still work normally.
Could you experts help us on the following questions:
- Why WebLogic Container generates so many "Info" kind of logs?
- Could we config the WebLogic Server to avoid such "Info" kind of logs being
written into weblogic.log file?
Thank you very much!
Bill Yuan--
Dimitri

Has anyone used JAAS with WebLogic?

Has anyone used JAAS with Weblogic? I was looking at their example, and I have a bunch of questions about it. Here goes:
Basically the problem is this: the plug-in LoginModule model of JAAS used in WebLogic (with EJB Servers) seems to allow clients to falsely authenticate.
Let me give you a little background on what brought me to this. You can find the WebLogic JAAS example (to which I refer below) in the pdf: http://e-docs.bea.com/wls/docs61/pdf/security.pdf . (I believe you want pages 64-74) WebLogic, I believe goes about this all wrong. They allow the client to use their own LoginModules, as well as CallBackHandlers. This is dangerous, as it allows them to get a reference (in the module) to the LoginContext's Subject and authenticate themselves (i.e. associate a Principal with the subject). As we know from JAAS, the way AccessController checks permissions is by looking at the Principal in the Subject and seeing if that Principal is granted the permission in the "policy" file (or by checking with the Policy class). What it does NOT do, is see if that Subject
has the right to hold that Principal. Rather, it assumes the Subject is authenticated.
So a user who is allowed to use their own Module (as WebLogic's example shows) could do something like:
//THEIR LOGIN MODULE (SOME CODE CUT-OUT FOR BREVITY)
public class BasicModule implements LoginModule
private NameCallback strName;
private PasswordCallback strPass;
private CallbackHandler myCB;
private Subject subj;
         //INITIALIZE THIS MODULE
           public void initialize(Subject subject, CallbackHandler callbackHandler, Map sharedState, Map options)
                  try
                       //SET SUBJECT
                         subj = subject; //NOTE: THIS GIVES YOU REFERENCE
TO LOGIN CONTEXT'S SUBJECT
                                                 // AND ALLOWS YOU TO PASS
IT BACK TO THE LOGIN CONTEXT
                       //SET CALLBACKHANDLERS
                         strName = new NameCallback("Your Name: ");
                         strPass = new PasswordCallback("Password:", false);
                         Callback[] cb = { strName, strPass };
                       //HANDLE THE CALLBACKS
                         callbackHandler.handle(cb);
                  } catch (Exception e) { System.out.println(e); }
     //LOG THE USER IN
       public boolean login() throws LoginException
          //TEST TO SEE IF SUBJECT HOLDS ANYTHING YET
          System.out.println( "PRIOR TO AUTHENTICATION, SUBJECT HOLDS: " +
subj.getPrincipals().size() + " Principals");
          //SUBJECT AUTHENTICATED - BECAUSE SUBJECT NOW HOLDS THE PRINCIPAL
           MyPrincipal m = new MyPrincipal("Admin");
           subj.getPrincipals().add(m);
           return true;
         public boolean commit() throws LoginException
               return true;
    }(Sorry for all that code)
I tested the above code, and it fully associates the Subject (and its principal) with the LoginContext. So my question is, where in the process (and code) can we put the LoginContext and Modules so that a client cannot
do this? With the above example, there is no Security. (a call to: myLoginContext.getSubject().doAs(...) will work)
I think the key here is to understand JAAS's plug-in security model to mean:
(Below are my words)
The point of JAAS is to allow an application to use different ways of authenticating without changing the application's code, but NOT to allow the user to authenticate however they want.
In WebLogic's example, they unfortunately seem to have used the latter understanding, i.e. "allow the user to authenticate however they want."
That, as I think I've shown, is not security. So how do we solve this? We need to put JAAS on the server side (with no direct JAAS client-side), and that includes the LoginModules as well as LoginContext. So for an EJB Server this means that the same internal permission
checking code can be used regardless of whether a client connects through
RMI/RMI-IIOP/JEREMIE (etc). It does NOT mean that the client gets to choose
how they authenticate (except by choosing YOUR set ways).
Before we even deal with a serialized subject, we need to see how JAAS can
even be used on the back-end of an RMI (RMI-IIOP/JEREMIE) application.
I think what needs to be done, is the client needs to have the stubs for our
LoginModule, LoginContext, CallBackHandler, CallBacks. Then they can put
their info into those, and everything is handled server-side. So they may
not even need to send a Subject across anyways (but they may want to as
well).
Please let me know if anyone sees this problem too, or if I am just completely
off track with this one. I think figuring out how to do JAAS as though
everything were local, and then putting RMI (or whatever) on top is the
first thing to tackle.

Send this to:
newsgroups.bea.com / security-group.

EJB 3.0 MDB deployment issue with weblogic 10.0

Hi there,
I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
Unable to deploy EJB: MessageBean from Message.jar:
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     Truncated. see log file for complete stacktrace
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
     at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
     Truncated. see log file for complete stacktrace
>
Any help really appreciated. It's too urgent.
Thanks in advance,
Piyush

here is the code for my bean.
package com.ups;
import java.util.logging.Logger;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.EJBException;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
* Message-Driven Bean implementation class for: MessageBean
@MessageDriven(
          activationConfig = { @ActivationConfigProperty(
                    propertyName = "destinationType", propertyValue = "javax.jms.Queue"
public class MessageBean implements MessageListener {
     private MessageDrivenContext mdc;
* Default constructor.
public MessageBean() {
// TODO Auto-generated constructor stub
* @see MessageListener#onMessage(Message)
public void onMessage(Message message) {
     TextMessage tmsg = null;
try {
tmsg = (TextMessage) message;
System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
System.out.println ("The onMessage() is called");
} catch (JMSException e) {
e.printStackTrace( );
mdc.setRollbackOnly( );
catch (Throwable th) {
th.printStackTrace();
public void ejbRemove( )throws EJBException{
     System.out.println("ejbRemove() is executed >>>>>>>");
I have configured my JMS Distributed queue in the Weblogic.
If possible please provide more details so that I can get rid of this error as soon as possible.
Thanks for reply.
Piyush

Security violation exception with Weblogic cluster installation on OIm 9.1

Hi,
I have OIM9.1 installed on weblogic 8.1 SP4 in clustered environment, which more often than not seems to work fine. But some time I get following exception on server console/log file which causes certain provisioning task to be rejected...
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: javax.ejb.AccessLocalException: [EJB:010160]Security Violation: User: 'xelsysad
m' has insufficient permission to access EJB: type=<ejb>, application=Xellerate, module=xl
DataObjectBeans.jar, ejb=tcFormInstanceOperations, method=create, methodInterface=LocalHom
e, signature={}.
at weblogic.ejb20.internal.MethodDescriptor.checkMethodPermissionsLocal(MethodDesc
riptor.java:486)
at weblogic.ejb20.internal.StatelessEJBLocalHome.create(StatelessEJBLocalHome.java
:80)
at com.thortech.xl.ejb.beans.tcFormInstanceOperations_2j82mm_LocalHomeImpl.create(
tcFormInstanceOperations_2j82mm_LocalHomeImpl.java:93)
... 126 more
ERROR,19 Dec 2008 14:20:03,752,[XELLERATE.APIS],Class/Method: tcBaseUtilityClient/getLocal
Interface encounter some problems: {1}
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.in
Problem is, I get this exception only 4 out of 6 times (when it is least expected). I have googled, and tried all possible means but have't been able to resolve it. One more thing I am sure of is, it only comes with Weblogic installation not with Jboss. So there should be some configuration issue with weblogic installation.
Any suggestions would be useful...

No Response???
Where are the good guys??

Error while deploying application with WebLogic server

Hi,
I use Jdeveloper 11g and created and ADF application which i want to deploy with WebLogic Server.But i have an error which is :
"There was a failure when processing annotations for application C:\...\xxx.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet "
Plz help me.
Thx

I am receiving same message for simple servlet. Running JDev11g build 5166 and embedded WLS 10.3. Servlet used to deploy to embedded WLS and ran fine. Recently running newly created servlets produces error message as in this thread.
Investigation turned up the fact that the class file for the servlet was not deployed to the context-root (o.j2ee\drs) on the server. Copying the class file from the mywork project folder to the context-root folder (o.j2ee\drs) permitted the servlet to run.
Don't know if this is the cause of what you are experiencing but it may assist in your investigation! I have not figured out why the class file for servlets does not deploy to server despite the fact that the log file shows war and ear files were deployed. As it turns out, the war file does not have the class file in it so something is wrong before the war file is created.
Cheers!

Problem with Weblogic Commerce Server 3.1

I am currently evaluating the Weblogic Commerce server 3.1 product. I have
installed the Weblogic server 5.1 and the service pack 6 along with the
Commerce Server. I can get into the WLCS Commerce Server Templates and can
navigate the store categories and search for items but when I try to add to
the shopping cart or view the shopping cart I get taken to the 'servererror'
template. I have included at the bottom of this message the message from
the log file. Does anyone have any idea why I am getting this error?
Thanks in advance,
Barry Childs
Manager Knowledgebase Applications
Xactsites
<<<<<<< weblogic.log >>>>>>>
Fri Nov 10 14:00:16 MST 2000:<E> <WebAppServletContext-wlcs> Servlet failed
with Exception
weblogic.servlet.jsp.JspException: (line -1): Error in tag library at: 'wl':
For tag 'repeat', cannot load extra info class
'weblogicx.jsp.tags.RepeatTagInfo'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java,
Compiled Code)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java,
Compiled Code)
at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java,
Compiled Code)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java, Compiled
Code)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
Compiled Code)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:154)
at
com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestinat
ion(ServletDestinationHandler.java:51)
at
com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:376
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)

I am currently evaluating the Weblogic Commerce server 3.1 product. I have
installed the Weblogic server 5.1 and the service pack 6 along with the
Commerce Server. I can get into the WLCS Commerce Server Templates and can
navigate the store categories and search for items but when I try to add to
the shopping cart or view the shopping cart I get taken to the 'servererror'
template. I have included at the bottom of this message the message from
the log file. Does anyone have any idea why I am getting this error?
Thanks in advance,
Barry Childs
Manager Knowledgebase Applications
Xactsites
<<<<<<< weblogic.log >>>>>>>
Fri Nov 10 14:00:16 MST 2000:<E> <WebAppServletContext-wlcs> Servlet failed
with Exception
weblogic.servlet.jsp.JspException: (line -1): Error in tag library at: 'wl':
For tag 'repeat', cannot load extra info class
'weblogicx.jsp.tags.RepeatTagInfo'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java,
Compiled Code)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java,
Compiled Code)
at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java,
Compiled Code)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java, Compiled
Code)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
Compiled Code)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:154)
at
com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestinat
ion(ServletDestinationHandler.java:51)
at
com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:376
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)

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

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

NPE in stopWeblogic.cmd with Server Logging Bridge

I'm migrating an EAR that depends on JDK logging to WLS 10.3.3. To activate the JDK logging in my domain logs I followed [url http://download.oracle.com/docs/cd/E14571_01/web.1111/e13739/logging_services.htm#WLLOG199]the instructions given in the WLS manual. The logging part works as expected now. However, my stopWeblogic.cmd fails with the following NPE:
Stopping Weblogic Server...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3://DT04748:7001 with userid weblogic ...
WLST detected that the RuntimeMBeanServer is not enabled. This
might happen if the RuntimeMBeanServer is disabled via the JMXMBean.
Please ensure that this MBeanServer is enabled. Online WLST cannot
function without this MBeanServer.
This Exception occurred at Thu Jan 06 13:20:24 CET 2011.
java.lang.NullPointerException
        at weblogic.logging.ServerLoggingHandler.publish(ServerLoggingHandler.java:24)
        at java.util.logging.Logger.log(Logger.java:481)
        at java.util.logging.Logger.doLog(Logger.java:503)
        at java.util.logging.Logger.logp(Logger.java:619)
        at com.sun.jmx.remote.util.ClassLogger.finer(ClassLogger.java:130)
        at com.sun.jmx.remote.util.ClassLogger.trace(ClassLogger.java:88)
        at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:333)
        at weblogic.management.remote.common.WLSRMIConnector.doConnect(WLSRMIConnector.java:150)
        at weblogic.management.remote.common.WLSRMIConnector.access$100(WLSRMIConnector.java:27)
        at weblogic.management.remote.common.WLSRMIConnector$2.run(WLSRMIConnector.java:138)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
        at weblogic.security.Security.runAs(Security.java:61)
        at weblogic.management.remote.common.WLSRMIConnector.connect(WLSRMIConnector.java:136)
        at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
        at weblogic.management.scripting.WLSTHelper.lookupMBeanServerConnection(WLSTHelper.java:678)
        at weblogic.management.scripting.WLSTHelper.initRuntimeServerConnection(WLSTHelper.java:398)
        at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:315)
        at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
        at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61)
        at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:147)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.python.core.PyReflectedFunction.__call__(Unknown Source)
        at org.python.core.PyMethod.__call__(Unknown Source)
        at org.python.core.PyObject.__call__(Unknown Source)
        at org.python.core.PyObject.invoke(Unknown Source)
        at org.python.pycode._pyx4.connect$1(<iostream>:16)
        at org.python.pycode._pyx4.call_function(<iostream>)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyFunction.__call__(Unknown Source)
        at org.python.pycode._pyx15.f$0(D:\Oracle\Middleware\user_projects\domains\FLUX\shutdown.py:6)
        at org.python.pycode._pyx15.call_function(D:\Oracle\Middleware\user_projects\domains\FLUX\shutdown.py)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyCode.call(Unknown Source)
        at org.python.core.Py.runCode(Unknown Source)
        at org.python.util.PythonInterpreter.execfile(Unknown Source)
        at weblogic.management.scripting.WLST.main(WLST.java:131)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at weblogic.WLST.main(WLST.java:29)
Problem invoking WLST - Traceback (innermost last):
File "D:\Oracle\Middleware\user_projects\domains\FLUX\shutdown.py", line 6, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : "Cannot connect to WLST."
Use dumpStack() to view the full stacktrace
Done
Stopping Derby Server...
Steps to reproduce
1. Create a logging.properties file with the following contents:
# Specify the handlers to create in the root logger
handlers = weblogic.logging.ServerLoggingHandler
# Register handlers for my.app and their child loggers
my.app.handlers = java.util.logging.ConsoleHandler, weblogic.logging.ServerLoggingHandler
# Do not send the my.app log messages to the root handler
my.app.useParentHandlers = false
# Set the default logging level for the root logger
.level = ALL
# Set the default logging level for new ConsoleHandler instances
java.util.logging.ConsoleHandler.level = INFO
# Set the default logging level for new FileHandler instances
weblogic.logging.ServerLoggingHandler.level = ALL2. Add the following directive in the setDomainEnv.cmd:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.util.logging.config.file=path/to/logging.properties3. Start-stop the domain and the above NPE occurs while WLS keeps running. Remove the directive from step 2 and the start-stop sequence goes back to normal.
Environment
Oracle JDK:
java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) Client VM (build 19.0-b09, mixed mode, sharing)OS: Windows XP Pro SP3
Your help would be very much appreciated! Please let me know if you need any additional info.
Thanks,
Bas

Hi Sandeep,
Thanks a lot for your quick reply! You were right, the logging directive was used both client and server side. I moved
-Djava.util.logging.config.file=path/to/logging.propertiesfrom setDomainEnv.cmd to startWeblogic.cmd and WLS can be stopped correctly now.
Regards,
Bas

Problem in developing jasper report in BEA workspace studio version 1.1 with weblogic server 10.0

Hi! all,
Myself developing a jasperReport in BEA workspace studio 1.1 and always getting the below mentioned exception, though i have run the same code in NetBeans successfully with the same jar file.
Even i have added weblogic.jar, wllog4j.jar, classes12.jar, commons-beanutils-1.8.0.jar, commons-collections-2.1.1.jar, commons-digester-1.7.jar, commons-javaflow-20060411.jar, commons-logging-1.0.4.jar, iText-2.1.7.jar, jasperreports-3.7.1.jar, jasperreports.jar, jasper-jdt-6.0.13.jar, jasper-compiler-jdt.jar, jasper-compiler.jar, jasper-runtime.jar, jasperreports-3.5.1.jar, jasperreports-2.0.5.jar in the WEB-INF/lib directory as well as build path. please help me.Thanks in advance.
==============================================================
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/logging/WLLogRecord : weblogic/logging/LogEntry
     at java.lang.ClassLoader.findBootstrapClass(Native Method)
     at java.lang.ClassLoader.findBootstrapClass0(ClassLoader.java:891)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:301)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at weblogic.logging.commons.LogFactoryImpl.getInstance(LogFactoryImpl.java:21)
     at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
     at org.apache.commons.digester.Digester.<init>(Digester.java:304)
     at net.sf.jasperreports.engine.xml.JRXmlDigester.<init>(JRXmlDigester.java:62)
     at net.sf.jasperreports.engine.xml.JRXmlDigesterFactory.createDigester(JRXmlDigesterFactory.java:980)
     at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:203)
     at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:168)
     at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:152)
     at net.sf.jasperreports.engine.JasperCompileManager.compileReport(JasperCompileManager.java:150)
     at com.generateJasperReport.test.GasperReportNew.main(GasperReportNew.java:38)
==============================================================================
My Code is..........................
============================
package com.generateJasperReport.test;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.util.HashMap;
import java.util.Map;
//import weblogic.logging.LogEntry;
import net.sf.jasperreports.engine.JRException;
import net.sf.jasperreports.engine.JRResultSetDataSource;
import net.sf.jasperreports.engine.JasperCompileManager;
import net.sf.jasperreports.engine.JasperExportManager;
import net.sf.jasperreports.engine.JasperFillManager;
import net.sf.jasperreports.engine.JasperPrint;
import net.sf.jasperreports.engine.JasperReport;
import net.sf.jasperreports.view.JasperViewer;
public class GenerateJasperReport {
     static JRResultSetDataSource jrds = null;
     static ResultSet rs = null;
     public static Connection connectDB() {
          Connection jdbcConnection = null;
          try {
               Class.forName("oracle.jdbc.driver.OracleDriver");
               jdbcConnection = DriverManager.getConnection(
                         "jdbc:oracle:thin:@192.161.5.35:1521:abc",
                         "xyz", "pqr");
          } catch (Exception ex) {
               String connectMsg = "Could not connect to the database: "
                         + ex.getMessage() + " " + ex.getLocalizedMessage();
               System.out.println(connectMsg);
          return jdbcConnection;
     public static void main(String[] args) throws JRException {
          Connection con = connectDB();
          JasperReport jasperReport=null;
          System.out.println("666666666666666666");
          String reportSource = "E:\\Pintu\\Project\\Bea Project\\workspace\\GenerateJasperReport\\src\\com\\generateJasperReport\\jrxmlFile\\JasperReportGeneration.jrxml";
          String reportDest = "E:\\Pintu\\Project\\Bea Project\\workspace\\GenerateJasperReport\\src\\com\\generateJasperReport\\output\\JasperReportGeneration.pdf";
          System.out.println("555555555555555");
          Map <String,String>parammap = new HashMap<String,String>();
          parammap.put("ReportTitle", "PDF JasperReport");
          System.out.println("444444444444444");
          try {
               try{
                    jasperReport = JasperCompileManager
                         .compileReport(reportSource);
               }catch(JRException e){e.printStackTrace();}
               System.out.println("ssssssssssssss");
               JasperPrint jasperPrint = JasperFillManager.fillReport(
                         jasperReport, parammap, con);
               System.out.println("vvvvvvvvvvvvvvv");
               JasperExportManager.exportReportToPdfFile(jasperPrint, reportDest);
               System.out.println("kkkkkkkkkkkkkkkkkkk");
               JasperViewer.viewReport(jasperPrint);
               System.out.println("gfrfrrrertfewrw");
          } catch (Exception ex) {
               ex.printStackTrace();
===========================================================

Thanks for the information. It makes so much more sense to do the configuration from within PFR instead of WLS but the engineer insisted I could just do everything from within the WLS config wizard. I'm very relieved that someone has had success with this.
Am I supposed to do the configuration wizard in WLS before doing the Configure Classic Interface from PFR?
Since we're only going to be using the PC for the developer, I wasn't sure how much of the Web Logic Server needed to be configured.
The Oracle engineer said to choose 'Oracle Ent. Mgr' and 'Oracle Classic 11g' from the WLS Config Wizard which I did - but now I have a choice on the 'Optional Configuration' page to choose 'Administration Server', 'Managed Servers', 'Deployments and Services' and 'RDMBS Security Store'. I'm not sure if I'm supposed to choose any of these. I want to be able to talk to the Solaris server that is going to be my application server via WLS and I'm not sure if I need any of these.
In your environment, are you developing 11g forms on a PC but hosting on another platform? I have a Windows 7 64 bit machine but was told I had to set up a 32bit XP VM on my Win7 machine to use Forms and Reports for development.

Re: Pb with weblogic.log

Similar Messages

Maybe you are looking for