Multi thread java applet

I cannot make multi thread applet. It seems like there is only one thread.
Here is the code:
public class My extends JApplet {
public void init() {
   new Thread() {
            public void run() {
                try {
                    nit();
                } catch (Exception e) {
        }.run();
        int i = 99;
        try {
            getAppletContext().showDocument(new URL("javascript:alert(" + String.valueOf(i) + ")"));
        catch (MalformedURLException e) { }
       public void nit() {
        for (int i = 0; i < 5; i++) {
            this.label.setText("Brojim: " + String.valueOf(i));
            try {
                getAppletContext().showDocument(new URL("javascript:alert(" + String.valueOf(i) + ")"));
            catch (MalformedURLException e) { }
            try {
                Thread.sleep(5000);
            } catch (InterruptedException e) { }
}and here is the result:
0
1
2
3
4
99which means that after run() call it not continue the flow, but waits for thread to finish. What is the problem?
OS: XP, browser: FF3

You are calling run() method of Thread class. This is wrong. If you want to create new thread you should call start() method. Try the following:
new Thread() {
            public void run() {
                try {
                    nit();
                } catch (Exception e) {
        }.start();

Similar Messages

  • Cannot get bitmap from native DLL from multi threaded Java app.

    I have a native DLL that gives me a HBITMAP (Windows handle to bitmap). I have made a JNI wrapper for this that gives me a BufferedImage back. The native code simple gets the actual bitmap for the handle, converts the RGB byte triplets to RGB ints, puts this in a jintArray and creates a BufferedImage.
    This all works fine within a single Java thread. If I do this multi threaded (thread 1 calls the native function and several seconds later, thread 2 calls the native function) I keep getting the last image of the first thread. Can enyone help me out?
    I know that this is probably a question for MSDN but I just know that they will tell me its a JNI question.
    The native code:
    JNIEXPORT jobject JNICALL Java_somenamespace_getPicture
    (JNIEnv *env, jclass cl, jstring serialNumber)
    jobject jImage;
    jclass jImageClass;
    jmethodID jMethod;
    jfieldID jField;
    jintArray rgbArray;
    char *str;
    char *charArray;
    int *intArray;
    int w, h, index, type;
    HBITMAP hbmp;
    BITMAP bmp;
    str = (char*)((*env)->GetStringUTFChars(env, serialNumber, NULL));
    // Gets the HBITMAP handle from the native DLL. The first argument is to select the device, based on serial number.
    getPicture(str, &hbmp);
    (*env)->ReleaseStringUTFChars(env, serialNumber, str);
    // Get the BITMAP for the HBITMAP
    GetObject(hbmp, sizeof(BITMAP), &bmp);
    // Create my BufferedImage
    jImageClass = (*env)->FindClass(env, "java/awt/image/BufferedImage");
    jMethod = (*env)->GetMethodID(env, jImageClass, "<init>", "(III)V");
    jField = (*env)->GetStaticFieldID(env, jImageClass, "TYPE_INT_RGB", "I");
    type = (*env)->GetStaticIntField(env, jImageClass, jField);
    jImage = (*env)->NewObject(env, jImageClass, jMethod, bmp.bmWidth, bmp.bmHeight, type);
    // Get the RGB byte triplets of the BITMAP
    charArray = (char *)malloc(sizeof(char) * bmp.bmHeight * bmp.bmWidth * 3);
    GetBitmapBits(hbmp, sizeof(char) * bmp.bmHeight * bmp.bmWidth * 3, charArray);
    // Allocate space to store the RGB ints and convert the RGB byte triplets to RGB ints
    intArray = (int *)malloc(sizeof(int) * bmp.bmHeight * bmp.bmWidth);
    index = 0;
    for (h = 0; h < bmp.bmHeight; ++h)
    for (w = 0; w < bmp.bmWidth; ++w)
    int b = *(charArray + index * 3) & 0xFF;
    int g = *(charArray + index * 3 + 1) & 0xFF;
    int r = *(charArray + index * 3 + 2) & 0xFF;
    *(intArray + index) = 0xFF000000 | (r << 16) | (g << 8) | b;
    ++index;
    // Create a jintArray for the C RGB ints
    rgbArray = (*env)->NewIntArray(env, bmp.bmHeight * bmp.bmWidth);
    (*env)->SetIntArrayRegion(env, rgbArray, 0, bmp.bmHeight * bmp.bmWidth, (jint*)intArray);
    // Use BufferedImage.setRGB() to fill the image
    jMethod = (*env)->GetMethodID(env, jImageClass, "setRGB", "(IIII[III)V");
    (*env)->CallVoidMethod(env, jImage, jMethod,
    0, // int startX
    0, // int startY
    bmp.bmWidth, // int width
    bmp.bmHeight, // int height
    rgbArray, // int[] rgbArray
    0, // int offset
    bmp.bmWidth); // int scansize
    // Free stuff
    (*env)->DeleteLocalRef(env, rgbArray);
    free(charArray);
    free(intArray);
    return jImage;
    }I already tried working with native HDCs (GetDC, CreateCompatibleBitmap, SelectObject, GetDIBits, ...) but this just complicates stuff and gives me the same result.

    Have you verified what the "native DLL" gives you back on the second call?The HBITMAP handle returned is the same each call (no matter which thread). The actual BITMAP associated with this handle is only updated in the first thread.
    How are you determining that the image is the same?If I point the camera (I don't get a stream, I just get individual images) to a moving scene, I get different images for each call from within the first thread. The second thread only gets the latest image from the first thread. There is no concurrency of the threads and all methods are synchronized.
    Specifically did you verify that the problem is not that your test code itself is using the same instance?Yes, I tested the native side as well as the Java side. The BufferedImage is always an exact copy of the native BITMAP.
    Try printing out the hash for each instance.I have written the image to a file in the native code itself to eliminate anything related to the mechanism of returning the BufferedImage. This had the same result.
    The return values of all native calls all indicate successful calls.
    I am suspecting the native side of creating a second graphical context for the second thread while it keeps refering to the first context.
    (I will start a thread on the MSDN as well and will post here if anything turns up.)

  • Multi-threaded java application and deadlock down in Oracle library

    Hello,
    I was running our Java (JDK 1.6_14) application from Windows XP hitting an Oracle (10g) instance on Linux and came across a deadlock issue with two (of 10) threads. Below is the stacktraces (based on Java thread-dump at the command line). This code I've run 30-40 times with no problems of deadlocks.
    The Oracle library that we're using for our Java application is ojdbc14.jar and sdoapi.jar (for spatial).
    We create our Connection as follows (for each thread -- 10 of them):
    public class Worker implements Runnable
    private Connection _Conn;
    public Worker(...)
    DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
    _Conn = DriverManager.getConnection(url, username, password);
    _Conn.setAutoCommit(false);
    The code that is already executing these same lines below was already executed by other threads (in their own instance of Worker). So this is very confusing.
    Any ideas? Version of the .jar files? Place how we're calling "DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());"?
    Thanks, Jim
    Found one Java-level deadlock:
    =============================
    "WORKER_1":
    waiting to lock monitor 0x02b50d8c (object 0x22e8af80, a oracle.jdbc.driver.T4CConnection),
    which is held by "WORKER_0"
    "WORKER_0":
    waiting to lock monitor 0x02b50d24 (object 0x22f6d258, a oracle.sql.StructDescriptor),
    which is held by "WORKER_1"
    Java stack information for the threads listed above:
    ===================================================
    "WORKER_1":
    at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3410)
    - waiting to lock <0x22e8af80> (a oracle.jdbc.driver.T4CConnection)
    at oracle.sql.StructDescriptor.initMetaData1_9_0(StructDescriptor.java:1516)
    - locked <0x22f6d258> (a oracle.sql.StructDescriptor)
    - locked <0x22eabd80> (a oracle.jdbc.driver.T4CConnection)
    at oracle.sql.StructDescriptor.initMetaData1(StructDescriptor.java:1408)
    at oracle.sql.StructDescriptor.isInstantiable(StructDescriptor.java:892)
    at oracle.sql.STRUCT.<init>(STRUCT.java:148)
    at oracle.spatial.geometry.JGeometry.store(JGeometry.java:2954)
    at oracle.spatial.geometry.JGeometry.store(JGeometry.java:3777)
    .......... <our package/class>
    "WORKER_0":
    at oracle.sql.StructDescriptor.initMetaData1_9_0(StructDescriptor.java:1494)
    - waiting to lock <0x22f6d258> (a oracle.sql.StructDescriptor)
    - locked <0x22e8af80> (a oracle.jdbc.driver.T4CConnection)
    at oracle.sql.StructDescriptor.initMetaData1(StructDescriptor.java:1408)
    at oracle.sql.StructDescriptor.isInstantiable(StructDescriptor.java:892)
    at oracle.sql.STRUCT.<init>(STRUCT.java:148)
    at oracle.spatial.geometry.JGeometry.store(JGeometry.java:2954)
    at oracle.spatial.geometry.JGeometry.store(JGeometry.java:3777)
    ..........<our package/class>
    Edited by: Jim Atharris on Aug 24, 2009 6:23 PM

    Thanks Toon for your reply.
    Yes each Worker (executing in their own thread) has their own instance of Connection as per the Constructor (shown in original post). That is why this is weird.
    I'll check the v$session when I get into work.
    Based on our code that I put in the original email, Connection is a non-static variable. We have a per Thread per instance of Worker of which that Worker instance has its own instance of Connection. So I'm wonder if the following needs to occur:
    Both of these lines (from original email) need to happen in the main thread as follows:
    DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
    for (i=0;i<NUM_OF_WORKERS)
    _Conn = DriverManager.getConnection(url, username, password);
    new Worker(_Conn);
    Thanks,Jim

  • Multi-threaded progam????

    I need help in writing a multi-threaded java program that creates 10 threads and waits until they finish to terminate(using join()). The main program will initialize an integer counter to 0 that each thread will access. THe main program should then dispplay the expected value in the counter and the actual valie in the counter

    Contestant: "Alex, I'll take 'This is somebody's homework for $1,000"

  • Java multi-thread Applet and Multi-processor

    Hello,
    I have a JAVA applet which work fine on a mono-processeur machine and not fine at all on multi-processors.
    It use multi thread (for reading on socket) and some times, request are lost.
    Is that a matter of programming or a JVM bug ?
    This happens on Linux and Windows NT bi-processors.
    We hare using JAVA 1.3.0_02
    Thanks for your help
    [email protected]

    I have already have a look to javax.swing.SwingUtilities.invokeLater() but (I think) it don't work for my need.
    A graphic applet which create 2 threads : one for reading and one for writing on a socket.
    Request sent to the server are memorized in a vector, and once answer is received, the request is remove from vector and treated. Access to the list is protected by synchronize.
    Everything works fine one several plateforme (linux, windows 98/2000/NT, Solaris). The only problem is on multi-processor : request are lost !

  • Running a Java Multi Thread Program in database

    I have created a multi threaded program in Java and it runs successfully from the command prompt. I want to create a DBMS Job which will wake up at regular intervals and runs the java program(Java stored procedure). Is this possible in 9.2/10G ?? If Yes, will there be any impact on the DB performance/increase memory etc.,
    The database (9.2...) resides on a RH 2.3 AS box.
    Any ideas...
    Thanks,
    Purush

    Purush,
    Java stored procedures cannot be multi-threaded. Well, they can, but the threads will not run in parallel. You may be able to find some more information in the Oracle documentation, which is available from:
    http://tahiti.oracle.com
    Good Luck,
    Avi.

  • The problem about multi-thread in java application

    i have problem with the multi-thread in java application, i don't know how to stop and restart a thread safely, because the function thread.stop(),thread.suspend() are both deprecated.
    now what i can only do is making the thread check a flag(true or false) to determine whether to start or to stop, but i think this thread will always be in the memory and maybe it will lower the performance of the system, as the program i am developping is working under realtime enviorement.
    please help me about it. thanks !

    hi,
    you can stop a thread by exiting it's run()-method which in terms can be done by checking the interrupted-flag:
    public void run(){
    while(interrupted()){ //if the thread consists of a loop
    or
    public void run(){
    if(interrupted())return;
    if(interrupted())return;
    or by the use of the return-statement anywhere withing the run-method. Afterwards, that is when the thread is no longer needed, you clear all the references to the specific thread object by setting them to null:
    Thread t;
    ... //working
    t.interrupt(); //interrupting
    while(t.isAlive()){
    Thread.yield(); //wait till thread t has stopped
    t=null;
    best regards, Michael

  • Java Security Manager in Multi-threaded application

    I am writing a multi-threaded application listening (TCP and UDP) to several ports. To help implement certain security features (eg. refusing connections from certain ip address), I'm using the java.lang.SecurityManager (by subclassing it). I am having a few problems and queries and am hoping someone here can help me.
    1. As all the threads are calling the checkAccept(host, port) method. Is there a way to know which thread is currently accessing the security manager? For example if host A were to make 2 connections to the application, one to thread 1 (say listening to port 5001) and the other to to thread 2 (say listening to port 5002). I intend to refuse the connection to thread 2 but there is not way of differentiating the 2 connections since they are from the same host and there isnt any way of knowing their port number.
    2. Are calls to the Security Manager thread safe?
    I have been having this problem for a long time, would appreciate if someone can help point me to the right direction. cheers.

    1. As all the threads are calling the
    checkAccept(host, port) method. Is there a way to
    know which thread is currently accessing the security
    manager?Just use Thread.currentThread(). As specified in the Javadoc for e.g. SecurityManager.checkAccept().
    2. Are calls to the Security Manager thread safe? No.

  • Question using Java API in a multi threaded application for MDX queries

    Currently I’m building a web application that makes a lot of MDX calls using the Essbase Java API. Each time we run an MDX call we basically run the following code:
    IEssbase ess = IEssbase.Home.create(IEssbase.JAPI_VERSION);
    IEssDomain dom = ess.signOn(userName, password, false, null, "embedded");
    IEssCubeView cv = cv=dom.openCubeView("view", hostName, appName, cubeName);
    IEssOpMdxQuery op = cv.createIEssOpMdxQuery();
    op.setQuery(false,mdx,false,IEssOpMdxQuery.EEssMemberIdentifierType.NAME);
    cv.performOperation(op);
    IEssMdDataSet mddata = cv.getMdDataSet();
    cv.close();
    My questions is, is this the correct way to use the API in multi threaded environment where many users may be hitting the application at the same time? For every request do I need to create a separate IEssbase object and sign on to an IEssDomain? Or can I use a single IEssbase and IEssDomain object for the entire application? If not should I call the IEssDomain.signOff() method after each user’s request has completed? Which of the above objects are thread safe? I’m using Essabae 9.3.1. Any insight would be really appreciated.
    Thanks
    David

    Thanks for the input friend,
    I should have mentioned that in my application all
    connections to Essbase use the same user name and
    password so the filtering isn’t a concern. This is my
    first Java application using Essbase has a data
    source, I’m used to connecting to various SQL
    databases and I always use a connection pool, how is
    connection pooling handled in the Essbase java API?I'm not sure what happened to it since I never used it, but there used to be something called the High Availability Services or something that was essentially a connection pool for Essbase JAPI connections, but it required an extra license.
    Since you don't care about identity (everyone has full access to everything), you can create your own connection pool, but you'll have to manage your multithreading yourself. Its been this way since the beginning. The C API isn't/wasn't thread-safe either (we tried).

  • Awful Java applet performance -- never mind, being handled in a different thread

    Awful Java applet performance -- never mind, being handled in a different thread.

    Here's some more info that may be of use ... The Applet is signed and this particular problem only occurs with Safari. It has not been seen as of yet when using Firefox. And it definitey does not occur on Windows platforms with IE or Firefox. It's been observed across multiple versions of the applet and appears to have become an issue around the time of Leopard 10.5.6/Safari 3.2.1. I don't know if it has anything to do with the problem, but the html that starts the applet is dynamically generated from javascript. A user clicks a thumbnail image on a web page, the javascript opens a dojo dialog, and within the div that contains the dialog, another div is inserted containing the html that starts the applet. The applet also does a number of liveconnect calls to call javascript methods. When a "close" button is clicked on the Applet, the inverse occurs. The javascript clears the html that contained the applet. The applet's destroy method is called and there are no apparent memory leaks.
    The problem never seems to occur the first time the applet is started. It's always on a subsequent instantiation. Frequently, when it occurs, the applet is only partially painted and I sometimes see paint related calls on the stack trace of the awt thread.

  • How to write a multi threaded Cache Event Listener

    I have a distributed data cache called tokenCache for my application. I have also added a mapListener to this cache to listen to a particular kind of events.
    tokenCache.addMapListener((MapListener) new TokenCacheListenerBean(), new MapEventFilter(tokenFilter), false);
    So bascially everytime a token (The domain object of this cache) is updated the entryUpdated() method in my EJB TokenCacheListenerBean is invoked.
    The issue I have though is that, from what I observe on running my code is that the Cache Listener is single threaded. So if two Token Objects on my tokenCache are updated,
    lets say Token Object A and Token Object B one after the other,  the entryUpdated() method in my EJB is invoked for Token Object A and  once the invocation is complete
    then the entryUpdated() method is invoked again for Token Object B(). At a given point of time there is only one instance of TokenCacheListenerBean EJB.  Is there a way to
    make this happen in multi-threaded manner ?
    Is there a configuration setting somewhere which allows multiple CacheListeners to be instantiated at a given point of time ?
    TokenCacheListenerBean  EJB_
    package oracle.communications.activation.asap.ace;
    import java.util.Iterator;
    import java.util.Set;
    import java.util.logging.Logger;
    import javax.ejb.Stateless;
    import com.tangosol.net.NamedCache;
    import com.tangosol.util.MapEvent;
    import com.tangosol.util.MapListener;
    import com.tangosol.util.ValueUpdater;
    import com.tangosol.util.extractor.PofExtractor;
    import com.tangosol.util.extractor.PofUpdater;
    import com.tangosol.util.filter.EqualsFilter;
    import com.tangosol.util.filter.LikeFilter;
    import com.tangosol.util.filter.LimitFilter;
    import com.tangosol.util.processor.UpdaterProcessor;
    * Session Bean implementation class TokenCacheListenerBean
    @Stateless
    public class TokenCacheListenerBean implements TokenCacheListenerBeanRemote, TokenCacheListenerBeanLocal, MapListener {
    NamedCache asdlCache;
    NamedCache tokenCache;
    private final int PAGE_SIZE = 1;
    private static Logger logger = Logger.getLogger(ConnectionManager.class.getName());;
    * An instance of the JCAModeler EJB, represents the JCA-JNEP
    JCAModeler jcaBean;
    * Default constructor.
    public TokenCacheListenerBean() {
    // TODO Auto-generated constructor stub
    public void entryDeleted(MapEvent Event) {
    public void entryInserted(MapEvent Event) {
    public void entryUpdated(MapEvent Event) {
    Token newToken = (Token) Event.getNewValue();
    Token oldToken = (Token) Event.getOldValue();
    if ((oldToken.getState() == Token.TOKEN_RESERVED)
    && (newToken.getState()== Token.TOKEN_AVAILABLE)) {
    String networkID = newToken.getNeID();
    asdlCache = AceCacheFactory.getCache("asdlCache");
    tokenCache = AceCacheFactory.getCache("tokenCache");
    EqualsFilter filterNE = new EqualsFilter(new PofExtractor(String.class,Asdl.NETWORKID), networkID);
    LimitFilter limitFilter = new LimitFilter(filterNE, PAGE_SIZE);
    Set removeASDL = asdlCache.keySet(limitFilter);
    Iterator asdlIterator = removeASDL.iterator();
    if (asdlIterator.hasNext()) {
    logger.info(printASDLCache());
    ValueUpdater updater = new PofUpdater(Token.STATE);
    System.out.println("Token ID:" + newToken.getTokenID());
    UpdaterProcessor updaterProcessor = new UpdaterProcessor(updater, Integer.toString(Token.TOKEN_RESERVED));
    tokenCache.invoke(newToken.getTokenID(), updaterProcessor);
    jcaBean = new JCAModeler(tokenCache);
    Object asdlID = asdlIterator.next();
    Asdl provisionAsdl = (Asdl) asdlCache.get(asdlID);
    asdlCache.remove(asdlID);
    jcaBean.provision(provisionAsdl, newToken.getTokenID());
    logger.info(ConnectionManager.printTokenCache());
    logger.info(printASDLCache());
    }

    Here is what I am asking!
    I have added 2 listeners (Listener A and Listener B) which each listen on for changes made to 2 different token Cache Objects (Token A and Token B).
    for (i = 0; i < 2 ; i++) {
    Token tokenAdded = new Token(UUID.randomUUID().toString(),TOKEN_AVAILABLE, networkID);
    tokenCache.put(tokenAdded.getTokenID(), tokenAdded);
         tokenCache.addMapListener((MapListener) new TokenCacheListener(), tokenAdded.getTokenID(), false);
    Now assume that updates are made to Token A and Token B simuntaneosly.
    Why do i observe in my diagnostic messages that only one Listener is invoked at a given point of time.
    Which means I see Listener A getting invoked and then once invocation of Listener A is complete I see Listener B bieng invoked.
    Ideally I would want both listeners to be invoked simultaneously rather than in a one off fashion.
    Here is the code for my token cache Listener
    package oracle.communications.activation.asap.ace;
    import java.util.Iterator;
    import java.util.Map;
    import java.util.Set;
    import java.util.logging.Level;
    import java.util.logging.Logger;
    import com.tangosol.net.CacheFactory;
    import com.tangosol.net.NamedCache;
    import com.tangosol.util.AbstractMapListener;
    import com.tangosol.util.Filter;
    import com.tangosol.util.MapEvent;
    import com.tangosol.util.MapListener;
    import com.tangosol.util.ObservableMap;
    import com.tangosol.util.ValueUpdater;
    import com.tangosol.util.extractor.PofExtractor;
    import com.tangosol.util.extractor.PofUpdater;
    import com.tangosol.util.filter.AndFilter;
    import com.tangosol.util.filter.EqualsFilter;
    import com.tangosol.util.filter.LikeFilter;
    import com.tangosol.util.filter.LimitFilter;
    import com.tangosol.util.processor.UpdaterProcessor;
    public class TokenCacheListener extends AbstractMapListener {
         NamedCache asdlCache;
         NamedCache tokenCache;
         AceCacheFactory cacheFactoryBean = new AceCacheFactory();
         private final int PAGE_SIZE = 1;
         private static Logger logger = Logger.getLogger(ConnectionManager.class
                   .getName());;
         * An instance of the JCAModeler EJB, represents the JCA-JNEP
         JCAModeler jcaBean;
         * This is a utility method and prints the tokens cache.
         public String printTokenCache() {
              NamedCache tokenCache = cacheFactoryBean.getCache("tokenCache");
              LikeFilter tokenList = new LikeFilter(new PofExtractor(String.class,
                        Token.STATE), "%", (char) 0, false);
              Set keySet = tokenCache.keySet(tokenList);
              StringBuffer cachedTokenList = new StringBuffer("\n################################## Token(s) Cache ##################################");
              int counter = 1;
              for (Object tokenInCache: keySet) {
                   Token tokenObject = (Token) tokenCache.get(tokenInCache.toString());
                   cachedTokenList.append("\nS.NO:" + (counter++)
                             + "\t ID:" + tokenInCache.toString()
                             + "\t State:" + Token.tokenToString(tokenObject.getState()));
              cachedTokenList.append("\n####################################################################################");
              return cachedTokenList.toString();     
         * This method is a utility method and it prints all the ASDL(s) currently present on the
         * asdlCache.
         private String printASDLCache() {
              NamedCache asdlCache = cacheFactoryBean.getCache("asdlCache");
              LikeFilter asdlList = new LikeFilter(new PofExtractor(String.class,
                                  Asdl.NETWORKID), "%", (char) 0, false);
              Set keySet = asdlCache.keySet(asdlList);
              StringBuffer cachedASDLList = new StringBuffer("\n################ ASDL Cache ######## ########");
              int counter = 1;
              for (Object asdlInCache: keySet) {
                   cachedASDLList.append("\nS.NO:" + (counter++) + "\t ID:" + asdlInCache.toString());
              cachedASDLList.append("\n################ ASDL Cache ######## ########\n");
              return cachedASDLList.toString();     
         public TokenCacheListener() {
         public void checkASDLCache(MapEvent Event) {
         // Not currently used
         public void entryUpdated(MapEvent Event) {
              Token newToken = (Token) Event.getNewValue();
              Token oldToken = (Token) Event.getOldValue();
              logger.info("\n=============================================================================================="
                        + "\nTOKEN CACHE LISTENER"
                        + "\n=============================================================================================="
                        + printTokenCache()
                        + "\n==============================================================================================");
              if ((oldToken.getState() == Token.TOKEN_RESERVED)
                        && (newToken.getState()== Token.TOKEN_AVAILABLE)) {
              String networkID = newToken.getNeID();
              asdlCache = cacheFactoryBean.getCache("asdlCache");
              tokenCache = cacheFactoryBean.getCache("tokenCache");
              EqualsFilter filterNE = new EqualsFilter(new PofExtractor(String.class,Asdl.NETWORKID), networkID);
              LimitFilter limitFilter = new LimitFilter(filterNE, PAGE_SIZE);
              Set removeASDL = asdlCache.keySet(limitFilter);
              Iterator asdlIterator = removeASDL.iterator();
              if (asdlIterator.hasNext()) {
              logger.info(printASDLCache());
              ValueUpdater updater = new PofUpdater(Token.STATE);
              System.out.println("Token ID:" + newToken.getTokenID());
              UpdaterProcessor updaterProcessor = new UpdaterProcessor(updater, Integer.toString(Token.TOKEN_RESERVED));
              tokenCache.invoke(newToken.getTokenID(), updaterProcessor);
              jcaBean = new JCAModeler(tokenCache);
              Object asdlID = asdlIterator.next();
              Asdl provisionAsdl = (Asdl) asdlCache.get(asdlID);
              asdlCache.remove(asdlID);
              jcaBean.provision(provisionAsdl, newToken.getTokenID());
              logger.info(printTokenCache());
              logger.info(printASDLCache());
    I only see one instance of this listener alive at any given point of time.
    Edited by: 807103 on Nov 3, 2011 1:00 PM
    Edited by: 807103 on Nov 3, 2011 1:12 PM

  • Problem Launching Java Applet with Plug-in: Version 1.4.2_01

    Hello out there:
    I recently installed j2re-1.4.2_01 on my home computer but have been unable to access Web sites emmploying JAva applets. The following is an email exchange with Jeff Hall of Lowell Observatory, manager of an educational site hosted by Lowell, trying to resolve my problem. The messages are better understood if read in reverse order.
    I'm hoping that someone will recognize the source of my problem and can recommmend a solution. I would appreciate any help offered.
    Thanks,
    Mike Coucke
    Hi Jeff:
    Well, I guess the problem lies with me somewhere. Here's my answer/status to your questions/suggestions:
    1) I'm using MS Windows Me version 4.90.3000
    2) I do have the directory C:\Windows\.jpi_cache\jar\, but the only thing in it is an empty folder labeled "1.0". The file LP.jar does not exist anywhere on my hard drive.
    3) I tried several game sites that utilized Java applets and got the same results: the Java cup in the upper left corner followed a few seconds later by the red "X". So, evidently the problem is somewhere on my end.
    I'm going to post our email exchanges in a Java Users Forum managed by Sun to see if anyone out there can solve my problem. However, if you have any more suggestions, I'll be glad to try them.
    Thanks for the help.
    Mike Coucke
    [email protected]
    ----- Original Message -----
    From: "Jeffrey Hall" <[email protected]>
    To: "'Mike Coucke'" <[email protected]>
    Sent: Friday, September 05, 2003 1:02 PM
    Subject: RE: Registration with Lowell Education Online
    Mike,
    Rats! What version of Windows are you using? It's a little strange to
    see the user directory set to C:\Windows; if you're using XP, I'd expect
    it to be something like C:\Documents and Settings\Mike Coucke. In any
    event, the output that is of concern is these two lines:
    java.lang.ClassNotFoundException: LPRemote.class
    Caused by: java.net.UnknownHostException: proxy
    It looks like your browser is not finding our server's IP when it comes
    time to download the necessary Java code.
    LPRemote.class is the fundamental code that runs LOPARC, and your
    browser should be downloading it automatically when you click connect.
    LPRemote.class is stored along with a bunch of other classes in a file
    called "LP.jar" that you download from our server. So, if you go to C:
    in Windows Explorer and do a file search for LP.jar, you should find it.
    On my machine, it's stored in a directory called ".jpi_cache\jar\" in my
    user home directory. Let me know if you have this file, or the
    jpi-cache directory.
    One other thing you might try is going to a different site that you know
    uses Java applets -- I think some of the online game rooms at Yahoo use
    Java. See if other sites that use Java load correctly. Then we'll know
    if it's our server specifically, or a more general problem on your end.
    Jeff Hall
    Lowell Observatory
    Hello Jeff:
    I still have the Java "blues". I followed your instructions, but am still unable to launch a LOPARC session. After an initial failure, I uninstalled all three Java versions I had (1.4.0, 1.4.1, 1.4.2), then reinstalled 1.4.2_01 from the Sun website.
    Now, when I try to launch LOPARC, I initially get a blank window with the Java cup in the upper left corner. After about 20 seconds, the cup changes to a red "X". During those 20 seconds, the following appear in the IE message bar at the bottom of the window: "Applet LPRemote notinited" (their spelling) which changes to "Loading Java Applet Failed..." when the red "X" appears.
    Following is a copy of the log from my Java Console during all of this:
    Java(TM) Plug-in: Version 1.4.2_01
    Using JRE version 1.4.2_01 Java HotSpot(TM) Client VM
    User home directory = C:\WINDOWS
    Proxy Configuration: Manual Configuration
    Proxy: http=proxy,https=proxy,ftp=proxy,gopher=proxy
    Proxy Overrides:
    c: clear console window
    f: finalize objects on finalization queue
    g: garbage collect
    h: display this help message
    l: dump classloader list
    m: print memory usage
    o: trigger logging
    p: reload proxy configuration
    q: hide console
    r: reload policy configuration
    s: dump system properties
    t: dump thread list
    v: dump thread stack
    x: clear classloader cache
    0-5: set trace level to <n>
    load: class LPRemote.class not found.
    java.lang.ClassNotFoundException: LPRemote.class
    at sun.applet.AppletClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at sun.applet.AppletClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at sun.applet.AppletClassLoader.loadCode(Unknown Source)
    at sun.applet.AppletPanel.createApplet(Unknown Source)
    at sun.plugin.AppletViewer.createApplet(Unknown Source)
    at sun.applet.AppletPanel.runLoader(Unknown Source)
    at sun.applet.AppletPanel.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
    Caused by: java.net.UnknownHostException: proxy
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at sun.net.NetworkClient.doConnect(Unknown Source)
    at sun.plugin.net.protocol.http.HttpClient.doConnect(Unknown Source)
    at sun.net.www.http.HttpClient.openServer(Unknown Source)
    at sun.net.www.http.HttpClient$3.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.net.www.http.HttpClient.privilegedOpenServer(Unknown Source)
    at sun.net.www.http.HttpClient.openServer(Unknown Source)
    at sun.net.www.http.HttpClient.<init>(Unknown Source)
    at sun.net.www.http.HttpClient.<init>(Unknown Source)
    at sun.plugin.net.protocol.http.HttpClient.<init>(Unknown Source)
    at sun.plugin.net.protocol.http.HttpClient.New(Unknown Source)
    at sun.plugin.net.protocol.http.HttpURLConnection.createConnection(Unknown Source)
    at sun.plugin.net.protocol.http.HttpURLConnection.connect(Unknown Source)
    at sun.plugin.net.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
    at java.net.HttpURLConnection.getResponseCode(Unknown Source)
    at sun.applet.AppletClassLoader.getBytes(Unknown Source)
    at sun.applet.AppletClassLoader.access$100(Unknown Source)
    at sun.applet.AppletClassLoader$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    ... 10 more
    I followed this up by executing the following three console commands:
    "dump system properties"
    "dump classholder list"
    "dump thread list"
    and obtained the following listings:
    Dump system properties ...
    acl.read = +
    acl.read.default =
    acl.write = +
    acl.write.default =
    application.home = C:\PROGRA~1\JAVA\J2RE14~1.2_0
    awt.toolkit = sun.awt.windows.WToolkit
    browser = sun.plugin
    browser.vendor = Sun Microsystems, Inc.
    browser.version = 1.1
    deployment.javaws.cache.dir = C:\WINDOWS\.javaws\cache
    deployment.javaws.jre.0.enabled = true
    deployment.javaws.jre.0.location = http://java.sun.com/products/autodl/j2se
    deployment.javaws.jre.0.osarch = x86
    deployment.javaws.jre.0.osname = Windows
    deployment.javaws.jre.0.path = C:\Program Files\Java\j2re1.4.2_01\bin\javaw.exe
    deployment.javaws.jre.0.platform = 1.4
    deployment.javaws.jre.0.product = 1.4.2_01
    deployment.javaws.jre.0.registered = true
    deployment.javaws.version = javaws-1.4.2_01
    deployment.system.cacerts = C:\PROGRA~1\JAVA\J2RE14~1.2_0\lib\security\cacerts
    deployment.system.home = C:\WINDOWS\Sun\Java\Deployment
    deployment.system.jssecacerts = C:\PROGRA~1\JAVA\J2RE14~1.2_0\lib\security\cacerts
    deployment.system.profile = C:\WINDOWS
    deployment.system.security.policy = file:/C:/WINDOWS/Sun/Java/Deployment/security/java.policy
    deployment.user.cachedir = C:\WINDOWS\Application Data\Sun\Java\Deployment\cache
    deployment.user.certs = C:\WINDOWS\Application Data\Sun\Java\Deployment\security\deployment.certs
    deployment.user.extdir = C:\WINDOWS\Application Data\Sun\Java\Deployment\ext
    deployment.user.home = C:\WINDOWS\Application Data\Sun\Java\Deployment
    deployment.user.jssecerts = C:\WINDOWS\Application Data\Sun\Java\Deployment\security\deployment.jssecerts
    deployment.user.logdir = C:\WINDOWS\Application Data\Sun\Java\Deployment\log
    deployment.user.profile = C:\WINDOWS\Application Data
    deployment.user.security.policy = file:/C:/WINDOWS/Application%20Data/Sun/Java/Deployment/security/java.policy
    deployment.user.tmpdir = C:\WINDOWS\Application Data\Sun\Java\Deployment\cache\tmp
    file.encoding = Cp1252
    file.encoding.pkg = sun.io
    file.separator = \
    file.separator.applet = true
    http.agent = Mozilla/4.0 (Windows Me 4.90)
    http.auth.serializeRequests = true
    https.protocols = SSLv3,SSLv2Hello
    java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
    java.awt.printerjob = sun.awt.windows.WPrinterJob
    java.class.path = C:\PROGRA~1\JAVA\J2RE14~1.2_0\classes
    java.class.version = 48.0
    java.class.version.applet = true
    java.endorsed.dirs = C:\PROGRAM FILES\JAVA\J2RE1.4.2_01\lib\endorsed
    java.ext.dirs = C:\PROGRAM FILES\JAVA\J2RE1.4.2_01\lib\ext
    java.home = C:\PROGRA~1\JAVA\J2RE14~1.2_0
    java.io.tmpdir = C:\WINDOWS\TEMP\
    java.library.path = D:\PROGRAM FILES\INTERNET EXPLORER 6;.;C:\WINDOWS\SYSTEM;C:\WINDOWS;D:\PROGRA~1\INTERN~1;;C:\WINDOWS;C:\WINDOWS\COMMAND
    java.protocol.handler.pkgs = sun.plugin.net.protocol|sun.plugin.net.protocol
    java.runtime.name = Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version = 1.4.2_01-b06
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Sun Microsystems Inc.
    java.specification.version = 1.4
    java.util.prefs.PreferencesFactory = java.util.prefs.WindowsPreferencesFactory
    java.vendor = Sun Microsystems Inc.
    java.vendor.applet = true
    java.vendor.url = http://java.sun.com/
    java.vendor.url.applet = true
    java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
    java.version = 1.4.2_01
    java.version.applet = true
    java.vm.info = mixed mode
    java.vm.name = Java HotSpot(TM) Client VM
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Sun Microsystems Inc.
    java.vm.specification.version = 1.0
    java.vm.vendor = Sun Microsystems Inc.
    java.vm.version = 1.4.2_01-b06
    javaplugin.maxHeapSize = 96m
    javaplugin.nodotversion = 142_01
    javaplugin.proxy.config.list = http=proxy,https=proxy,ftp=proxy,gopher=proxy
    javaplugin.proxy.config.type = manual
    javaplugin.version = 1.4.2_01
    javaplugin.vm.options = -Djava.class.path=C:\PROGRA~1\JAVA\J2RE14~1.2_0\classes -Xbootclasspath/a:C:\PROGRA~1\JAVA\J2RE14~1.2_0\lib\plugin.jar -Xmx96m -Djavaplugin.maxHeapSize=96m -Xverify:remote -Djavaplugin.version=1.4.2_01 -Djavaplugin.nodotversion=142_01 -Dbrowser=sun.plugin -DtrustProxy=true -Dapplication.home=C:\PROGRA~1\JAVA\J2RE14~1.2_0 -Djava.protocol.handler.pkgs=sun.plugin.net.protocol
    line.separator = \r\n
    line.separator.applet = true
    os.arch = x86
    os.arch.applet = true
    os.name = Windows Me
    os.name.applet = true
    os.version = 4.90
    os.version.applet = true
    package.restrict.access.netscape = false
    package.restrict.access.sun = true
    package.restrict.definition.java = true
    package.restrict.definition.netscape = true
    package.restrict.definition.sun = true
    path.separator = ;
    path.separator.applet = true
    sun.arch.data.model = 32
    sun.boot.class.path = C:\PROGRAM FILES\JAVA\J2RE1.4.2_01\lib\rt.jar;C:\PROGRAM FILES\JAVA\J2RE1.4.2_01\lib\i18n.jar;C:\PROGRAM FILES\JAVA\J2RE1.4.2_01\lib\sunrsasign.jar;C:\PROGRAM FILES\JAVA\J2RE1.4.2_01\lib\jsse.jar;C:\PROGRAM FILES\JAVA\J2RE1.4.2_01\lib\jce.jar;C:\PROGRAM FILES\JAVA\J2RE1.4.2_01\lib\charsets.jar;C:\PROGRAM FILES\JAVA\J2RE1.4.2_01\classes;C:\PROGRA~1\JAVA\J2RE14~1.2_0\lib\plugin.jar
    sun.boot.library.path = C:\PROGRAM FILES\JAVA\J2RE1.4.2_01\bin
    sun.cpu.endian = little
    sun.cpu.isalist = pentium i486 i386
    sun.io.unicode.encoding = UnicodeLittle
    sun.java2d.fontpath =
    sun.net.client.defaultConnectTimeout = 120000
    sun.os.patch.level =
    trustProxy = true
    user.country = US
    user.dir = C:\WINDOWS\Desktop
    user.home = C:\WINDOWS
    user.language = en
    user.name = Michael G. Coucke
    user.timezone =
    user.variant =
    Done.
    Dump classloader list ...
    codebase=http://kraken.lowell.edu/, key=http://kraken.lowell.edu/,IONJava/classes/ion_16.jar,IONJava/classes/LP.jar, zombie=false, cache=true, refcount=1, info=sun.plugin.ClassLoaderInfo@109de5b
    Done.
    Dump thread list ...
    Group main,ac=11,agc=2,pri=10
    main,5,alive
    AWT-Windows,6,alive,dameon
    AWT-Shutdown,5,alive
    Java2D Disposer,10,alive,dameon
    AWT-EventQueue-0,6,alive
    Group Plugin Thread Group,ac=3,agc=0,pri=10
    Main Console Writer,6,alive
    AWT-EventQueue-1,6,alive
    TimerQueue,5,alive,dameon
    Group http://kraken.lowell.edu/-threadGroup,ac=2,agc=0,pri=4
    thread applet-LPRemote.class,4,alive
    AWT-EventQueue-2,4,alive
    Done.
    I'm not a Java expert, so this may be more information than you ever wanted to see.
    Once again, I hope that you can help. My experience has been that I usually have some obscure option set incorrectly and that causes me great grief.
    Thanks fo your help,
    Mike Coucke
    [email protected]
    ----- Original Message -----
    From: "Jeffrey Hall" <[email protected]>
    To: "'Mike Coucke'" <[email protected]>
    Sent: Thursday, September 04, 2003 11:48 AM
    Subject: RE: Registration with Lowell Education Online
    Hi Mike,
    Try it now. I think this problem has arisen because Sun just
    released a new version of the Plug-in (1.4.2), and when we released the
    public beta of LOPARC, only one relevant version (1.4.0) was available
    and the LOPARC code was written to look for that by default. I have
    just recoded the relevant routines so they should now cause your browser
    to simply pick up the latest 1.4 version of the Plug-in you have
    installed, whatever it is. I "broke" Java on my machine to replicate
    your problem, and the code I inserted today did fix it. Hopefully it
    will have the same effect for you. I am running IE 6 and plugin
    1.4.2_01 (as accessed via Tools->Sun Java Console).
    One broader problem: some (non-LOPARC-specific) users on the Sun
    forums have reported the "JRE collision" you are seeing when multiple
    versions of the Plug-in are installed on the same machine. So if the
    fix I made to our code doesn't work, one option would be to uninstall
    all Java components from your computer and do a fresh install of the
    latest runtime environment.
    Let me know how/if this works. Thanks for the feedback and for your
    patience.
    Best regards,
    Jeff Hall
    Lowell Observatory
    -----Original Message-----
    From: Mike Coucke [mailto:[email protected]]
    Sent: Wednesday, September 03, 2003 6:30 PM
    To: [email protected]
    Subject: Re: Registration with Lowell Education Online
    Hello Jeff:
    So far, I have been unable to launch a LOPARC session. I repeatedly
    get the following error message:
    "Exception: java.lang.ClassNotFoundException: LPRemote.class"
    My browser is MS Internet Explorer version 6.0.2800.1106 Initially I was
    using Java Plug-In version 1.4.1 and received the error message. I went
    to the Sun website and downloaded/installed Java Plug-In version 1.4.2
    and still get the message.
    Before I try to launch LOPARC, I can select Tools->Sun Java Console from
    IE's pull down menu to check my Java Plug-In version. When I try to
    launch LOPARC, I get the following message:
    "Applet(s) in this HTML page requires a version of Java different from
    the one the browser is currently using. In order to run the applet(s)
    in this HTML page, a new browser session is required, press 'Yes' to
    start a new browser session." If I select 'No', I get the following
    message: "Java Plug-in detected JRE collission"
    If I select 'Yes', a new browser window opens and then I get the first
    message above.
    Can you help?
    Mike Coucke
    [email protected]
    ----- Original Message -----
    From: <[email protected]>
    To: <[email protected]>
    Sent: Monday, September 01, 2003 5:30 PM
    Subject: Registration with Lowell Education Online
    September 1, 2003
    Dear Michael Coucke:
    Thank you for registering with Lowell Observatory's online education
    site. We hope you enjoy using it and visit regularly as we continue to
    expand its features and capabilities. This is a one-time welcoming
    email.
    For your records, your user ID is xxxxx, and your password is #########.
    You'll need to supply these each time you log in.
    This site gives you access to research-grade equipment including a 16"
    telescope, CCD detector, and image processing software. Our online
    archive of data is now available 24/7. The telescope will be opening to
    our onsite users in May, and on select nights to the Internet at large
    in June.
    We have designed this site so you don't need a huge monitor or a
    supercomputer to use it. All pages are viewable on screens running at
    800x600 resolution or higher. To use LOPARC, you'll need a Java-enabled
    browser with the Java 1.4 plug-in installed. If you don't have the
    plug-in, you'll be prompted to download it the first time you attempt to
    connect. This is an admittedly large (9 MB) but one-time-only download.
    This site works correctly under Internet Explorer version 5 or higher.
    If you use Netscape, you must be running version 6 or higher, and
    display or applet behavior anomalies may occur.
    If at any time you can't connect to our server, simply try again later.
    We do experience several power outages each year, particularly during
    Flagstaff's summer thunderstorm season. Our server is fully protected
    and backed up, and can be quickly brought back on line, but any active
    user sessions will be lost. Thanks for your patience during these
    inevitable downtimes.
    Your questions, comments, suggestions, and bug reports about this site
    are always welcome. On behalf of the LOPARC development team, thanks
    for signing up!
    Jeffrey Hall
    Assistant Research Scientist
    Associate Director, Education and Special Programs
    Lowell Observatory
    Flagstaff, Arizona

    Hi Mike,
    I see this in your logs:
    Java(TM) Plug-in: Version 1.4.2_01
    Using JRE version 1.4.2_01 Java HotSpot(TM) Client VM
    User home directory = C:\WINDOWS
    Proxy Configuration: Manual Configuration
    Proxy: http=proxy,https=proxy,ftp=proxy,gopher=proxy
    Proxy Overrides:
    I just helped my Dad set up his computer with a new
    cable modem, and had the situation where we couldn't
    access any secure Web sites. The cable folks had us
    disable the proxy. It looks like the error message is
    saying it can't find your proxy server, and the logs
    you posted say that you've decided to configure your
    proxy manually, rather than using the settings from
    IE (which is how mine is set up in the plugin
    control panel.)
    Could that be the problem?
    --Steve                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • SeaMonkey v2.0.4's Java applets doesn't work all the time.

    Hello. I use Mozilla's SeaMonkey v2.0.4 (using binary from mozilla.org) in Debian/Linux. I can get Java applets to work on https://eetime11.adp.com/c08e/logon but not on http://javatester.org, http://java.com/en/download/installed.jsp, and http://java.com/en/download/help/testvm.xml
    Java Plug-in 1.6.0_20
    Using JRE version 1.6.0_20-b02 Java HotSpot(TM) Client VM
    User home directory = /home/ant
    c: clear console window
    f: finalize objects on finalization queue
    g: garbage collect
    h: display this help message
    l: dump classloader list
    m: print memory usage
    o: trigger logging
    p: reload proxy configuration
    q: hide console
    r: reload policy configuration
    s: dump system and deployment properties
    t: dump thread list
    v: dump thread stack
    x: clear classloader cache
    0-5: set trace level to <n>
    load: class testvm2/Main.class not found.
    java.lang.ClassNotFoundException: testvm2.Main.class
         at sun.applet.AppletClassLoader.findClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at sun.applet.AppletClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at sun.applet.AppletClassLoader.loadCode(Unknown Source)
         at sun.applet.AppletPanel.createApplet(Unknown Source)
         at sun.plugin.AppletViewer.createApplet(Unknown Source)
         at sun.applet.AppletPanel.runLoader(Unknown Source)
         at sun.applet.AppletPanel.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    FYI on my setups:
    $ pwd
    /home/Programs/seamonkey2/plugins
    $ ls -all
    total 28
    drwxr-xr-x 2 ant ant 4096 2010-04-15 15:46 .
    drwxr-xr-x 15 ant ant 4096 2010-04-16 08:32 ..
    lrwxrwxrwx 1 root root 32 2009-11-27 17:19 libflashplayer.so -> /home/Programs/libflashplayer.so
    lrwxrwxrwx 1 root root 63 2010-04-15 15:46 libjavaplugin_oji.so -> /home/Programs/jre1.6.0_20/plugin/i386/ns7/libjavaplugin_oji.so
    -rwxr-xr-x 1 ant ant 15824 2009-10-17 09:30 libnullplugin.so
    $ ls -all /home/Programs/jre1.6.0_20/plugin/i386/ns7/libjavaplugin_oji.so
    -rwxr-xr-x 1 ant ant 137021 2010-04-12 14:39 /home/Programs/jre1.6.0_20/plugin/i386/ns7/libjavaplugin_oji.so
    Does anyone know why? Thank you in advance. :)
    Edited by: antdude on Apr 16, 2010 8:37 AM

    More poking around:
    $ java -version
    java version "1.6.0_18"
    OpenJDK Runtime Environment (IcedTea6 1.8pre) (6b18~pre2-1)
    OpenJDK Server VM (build 14.0-b16, mixed mode)
    # dpkg -l | grep ^ii |grep java
    ii ca-certificates-java 20091021 Common CA certificates (JKS keystore)
    ii java-common 0.35 Base of all Java packages
    ii libaccess-bridge-java 1.26.2-4 Java Access Bridge for GNOME
    ii libaccess-bridge-java-jni 1.26.2-4 Java Access Bridge for GNOME (jni bindings)
    ii libhsqldb-java 1.8.0.10-6 Java SQL database engine
    ii liblucene2-java 2.9.2+ds1-1 Full-text search engine library for Java(TM)
    ii libservlet2.4-java 5.0.30-12 Servlet 2.4 and JSP 2.0 Java library
    ii openoffice.org-java-common 1:3.2.0-4 full-featured office productivity suite -- arch-independent Java support files
    ii tzdata-java 2010h-1 time zone and daylight-saving time data for use by java runtimes
    # dpkg -l | grep ^ii |grep jre
    # locate bin/java
    /home/Programs/jre1.6.0_20/bin/java
    /home/Programs/jre1.6.0_20/bin/java_vm
    /home/Programs/jre1.6.0_20/bin/javaws
    /usr/bin/java
    /usr/bin/javaws
    /usr/lib/jvm/java-6-openjdk/bin/java
    /usr/lib/jvm/java-6-openjdk/bin/java-rmi.cgi
    /usr/lib/jvm/java-6-openjdk/bin/javaws
    /usr/lib/jvm/java-6-openjdk/jre/bin/java
    /usr/lib/jvm/java-6-openjdk/jre/bin/javaws
    /usr/lib/jvm/java-6-openjdk/jre/bin/javaws.real
    I tried to uninstall all the unneccesary Java packages, but still had some can't be removed because of other programs requiring it like OpenOffice:
    # apt-get remove openjdk-6-jre-headless
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer required:
    openoffice.org-filter-mobiledev ttf-sil-gentium ttf-sil-gentium-basic
    Use 'apt-get autoremove' to remove them.
    The following packages will be REMOVED:
    ca-certificates-java libaccess-bridge-java libaccess-bridge-java-jni libhsqldb-java liblucene2-java libservlet2.4-java
    openjdk-6-jre openjdk-6-jre-headless openjdk-6-jre-lib openoffice.org openoffice.org-base openoffice.org-officebean
    openoffice.org-report-builder-bin
    0 upgraded, 0 newly installed, 13 to remove and 125 not upgraded.
    After this operation, 114MB disk space will be freed.
    Do you want to continue [Y/n]? n
    Abort.
    # apt-get remove java-common
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer required:
    openoffice.org-filter-mobiledev ttf-sil-gentium ttf-sil-gentium-basic
    Use 'apt-get autoremove' to remove them.
    The following packages will be REMOVED:
    ca-certificates-java java-common libaccess-bridge-java libaccess-bridge-java-jni libhsqldb-java liblucene2-java
    libservlet2.4-java openjdk-6-jre openjdk-6-jre-headless openjdk-6-jre-lib openoffice.org openoffice.org-base
    openoffice.org-officebean openoffice.org-report-builder-bin
    0 upgraded, 0 newly installed, 14 to remove and 125 not upgraded.
    After this operation, 115MB disk space will be freed.
    Do you want to continue [Y/n]? n
    Abort.
    Any ideas? :(

  • Crashes when running Java Applets and trying to open Security System Preferences

    Browser crashes when trying to run Java Applets, I've tried 4 different browsers. This is the crash report.
    Process:         java [90472]
    Path:            /usr/bin/java
    Identifier:      com.apple.javajdk16.cmd
    Version:         1.0 (1.0)
    Code Type:       X86-64 (Native)
    Parent Process:  Google Chrome Helper EH [90460]
    Date/Time:       2012-02-17 15:04:44.693 -0500
    OS Version:      Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Interval Since Last Report:          9110 sec
    Crashes Since Last Report:           8
    Per-App Interval Since Last Report:  43908 sec
    Per-App Crashes Since Last Report:   8
    Anonymous UUID:                      DFA20D26-FD7E-4507-AAA9-EBF29199EC56
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
    Crashed Thread:  31  Java: Thread-11
    Application Specific Information:
    Java information:
    Exception type: Bus Error (0xa) at pc=00000000
    Java VM: Java HotSpot(TM) 64-Bit Server VM (20.4-b02-402 mixed mode macosx-amd64)
    Current thread (102a13000):  JavaThread "Thread-11" daemon [_thread_in_Java, id=607662080, stack(124283000,124383000)]
    Stack: [124283000,124383000]
    Java Threads: ( => current thread )
      126525000 JavaThread "Thread-26" daemon [_thread_blocked, id=878407680, stack(1344b7000,1345b7000)]
      126524000 JavaThread "Thread-25" daemon [_thread_in_native, id=877346816, stack(1343b4000,1344b4000)]
      102f20800 JavaThread "Thread-21" daemon [_thread_blocked, id=636690432, stack(125e32000,125f32000)]
      102b96000 JavaThread "Thread-20" daemon [_thread_in_native, id=550666240, stack(120ca8000,120d28000)]
      102b95000 JavaThread "Thread-19" daemon [_thread_blocked, id=632483840, stack(125a2f000,125b2f000)]
      1261e6000 JavaThread "Java Sound Event Dispatcher" daemon [_thread_blocked, id=591368192, stack(1232f9000,1233f9000)]
      10191b800 JavaThread "Thread-15" daemon [_thread_blocked, id=611905536, stack(12468f000,12478f000)]
      1029c7800 JavaThread "Thread-14" daemon [_thread_blocked, id=610844672, stack(12458c000,12468c000)]
      102b11000 JavaThread "Thread-13" daemon [_thread_blocked, id=609783808, stack(124489000,124589000)]
      101929000 JavaThread "Thread-12" daemon [_thread_blocked, id=608722944, stack(124386000,124486000)]
    =>102a13000 JavaThread "Thread-11" daemon [_thread_in_Java, id=607662080, stack(124283000,124383000)]
      1029d2000 JavaThread "Poller SunPKCS11-Darwin" daemon [_thread_blocked, id=541855744, stack(1203c1000,1204c1000)]
      101a43800 JavaThread "thread applet-Rs2Applet.class-1" [_thread_blocked, id=534294528, stack(11fc8b000,11fd8b000)]
      102a07800 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=527765504, stack(11f651000,11f751000)]
      102878000 JavaThread "JVM[id=0]-Heartbeat" daemon [_thread_blocked, id=490639360, stack(11d2e9000,11d3e9000)]
      101943000 JavaThread "AWT-EventQueue-2" [_thread_blocked, id=494882816, stack(11d6f5000,11d7f5000)]
      102933000 JavaThread "Applet 1 LiveConnect Worker Thread" [_thread_blocked, id=466014208, stack(11bb6d000,11bc6d000)]
      101933800 JavaThread "Browser Side Object Cleanup Thread" [_thread_blocked, id=191471616, stack(10b59a000,10b69a000)]
      101944000 JavaThread "AWT-EventQueue-0" [_thread_blocked, id=493821952, stack(11d5f2000,11d6f2000)]
      1029ae800 JavaThread "CacheCleanUpThread" daemon [_thread_blocked, id=492761088, stack(11d4ef000,11d5ef000)]
      102a04800 JavaThread "CacheMemoryCleanUpThread" daemon [_thread_blocked, id=491700224, stack(11d3ec000,11d4ec000)]
      102b2e000 JavaThread "SysExecutionTheadCreator" daemon [_thread_blocked, id=489578496, stack(11d1e6000,11d2e6000)]
      1018e6800 JavaThread "Java Plug-In Pipe Worker Thread (Client-Side)" daemon [_thread_in_native, id=464945152, stack(11ba68000,11bb68000)]
      101a46800 JavaThread "AWT-Shutdown" [_thread_blocked, id=463884288, stack(11b965000,11ba65000)]
      101934800 JavaThread "AWT-AppKit" daemon [_thread_in_native, id=1896107200, stack(7fff5f400000,7fff5fc00000)]
      101933000 JavaThread "Timer-0" [_thread_blocked, id=190410752, stack(10b497000,10b597000)]
      1018cd000 JavaThread "traceMsgQueueThread" daemon [_thread_blocked, id=188145664, stack(10b26e000,10b36e000)]
      102853000 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=172019712, stack(10a30d000,10a40d000)]
      102852800 JavaThread "C2 CompilerThread1" daemon [_thread_blocked, id=170958848, stack(10a20a000,10a30a000)]
      102851800 JavaThread "C2 CompilerThread0" daemon [_thread_blocked, id=169897984, stack(10a107000,10a207000)]
      102851000 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=168837120, stack(10a004000,10a104000)]
      102850000 JavaThread "Surrogate Locker Thread (Concurrent GC)" daemon [_thread_blocked, id=167776256, stack(109f01000,10a001000)]
      102842800 JavaThread "Finalizer" daemon [_thread_blocked, id=162287616, stack(1099c5000,109ac5000)]
      102841800 JavaThread "Reference Handler" daemon [_thread_blocked, id=161226752, stack(1098c2000,1099c2000)]
      101801000 JavaThread "main" [_thread_blocked, id=5246976, stack(100401000,100501000)]
    Other Threads:
      10283d000 VMThread [stack: 1097bf000,1098bf000] [id=160165888]
      10285d000 WatcherThread [stack: 10a410000,10a510000] [id=173080576]
    VM state:not at safepoint (normal execution)
    VM Mutex/Monitor currently owned by a thread: None
    Heap
    par new generation   total 19136K, used 9943K [7eae00000, 7ec2c0000, 7ece00000)
      eden space 17024K,  46% used [7eae00000, 7eb5a5ec8, 7ebea0000)
      from space 2112K, 100% used [7ec0b0000, 7ec2c0000, 7ec2c0000)
      to   space 2112K,   0% used [7ebea0000, 7ebea0000, 7ec0b0000)
    concurrent mark-sweep generation total 144152K, used 110056K [7ece00000, 7f5ac6000, 7fae00000)
    concurrent-mark-sweep perm gen total 62268K, used 37524K [7fae00000, 7feacf000, 800000000)
    Code Cache  [103801000, 104192000, 106801000)
    total_blobs=2217 nmethods=1445 adapters=734 free_code_cache=40529280 largest_free_block=47360
    Virtual Machine Arguments:
    JVM Args: -D__jvm_launched=1329508711033330 -Xbootclasspath/a:/System/Library/Frameworks/JavaVM.framework/Resources/Deploy. bundle/Contents/Resources/Java/deploy.jar:/System/Library/Frameworks/JavaVM.fram ework/Resources/Deploy.bundle/Contents/Resources/Java/javaws.jar:/System/Library /Frameworks/JavaVM.framework/Resources/Deploy.bundle/Contents/Resources/Java/plu gin.jar -Djava.applet.host=world8.runescape.com -Dapple.awt.UIElement=true -Dsun.awt.warmup=true -Xmx256m -Xss1m -Xincgc -XX:+UseConcMarkSweepGC -Dsun.java2d.noddraw=true
    Java Command: sun.plugin2.main.client.PluginMain write_pipe_name=/var/folders/Aa/Aa4dzX7xHJmbzy55DpvyiE+++TI/-Tmp-/.java.deploy. 90460.994108354874315847
    Launcher Type: SUN_STANDARD
    Physical Memory: Page Size = 4k, Total = 3840M, Free = 774M
    Thread 0:  Dispatch queue: com.apple.main-thread
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   com.apple.CoreFoundation                0x00007fff864f2902 __CFRunLoopRun + 1698
    3   com.apple.CoreFoundation                0x00007fff864f1d8f CFRunLoopRunSpecific + 575
    4   com.apple.HIToolbox                     0x00007fff857827ee RunCurrentEventLoopInMode + 333
    5   com.apple.HIToolbox                     0x00007fff857825f3 ReceiveNextEventCommon + 310
    6   com.apple.HIToolbox                     0x00007fff857824ac BlockUntilNextEventMatchingListInMode + 59
    7   com.apple.AppKit                        0x00007fff85ae6eb2 _DPSNextEvent + 708
    8   com.apple.AppKit                        0x00007fff85ae6801 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
    9   libawt.jnilib                           0x000000010b6f1f0d -[NSApplicationAWT nextEventMatchingMask:untilDate:inMode:dequeue:] + 124
    10  com.apple.AppKit                        0x00007fff85aac68f -[NSApplication run] + 395
    11  libawt.jnilib                           0x000000010b69e19c +[AWTStarter startAWT:] + 1495
    12  libawt.jnilib                           0x000000010b69db16 -[CPerformer perform] + 93
    13  com.apple.Foundation                    0x00007fff8357745f __NSThreadPerformPerform + 219
    14  com.apple.CoreFoundation                0x00007fff864f43d1 __CFRunLoopDoSources0 + 1361
    15  com.apple.CoreFoundation                0x00007fff864f25c9 __CFRunLoopRun + 873
    16  com.apple.CoreFoundation                0x00007fff864f1d8f CFRunLoopRunSpecific + 575
    17  java                                    0x000000010000483f 0x100000000 + 18495
    18  java                                    0x0000000100004296 0x100000000 + 17046
    19  java                                    0x0000000100001a94 0x100000000 + 6804
    Thread 1:
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103811d6e 0 + 4353760622
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x00000001038069b3 0 + 4353714611
    11  ???                                     0x00000001038069b3 0 + 4353714611
    12  ???                                     0x000000010380685a 0 + 4353714266
    13  ???                                     0x000000010380685a 0 + 4353714266
    14  ???                                     0x0000000103801438 0 + 4353692728
    15  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    16  libclient64.dylib                       0x00000001010a4f16 JVM_Lseek + 192613
    17  libclient64.dylib                       0x00000001010c8e0e JVM_FindLoadedClass + 3186
    18  libclient64.dylib                       0x00000001010c8cb6 JVM_FindLoadedClass + 2842
    19  java                                    0x0000000100002cef 0x100000000 + 11503
    20  java                                    0x000000010000323c 0x100000000 + 12860
    21  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    22  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 2:  Java: Exception Handler Thread
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libSystem.B.dylib                       0x00007fff8864aa17 mach_msg_server + 468
    3   libclient64.dylib                       0x000000010100e7cb jio_snprintf + 41425
    4   libclient64.dylib                       0x000000010100e683 jio_snprintf + 41097
    5   libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    6   libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    7   libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 3:  Java: Gang worker#0 (Parallel GC Threads)
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x000000010100d722 jio_snprintf + 37160
    5   libclient64.dylib                       0x000000010100d2fd jio_snprintf + 36099
    6   libclient64.dylib                       0x000000010100d1a3 jio_snprintf + 35753
    7   libclient64.dylib                       0x0000000101025fa4 jio_vsnprintf + 312
    8   libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    9   libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    10  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 4:  Java: Gang worker#1 (Parallel GC Threads)
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x000000010100d722 jio_snprintf + 37160
    5   libclient64.dylib                       0x000000010100d2fd jio_snprintf + 36099
    6   libclient64.dylib                       0x000000010100d1a3 jio_snprintf + 35753
    7   libclient64.dylib                       0x0000000101025fa4 jio_vsnprintf + 312
    8   libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    9   libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    10  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 5:  Java: Concurrent Mark-Sweep GC Thread
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x000000010100d722 jio_snprintf + 37160
    5   libclient64.dylib                       0x000000010100d2fd jio_snprintf + 36099
    6   libclient64.dylib                       0x000000010100d1a3 jio_snprintf + 35753
    7   libclient64.dylib                       0x0000000101302097 JVM_Timeout + 883428
    8   libclient64.dylib                       0x000000010122803c JVM_Yield + 40397
    9   libclient64.dylib                       0x000000010122783d JVM_Yield + 38350
    10  libclient64.dylib                       0x00000001012277af JVM_Yield + 38208
    11  libclient64.dylib                       0x000000010122764e JVM_Yield + 37855
    12  libclient64.dylib                       0x00000001012273eb JVM_Yield + 37244
    13  libclient64.dylib                       0x000000010121edca JVM_Yield + 2907
    14  libclient64.dylib                       0x000000010102c3dc jio_vsnprintf + 25968
    15  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    16  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    17  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 6:  Java: VM Thread
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d995 jio_snprintf + 37787
    3   libclient64.dylib                       0x000000010102c54a jio_vsnprintf + 26334
    4   libclient64.dylib                       0x000000010100d2fd jio_snprintf + 36099
    5   libclient64.dylib                       0x000000010100d1a3 jio_snprintf + 35753
    6   libclient64.dylib                       0x00000001010a3f8f JVM_Lseek + 188638
    7   libclient64.dylib                       0x00000001010a3cdf JVM_Lseek + 187950
    8   libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    9   libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    10  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 7:  Java: Reference Handler
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103a3d848 0 + 4356036680
    9   ???                                     0x00000001039622d4 0 + 4355138260
    10  ???                                     0x0000000103801438 0 + 4353692728
    11  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    12  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    13  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    14  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    15  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    16  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    17  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    18  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    19  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 8:  Java: Finalizer
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103a3d848 0 + 4356036680
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x00000001038069b3 0 + 4353714611
    11  ???                                     0x00000001038069b3 0 + 4353714611
    12  ???                                     0x0000000103801438 0 + 4353692728
    13  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    14  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    15  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    16  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    17  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    18  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    19  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    20  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    21  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 9:  Dispatch queue: com.apple.libdispatch-manager
    0   libSystem.B.dylib                       0x00007fff885e6c0a kevent + 10
    1   libSystem.B.dylib                       0x00007fff885e8add _dispatch_mgr_invoke + 154
    2   libSystem.B.dylib                       0x00007fff885e87b4 _dispatch_queue_invoke + 185
    3   libSystem.B.dylib                       0x00007fff885e82de _dispatch_worker_thread2 + 252
    4   libSystem.B.dylib                       0x00007fff885e7c08 _pthread_wqthread + 353
    5   libSystem.B.dylib                       0x00007fff885e7aa5 start_wqthread + 13
    Thread 10:  Java: Surrogate Locker Thread (Concurrent GC)
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x000000010100d722 jio_snprintf + 37160
    5   libclient64.dylib                       0x000000010100d2fd jio_snprintf + 36099
    6   libclient64.dylib                       0x000000010100d10a jio_snprintf + 35600
    7   libclient64.dylib                       0x00000001010c2261 JVM_IsPrimitiveClass + 6521
    8   libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    9   libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    10  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    11  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    12  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 11:  Java: Signal Dispatcher
    0   libSystem.B.dylib                       0x00007fff885cddb6 semaphore_wait_trap + 10
    1   libclient64.dylib                       0x00000001010c2aa3 JVM_IsPrimitiveClass + 8635
    2   libclient64.dylib                       0x00000001010c252a JVM_IsPrimitiveClass + 7234
    3   libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    4   libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    5   libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    6   libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    7   libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 12:  Java: C2 CompilerThread0
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x000000010100d722 jio_snprintf + 37160
    5   libclient64.dylib                       0x000000010100d2fd jio_snprintf + 36099
    6   libclient64.dylib                       0x000000010100d10a jio_snprintf + 35600
    7   libclient64.dylib                       0x00000001010c9319 JVM_Write + 346
    8   libclient64.dylib                       0x00000001010c3913 JVM_IsPrimitiveClass + 12331
    9   libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    10  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    11  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    12  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    13  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 13:  Java: C2 CompilerThread1
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x000000010100d722 jio_snprintf + 37160
    5   libclient64.dylib                       0x000000010100d2fd jio_snprintf + 36099
    6   libclient64.dylib                       0x000000010100d10a jio_snprintf + 35600
    7   libclient64.dylib                       0x00000001010c9319 JVM_Write + 346
    8   libclient64.dylib                       0x00000001010c3913 JVM_IsPrimitiveClass + 12331
    9   libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    10  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    11  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    12  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    13  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 14:  Java: Low Memory Detector
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x000000010100d722 jio_snprintf + 37160
    5   libclient64.dylib                       0x000000010100d2fd jio_snprintf + 36099
    6   libclient64.dylib                       0x000000010100d1a3 jio_snprintf + 35753
    7   libclient64.dylib                       0x00000001010c5318 JVM_IsPrimitiveClass + 18992
    8   libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    9   libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    10  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    11  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    12  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 15:  Java: VM Periodic Task Thread
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d995 jio_snprintf + 37787
    3   libclient64.dylib                       0x00000001011afc26 JVM_GetClassInterfaces + 11348
    4   libclient64.dylib                       0x00000001010c73a7 JVM_IsPrimitiveClass + 27327
    5   libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    6   libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    7   libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 16:  Java: traceMsgQueueThread
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103811d6e 0 + 4353760622
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x000000010380685a 0 + 4353714266
    11  ???                                     0x0000000103806d34 0 + 4353715508
    12  ???                                     0x0000000103801438 0 + 4353692728
    13  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    14  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    15  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    16  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    17  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    18  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    19  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    20  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    21  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 17:  Java: Timer-0
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103811d6e 0 + 4353760622
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x000000010380685a 0 + 4353714266
    11  ???                                     0x000000010380685a 0 + 4353714266
    12  ???                                     0x0000000103801438 0 + 4353692728
    13  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    14  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    15  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    16  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    17  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    18  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    19  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    20  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    21  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 18:  Java: AWT-Shutdown
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103811d6e 0 + 4353760622
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x000000010380685a 0 + 4353714266
    11  ???                                     0x0000000103806d34 0 + 4353715508
    12  ???                                     0x0000000103801438 0 + 4353692728
    13  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    14  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    15  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    16  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    17  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    18  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    19  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    20  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    21  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 19:  Java: Java Plug-In Pipe Worker Thread (Client-Side)
    0   libSystem.B.dylib                       0x00007fff885d8466 read + 10
    1   libdeploy.jnilib                        0x0000000109d4d5d9 Java_com_sun_deploy_net_socket_UnixSocketImpl_unStreamSocketRead + 140
    2   ???                                     0x0000000103811d6e 0 + 4353760622
    3   ???                                     0x000000010380696e 0 + 4353714542
    4   ???                                     0x000000010380696e 0 + 4353714542
    5   ???                                     0x000000010380696e 0 + 4353714542
    6   ???                                     0x000000010380696e 0 + 4353714542
    7   ???                                     0x000000010386d2b4 0 + 4354134708
    8   ???                                     0xfda21644ff67b8d7 0 + 18276194723421468887
    Thread 20:  Java: SysExecutionTheadCreator
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103811d6e 0 + 4353760622
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x000000010380685a 0 + 4353714266
    11  ???                                     0x0000000103801438 0 + 4353692728
    12  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    13  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    14  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    15  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    16  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    17  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    18  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    19  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    20  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 21:  Java: CacheMemoryCleanUpThread
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103811d6e 0 + 4353760622
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x00000001038069b3 0 + 4353714611
    11  ???                                     0x00000001038069b3 0 + 4353714611
    12  ???                                     0x0000000103801438 0 + 4353692728
    13  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    14  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    15  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    16  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    17  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    18  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    19  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    20  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    21  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 22:  Java: CacheCleanUpThread
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103811d6e 0 + 4353760622
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x000000010380685a 0 + 4353714266
    11  ???                                     0x0000000103801438 0 + 4353692728
    12  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    13  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    14  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    15  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    16  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    17  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    18  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    19  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    20  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 23:  Java: AWT-EventQueue-0
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103a3d848 0 + 4356036680
    9   ???                                     0x0000000103aaac60 0 + 4356484192
    Thread 24:  Java: Browser Side Object Cleanup Thread
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103811d6e 0 + 4353760622
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x00000001038069b3 0 + 4353714611
    11  ???                                     0x00000001038069b3 0 + 4353714611
    12  ???                                     0x0000000103801438 0 + 4353692728
    13  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    14  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    15  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    16  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    17  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    18  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    19  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    20  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    21  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 25:  Java: Applet 1 LiveConnect Worker Thread
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103811d6e 0 + 4353760622
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x000000010380685a 0 + 4353714266
    11  ???                                     0x0000000103806d34 0 + 4353715508
    12  ???                                     0x0000000103801438 0 + 4353692728
    13  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    14  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    15  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    16  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    17  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    18  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    19  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    20  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    21  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 26:  Java: AWT-EventQueue-2
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d903 jio_snprintf + 37641
    3   libclient64.dylib                       0x000000010100d7c3 jio_snprintf + 37321
    4   libclient64.dylib                       0x00000001010b2597 JVM_MonitorWait + 4001
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103a3d848 0 + 4356036680
    9   ???                                     0x0000000103aaac60 0 + 4356484192
    Thread 27:  Java: JVM[id=0]-Heartbeat
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_msg + 59
    2   libclient64.dylib                       0x000000010100d995 jio_snprintf + 37787
    3   libclient64.dylib                       0x000000010102c54a jio_vsnprintf + 26334
    4   libclient64.dylib                       0x00000001010b25a1 JVM_MonitorWait + 4011
    5   libclient64.dylib                       0x00000001010b1a24 JVM_MonitorWait + 1070
    6   libclient64.dylib                       0x00000001010b1690 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib                     0x0000000100093b9b JVM_MonitorWait + 59
    8   ???                                     0x0000000103a3d848 0 + 4356036680
    9   ???                                     0x000000010380685a 0 + 4353714266
    10  ???                                     0x00000001038069b3 0 + 4353714611
    11  ???                                     0x00000001038069b3 0 + 4353714611
    12  ???                                     0x0000000103801438 0 + 4353692728
    13  libclient64.dylib                       0x00000001010a5152 JVM_Lseek + 193185
    14  libclient64.dylib                       0x00000001010b11dc JVM_StartThread + 2565
    15  libclient64.dylib                       0x00000001010b10d2 JVM_StartThread + 2299
    16  libclient64.dylib                       0x00000001010b1072 JVM_StartThread + 2203
    17  libclient64.dylib                       0x00000001010b0f14 JVM_StartThread + 1853
    18  libclient64.dylib                       0x00000001010b0d29 JVM_StartThread + 1362
    19  libclient64.dylib                       0x000000010100d264 jio_snprintf + 35946
    20  libSystem.B.dylib                       0x00007fff88606fd6 _pthread_start + 331
    21  libSystem.B.dylib                       0x00007fff88606e89 thread_start + 13
    Thread 28:  Java: Java2D Disposer
    0   libSystem.B.dylib                       0x00007fff885cdd7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff885ce3ed mach_m

    Did you get this fixed? I have had this error everytime I try to access my bank, inventory, and ither things. Please help.

  • Socket communication failure between Java applet and C++ application

    I have a java applet that connects to a C++ application via Java's ServerSocket and Socket objects. THe C++ application is using the Winsock 2 API. The applet and application are running on an NT workstation (SP 6) and using IE (5.5) For a very simple C++ test applications the communictions work fine. Once more code gets added to the C++ application the portion of the socket that C++ listens to seems to close. Upon performing a recv call the return value is a zero. Microsoft insists this is a sign the Java side has shut down the socket. The Java applet can still receive messages from the C++ app but C++ cannot receive responses from the Java side. Java throws no exceptions and an explicit check of the socket shows no errors. Again, what puzzles me is that it works for simple C++ applications. Are there any known conflicts between Java and C++ in this regard?
    I have inlcuded the basic java code segments below.
    / run Method.
      * This method is called by the Thread.start() method. This
      * method is required for the implementation of the Runnable interface
      * This method sets up the server side socket communication and
      * contiuously loops looking for requests from a external
      * socket.
      * @author Chris Duke
      public void run(){
         // create socket connections
         boolean success = false;
         try {
             cServerSocket = new ServerSocket(cPortID);
             System.out.println("Waiting for client to connect...");
             cClientSocket = cServerSocket.accept();
             System.out.println("Client connected");
             // Create a stream to read from the client
             cInStream = new BufferedReader(new InputStreamReader(
               cClientSocket.getInputStream()));
             // Create a stream to write to the client       
             cOutStream = new PrintWriter(
               cClientSocket.getOutputStream(), true);
             success = true;
         }catch (IOException e) {
             System.out.println("CommSocket:Run - Socket Exception(1) " + e);
             success = false;
         // if the socket was successfully created, keep the thread running
         while (success){
             try{
                // check socket to see if it is still available for reading
                if (cInStream != null && cInStream.ready()){
                    // check for an incoming message
                    String message = ReceiveMessage();
                    // Send message to listeners
                    Event(message);
                if (cInStream == null){
                    success = false;
                    System.out.println("CommSocket:Run - shutdown");
             }catch (IOException e){
                System.out.println("CommSocket:Run - Socket not ready exception");
                break;
    // SendMessage method -
      *  Sends a text message to a connected listener through port specified by portID
      * @author Chris Duke
      * @param  String message - This will be the message sent out through the server
      * socket's port specified by portID.
       public void SendMessage(String message){
          cOutStream.println(message);
          if (cOutStream.checkError() == true)
            System.out.println("SendMessage : Flush = Error");
          else{
            System.out.println("SendMessage : Flush - No Error");
       }

    a very simple C++ test applications the communictions work fine. Once more code gets added to the C++ application the portion of the socket that C++ listens to seems to close.
    This quite strongly implicates the extra code in the C++ App. The firstly thing I would try would be telnet. Try connecting to both versions of the C++ Application and manually reproducing a proper exchange.
    a recv call the return value is a zero. Microsoft insists this is a sign the Java side has shut down the socket.
    A correct implementation of recv should return the number of bytes received, or -1 for an error. A zero return indicates no bytes received not a socket closed/error. This sounds like FUD to me.
    Are there any known conflicts between Java and C++ in this regard?
    I can see no obvious faults, though the code is incomplete, I don't think it's an sockets implementation issue, at either end, it sounds more likely to be a protocol/handshaking bug in the C++ App.

Maybe you are looking for

  • Connect is not working on Hyper-V Manager on Windows 8.1 ( vmconnect does not work )

    Hi all, I have been running Windows 8.1 and in Hyper-V Manager, i can see 2 VM ( 1 Linux-Ubuntu , 1 Win 7 ) for couple of months. Few days ago as usual i wanted to connect one of them while they were running but it did not work. I tried actions below

  • How can i recover files from iphone 3gs 4.2.1 while in recovery mode ?

    I had tried already multiple ways to get it off recovery mode but nothing works...it went into recovery mode while it was charging :( .. I REALLY DON'T WANT TO LOOSE MY DATA because just a couple of weeks ago my dad deleted EVERYTHING from our comput

  • MacBook Pro Screen suddenly turns blue

    I have a MacBook Pro that I've had for about two years now.  Lately, I will be surfing the net (generally use Firefox), and my screen suddenly turns blue.  If I close the lid, reopen, and push the power button, it fires back up.  Anyone have any idea

  • Taking a snap shot of an entire web page

    anyone know how to take a screen grab of an entire web page - i cant scroll down to take it?

  • OWB Demo Import Error

    Hi, I am trying to run the OWB 92 Demo available from OTN. I am getting an error when I import the mdl file: Import started at 12/29/2004 3:00:37 PM * Import for OWB Release: 10.1.0.2.0 Version: 10.1.0.1.0 * User: owb92 Connect String: (DESCRIPTION=(