Monday, November 30, 2009

SiteScope and configuring a MDB for monitoring

Are you lost? That's normal.... SiteScope is designed with that purpose in mind.

When adding a counter, search for:


(or whatever other attribute)

practical example:


Easy, isn't it?

Anatomy of a MDB

EJBRuntimeMBean is the base Interface for all EJB-related MBeans.

subinterfaces are:

- MessageDrivenEJBRuntimeMBean, EntityEJBRuntimeMBean and StatelessEJBRuntimeMBean, which all contain a EJBPoolRuntimeMBean:

with attributes:

AccessTotalCount, BeansInUseCurrentCount, DestroyedTotalCount, MissTotalCount, PooledBeansCurrentCount, TimeoutTotalCount, WaiterCurrentCount

- StatefulEJBRuntimeMBean contains instead a EJBCacheRuntimeMBean (Stateful are cached, not pooled, since they contain stateful info which should not be discarded or shared) and EJBLockingRuntimeMBean

All types of Bean contain a EJBTransactionRuntimeMBean.

How do I retrieve a MDB RuntimeMBean?

From a DomainRuntimeMBean, retrieve a ServerRuntimeMBean, then its ApplicationRuntimeMBean[], then its ComponentRuntimeMBean[], and test if its type is EJBComponentRuntime, in this case you can cast it to EJBComponentRuntimeMBean

Painful, no? Here is the code:

public List getEBJs(String serverName) {
List result = new ArrayList();
ServerRuntimeMBean serverRuntimeMBean = getServerRuntimeMBean(serverName);
if (serverRuntimeMBean != null) {
ApplicationRuntimeMBean[] apps = serverRuntimeMBean.getApplicationRuntimes();
for (ApplicationRuntimeMBean app : apps) {
ComponentRuntimeMBean[] components = app.getComponentRuntimes();
for (ComponentRuntimeMBean bean : components) {
if (bean.getType().equals("EJBComponentRuntime")) {
return result;

What to monitor in an Application Server

EJBCache (ActivationCount CacheAccessCount CachedBeansCurrentCount CacheHitCount PassivationCount)

EJBLocking (LockEntriesCurrentCount LockManagerAccessCount TimeoutTotalCount WaiterCurrentCount WaiterTotalCount)

EJBPool (BeansInUseCount IdleBeansCount TimeoutTotalCount WaiterTotalCount)

EJBTransactions (TransactionsCommittedTotalCount TransactionsRolledBackTotalCount TransactionsTimedOutTotalCount)

JDBC (ActiveConnectionsCurrentCount ActiveConnectionsHighCount ConnectionsTotalCount LeakedConnectionCount MaxCapacity WaitingForConnectionCurrentCount WaitingForConnectionHighCount WaitSecondsHighCount)

JMS (MessagesCurrentCount MessagesHighCount MessagesPendingCount MessagesReceivedCount BytesCurrentCount BytesHighCount BytesPendingCount BytesReceivedCount)

JRockit (JvmProcessorLoad AllProcessorsAverageLoad TotalGarbageCollectionTime)

ThreadPool (busyThrdCurrCnt idleThrdCurrCnt totalThrdCurrCnt standbyThrdCurrCnt stuckThrdCurrCnt queueLength)

Friday, November 27, 2009

kill -3 and JRockit

in your domain home, create a file ctrlhandler.act

set_filename filename=/tmp/output.txt
jrarecording nativesamples=false latency filename=myjrarecording time=120

every time you do a kill -3 pid, the JRockit VM will execute the control handler.

Thursday, November 26, 2009

Which JMS Connection Factory shall I use?

unless a Connection Factory has been explicitely specified for a Queue, WebLogic will use a default connection factory named:


this will be in the JNDI_TREE for you to use:

Here is the (crazy and cumbersome) code:

Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
InitialContext ctx = new InitialContext(env);

QueueConnectionFactory   qConFactory = (QueueConnectionFactory)ctx.lookup("weblogic.jms.ConnectionFactory");
QueueConnection     qCon        = qConFactory.createQueueConnection();
QueueSession     qSession    = qCon.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
Queue       queue2       = (Queue)ctx.lookup(jms_queue);
QueueSender        qSender     = qSession.createSender(queue2);
TextMessage      msg         = qSession.createTextMessage();



a property named JMS_BEA_DeliveryFailureReason is being used in error messages in a WLI application; its value is an integer, and it means that the delivery limit was reached. The number 2 has nothing to do with the delivery count. See weblogic.jms.backend.BEDestinationImpl.

JRMC JRockit mission control, unable to connect console

still investigating on this problem, most likely I have not set -Xmanagement when running the WebLogic server... Thanks to the developers for the immense clarity of the error message.

Oh yes of course, you should change your startWebLogic.cmd adding
set JAVA_OPTIONS=%JAVA_OPTIONS% -Xmanagement:ssl=false,authenticate=false,port=7099

once you restart weblogic, you should see this:
[INFO ][mgmnt  ] Remote JMX connector started at address esp50ws112345:7099
[INFO ][mgmnt  ] Local JMX connector started

Of course make sure you specify 7099 (and NOT 7001) in the JRMC client new connection parameters.

This was the original error message:

Could not open Management Console for frparmat01.acme.dns:8765. Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:] Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:]
    Caused by: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:]
        ... 3 more
    Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:]
        at com.sun.jndi.rmi.registry.RegistryContext.lookup(
        at com.sun.jndi.toolkit.url.GenericURLContext.lookup(
        at javax.naming.InitialContext.lookup(
        ... 10 more
    Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
        at sun.rmi.transport.tcp.TCPChannel.createConnection(
        at sun.rmi.transport.tcp.TCPChannel.newConnection(
        at sun.rmi.server.UnicastRef.newCall(
        at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
        at com.sun.jndi.rmi.registry.RegistryContext.lookup(
        ... 15 more
    Caused by:
        at sun.rmi.transport.tcp.TCPChannel.createConnection(
        ... 19 more

Wednesday, November 25, 2009

JMS: difference between PENDING and CURRENT


The number of pending messages in the destination.
Pending messages are over and above the current number of messages. A pending message is one that has either been sent in a transaction and not committed, or that has been received and not committed or acknowledged.


The current number of messages in the destination. This does not include the pending messages.

When you do "show messages",

The beauty of verbose:class

java -verbose:class is simply wonderful, when you are trying to troubleshoot classloader problems.

Here is a sample output:

[INFO ][class  ] created: #2859 org/apache/poi/poifs/filesystem/POIFSDocument (file:/acme/users/abraham/abrahammonitoring/lib/poi-3.5-FINAL-20090928.jar)
[INFO ][class  ] 4391 org/apache/poi/poifs/filesystem/POIFSDocument success (0.36 ms)
[INFO ][class  ] 4394 org/apache/poi/poifs/storage/DocumentBlock fail (0.00 ms)
[INFO ][class  ] 4396 org/apache/poi/poifs/storage/BigBlock fail (0.00 ms)
[INFO ][class  ] created: #2861 org/apache/poi/poifs/storage/BigBlock (file:/acme/users/abraham/abrahammonitoring/lib/poi-3.5-FINAL-20090928.jar)
[INFO ][class  ] 4395 org/apache/poi/poifs/storage/BigBlock success (0.12 ms)
[INFO ][class  ] created: #2860 org/apache/poi/poifs/storage/DocumentBlock (file:/acme/users/abraham/abrahammonitoring/lib/poi-3.5-FINAL-20090928.jar)
[INFO ][class  ] 4393 org/apache/poi/poifs/storage/DocumentBlock success (0.30 ms)
[INFO ][class  ] 4398 org/apache/poi/poifs/filesystem/POIFSDocument$BigBlockStore fail (0.00 ms)
[INFO ][class  ] created: #2862 org/apache/poi/poifs/filesystem/POIFSDocument$BigBlockStore (file:/acme/users/abraham/abrahammonitoring/lib/poi-3.5-FINAL-20090928.jar)

Tuesday, November 24, 2009

Grepper Monkey or Singe Greppeur

"Grepper Monkey" is a guy who spends his time grepping log files in search for errors, and reporting them to developers....
this is what I am doing right now... I am writing a tool to do this intelligently though....

WebLogic portal generating lot of info into the diagnostic framework store file WLS_DIAGNOSTICS000000.DAT


try using:


in your startup command, especially of the admin

it seems to be a "best practice"

Monday, November 23, 2009

Connection Pools reaching their max capacity and over

to make sure you are not leaking connections (forgetting to close them),
in your DataSource configuration go to "configuration"/diagnostics and check the "Profile Connection Leak"
This will generate a "profile-type" element in the jdbc-config.xml and set it to 4.
then in your Connection Pool configuration, click on advanced, and enter some large value for "Inactive Connection Timeout" (should be greater than the JTA timeout IMHO)

For more details, see Oracle Support Doc "How to enable WLS Database Profiling to diagnose database connection problems in Webcenter Content (Doc ID 2071557.1) "

Thursday, November 19, 2009

WLI: how to clean up a WLI environment

- TERMINATE all processes (using for instance the WLI Console)
- purge all tasks
- stop all processes and task applications
- uninstall all processes and task applications
- stop application servers
- delete all this:

¤ / pathToYourDomain / yourDomain /wliconfig /ProcessTypeProperties.xml

¤ / pathToYourDomain / yourDomain /wliconfig /AppliServers /ProcessTypeProperties.xml

¤ / pathToYourDomain / yourDomain /servers/ adminServer /cache/*

¤ / pathToYourDomain / yourDomain /servers/ adminServer /tmp/*

¤ / pathToYourDomain / yourDomain /servers/ appliServer /cache/*

¤ / pathToYourDomain / yourDomain /servers/ appliServer /tmp/*

¤ / pathToYourDomain / yourDomain /servers/ appliServer /stage

- you must disable constraints
- truncate all tables starting by JPD_* WLI_*, BUT WLI_CALENDAR and WLI_CALENDAR_SEQUENCE

restart servers
ProcessTypeProperties.xml will be recreated

verify with WLI Console that no process nor process instance exist

redeploy processes and tasks applications

recreate all resources

Wednesday, November 18, 2009

WLST useful tips and tricks

Run a .py script with:

java weblogic.WLST

How to define a function with exception handling:

def connect_to_weblogic(username,password,adminurl):
try :
except :
print 'Cannot connect to server '

How to get the list of defined servers:

serverList = ls('Servers',returnMap='true')

(the "returnMap" options makes the serverList variable a HashMap with key=serverName)

How to get a list of RUNNING servers:

runningList = ls('ServerRuntimes',returnMap='true')

Tuesday, November 17, 2009

Windows XP crashing with message "missing or corrupt system32/hal.dll"

Welcome to the wonderful world of Bill Mafia and his treacherous connections with the DOD USA which allowed him to impose this horrible piece of crap as a world standard.

You can boot the PC with UBUNTU 9.10, retrieve the hal.dll file from the c:/windows directory and copy it to c:/windows/system32 directory! It works! Don't ask me why there are 2 copies of the same file!

Friday, November 13, 2009

JRockit crash resolved

if your dump file contains something like:

Thread Stack Trace:
at known_ld_opt+685()@0x2b36a098d091
at strength_reduction_generic+158()@0x2b36a098d287
at optStrengthReduction+152()@0x2b36a098d36b
at optmanOptimizeMIR+330()@0x2b36a0935cd7
at generateMethodWithStage+102()@0x2b36a08212b7
at cmgrGenerateMethodFromPhase+216()@0x2b36a0822126
at cmgrGenerateNormalMethod+91()@0x2b36a082122d
at cmgrGenerateCode+209()@0x2b36a08210c1
at generate_code2+205()@0x2b36a09048a3
at codegenThread+1006()@0x2b36a0904f45
at tsiCallStartFunction+67()@0x2b36a08dd5cb
at tsiThreadStub+308()@0x2b36a08de7d5
at ptiThreadStub+14()@0x2b36a09468a6
at start_thread+199()@0x3def806367

a workaround could be that you add the method reported by the
Method :
line to an exclusion file myOptfile, which tells JRockit which methods it should NOT optimize.

then start your application with the flags
-Xverbose:opt -Djrockit.optfile=myOptfile

WebLogic Performance checklist

Pinned-To-Thread on JDBC Connection Pool : to enable

"Set XA Transaction Timeout" and "XA Transaction Timeout" sets the timeout on this resource. It is advisable to define it explicitly and must be greater than the overall timeout of the transaction (and therefore higher than the overall timeout of JTA or of timeout of the EJB that initiated the transaction).

JMS bridges and Distributed Destinations

Can the messaging bridge use distributed destinations as source and target destinations?

Yes, the messaging bridge can send to and receive from distributed destinations. Bea recommends the following configurations:

* If the source is distributed destination, the bridge is pinned to one of the members when it connects to the destination. It stays connected only to that member until it reconnects. This means that the bridge will not receive messages from the other members of the distributed destination. Therefore, the best practice is to configure one bridge for each member of a distributed destinations using the member's JNDIName.

* If the target is a distributed destination, the best practice is to send to the distributed destination using the distributed destination’s JNDIName and disable server affinity. This allows the distributed destination to load balance incoming messages.

Thursday, November 12, 2009

Querying and terminating WLI instances


package com.acme.wli;

import java.util.Iterator;
import java.util.Set;

import javax.naming.Context;
import javax.naming.NamingException;

import com.bea.wli.bpm.runtime.ProcessStatus;

import weblogic.jndi.Environment;
* Ajouter D:\beawliwlp103\wli_10.3\lib\jpdpublic.jar:
* @author vernetto
public class WLITerminator {
//private static final String SERVICE_URI = "/ProtectionProcesses/com/acme/corp/protectionProcesses/iris/ReceiveCIUN_v5.jpd";
//private static final String SERVICE_URI = "/ProtectionProcesses/com/acme/corp/protectionProcesses/iris/CotationDataReady_v4.jpd";
private static final String SERVICE_URI = "/ProtectionProcesses/com/acme/corp/protectionProcesses/iris/HandleCIUN_v1.jpd";

public static void main(String[] args) throws NamingException {
Environment env = new Environment();
Context ctx = env.getInitialContext();
MBeanHome home = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
System.out.println("Got the Server-specific MBeanHome: " + home);
Set s = home.getMBeansByType("ProcessRuntime");
Iterator it = s.iterator();
try {
            if (it.hasNext()) {
                ProcessRuntimeMBean bean = (ProcessRuntimeMBean);
                ProcessInstanceQuery query = new ProcessInstanceQuery();
                ProcessInstanceQueryResult info = bean.getProcessInstances(query);
                int count = info.getResultCard();
                String[] instances = info.getInstanceIds();
                System.out.println("found " + instances.length + " instances");
                for (int i = 0 ; i <  instances.length; i++) {
                    String instanceId = instances[i];
                    ProcessInstanceInfo pi = bean.getProcessInstanceInfo(instanceId, false);
                    System.out.println(pi.getServiceURI() + " " + instanceId);
                    //bean.terminate(pi.getServiceURI(), instanceId);
} catch (Exception ex) {

WLI: configuring JMS queues for performance

The JMS queues AsyncDispatcher and AsyncDispatcher_error are needed for each project containing process.
All WLI process are based on these 2 queues, and it is therefore necessary to configure them properly.

For the queue AsyncDispatcher:
- Retry => 0 or a low value with a redelivery delay set. The retry may be useful in case of unavailability of external system.
- Error destination => AsyncDispatcher_error.

For the queue AsyncDispatcher_error:
- Retry => maximum value in order not to lose messages.
- Redelivery delay positioned so as not to saturate the server.


<Warning> <Connector> <<WLS Kernel>> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException thr
own by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">

it's evidently a JMS Bridge problem.

This teaches me the following:

The bridge uses a JCA Connector packaged in this jar:


and its JNDI name is eis.jms.WLSConnectionFactoryJNDIXA

see more info here:

.... more to come...

Wednesday, November 11, 2009

WebLogic: unable to log into console

if you can't login into your console and you get a message:

"It's likely that this condition is the result of a configuration problem"

and a "response has already been committed" in the logs,

search in your $DOMAIN_HOME/pending directory and remove what might be there. Also, clean your config.xml from any garbage, and copy it to any other nodes.

If this still fails, empty all "stage" and "tmp" directories.

Friday, November 6, 2009

Avoiding overload

in a nutshell:

* limit the number of execute threads with JVM properties:

* create a Network Channel and assign to it a "Maximum Connected Clients"

* in configuration / overload, set "Shared Capacity For Work Managers"

* for WebApps, set the max-in-memory-sessions in the deployment descriptor

* create a global Work Manager called default, and assign constraints to it


In post 8.1 WebLogic, the threads belong to a unique queue weblogic.kernel.Default.

Hogging Threads, Idle Threads...

See here for more info.

A thread in the pool can be: Standby, Active, Stuck or Idle

The Monitoring Threads console shows us:

Hogging Thread Count: not well defined. Seemingly, a hogging thread is a thread which has been busy for a "long" (how long?) time... the difference between a hogging thread and a stuck thread is not clear.

Standby Thread Count: the threads who are sitting idle in the standby pool

Queue Length:

Execute Thread Idle Count:

Execute Thread Total Count:

Active Execute Threads: the threads actually working now

Standby Thread Count + Active Execute Threads = Execute Thread Total Count

Thursday, November 5, 2009

JRockit, how to enable a .core file (core dump)

first, check with "ulimit -a" that you have no limits on core file size:

ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 137215
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 65535
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 137215
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

if your file is limited, then issue a
"ulimit -c unlimited"

check that no "-XXdumpSize" is specified in your java command options
(default is "large")

Also, run df -h to make sure you have enough space on disk

JRockit crash and dump

When JRockit crashes, it produces a .dump file

for more info see:

here is a sample .dump file:

===== BEGIN DUMP =============================================================
JRockit dump produced after 0 days, 23:20:28 on Wed Nov 4 17:13:48 2009

* If you see this dump, please go to *
* *
* for troubleshooting information. *

Additional information is available in:
No snapshot file (core dump) will be created because core dumps have been
disabled. To enable core dumping, try "ulimit -c unlimited"
before starting JRockit again.

Error Message: Illegal memory access. [54]
Signal info : si_signo=11, si_code=1 si_addr=(nil)
Version : BEA JRockit(R) R27.6.3-40_o-112056-1.5.0_17-20090318-2103-linux-x86_64
CPU : Intel Core 2 SSE SSE2 SSE3 SSSE3 SSE4.1 Core Intel64
Number CPUs : 8
Tot Phys Mem : 16833388544 (16053 MB)
OS version : Red Hat Enterprise Linux Server release 5.3 (Tikanga)
Linux version 2.6.18-128.el5 ( (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Dec 17 11:41:38 EST 2008 (x86_64)
Thread System: NPTL
Java locking : Normal
State : JVM is running
Command Line : -Xms4096m -Xmx4096m -Xverify:none -XgcPrio:throughput -Xverbose:gc,gcreport -XverboseTimeStamp -XverboseLog:/serveur/wlsapp/logs/irisappli1/gc.log -da -Dplatform.home=/opt/tuxedo/platform922/weblogic92 -Dwls.home=/opt/tuxedo/platform922/weblogic92/server -Dwli.home=/opt/tuxedo/platform922/weblogic92/integration -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.http.descriptor.merge=true -Dlog4j.configuration=log4j.xml -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.Stdout=/serveur/wlsapp/logs/irisappli1/stdout.log -Dweblogic.Stderr=/serveur/wlsapp/logs/irisappli1/stderr.log -Dweblogic.ext.dirs=/opt/tuxedo/platform922/patch_weblogic922/profiles/default/sysext_manifest_classpath -Duser.language=fr -Dacme.config.path=/serveur/wlsapp/IRISDomain/acmeConfig -Dacme.framework.server=true -Dlog4j.debug=true -Dacme.persistence.loginAtStartup=false -Dacme.server.standAlone=false -Dweblogic.Name=irisappli1 weblogic.Server
java.home : /opt/jrmc-3.1.0-1.5.0/jre
j.class.path : :/opt/tuxedo/platform922/patch_weblogic922/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/jrockit/lib/tools.jar:/opt/tuxedo/platform922/weblogic92/server/lib/weblogic_sp.jar:/opt/tuxedo/platform922/weblogic92/server/lib/weblogic.jar:/opt/tuxedo/platform922/weblogic92/server/lib/webservices.jar::/opt/tuxedo/platform922/weblogic92/server/lib/jpd.jar:/opt/tuxedo/platform922/weblogic92/integration/L10N:/opt/tuxedo/platform922/weblogic92/integration/lib/worklist-system-required.jar:/opt/tuxedo/platform922/weblogic92/common/eval/pointbase/lib/pbclient51.jar:/opt/tuxedo/platform922/weblogic92/server/lib/xqrl.jar:/serveur/wlsapp/IRISDomain/acmeConfig::/serveur/wlsapp/IRISDomain/acmeLib/framework.jar:/serveur/wlsapp/IRISDomain/acmeLib/commons-beanutils-1.7.0.jar:/serveur/wlsapp/IRISDomain/acmeLib/toplink.jar:/serveur/wlsapp/IRISDomain/acmeLib/baseInfo.jar:/serveur/wlsapp/IRISDomain/acmeLib/commons-lang-2.1.jar:/serveur/wlsapp/IRISDomain/acmeLib/jmxtools-1.1.jar:/serveur/wlsapp/IRISDomain/acmeLib/wtc-internalCollaborate.jar:/serveur/wlsapp/IRISDomain/acmeLib/commons-logging-1.0.2.jar:/serveur/wlsapp/IRISDomain/acmeLib/commons-pool-1.3.jar:/serveur/wlsapp/IRISDomain/acmeLib/log4j-1.2.14.jar:/serveur/wlsapp/IRISDomain/acmeLib/xmlparserv2.jar:/serveur/wlsapp/IRISDomain/acmeLib/baseInfoXmlBeans.jar:/serveur/wlsapp/IRISDomain/acmeLib/jmxri-1.1.jar:/serveur/wlsapp/IRISDomain/acmeLib/ehcache-1.2.2.jar:/serveur/wlsapp/IRISDomain/acmeLib/baseXmlBeans.jar:/serveur/wlsapp/IRISDomain/acmeLib/externalCollaborateField32.jar:/serveur/wlsapp/IRISDomain/acmeLib/wrapperMgt.jar:/serveur/wlsapp/IRISDomain/acmeLib/commons-digester-1.7.jar:/serveur/wlsapp/IRISDomain/acmeLib/xercesImpl.jar:/serveur/wlsapp/IRISDomain/acmeLib/dbunit-2.2.jar:/serveur/wlsapp/IRISDomain/acmeLib/commons-collections-3.2.jar:/serveur/wlsapp/IRISDomain/acmeLib/xml.jar:/serveur/wlsapp/IRISDomain/acmeLib/base.jar:/serveur/wlsapp/IRISDomain/acmeLib/ojdbc14.jar:/serveur/wlsapp/IRISDomain/acmeLib/castor-1.0.5-xml.jar:/opt/tuxedo/platform922/weblogic92/server/lib/xquery.jar:/opt/tuxedo/platform922/weblogic92/server/lib/binxml.jar:/serveur/wlsapp/IRISDomain/configTemp/:
j.lib.path : /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/jrockit:/opt/jrmc-3.1.0-1.5.0/jre/lib/amd64:/opt/jrmc-3.1.0-1.5.0/jre/../lib/amd64:/opt/tuxedo/platform922/patch_weblogic922/profiles/default/native:/opt/tuxedo/platform922/patch_weblogic922/profiles/default/native:/opt/tuxedo/platform922/weblogic92/server/native/linux/x86_64:/opt/tuxedo/platform922/weblogic92/server/native/linux/x86_64/oci920_8:/opt/tuxedo/platform922/weblogic92/server/native/linux/x86_64:/opt/tuxedo/platform922/weblogic92/server/native/linux/x86_64/oci920_8
JAVA_HOME : /opt/jrockit
_JAVA_OPTIONS: <not set>
LD_LIBRARY_PATH: /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/jrockit:/opt/jrmc-3.1.0-1.5.0/jre/lib/amd64:/opt/jrmc-3.1.0-1.5.0/jre/../lib/amd64:/opt/tuxedo/platform922/patch_weblogic922/profiles/default/native:/opt/tuxedo/platform922/patch_weblogic922/profiles/default/native:/opt/tuxedo/platform922/weblogic92/server/native/linux/x86_64:/opt/tuxedo/platform922/weblogic92/server/native/linux/x86_64/oci920_8:/opt/tuxedo/platform922/weblogic92/server/native/linux/x86_64:/opt/tuxedo/platform922/weblogic92/server/native/linux/x86_64/oci920_8
Method : com/acme/corp/request/RequestCtrlImpl.modifyRequest(Lcom/acme/x2002/bdt/RqtUpdtBDTDocument;)Lcom/acme/x2002/bdt/RqtBDTDocument;
StackOverFlow: 0 StackOverFlowErrors have occured
OutOfMemory : 0 OutOfMemoryErrors have occured
C Heap : Good; no memory allocations have failed
GC Strategy : Mode: throughput. Currently using strategy: genparpar
GC Status : OC is not running. Last finished OC was OC#393.
: YC is not running. Last finished YC was YC#84.
OC History : Strategy genparpar was used for OC#125.
: Strategy singleparpar was used for OC#126 to OC#127.
: Strategy genparpar was used for OC#128.
: Strategy singleparpar was used for OC#129.
: Strategy genparpar was used for OC#130 to OC#393.
YC History : Ran 3 YCs before OC#389.
: Ran 1 YCs before OC#390.
: Ran 2 YCs before OC#391.
: Ran 2 YCs before OC#392.
: Ran 3 YCs before OC#393.
: Ran 2 YCs since last OC.
YC Promotion : Last YC successfully promoted all objects
Heap : 0x2ad688312000 - 0x2ad788312000 (Size: 4096 MB)
Compaction : 0x2ad6c8312000 - 0x2ad6d8312000 (Current compaction type: external)
NurseryList : 0x2ad6c7eafa98 - 0x2ad752410450
KeepArea : 0x2ad70f0e22d0 - 0x2ad752410450
NurseryMarker: [ 0x2ad6f7450178, 0x2ad70f0e22d0 ]
CompRefs : References are uncompressed 64-bit.

Registers (from ThreadContext: 0x41aaa3b0 / OS context: 0x41aaa470):
rax = 00002ad68806f091 rcx = 0000000000000000
rdx = 00002ad6880d1fac rbx = 0000000000000000
rsp = 0000000041aaa8b0 rbp = 0000000041aaa8f0
rsi = 000000002000002f rdi = 0000000000000000
r8 = 0000000000000000 r9 = 0000000041aaa8c4
r10 = 0000000000000000 r11 = 00002aaaaeb0dbc8
r12 = 0000000041aaabb0 r13 = 00002aaaafcb8f70
r14 = 0000000000000001 r15 = 00002aaac50cb408
cs = 0000000000000033 fs = 0000000400000000
gs = 0004000000000000
rip = 00002ad68806f091 flags = 0000000000000213

Loaded modules:
(* denotes the module causing the exception)
0000000000400000-00000000004119eb /opt/jrmc-3.1.0-1.5.0/bin/java
0000003def800000-0000003def815507 /lib64/
0000003a6aa00000-0000003a6aa8122f /lib64/
0000003def000000-0000003def001f93 /lib64/
0000003deec00000-0000003deed4b937 /lib64/
0000003dee800000-0000003dee81b99f /lib64/
00002ad687eae000-00002ad6880de56f */opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/jrockit/
0000003df0800000-0000003df0806e8b /lib64/
00002ad79131d000-00002ad79132664b /lib64/
00002ad791587000-00002ad791593467 /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/
00002ad791696000-00002ad7916b921b /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/
0000003df2800000-0000003df28140c7 /lib64/
00002ad7d1850000-00002ad7d185663f /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/native_threads/
00002aaaae0b6000-00002aaaae0c3fa3 /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/
00002aaaae1fa000-00002aaaae20b5cf /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/
00002aaaae30e000-00002aaaae3145db /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/
00002aaaae41f000-00002aaaae422d73 /lib64/
0000003df3c00000-0000003df3c10823 /lib64/
00002aaaae624000-00002aaaae62918b /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/
00002aaaae72b000-00002aaaae73363f /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/
00002aaaae845000-00002aaaae8472af /opt/tuxedo/platform922/weblogic92/server/native/linux/x86_64/
00002aaaae9ff000-00002aaaae9ff96b /opt/jrmc-3.1.0-1.5.0/jre/lib/amd64/

(* marks the word pointed to by the stack pointer)
0000000041aaa8b0: 0000000041aaa920* 000000008805e841 0000000310000408 00002aaaafcb8f70
0000000041aaa8d0: 0000000041aaabb0 0000000000000018 0000000041aaa934 0000000041aaabb0
0000000041aaa8f0: 0000000041aaa920 00002ad68806f287 00000000000005dc 00002aaac50cb408
0000000041aaa910: 00000000000006d8 0000000000000000 0000000041aaa960 00002ad68806f36b
0000000041aaa930: 0000000000000000 0000000000000000 0000000000000001 0000000041aaabb0
0000000041aaa950: 0000000000000000 00002aaac50cb408 0000000041aaa9b0 00002ad688017cd7

(* marks the word pointed to by the instruction pointer)
00002ad68806f030: 49c08949fff1298f 6674c0854870458b 00000001b8063883 894858ebf0440f44
00002ad68806f050: f8e28102eac148f2 484057034903ffff e0c1481fe083f089 08488b4802034804
00002ad68806f070: 7708fe8341d1014c 29158d48f0894432 488204634800062f eb01634ce0ffd001
00002ad68806f090: 0f4c10eb018b4c15* 01b70f4c0aeb01bf 01bf01be0f4c04eb 415f74ff85000000
00002ad68806f0b0: 8944c2894c485d8b 000000b8ff894cf6 0f41ffee8f59e800 0f06e9c166044db7
00002ad68806f0d0: 048908245c89c9b6 4100000001b94124 0000ba00000001b8 4c0000001dbe0000

"(Code Optimization Thread 1)" id=5 idx=0x34 tid=27456 lastJavaFrame=0xfffffffffffffffc

Stack 0: start=0x41a8a000, end=0x41aac000, guards=0x41a8f000 (ok), forbidden=0x41a8d000
Thread Stack Trace:
at known_ld_opt+685()@0x2ad68806f091
at strength_reduction_generic+158()@0x2ad68806f287
at optStrengthReduction+152()@0x2ad68806f36b
at optmanOptimizeMIR+330()@0x2ad688017cd7
at generateMethodWithStage+102()@0x2ad687f032b7
at cmgrGenerateMethodFromPhase+216()@0x2ad687f04126
at cmgrGenerateNormalMethod+91()@0x2ad687f0322d
at cmgrGenerateCode+209()@0x2ad687f030c1
at generate_code2+205()@0x2ad687fe68a3
at codegenThread+1006()@0x2ad687fe6f45
at tsiCallStartFunction+67()@0x2ad687fbf5cb
at tsiThreadStub+308()@0x2ad687fc07d5
at ptiThreadStub+14()@0x2ad6880288a6
at start_thread+199()@0x3def806367
-- Java stack --

Extended, platform specific info:
libc release: 2.5-stable
Elf headers:
libc ehdrs: EI: 7f454c46020101000000000000000000 ET: 3 EM: 62 V: 1 ENTRY: 0000003deec1da70 PHOFF: 0000000000000040 SHOFF: 00000000001a1080 EF: 0x0 HS: 64 PS: 56 PHN; 10 SS: 64 SHN: 77 STIDX: 76
libpthread ehdrs: EI: 7f454c46020101000000000000000000 ET: 3 EM: 62 V: 1 ENTRY: 0000003def805780 PHOFF: 0000000000000040 SHOFF: 0000000000022ef8 EF: 0x0 HS: 64 PS: 56 PHN; 9 SS: 64 SHN: 39 STIDX: 38
libjvm ehdrs: EI: 7f454c46020101000000000000000000 ET: 3 EM: 62 V: 1 ENTRY: 000000000002de90 PHOFF: 0000000000000040 SHOFF: 000000000252ee50 EF: 0x0 HS: 64 PS: 56 PHN; 3 SS: 64 SHN: 30 STIDX: 27

* If you see this dump, please go to *
* *
* for troubleshooting information. *

===== END DUMP ===============================================================

Monday, November 2, 2009

Sitescope and Weblogic using JMX

a good introduction on the topic:

especially useful is the test using JConsole:

jconsole.exe -J-Dcom.sun.CORBA.transport.ORBTCPReadTimeouts=10:60000:500:10

and connecting to

Anyway Sitescrotum UI is a POC (piece of crap), for instance if you enter the good JMX URL with the wrong weblogic username you still get "invalid URL" error...
frankly pathetic.

I could make Sitescrotum work only by adding

of course Sitescrotum doesn't give you any warning or error message...
also I didn't provide the optional domain name... also try hitting the "clear selection" and "reload configuration" many times...

Sitescrotum UI sucks!