Weblogic 9.0 WLDF Instrumentation

I am tryin to understand WLDF Instrumentation capabilities by looking at MedRecServer --> MedRecWLDF--> Instrumentation --> DyeInjection configuration.
It loooks like that DyeInjection monitor sets DiagnosticContext when request enters into the weblogic server with following properties.
ADDR1=127.0.0.1
USER1=[email protected]
I have executed request with above properties in medrec application.
What I am trying to find is How to access diagnostic context/data/information as result of the execution of DyeInjection monitor ?
Thank you,
-Jayesh

Hi Jayesh,
Instrumentation ("event") data is stored in the WLDF archive, in a binary store. This data can be accessed viewed via the WLS Console, via the WLST "exportDiagnosticData" command, and programmatically via the WLDF Accessor APIs.
To view data via the console, log into the console and choose
Diagnostics -> Log Files
select the "EventsDataArchive" radio button, and click the "View" button. You can also specify custom query parameters via the "Customize this table" link.
See
http://e-docs.bea.com/wls/docs90/wldf_configuring/access_diag_data.html#1099608
for info on accessing WLDF data,
http://e-docs.bea.com/wls/docs90/wldf_configuring/config_prog_intro.html#1043185
for an introduction on programming using the WLDF APIs, and
http://e-docs.bea.com/wls/docs90/wldf_configuring/appendix_query.html#1043050
for information on the WLDF query language.
Regards,
Mike Cico

Similar Messages

WLDF - Instrumentation for EJB call statistics

Hello,
I'm new with Weblogic and I'm looking for stats concerning my ejbs. I'm using weblogic 10.3.
With JMX I have only found data concerning EJB pool size but no statistics (like execution time)
thus, I'm looking for instrumentation using WLDF to see if it is possible to get the execution time of an EJB method.
Firstly, I try to instrument a method, i've used the following weblogic-diagnostic.xml file.
<wldf-resource xmlns="http://www.bea.com/ns/weblogic/90/diagnostics">
     <instrumentation>
     <enabled>true</enabled>
     <include>com.gemalto.*</include>
     <wldf-instrumentation-monitor>
     <name>ConfigurationManagerBean_Monitor</name>
<enabled>true</enabled>
     <action>DisplayArgumentsAction</action>
<location-type>before</location-type>
<pointcut>execution(public * com.xxx.* get*(...))</pointcut>
     </wldf-instrumentation-monitor>
     </instrumentation>
</wldf-resource>
When I put this file into my MEAT-INF EAR, the deploying is OK but I'cant see nothing into WLDF console extension ?
Could you please explain me a little bit how to configure correctly my instrumentation ?
Thank you a lot.
C.

When I put this file into my MEAT-INF EAR, the deploying is OK but I'cant see nothing into WLDF console extension ?Are there events in the WLDF Archive for the deployed monitor? Have you enabled Instrumentation through a WLDF System Resource targeted to the server?
In order to view instrumentation data through the console extension,
- the WLDF DyeInjection monitor needs to be deployed through the WLDF SystemResouce at server scope as well.
- the application monitors must be of the "Around" type with the TraceElapsedTimeAction assigned to them
Then the console extension can build a call-tree of known requests that have passed through the server, based on each request's Diagnostic Context ID.
If you truly want to view information from the DisplayArgumentsAction, you will need to view the data stored in the WLDF Archive using the WLS Console, or WLST. In the Console, you can view the data by navigating to Diagnostic Modules -> Logs and selecting the EventsDataArchive "log". On the resulting page you can customize your views (the default view only shows you the last 5 minutes of data in the archive, I believe).
Using WLST you can use the exportDiagnosticData (offline) or exportDiagnosticDataFromServer (online) functions. See the WLST help on these functions for details on how to use them.
Mike

Custom weblogic instrumentation does not work for me :(

Hello.
First of all excuse me about my english.
I have developed a simple class, I have compile it, and I have packaged it into a war file.
The application Works ok when I do a request: http://192.168.1.5:7100/simple/hello
But when I want to instrumentalize it, it cannot works. I have enabled instrumentation, but it I don't see anything in: Request Performance.
Can you help me?.
These are the files:
simple_temp3
|
+- hello.html
|
+- WEB-INF
     +- web.xml
     |
+- META-INF
     +- weblogic-diagnostics.xml
          |
     +- classes
         +- edu
             +- ucla
                 +- hello.class
[weblogic@localhost simple_temp3]$ cat hello.html
<html>
    <head><title>Hello World</title></head>
    <body><h1>Hello World</h1></body>
</html>
[weblogic@localhost simple_temp3]$ cat META-INF/weblogic-diagnostics.xml
<wldf-resource xmlns="http://www.bea.com/ns/weblogic/90/diagnostics"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/diagnostics.xsd">
    <name>Sample WLDF resource</name>
    <instrumentation>
          <enabled>true</enabled>
              <wldf-instrumentation-monitor>
                  <name>sample</name>
                  <enabled>true</enabled>
                  <action>TraceElapsedTimeAction</action>
                  <location-type>around</location-type>
              </wldf-instrumentation-monitor>
    </instrumentation>
</wldf-resource>
[weblogic@localhost simple_temp3]$ cat WEB-INF/web.xml
<web-app id="simple" version="2.4">
    <welcome-file-list>
            <welcome-file>hello.html</welcome-file>
    </welcome-file-list>
<servlet>
    <servlet-name>Hello</servlet-name>
        <servlet-class>Hello</servlet-class>
</servlet>
<servlet-mapping>
     <servlet-name>Hello</servlet-name>
         <url-pattern>/hello</url-pattern>
</servlet-mapping>
</web-app>
[weblogic@localhost simple_temp3]$ cat WEB-INF/classes/edu/ucla/Hello.java (this is the source Class)
import javax.servlet.Servlet;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.io.IOException;
import java.io.PrintWriter;
public class Hello extends HttpServlet implements Servlet {
    public Hello() {}
    protected void doGet(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        PrintWriter out = response.getWriter();
        out.println("<HTML>");
        out.println("<HEAD><TITLE>Hello World</TITLE></HEAD>");
        out.println("<BODY>");
        out.println("<H1>Hello World</H1>");
        out.println("Today is: " + (new java.util.Date().toString()) );
        out.println("</BODY></HTML>");
        out.close();

Can anyone help me?

How best to debug Weblogic 10.3 request slowness

We recently migrated our app from another container to Weblogic 10.3 and are having significant performance problems. We are struggling to put our finger on the actual issue. Does anyone have any suggestions for debugging the below problem that might push us in a direction to resolve this?
Client is a standalone process and the server process is a stateless session bean in a 3 managed server cluster w/ 'random-affinity' load balancing policy (we have to use this policy due to other app requirements). When the client calls the ejb we see either the request to the server get delayed or the response back from the server get delayed. Here is example of getting delayed coming back.
Client - 14.29.20.875 findByFilter() RQID=1289593760875 - START
Server - 14:29:20.878 findByFilter() RQID=1289593760875_null - START
Server - 14:29:20.892 findByFilter() - FINISHED - 13 ms
Client - 14.29.22.879 findByFilter() - FINISHED - returned in 2004 ms.This call does a simple select against our database and we are not setting a container managed transaction strategy so no transaction is being explicitly created. The object returned from this call is only 3 KB. We don't understand where the ~ 1.9 seconds are going. They seem to be lost to WL post method processing, network latency, or something else. Has anyone run into this or has any suggestions for what to look at from a WL perspective to debug further?
Lance Johnson

You can use a diagnostic module to debug the timing. The diagnostic module must be placed
in the META-INF directory (also where application.xml is located) and must be called weblogic-diagnostics.xml.
An example of a diagnostic module is the following:
<?xml version="1.0" encoding="UTF-8"?>
<wldf-resource xmlns="http://xmlns.oracle.com/weblogic/weblogic-diagnostics"
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-diagnostics
               http://xmlns.oracle.com/weblogic/weblogic-diagnostics/1.0/weblogic-diagnostics.xsd">
    <instrumentation>
        <enabled>true</enabled>
        <wldf-instrumentation-monitor>
            <name>AddKlantInstrumentationEJB</name>
            <action>MethodInvocationStatisticsAction</action>
            <location-type>around</location-type>
            <pointcut>execution(* datamodel.logic.BedrijfBean addKlant(...))</pointcut>
        </wldf-instrumentation-monitor>
        <wldf-instrumentation-monitor>
            <name>OnMessageInstrumentationMDB</name>
            <action>MethodInvocationStatisticsAction</action>
            <location-type>around</location-type>
            <pointcut>execution(* datamodel.logic.BedrijfMDB onMessage(...))</pointcut>
        </wldf-instrumentation-monitor>
    </instrumentation>
</wldf-resource>You also need to a create diagnostic system modules using the WebLogic Console and target the module
to the appropriate server and enable instrumentation using the Enabled checkbox on the Instrumentation Configuration tab.
The information recorded by the MethodInvocationStatisticsAction is available through the application's
WLDFInstrumentationRuntime MBean. This MBean has a MethodInvocationStatistics attribute that returns
a nested set of maps containing of all the recorded statistics for the application. It also has a getMethodInvocationStatisticsData()
operation that allows you to query for a subset of the data. The listing below is an example WLST script that
queries the WLDFInstrumentationRuntimeMBean and displays all of the results. For example
connect('weblogic','transfer11g');
cd('serverRuntime:/WLDFRuntime/WLDFRuntime/WLDFInstrumentationRuntimes/ApplicationName');
def formatTime(t):
     return "%.2f" % (t/1e6)
print('OBTAINING STATISTICS');
for classStats in cmo.getMethodInvocationStatistics().entrySet():
     print('OBTAINED THE CLASS STATISTICS');
     for methodStats in classStats.value.entrySet():
          print('OBTAINED THE METHOD STATISTICS');
          for signatureStats in methodStats.value.entrySet():
               print('PRINTING SOME OUTPUT');
               print "%s.%s(): %d %s %s %s %s" % (
                    classStats.key,
                    methodStats.key,
                    signatureStats.value['count'],
                    formatTime(signatureStats.value['min']),
                    formatTime(signatureStats.value['avg']),
                    formatTime(signatureStats.value['max']),
                    formatTime(signatureStats.value['std_deviation']),)If you run the above WLST script, you see something like the following output:
model.logic.VideotheekWizardBean.confirm(): 50 1.52 8.46 66.94 11.09
model.logic.VideotheekMDB.onMessage():      50 0.13 0.75 2.46 0.70All values are in milliseconds.
I do not know what your findByFilter method is doing, but to best pin point the problem
is divide it in individual actions (methods) it is performing which you can profile using the
above.

WebLogic Server 10.0 Logging Configuration

Does anyone know if there is a way to update / modify / configure the logging for WebLogic Server logs to make the time stamp on log entries go out to milliseconds? Right now log entries only have precision to seconds, but we want and need to see them out to the millisecond.
We are well aware that log4j is an option, but that seems to require coding and we were hoping to avoid that given our only additional need was precision out to milliseconds.
Thanks.
Marc

You may want to ask in the WebLogic Server - Diagnostics / WLDF / SNMP forum. They own logging.
I asked them to reply here.

Wldf 9.2 diagnostic archive retirement

Hi to all,
Is there a way to retire diagnostic data from weblogic 9.2 wldf WLS_DIAGNOSTICS000000.DAT? I am planning to setup a diagnostic module on our server and wondering if this diagnostic data can be retired, I have seen this feature in weblogic 10, Retiring Data from the Archives and wondering if there is an equivalent for this in weblogic 9.2. Eventually this diagnostic will grow and we need to manage this growth.
regards.

Hello,
WLS 9.x did not provide a configuration based data retirement feature. However, it provided operations on runtime mbeans which could be used to delete selected records. You can periodically execute a WLST script to remove older data. For example:
import sys
# Usage:
# java weblogic.WLST delete_old_data.py url username password keep_days
# eg, following will delete data older than 2 days from the harvester and events
# archives:
# java weblogic.WLST delete_old_data.py t3://localhost:7001 weblogic weblogic 2
def getParam(pos, default):
value=None
try:
value=sys.argv[pos]
except:
value=default
return value
url = getParam(1, "t3://localhost:7001")
user = getParam(2, "weblogic")
password = getParam(3, "weblogic")
days = getParam(4, 1)
try:
connect(user,password,url)
now=System.currentTimeMillis()
bound=(now - days*3600*24*1000)
serverRuntime()
cd('/WLDFRuntime/WLDFRuntime/WLDFAccessRuntime/Accessor/WLDFDataAccessRuntimes/HarvestedDataArchive')
print "Deleting records older than", days, " days from Harvester data archive"
deleted=cmo.deleteDataRecords(0L, bound, "")
print "Deleted ", deleted, " record(s) from Harvester data archive"
cd('/WLDFRuntime/WLDFRuntime/WLDFAccessRuntime/Accessor/WLDFDataAccessRuntimes/EventsDataArchive')
print "Deleting records older than", days, " days from Events data archive"
deleted=cmo.deleteDataRecords(0L, bound, "")
print "Deleted ", deleted, " record(s) from Events data archive"
except:
print "exception found"
Hope this helps.
/Raj

Action DisplayArgumentsAction retrieve nothing

Hi, guys
I had a problem with weblogic wldf instrumentation.
I configured 2 instrumentation monitors for my app.
1st: a monitor 'servlet_around_service' with an action 'traceElapsedTimeAction'. It works fine. I can get events data through wls console and every record seems good.
2nd: a monitor 'servlet_before_service' with an action 'DisplayArgumentsAction'. While, I can get events data through wls console, but however the column 'arguments' of each record is empty. Question is how can I get out the http parameters(which a browser send to a http server through http get or http post)
any suggestions would be appreciated.
Edited by: Calvin on 2011-10-10 上午12:25

Problem solved.
Use custom monitor and '%' due to security issue.

HttpSessionDebug Not Working For Session Monitoring through Admin Console

Hi,
I want to Analyze the HttpSession Payload (Size) in the AdminConsole-->Diagnostics-->Log Files -->EventsDataArchive
I followed the Link http://jayesh-patel.blogspot.com/2008_04_01_archive.html
I am using "MyDiagnosticEar\META-INF\weblogic-diagnostics.xml" as following:
<?xml version="1.0" encoding="UTF-8"?>
<wldf-resource xmlns="http://www.bea.com/ns/weblogic/90/diagnostics">
<instrumentation>
<enabled>true</enabled>
<wldf-instrumentation-monitor>
<name>HttpSessionDebug</name>
<enabled>true</enabled>
</wldf-instrumentation-monitor>
</instrumentation>
</wldf-resource>
I am using a Simple JSP page to set Some Attribute inside the newly Created Session
MyDiagnosticEar\SimpleActionWebApp\index.jsp
<%@ page language="java" contentType="text/html;charset=UTF-8"%>
<%@ page session="false" %>
<html>
<body>
<%
HttpSession session=request.getSession(true);
out.println("<h4>Session ID: "+session.getId());
session.setAttribute("AAAAAAAAA","BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB");
java.util.Vector v=new java.util.Vector();
v.add(new java.util.Date());
v.add(new java.util.ArrayList());
v.add("AAAAABBCCCC");
session.setAttribute("EEEEEEEEEEEEEE",v);
%>
Data is Set As an Attribute inside the HttpSession:
session.setAttribute("AAAAAAAAA","BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB");
session.setAttribute("EEEEEEEEEEEEEE",v);
<%
System.out.println((String)request.getSession().getAttribute("AAAAAAAAA"));
System.out.println(session.getAttribute("EEEEEEEEEEEEEE"));
%>
</body>
</html>
Please let me know if there is any thing missing.....I have tested it in All WLS9.2, WLS10MP1 and WLS10.3 versions ..But no Success...
I am not able to see anything After hitting the JSP...in AdminConsole-->Diagnostics-->Log Files -->EventsDataArchive
But i can see that the Diagnostic Module has been Picked up successfully...
AdminConsole--->Deployments--->MyDiagnosticEar -->Configuration--->Instrumentation page
Thanks
Jay SenSharma

Hi Raj,
Thanks for looking into this issue.
I tried to Configure DiagnosticModule as well from Admin Console but could not make it work...Can u Please elaborate more on this...It will be really helpful.
Below is the Diagnostic Module...Created using Admin Console....Diagnostics -> Diagnostics Modules.
<?xml version='1.0' encoding='UTF-8'?>
<wldf-resource xmlns="http://www.bea.com/ns/weblogic/weblogic-diagnostics" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-diagnostics http://www.bea.com/ns/weblogic/weblogic-diagnostics/1.1/weblogic-diagnostics.xsd">
<name>Module-0</name>
<instrumentation>
<enabled>true</enabled>
<wldf-instrumentation-monitor>
<name>Connector_Around_Work</name>
<description></description>
</wldf-instrumentation-monitor>
</instrumentation>
<harvester>
<enabled>true</enabled>
<sample-period>3000</sample-period>
<harvested-type>
<name>weblogic.management.runtime.WebAppComponentRuntimeMBean</name>
<harvested-attribute>SessionMonitoringEnabled</harvested-attribute>
<harvested-instance>com.bea:ApplicationRuntime=TestDiagnosticsEAR,Name=AdminServer_/TestDiagnostics,ServerRuntime=AdminServer,Type=WebAppComponentRuntime</harvested-instance>
<namespace>ServerRuntime</namespace>
</harvested-type>
</harvester>
<watch-notification>
<watch>
<name>WatchA</name>
<enabled>true</enabled>
<rule-type>Harvester</rule-type>
<rule-expression>(${ServerRuntime//[weblogic.management.runtime.WebAppComponentRuntimeMBean]com.bea:ApplicationRuntime=TestDiagnosticsEAR,Name=AdminServer_/TestDiagnostics,ServerRuntime=AdminServer,Type=WebAppComponentRuntime//SessionMonitoringEnabled} = '')</rule-expression>
<alarm-type>AutomaticReset</alarm-type>
<alarm-reset-period>60000</alarm-reset-period>
</watch>
</watch-notification>
</wldf-resource>
TestDiagnostics
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 8, 2010 10:38 AM

Configuration of logging severity

Hello everyone,
I am trying to use the weblogic Admin console to modify the logging severity at runtime. I have an application deployed on the AdminServer.
In the web console, I go to the AdminServer Settings page and navigate to the Logging tab. I click the "Advanced" link to show the "Logger severity properties". In this box I have tried entering many different values. I save. There is no change to the logs. I restart the server, there is still no change to the logs.
Some values I've attempted to use:
com.mycompany.level=Trace
com.mycompany.level=Debug
com.mycompany=Trace
com.mycompany=Debug
.level=Trace
.level=Debug
I am using weblogic 10.3.2.0 with jdk logging.
Does anyone know if these configuration changes are supposed to affect the log files? Am I using this configuration parameter incorrectly?
Note that I have found a way to configure the logging severity using a logging.properties file, by calling:
LogManager.getLogManager().readConfiguration(EventDAOEJBImpl.class.getResourceAsStream("/logging.properties"));
However, this does not allow me to configure the application from the weblogic console. Is there a way to configure the logging severity using the weblogic console?

You may want to ask in the WebLogic Server - Diagnostics / WLDF / SNMP forum. They own logging.
I asked them to reply to this message.

[logging] Problems to configure logging rotation.

Hi,
I have an application .ear deployed in weblogic v10.3.1.0
This application use java.util.logging to write a log file.
      fh = new FileHandler(logFileName,0,1,true);
      fh.setFormatter(new XMLFormatter());
      logger.addHandler(fh);
FileHandler(String pattern, int limit, int count, boolean append)
pattern - the pattern for naming the output file
limit - the maximum number of bytes to write to any one file. If this is zero, then there is no limit. (Defaults to no limit).
count - the number of files to use
append - specifies append mode
http://www.javadocexamples.com/java/util/logging/java.util.logging.FileHandler.html
logFileName is dynamic with date formated like this yyyMMdd + ApplicationName + ".log"
This file is created but I have also yyyyMMddSEC.log.1, yyyyMMddSEC.log.2, yyyyMMddSEC.log.3,...
I DON'T WANT THESE FILES_, that's why I put limit to 0, count to 1 and append to true.
This code works without jdev/weblogic but has not effect in weblogic.
Q1. Why?
So I go to Weblogic console: Domain Structure-> DefaultDomain->Logging
Log file name: logs/DefaultDomain.log
Rotation type: None
NONE
Messages accumulate in a single file.
You must erase the contents of the file when the size is too large.
Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.
But it doesn't work, Weblogic continue to create log files like this *<filename>.log.<n>*
Q2. Why?
I have also created weblogic.xml in ViewControler/WEB-INF
thanks to this documentation:
http://download.oracle.com/docs/cd/E13222_01/wls/docs103/webapp/weblogic_xml.html#wp1063199
but it doesn't work...again.
Q3. Why?
Q4. If I want applications manage themselves their log, how to deactivate the logging handler in weblogic (LogFileMBean?)
Thanks for your help.

You may want to ask in the WebLogic Server - Diagnostics / WLDF / SNMP forum. They own logging.

Issue with WLDF Console extension displaying Instrumentation details

Hi,
I have enabled WLSDF Console extension on WLS9.1.
I am able to monitor weblogic metric data but when I enable instrumentation in my diagnostic module WLDF console displays server state as Unknown.
I am not able to monitor any metric data or request details after enabling instrumentation.
I have enabled DEBUG for diagnostic package and I can see diagnostic data getting collected in a server file store.But I am not able to see any details on WLDF dash board.
Has anyone experienced similar issue ?
Thanks & Regards,
Bhushan

Hi Bhushan,
Can you post your WLDF descriptor, and your config.xml? I'm not sure I can decipher what's going on based on the problem description.
Modifying or deploying a WLDF descriptor to a server should not affect the console extension behavior. Are there any error messages in the server log?
Are you actively graphing metrics in a DB configuration that are not displaying after this change?
Thanks,
Mike

WLDF in WebLogic 12.1.1 - Is it part of Standard Edition (without additional cost)?

I know Mission Control is not allowed in production for WebLogic Standard Edition without additional licensing costs. How about WLDF?
I haven't been able to find any documentation to state one way or the other and I don't want to assume since it took me quite a while to understand the JRMC licensing back in WL10 and WL11 versions.
Thanks,
Bill

http://www.oracle.com/us/products/middleware/application-server/oracle-weblogic-server-ds-1391360.pdf
"The WebLogic Management Framework includes the administration
server, its communication with managed servers, lifecycle
management via the Node Manager, and the WebLogic
Administration Console. The console provides the starting point for
essential operations, administration, automation and management. It
enables access to all the functions of Oracle WebLogic Server and
includes built-in intelligence to help prevent human configuration
errors. The WebLogic Scripting Tool enables command-line and
scriptable control over Oracle WebLogic Server. The WebLogic
Diagnostic Framework enables users to instrument applications for
monitoring and diagnostic purposes."
According to this (the way I read it) WLDF belongs to the WebLogic Management Framework, which is part of the standard edition (so from this you would assume no additional costs are needed when using WLDF).

We have a problem when we hitting instrumented axis services in weblogic 8.

First we create a domain its only support for axis services.we need to set classpath according to my project.The classpath is going to set in my creating domian name like as "AxisDomain" in that "startweblogic.cmd" file set classpath like
"%JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME% -Div.home=c:/work/build/Java/ -Dweblogic.ProductionModeEnabled=%PRODUCTION_MODE% -Djava.security.policy="%WL_HOME%\server\lib\weblogic.policy" weblogic.Server"
in this we add our classpath like " Div.home=c:/work/build/Java/ ".Then i start the server and deploy the sample axis service war file it contains " server-config.wsdd" file.In that file the following line shows.
<service name="CalCService" provider="java:RPC">
<parameter name="allowedMethods" value="*"/>
<parameter name="className" value="test.chap.calc"/>
</service>
In this sample war works fine.After that used my project and configure the services to getting log file purpose.Then used my project Configure/Instrument the Sample War file.we have config.xml file in our project use that file we configure the sample war file.Configuration is used for added our expected jar like "Handle.jar" file into the deployed services lib folder.Our hadlers are also added into the server-config.wsdd file like
<service name="CalCService" provider="java:RPC"><responseFlow><chain name="HANDLER_JAVA"><handler type="java:org.apache.axis.handlers.JAXRPCHandler"><parameter name="className" value="com.collectors.jt.WebServiceCollector"/><parameter name="endpointId" value="http://localhost:7001/calc1/services/CalCService"/></handler></chain></responseFlow><requestFlow><chain name="HANDLER_JAVA"><handler type="java:org.apache.axis.handlers.JAXRPCHandler"><parameter name="className" value="com.collectors.jt.WebServiceCollector"/><parameter name="endpointId" value="http://localhost:7001/calc1/services/CalCService"/></handler></chain></requestFlow>
<parameter name="allowedMethods" value="*"/>
<parameter name="className" value="test.chap.calc"/>
</service>
Configuration finished after that i want to restart my server that time only redeploy the configured services into the below location :
"C:\bea\user_projects\domains\javadomain\myserver\.wlnotdelete\extract".
Our nedded jar files also added into this location given below:
"C:\bea\user_projects\domains\javadomain\myserver\.wlnotdelete\extract\myserver_calc1_calc1\jarfiles\WEB-INF\lib"
Its not happening in weblogic 8.1.1 and weblogic 8.1.3.
But its not added the needed jar files into the above location in weblogic 8.1.1 and 8.1.3.when i deploy the same configured services that time only its works fine.I don't need to redeploy the service whenever i restart the server that time only i want to added jar files into that location.
This problem is only happening in weblogic 8.1.1 and 8.1.3 its not happening in weblogic 7.5 and 8.1.4 .
In the weblogic 7.5 and 8.1.4 when finished my configuration and restart the server that time its added the jar files into the below location
"C:\bea\user_projects\domains\javadomain\myserver\.wlnotdelete\extract\myserver_calc1_calc1\jarfiles\WEB-INF\lib"
after that i hitted the services using vordel box its working fine and getting log files.
can any one give me a solution to rectify this problem in Weblogic 8.1.1 and 8.1.3.?

forgot to say that I can only use 1 core and it´s not possible/locked to change in preferences/memory and multiprocessing

WLDF in weblogic 10,3,5

Hi ,
Please some one help how to configure wldf 10.3.5 . is there is any sample script?
Thanks,

Hi,
For Email notification for stuck threads on your Server, you need to first create a Diagnostic
Module. Within this you have to configure the Watches and Notifications.
In this example, we are setting up a watch on the server log to look for the MaxStuckThread warning being reported. We do this be setting the Rule Expression to be equal to the message ID for this warning, when examining the output of the server log.
Within the notification, we can set up any type of notification, but in this example we are setting up an SMTP (mail notification), so that when the rule expression matches the mail notification is sent.
Below is the content of the Diagnostic_module.xml file created after completing the above tasks:
<?xml version='1.0' encoding='UTF-8'?>
<wldf-resource xmlns="http://www.bea.com/ns/weblogic/weblogic-diagnostics"
xmlns:sec="http://www.bea.com/ns/weblogic/90/security"
xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-diagnostics
http://www.bea.com/ns/weblogic/weblogic-diagnostics/1.1/weblogic-diagnostics.xsd">
<name>Module-0</name>
<watch-notification>
<watch>
<name>Serverlog</name>
<enabled>true</enabled>
<rule-type>Log</rule-type>
<rule-expression>(SERVER = 'AdminServer') AND (MSGID =
'BEA-000337')</rule-expression>
<alarm-type>None</alarm-type>
<notification>mailNotification</notification>
</watch>
<smtp-notification>
<name>mailNotification</name>
<enabled>true</enabled>
<mail-session-jndi-name>myMailSession</mail-session-jndi-name>
<subject>stuck thread problem</subject>
<body>testing</body>
<recipient>[email protected]</recipient>
</smtp-notification>
</watch-notification>
</wldf-resource>
Further details on creating a diagnostic module can be found here -
http://download.oracle.com/docs/cd/E13222_01/wls/docs103/ConsoleHelp/taskhelp/diagnostics/UseDiagnosticModulesToMonitorServers.html
and further details on how to create watches and notifications can be found here
http://download.oracle.com/docs/cd/E13222_01/wls/docs103/ConsoleHelp/taskhelp/diagnostics/ConfigureWatchesAndNotifications.html
Regards,
Kal

Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/JoinPoint

Hi,
I have an application jar file which is run from a .sh file.
The application uses ridc api to checkin a document on UCM.
I have placed jars for supporting the application on the folder where we have kept the application jar
also we have mentioned the supporting jar file names in the Manifest.mf file of the application jar.
The necessary jar files which we have placed are:
com.lnt.ucm.integrationutility.ucm.Client
log4j-1.2.16.jar
oracle.ucm.ridc-11.1.1.jar
poi-2.5.1.jar
commons-codec-1.2.jar
commons-httpclient-3.1.jar
commons-logging-1.0.4.jar
mail.jar
jxl-2.6.10.jar
com.bea.core.antlr.runtime_2.7.7.jar
com.oracle.toplink_1.0.0.0_11-1-1-5-0.jar
jrf.jar
org.eclipse.persistence_1.1.0.0_2-1.jar
weblogic.jar
wlfullclient.jar
wseeclient.jar
jaxws-rt-2.1.4.jar
we are getting below exception when we run the jar from the .sh file.
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/JoinPoint
at weblogic.wsee.jaxws.spi.WLSProvider.<clinit>(WLSProvider.java:90)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:31)
at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:90)
at javax.xml.ws.spi.Provider.provider(Provider.java:83)
at javax.xml.ws.Service.<init>(Service.java:56)
at com.abc.ucm.proxy.JDEUCMManagerService.<init>(JDEUCMManagerService.java:66)
at com.abc.ucm.integrationutility.ucm.Client.executeUtilty(Client.java:50)
at com.abc.ucm.integrationutility.ucm.Client.main(Client.java:540)
I'm not able to find any jar for weblogic/diagnostics/instrumentation/JoinPoint can you please tell me which jar needs to be added.
Regards,
Tejaswini L

914897 wrote:
I encounter the similar error. Anyone knows how to fix it?By providing a configuration file which validates with the corresponding XSDs found in coherence.jar. Sorry, but can't point you to the specific issue without seeing the erroneous configuration file.
Best regards,
Robert

Weblogic 9.0 WLDF Instrumentation

Similar Messages

Maybe you are looking for