org.xmlBlaster.test.memoryleak
Class Volatile

java.lang.Object
  org.xmlBlaster.test.memoryleak.Volatile

public class Volatile
extends java.lang.Object

You can use this client to test with tools like OptimizeIt if we have memory leaks with volatile messages.

See Also:

CORBA xmlBlaster.idl

Field Summary

private int	bulkSize
private I_XmlBlasterAccess	con
private boolean	connected
private ConnectReturnQos	conRetQos
private static java.util.logging.Logger	log
private java.lang.String	ME

Constructor Summary

Volatile(Global glob)

Method Summary

static void

main(java.lang.String[] args) Try

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

ME

private final java.lang.String ME

See Also:

Constant Field Values

log

private static java.util.logging.Logger log

con

private I_XmlBlasterAccess con

conRetQos

private ConnectReturnQos conRetQos

connected

private boolean connected

bulkSize

private int bulkSize

Constructor Detail

Volatile

public Volatile(Global glob)

Method Detail

main

public static void main(java.lang.String[] args)

Try

   java org.xmlBlaster.test.memoryleak.Volatile -help
 

for usage help