Native threads on solaris 2.6

Hi everyone,
I was wondering if anyone had any problems using WLS 4.5.1 with weblogic's
oracle pool driver with a JDK1.2.2 vm running with native threads. We had
been running with green threads and we want to consider using native threads
for performance reasons. Is native threads in Solaris supported?
Thanks!
Gary Mui
[email protected]

g> I was wondering if anyone had any problems using WLS 4.5.1 with
g> weblogic's oracle pool driver with a JDK1.2.2 vm running with
g> native threads.
Provided you're running a recent WLS service pack, you should be in
fine shape.
     <b
Let us pray:
What a Great System.
Please Do Not Crash.
^G^IP@P6

Similar Messages

  • App crash when using JAVA callbacks from native threads in solaris

    Hi all,
    Sorry for putting the thread here. I did use the native methods forum, I wasnt lucky. I Hope more people would look into this forum, which brings me here.
    I have a solaris application which crashes when I try to callback the JAVA methods and variables from the native code. The description of the problem is below
    Written a native library, the library is multithreaded (i.e) I create a thread using pthread_create() in the native code which performs the operation of calling a JAVA method from the native code. The routine of calling the JAVA method works perfectly elsewhere outside the new thread.
    There are two scenarios I've tested it in
    1. I created a thread (say X) from the main thread (say Y) and made the y to wait until the X is complete using the pthread_join(). The JAVA callbacks works fine when called from Y but the app crashes if done from X.
    2. Did not make the Y to wait until the X is complete, hoping that both will run paralelly and even the the App crashes.
    And to be precise the Y is the thread where the native method is called from JAVA.
    I have tested for any memory leaks or stack corruption by removing the JAVA callbacks and bulding a executable and using purify, the report doesnot hint any such occurances.
    The linker options used for building the shared library is as follows
    ${GPP} ${INC} -G ${LIB} -mt -g -lCstd -lCrun -lpthread ${OBJS} -o <lib-name>
    I wonder if we can create threads in the native code when using JAVA callbacks and even if we can whether it would be appropiate to use the callbacks with in the threads
    Looking forward for any help.
    Regards,
    Vamsi

    Guys... can't any one help me with this problem :(

  • Nativ threads

    Hi,
    Using the version solaris 8 java 1.2.2 , the threads are native so not
    controlled by the user. Having 2 threads wich interfere each others because they share the same data, i have a critical section. How can i protect my data ? Is there semaphore in Java ? Any idea ?
    Thanks in advance...
    Olivier

    Ok, here a exemple of code,
    ----with green thread it works only if T1 is run before T2 (normal, you will say me)
    ----with nativ thread on solaris, it works only if i run T1 before T2, I understand that T2 has to call notify method, after that T1 calls the wait method, how to prevent the reverse to happen, it cause a thread to block ( i think this is call a dead lock). we don't know how the system will switch beetween T1 and T2,perhaps it works by hasards and one time it will block.
    Thanks a lot
    PS: I know how to do it with a flag and the Thread.wait() method, but i am looking for a code that is not ugly.
    Also java is supposed to be portable, or that show java is NOT. How to make it protable
    //the purpose of the test prog is to push on a stack (in T2 thread) and
    //after to pop the stack (in T1 thread);
    public static void main (String[] a) {
             Block aBlock = new Block();
             System.out.println ("Main thread starts executing.");
             try {
                System.out.println ("Initial value of stack top = " + aBlock.getTopValue() + ".");
                 catch (BlockException e) {
                   System.out.println("error : " + e.getMessage());
             System.out.println ("Main thread will now fork two threads.");
             AcquireBlock t1 = new AcquireBlock (aBlock);
             ReleaseBlock t2 = new ReleaseBlock (aBlock);
             t2.start ();                   // RB added to ready queue
             t1.start ();                   // AB added to ready queue
             try {                          // wait for termination of AB & RB
                t1.join ();
                t2.join ();
                 catch (InterruptedException e) {
             System.out.println ("System terminates normally.");
             try {
                System.out.println ("Final value of stack top = " + aBlock.getTopValue() + ".");
                 catch (BlockException e) {
    class AcquireBlock extends Thread {//T1
          private Block aBlock;
           public AcquireBlock(Block aBlock) {
             this.aBlock = aBlock;
           public void run () {
             System.out.println ("AcquireBlock thread starts executing.");
             try {
                synchronized(aBlock) {
                   try {
                      aBlock.wait();
                       catch (InterruptedException e) {}
                   aBlock.pop();
                 catch (BlockException e) {
                   System.out.println("error : " + e.getMessage());
             System.out.println ("AcquireBlock thread terminates.");
    class ReleaseBlock extends Thread {// T2
          private Block aBlock;
           public ReleaseBlock (Block aBlock) {
             this.aBlock = aBlock;
           public void run () {
             System.out.println ("ReleaseBlock thread starts executing.");
             try {
                synchronized(aBlock) {
                   aBlock.push('e');
                   try {
                      aBlock.notify();
                       catch (IllegalMonitorStateException e) {}
                 catch (BlockException e) {
                   System.out.println("error : " + e.getMessage());
             System.out.println ("ReleaseBlock thread terminates.");
    }

  • Problem with native ldapsearch in Solaris 10

    Hi all,
    someone could tell me please why native ldapsearch in Solaris 10 do not work with SSL connection when same command comes with Sun Directory Server 5.2 works perfectly ?
    With native ldapsearch in Solaris 10, I get the error message "Can't contact LDAP server":
    # /bin/ldapsearch -v -h ldapserver -p 636 -Z -P /var/ldap -b dc=exemple,dc=fr -s base objectclass=\*
    ldap_init( ldapserver, 636 )
    filter pattern: objectclass=*
    returning: ALL
    filter is: (objectclass=*)
    ldap_search: Can't contact LDAP server
    When, on the same host, on which Directory server is installed, there's no problem:
    # /var/opt/mps/serverroot/shared/bin/ldapsearch -v -h ldapserver -p 636 -Z -P /var/ldap -b dc=exemple,dc=fr -s base objectclass=\*
    ldap_init( exemple, 636 )
    ldaptool_getcertpath -- /var/opt/mps/serverroot/alias
    ldaptool_getkeypath -- /var/opt/mps/serverroot/alias
    ldaptool_getdonglefilename -- (null)
    filter pattern: objectclass=*
    returning: ALL
    filter is: (objectclass=*)
    version: 1
    dn: dc=exemple,dc=fr
    nisDomain: exemple.fr
    objectClass: top
    objectClass: domain
    objectClass: nisDomainObject
    1 matches
    What can I do to bind to ldap server with SSL connection from an ordinary work station?
    Thank you in advance.
    Dra

    Hi :
    "The /usr/bin/ldapsearch is an old version that does not support the "-Z" and "-P" flags to test SSL connection on port 636, use the ldapsearch command from SUN DS5.0/5.1 that comes bundled with Solaris9 and usually installed at /usr/iplanet/ds5 (DS5.0/5.1) or /var/Sun/mps (DS5.1/5.2) or /var/opt/mps/serverroot (DS5.2)"
    Source : http://forums.sun.com/thread.jspa?threadID=5089467
    Hope this can help,
    Regards,
    Groucho_fr

  • WS 6.1SP5 gives error "unable to create native threads"

    Hi All,
    We are using AM7.0 on Sun Java Web Server 6.1 SP5. This is running on T2000 with 8 GB RAM on Solaris 10. We have implemented all the recommendations given by amtune script except Stack Size (-Xss128K). amtune recommends Stack Size of 128K. But our Web Server doesn't run with 128K. We had to bump it up to 192K.
    After some time in our load test, we get following error in our logs:
    ERROR: ConsoleServletBase.onUncaughtException
    com.iplanet.jato.NavigationException: Exception encountered during forward
    Root cause = [java.lang.OutOfMemoryError: unable to create new native thread]
    at com.iplanet.jato.view.ViewBeanBase.forward(ViewBeanBase.java:380)
    at com.iplanet.jato.view.ViewBeanBase.forwardTo(ViewBeanBase.java:261)
    at com.sun.identity.console.base.AMViewBeanBase.forwardTo(AMViewBeanBase.java:135)
    at com.sun.identity.console.base.AMAdminFrameViewBean.forwardTo(AMAdminFrameViewBe an.java:111)
    at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase. java:981)
    at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.j ava:615)
    at com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.java:459)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:787)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFil terChain.java:247)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain .java:193)
    at com.sun.mobile.filter.AMLController.doFilter(AMLController.java:163)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFil terChain.java:213)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain .java:193)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java: 280)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java: 212)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:209)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
    at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java: 161)
    at com.iplanet.ias.web.WebContainer.service(WebContainer.java:580)
    Root cause:
    java.lang.OutOfMemoryError: unable to create new native thread
    at java.lang.Thread.start0(Native Method)
    at java.lang.Thread.start(Thread.java:574)
    at netscape.ldap.LDAPConnSetupMgr.openConnection(LDAPConnSetupMgr.java:212)
    at netscape.ldap.LDAPConnThread.connect(LDAPConnThread.java:109)
    at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:1075)
    at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:946)
    at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:858)
    Does anybody knows what this error is and how to tackle this problem ?
    Thanks in advance,
    Vivek

    Hi Sultal,
    Thanks for the response. I will try reducing the ms and mx options. BTW, following are my WS' JVM settings:
    <JAVA javahome="/usr/jdk/entsys-j2se" serverclasspath="/opt/SUNWwbsvr/bin/https/jar/webserv-rt.jar:${java.home}/lib/t
    ools.jar:/opt/SUNWwbsvr/bin/https/jar/webserv-ext.jar:/opt/SUNWwbsvr/bin/https/jar/webserv-jstl.jar:/usr/share/lib/ktse
    arch.jar" classpathsuffix="/opt/SUNWam/lib/xalan.jar:/opt/SUNWam/lib/xmlsec.jar:/opt/SUNWam/lib/xercesImpl.jar:/opt/SUN
    Wam/lib/dom.jar:/opt/SUNWam/lib/saaj-api.jar:/opt/SUNWam/lib/jaxrpc-api.jar:/opt/SUNWam/lib/jaxrpc-impl.jar:/opt/SUNWam
    /lib/jaxrpc-spi.jar:/opt/SUNWam/lib/saaj-impl.jar:/etc/opt/SUNWam/config:/opt/SUNWam/lib:/opt/SUNWam/locale:/usr/share/
    lib/mps/secv1/jss4.jar:/opt/SUNWam/lib/am_sdk.jar:/opt/SUNWam/lib/ldapjdk.jar:/opt/SUNWam/lib/am_services.jar:/opt/SUNW
    am/lib/am_sso_provider.jar:/opt/SUNWam/lib/swec.jar:/opt/SUNWam/lib/acmecrypt.jar:/opt/SUNWam/lib/iaik_ssl.jar:/opt/SUN
    Wam/lib/iaik_jce_full.jar:/opt/SUNWam/lib/mail.jar:/opt/SUNWam/lib/activation.jar:/opt/SUNWam/lib/am_logging.jar:/opt/S
    UNWam/lib/jaas.jar:/opt/SUNWam/lib/jax-qname.jar:/opt/SUNWam/lib/jaxm-api.jar:/opt/SUNWam/lib/jaxm-runtime.jar:/opt/SUN
    Wam/lib/jce1_2_1.jar:/opt/SUNWam/lib/jdk_logging.jar:/opt/SUNWam/lib/namespace.jar:/opt/SUNWam/lib/relaxngDatatype.jar:
    /opt/SUNWam/lib/xsdlib.jar:/opt/SUNWam/lib/jaxb-api.jar:/opt/SUNWam/lib/jaxb-impl.jar:/opt/SUNWam/lib/jaxb-libs.jar:/op
    t/SUNWam/lib/jaxb-xjc.jar:/opt/SUNWma/lib/wireless_rendering.jar:/opt/SUNWma/lib/wireless_rendering_util.jar:/opt/SUNWm
    a/lib/mobile_services.jar:/opt/SUNWma/lib/ccpp-1_0.jar:/opt/SUNWma/lib/ccpp-ri-1_0.jar:/opt/SUNWma/lib/jena-1.4.0.jar:/
    opt/SUNWma/lib/rdffilter.jar:/opt/SUNWma/lib/locale:/opt/SUNWam/lib/mobile_identity.jar:" envclasspathignored="true" na
    tivelibrarypathprefix="" debug="false" debugoptions="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n" dynamicr
    eloadinterval="-1">
    <JVMOPTIONS>-Ds1is.java.util.logging.config.class=com.sun.identity.log.s1is.LogConfigReader</JVMOPTIONS>
    <JVMOPTIONS>-DLOG_COMPATMODE=Off</JVMOPTIONS>
    <JVMOPTIONS>-Djava.security.auth.login.config=/opt/SUNWwbsvr/https-ndmseauqa01.ndc.nasa.gov/config/login.conf</JVMO
    PTIONS>
    <JVMOPTIONS>-Djava.protocol.handler.pkgs=com.iplanet.services.comm</JVMOPTIONS>
    <JVMOPTIONS>-Dcom.iplanet.am.serverMode=true</JVMOPTIONS>
    <JVMOPTIONS>-Djava.util.logging.manager=com.iplanet.ias.server.logging.ServerLogManager</JVMOPTIONS>
    <JVMOPTIONS>-Xmx3136M</JVMOPTIONS>
    <JVMOPTIONS>-Xms3136M</JVMOPTIONS>
    <JVMOPTIONS>-Xloggc:/opt/SUNWwbsvr/https-eauthws/logs/gc.log</JVMOPTIONS>
    <JVMOPTIONS>-server</JVMOPTIONS>
    <JVMOPTIONS>-Xss192K</JVMOPTIONS>
    <JVMOPTIONS>-XX:NewSize=392M</JVMOPTIONS>
    <JVMOPTIONS>-XX:MaxNewSize=392M</JVMOPTIONS>
    <JVMOPTIONS>-XX:PermSize=260M</JVMOPTIONS>
    <JVMOPTIONS>-XX:MaxPermSize=260M</JVMOPTIONS>
    <JVMOPTIONS>-XX:+DisableExplicitGC</JVMOPTIONS>
    <JVMOPTIONS>-XX:+UseParNewGC</JVMOPTIONS>
    <JVMOPTIONS>-XX:+CMSPermGenSweepingEnabled</JVMOPTIONS>
    <JVMOPTIONS>-XX:+CMSClassUnloadingEnabled</JVMOPTIONS>
    <JVMOPTIONS>-XX:+UseCMSCompactAtFullCollection</JVMOPTIONS>
    <JVMOPTIONS>-XX:CMSFullGCsBeforeCompaction=0</JVMOPTIONS>
    <JVMOPTIONS>-XX:SoftRefLRUPolicyMSPerMB=0</JVMOPTIONS>
    <JVMOPTIONS>-XX:+PrintClassHistogram</JVMOPTIONS>
    <JVMOPTIONS>-XX:+PrintGCDetails</JVMOPTIONS>
    <JVMOPTIONS>-XX:+PrintGCTimeStamps</JVMOPTIONS>
    <JVMOPTIONS>-XX:+UseConcMarkSweepGC</JVMOPTIONS>
    The error happens when the LWPs of the process goes beyond 500. In our load testing the server is getting hit 2000 requests per minute.
    I will reduce the mx and ms size, in the mean time, if you can take a look at any other thing that I need to do.
    One more thing, from where the native threads get allocated? (Heap/Perm/somewhere else)
    Regards,
    Vivek
    There is a certain limit for a number of threads that
    JVM can create. This limit depends on the OS and JVM
    options. You can try using XX:PermSize and
    -XX:MaxPermSize options as well as lowering -Xms and
    -Xmx options.

  • Native threads for NSAPI

    Hello
    I'm using the NSAPI plugin for iPlanet 4.1 on Solaris.
    The NSAPI is written in native code.
    Do I need to tune the iPlanet parameters that specify the native thread pool
    of iPlanet in order to optimize its performance?
    Thanks,
    Alex

    g> I was wondering if anyone had any problems using WLS 4.5.1 with
    g> weblogic's oracle pool driver with a JDK1.2.2 vm running with
    g> native threads.
    Provided you're running a recent WLS service pack, you should be in
    fine shape.
         <b
    Let us pray:
    What a Great System.
    Please Do Not Crash.
    ^G^IP@P6

  • Nativ thread

    Hi,
    Using the version solaris 8 java 1.2.2 , the threads are native so not
    controlled by the user. Having 2 threads wich interfere each others because they share the same data, i have a critical section. How can i protect my data ? Is there semaphore in Java ? Any idea ?
    Thanks in advance...
    Olivier

    Not sure I understand exactly your question but I will offer some tips.
    First make sure all the native threads are attached to the VM, so they can all make use of the Java methods.
    There is no semaphore built-in to Java. You can implement your own if you like, using synchronized methods of a class. A simple Semaphore class containing a private int to keep track of counting, and synchronized methods to increment, decrement, and optionally get and set the value of the counter, is sufficient for a simple semaphore. Synchronized anything is very slow in the 1.2 VM so if you are worried about performance, you are better off either upgrading to 1.4 or avoiding the Java synchronization operations.
    If you are controlling access only to native resources, accessed only through native code, then you can use regular C++ thread operations. The Java thread calling the native methods will be safely controlled by the C++ threading functions, however you must not destroy a Java thread directly from native code. If you have a C++ thread you have created you can destroy it from your C++ code provided it is first detached from the VM. Of course, as with any native code, you must be very careful, because bugs in native code can cause truly bizarre VM behavior and thread problems are no different.
    However, this approach will not work if you are working with a VM using a user-thread library, and it will not (necessarily) work if you are controlling access to a Java object which might be accessed both from native and from Java code. In this case, you must synchronize on the contested object using the JNI functions MonitorEnter and MonitorExit. C++ code between a MonitorEnter call and MonitorExit call will work exactly as if it were enclosed in a Java synchronized(){} block. You can call MonitorEnter and MonitorExit many times and on different objects, just as long as you call MonitorExit on each object as many times as you call MonitorEnter on it. Be aware of possible deadlock issues here, two threads can deadlock each trying to acquire locks held by the other. It is good practice also to exit monitors in the reverse order from which they were entered, although I do not know if this is a hard restriction or not in any particular VM.
    Let me know if this answers your question or not :}

  • Stack size for native thread attaching to JVM

    All:
    I have a native thread (see below, FailoverCallbackThread) that attaches to the JVM and does a Java call through JNI. The stack size for the native thread is 256KB.
    at psiUserStackBangNow+112()@0x20000000007a96d0
    at psiGuessUserStackBounds+320()@0x20000000007a8940
    at psiGuessStackBounds+48()@0x20000000007a8f60
    at psiGetPlatformStackInfo+336()@0x20000000007a9110
    at psiGetStackInfo+160()@0x20000000007a8b40
    at psSetupStackInfo+48()@0x20000000007a5e00
    at vmtiAttachToVMThread+208()@0x20000000007c88b0
    at tsAttachCurrentThread+896()@0x20000000007ca500
    at attachThread+304()@0x2000000000751940
    at genericACFConnectionCallback+400(JdbcOdbc.c:4624)@0x104b1bc10
    at FailoverCallbackThread+512(vocctx.cpp:688)@0x104b8ddc0
    at start_thread+352()@0x20000000001457f0
    at __clone2+208()@0x200000000030b9f0
    This causes stack overflow in Oracle JRockit JVM. (It does not cause overflow with Oracle Sun JDK.) Is there a recommended stack size for this use case for JRockit? Is there a way to compute it roughly?
    Platform Itanium 64 (linux)]
    java version "1.5.0_06"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
    BEA JRockit(R) (build R26.4.0-63-63688-1.5.0_06-20060626-2259-linux-ia64, )
    mp

    How do I found default heap size, stack size for the
    thread, number of threads per jvm/process supported ?The threads is OS, OS install and jvm version specific. That information is also not useful. If you create the maximum number of threads that your application can create you will run out of memory. Threads require memory. And it is unlikely to run very well either.
    The default heap size and stack size are documented in the javadocs that explain the tools that come with the sun jdk.
    and how the above things will vary for each OS and how
    do I found ? Threads vary by OS, and OS install. The others do not (at least not with the sun jvm.)
    If I get "OutOfMemoryError: Unable to create new native thread" Most of the time it indicates a design problem in your code. At the very lease, you should consider using a thread pool instead.
    I found in one forum, in linux you can create maximum
    of 894 threads. Is it true ?Seems high since in linux each thread is a new process, but it could be.

  • Java.lang.OutOfMemoryError: unable to create new native thread on Win2000

    Dear all,
    I install a java server (SAP J2EE) on the windows machine and run into the following problem: the total number of threads cannot exceed 1200 (as i see this in the task manager)
    After it does reach this number no other tasks can be started. Thereafter i get java.lang.OutOfMemoryError: unable to create new native thread error .
    However the other machine where the same distribution of Win2000 Server is installed can easily coupe with more than 2500 theads. The same is true when the safe mode on the first machine is on: I can generate more than 1200 threads. So it seems the problem has something to do with Windows itself.
    I am really puzzled here, would really appreciate any help.
    Thanks in advance,
    Dimitry
    Surkov Dimitry
    [email protected]
    +49.1632.492618

    well, i do not supply any options when i start jvm, but it is not the course:
    it also happens with c programs. however in the safe mode it works. both for c and for java program.
    so it must be either some software (however memory is ok) or ...? i am lost. In some Unix system you can set the total number of threads allowed as an option in the kernal. But i guess this is not the case with windows.
    Thanks a lot for your reply,
    dimitry

  • Java.lang.OutOfMemoryError: unable to create new native thread

    Hi All,
    I have installed weblogic server 8 sp4 in production environment . I am facing problems with JVM issues .
    JVM is crashing very frequently with the following errro :
    ####<Jun 18, 2009 10:58:22 AM IST> <Info> <Common> <IMM90K-21> <SalesCom> <ExecuteThread: '24' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-000628> <Created "1" resources for pool "PIConnectionPool", out of which "1" are available and "0" are unavailable.>
    ####<Jun 18, 2009 11:00:09 AM IST> <Info> <EJB> <IMM90K-21> <SalesCom> <ExecuteThread: '23' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-010051> <EJB Exception occurred during invocation from home: payoutCheck.ejb.payoutCheck_s6v3so_HomeImpl@121a735 threw exception: java.lang.OutOfMemoryError: unable to create new native thread
    java.lang.OutOfMemoryError: unable to create new native thread
         at java.lang.Thread.start(Native Method)
         at payoutCheck.classes.MyThread2.MyThreadv(PayoutCheckBOImpl.java:249)
         at payoutCheck.classes.PayoutCheckBOImpl.genSP(PayoutCheckBOImpl.java:184)
         at payoutCheck.ejb.PayoutCheckSLSB.genSP(PayoutCheckSLSB.java:191)
         at payoutCheck.ejb.payoutCheck_s6v3so_EOImpl.genSP(payoutCheck_s6v3so_EOImpl.java:315)
         at payoutCheck.ejb.payoutCheck_s6v3so_EOImpl_CBV.genSP(Unknown Source)
         at payoutCheck.deligate.PayoutCheckBD.genSP(PayoutCheckBD.java:226)
         at ui.action.SearchAction.callFilter(SearchAction.java:378)
         at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
         at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:220)
         at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:446)
         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:266)
         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292)
         at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    The above mentioned is coming several times , anybody please help out to get rid of this issue.
    Thanks in advance ,
    Krikar.

    This only tells you that the JVM is running out of heap space. It doesn't tell you what is causing the problem. You likely have a memory leak, but you could also try increasing the max heap size of the JVM (-Xmx command line option). It would help to watch the % mem in use statistic, but only immediately after a garbage collection cycle (you can force a GC from the admin console). If the % mem in use after the GC is increasing over time, then that likely confirms you have a memory leak. Note that looking at that statistic during the server startup probably is irrelevant. You'd need to wait until the server finishes starting up, and likely processed a few messages (to load static data).
    If you get to the point of confirming that you have a memory leak, that requires doing detailed analysis with a Java profiler (JProfiler, JProbe, YourKit, etc.) to track down the source of the leak.

  • Help! Unable to create new native thread

    Ok I see this problem all over the web but most of the posts are many years old and still leave me a little confused.  Often at random times on the same tags like CFLDAP I get the error "Unable to create new native thread".  Then a few minutes later the same tag on the same page works just fine.
    I have 4GB of memory in this box with 1400 MB set as the maximum Java heap size by the way.
    Here are my arguments from the jvm.config file.
    # Arguments to VM
    java.args=-server  -Xmx1400m -Dsun.io.useCanonCaches=false -XX:MaxPermSize=192m -XX:+UseParallelGC -Dcoldfusion.rootDir={application.home}/../ -Dcoldfusion.libPath={application.home}/../lib -Dcoldfusion.classPath={application.home}/../lib/updates,{application.home}/../lib,{appli cation.home}/../gateway/lib/,{application.home}/../wwwroot/WEB-INF/flex/jars,{application. home}/../wwwroot/WEB-INF/cfform/jars,"C:\\Program Files\\Apache Software Foundation\\Apache2.2\\htdocs\\InterWeb-Prod\\includes\\classes"
    Here is a typical error that comes through.
    struct     
    Browser     Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.70 Safari/533.4    
    DateTime    {ts '2010-06-23 10:07:44'}  
    Diagnostics unable to create new native thread null <br>The error occurred on line 122.
    GeneratedContent      
    HTTPReferer http://--------------------/index.cfm?FuseAction=HR.main    
    Mailto      interweb@--------------------- 
    Message     unable to create new native thread      
    QueryString fuseaction=ManagedLists.MailSubscriptions     
    RemoteAddress     192.168.250.124
    RootCause   struct    
    Message     unable to create new native thread      
    StackTrace          java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:597) at com.sun.jndi.ldap.Connection.<init>(Connection.java:208) at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:112) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2504) at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:263) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:76) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82) at coldfusion.tagext.net.LdapTag.do_ActionQuery(LdapTag.java:839) at coldfusion.tagext.net.LdapTag.doStartTag(LdapTag.java:616) at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:2661) at cfadfunctions2ecfm1473603830$funcADLOOKUPUSERNAME.runFunction(C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\InterWeb-Prod\includes\adfunctions.cfm:122) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:418) at coldfusion.runtime.UDFMethod$ArgumentCollectionFilter.invoke(UDFMethod.java:324) at coldfusion.filter.FunctionAccessFilter.invoke(FunctionAccessFilter.java:59) at coldfusion.runtime.UDFMethod.runFilterChain(UDFMethod.java:277) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:192) at coldfusion.runtime.CfJspPage._invokeUDF(CfJspPage.java:2471) at cfadfunctions2ecfm1473603830$funcADLOOKUPMULTIPLEUSERNAMES.runFunction(C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\InterWeb-Prod\includes\adfunctions.cfm:54) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:418) at coldfusion.runtime.UDFMethod$ArgumentCollectionFilter.invoke(UDFMethod.java:324) at coldfusion.filter.FunctionAccessFilter.invoke(FunctionAccessFilter.java:59) at coldfusion.runtime.UDFMethod.runFilterChain(UDFMethod.java:277) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:192) at coldfusion.runtime.CfJspPage._invokeUDF(CfJspPage.java:2471) at cfdsp_managedlists2ecfm55598920.runPage(C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\InterWeb-Prod\hr\managedlists\dsp_managedlists.cfm:232) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:196) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:370) at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:2661) at cffbx_switch2ecfm2121232114.runPage(C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\InterWeb-Prod\hr\managedlists\fbx_switch.cfm:23) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:196) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:370) at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:2661) at cffbx_fusebox30_cf502ecfm1180471387._factor4(C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\InterWeb-Prod\fbx_fusebox30_cf50.cfm:241) at cffbx_fusebox30_cf502ecfm1180471387._factor5(C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\InterWeb-Prod\fbx_fusebox30_cf50.cfm:1) at cffbx_fusebox30_cf502ecfm1180471387.runPage(C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\InterWeb-Prod\fbx_fusebox30_cf50.cfm:1) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:196) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:370) at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:2661) at cfindex2ecfm749274359.runPage(C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\InterWeb-Prod\index.cfm:23) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:196) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:370) at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65) at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:273) at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48) at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40) at coldfusion.filter.PathFilter.invoke(PathFilter.java:86) at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70) at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:2 8) at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38) at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46) at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38) at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22) at coldfusion.CfmServlet.service(CfmServlet.java:175) at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89) at jrun.servlet.FilterChain.doFilter(FilterChain.java:86) at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42 ) at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46) at jrun.servlet.FilterChain.doFilter(FilterChain.java:94) at jrun.servlet.FilterChain.service(FilterChain.java:101) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543) at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203) at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428) at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)  
    I could really use some help figuring this out.  We are getting random errors a few times a day and usually in places where we are using CFLDAP.
    Thanks,
    David

    Absolutely unbelievable that this has been going on for 4 YEARS and there are still NO definitive answers from Adobe!!
    There's no definite answer from Adobe, because there's no definitive single question.  These errors come up because - for any number of possible reasons - the JVM becomes overloaded.  And it's almost always down to an issue with the application code being run, and nothing to do with CF, per-se.  So what's Adobe supposed to do?  Come and fix your application for you?  There are plenty of diagnostic tools out there - some built into CF itself - which you could use to sort the problem out.  Or you could hire someone like Mike Brunt to come and have a look at your set up.  All it takes to fix these things is to actually do something about fixing it, rather than slamming one's fist on the desk saying "why doesn't Adobe do something!"
    I thought - and my knowledge in the area isn't expansive - the inability to allocate threads was down to the app being choked up: threads are a finite commodity, and if requests are queuing up faster than the JVM can clear them, you're gonna get errors eventually.  What causes this sort of thing?  More traffic than the server can process.  This could be because of server kit, or it could be due to code that doesn't scale to the requirement.  Usually the latter.  Basically one cannot polish a turd.
    I have a 24x7 production server that services 180,000 clients in 300 countries around the clock that cannot afford to be down for more than a few minutes at a time.
    I'm running Windows 2008 32-bit with 4GB of RAM because I have some graphics software that cannot tolerate a 64-bit OS.  Everything has been running fine for the past few months, but now it's starting to crash more and more frequently.  I have CF 8.0.1.195765 and Java 1.6.0_04
    How many concurrent requests for 180000 clients generate?  The number of clients matters less than how heavily the site is used.  But, to be honest, I get the impression the implication is "it's a busy site", in which case I think your hardware is a bit on the lean side.  Also, if it's a mission-critical app, running it on a single server is probably ill-advised, just from a fault-tolerance perspective even before one starts thinking about performance.
    If I was in your situation, I'd consider the following options:
    * upgrade your JVM to the most recent version (1.6.0_21?)
    * put more RAM in the box, and run a second CF instance on it.
    * get another box.
    * refactor the environment so the graphics software runs on a different box, upgrading the CF server to 64-bit (again, with more RAM)
    * run some diagnostics on the server, seeing what's taking up threads and where any bottlenecks might be
    * get an expert in to do the analysis side of things.
    * stop expecting Adode to fix "something".
    One of my other symptoms I have noticed is that any work done using RDP starts getting really really bogged down.  Opening Windows Explorer and searching for files can take minutes.  Restarting the CF service will sometimes fail to complete, and you have to wait a few minutes before the manual Start option appears in the dropdown.  Maybe coincidentally, the Performance Monitor will fail to add any of the ColdFusion metrics, for example Running Requests and Queued Requests, and the Event Monitor shows an error relating to an 8-byte boundary not being maintained.
    You don't, by any chance, store your client variables in the registry do you?  The only time I've seen this happen is when the CF box is munging the OS environment, and the only way I can think this could happen if it was clogging the registry.  Never store client variables in the registry.
    Adam

  • Unable to create native thread in Normal Condition

    I am trying to analyze the "OOM unable to create native thread" error that occurred in our application. I wrote a sample program which has to creates 5000 threads and monitored it using JConsole.
    import java.io.BufferedReader;
    import java.io.IOException;
    import java.io.InputStreamReader;
    * ThreadJvmMemory.java
    * Created on June 1, 2007, 9:49 AM
    * To change this template, choose Tools | Template Manager
    * and open the template in the editor.
    * @author Administrator
    public class ThreadJvmMemory extends Thread{
    /** Creates a new instance of ThreadJvmMemory */
    BufferedReader in = null;
    public ThreadJvmMemory() {
    public static void main(String args[]){
    ThreadJvmMemory dummy = new ThreadJvmMemory();
    dummy.waitTillEnter();
    for(int i=0;i<5000;i++){
    if(i%1000==0){
    System.out.println(i);
    dummy.waitTillEnter();
    ThreadJvmMemory dummy1 = new ThreadJvmMemory();
    dummy1.start();
    public void run(){
    //System.out.println("Here");
    Object dummyObject = new Object();
    try {
    in = new BufferedReader(new InputStreamReader(System.in));
    in.readLine();
    } catch (IOException ex) {
    ex.printStackTrace();
    System.out.println("Came out of the thread");
    public void waitTillEnter(){
    try {
    if(in==null)
    in = new BufferedReader(new InputStreamReader(System.in));
    in.readLine();
    } catch (IOException ex) {
    ex.printStackTrace();
    I started the program using the following command line option..
    "c:\Program Files\Java\jdk1.5.0_09\bin\java.exe" -Dcom.sun.management.jmxremote.port=9979 -Xmx512m -Xminf0.1 -Xmaxf0.1 -XX:MaxPermSize=256m -XX:PermSize=256m -XX:+<GCTYPE> -XX:+PrintGCDetails
    where GCType will be UseTrainGC or UseSerialGC or UseParallelGC or
    What i observe in all the cases, there are no more than 1000 threads getting created . After completion of 1000 threads garbage collector keeps running and no more threads get created. Since i have configured heapsize to be 512m, PermGenSpace to be 256 and default value for process sapece is 2gb, JVM would be able to create only 1000 threads as per the formula "NoOfThreads = Process space - (Heap + permGen+some for VM initialization)/Stack Size" (correct me if i am wrong). But why i am not getting OutOfMemoryError while creating native thread. Moreover i can observer non-heap (Perm Gen) space keep growing overtime. But there is enough space in all other spaces.So my doubts are
    1. Actually when we will get OOM error saying unable to create Native thread. To be more specific when which space occupied i will get this error.
    2. Is there any way to configure process space. IMO No ?? Confirm ??
    3. Does any one tried using a a tool that analyzes verboseGC output of SUN JVM. If so can you give any pointer. I have read through GCPortal, but i havent fully deployed it.
    Java version is 1.5.0
    OS Windows 2k3
    Snippet of GC Output
    [GC [DefNew: 5208K->38K(5824K), 0.0072564 secs] 32049K->26879K(34636K), 0.0080451 secs]
    [GC [DefNew: 5222K->24K(5824K), 0.0070320 secs] 32063K->26868K(34636K), 0.0078097 secs]
    [GC [DefNew: 5208K->39K(5824K), 0.0082161 secs] 32052K->26883K(34636K), 0.0090173 secs]
    [GC [DefNew: 5223K->27K(5824K), 0.0080766 secs] 32067K->26874K(34636K), 0.0089273 secs]
    [GC [DefNew: 5211K->39K(5824K), 0.0071186 secs] 32058K->26886K(34636K), 0.0078970 secs]
    [GC [DefNew: 5223K->25K(5824K), 0.0070952 secs] 32070K->26875K(34636K), 0.0078766 secs]
    [GC [DefNew: 5209K->21K(5824K), 0.0069871 secs] 32059K->26872K(34636K), 0.0077657 secs]

    I am trying to analyze the "OOM unable to create native thread" error that occurred in our application. I wrote a sample program which has to creates 5000 threads and monitored it using JConsole.
    import java.io.BufferedReader;
    import java.io.IOException;
    import java.io.InputStreamReader;
    * ThreadJvmMemory.java
    * Created on June 1, 2007, 9:49 AM
    * To change this template, choose Tools | Template Manager
    * and open the template in the editor.
    * @author Administrator
    public class ThreadJvmMemory extends Thread{
    /** Creates a new instance of ThreadJvmMemory */
    BufferedReader in = null;
    public ThreadJvmMemory() {
    public static void main(String args[]){
    ThreadJvmMemory dummy = new ThreadJvmMemory();
    dummy.waitTillEnter();
    for(int i=0;i<5000;i++){
    if(i%1000==0){
    System.out.println(i);
    dummy.waitTillEnter();
    ThreadJvmMemory dummy1 = new ThreadJvmMemory();
    dummy1.start();
    public void run(){
    //System.out.println("Here");
    Object dummyObject = new Object();
    try {
    in = new BufferedReader(new InputStreamReader(System.in));
    in.readLine();
    } catch (IOException ex) {
    ex.printStackTrace();
    System.out.println("Came out of the thread");
    public void waitTillEnter(){
    try {
    if(in==null)
    in = new BufferedReader(new InputStreamReader(System.in));
    in.readLine();
    } catch (IOException ex) {
    ex.printStackTrace();
    I started the program using the following command line option..
    "c:\Program Files\Java\jdk1.5.0_09\bin\java.exe" -Dcom.sun.management.jmxremote.port=9979 -Xmx512m -Xminf0.1 -Xmaxf0.1 -XX:MaxPermSize=256m -XX:PermSize=256m -XX:+<GCTYPE> -XX:+PrintGCDetails
    where GCType will be UseTrainGC or UseSerialGC or UseParallelGC or
    What i observe in all the cases, there are no more than 1000 threads getting created . After completion of 1000 threads garbage collector keeps running and no more threads get created. Since i have configured heapsize to be 512m, PermGenSpace to be 256 and default value for process sapece is 2gb, JVM would be able to create only 1000 threads as per the formula "NoOfThreads = Process space - (Heap + permGen+some for VM initialization)/Stack Size" (correct me if i am wrong). But why i am not getting OutOfMemoryError while creating native thread. Moreover i can observer non-heap (Perm Gen) space keep growing overtime. But there is enough space in all other spaces.So my doubts are
    1. Actually when we will get OOM error saying unable to create Native thread. To be more specific when which space occupied i will get this error.
    2. Is there any way to configure process space. IMO No ?? Confirm ??
    3. Does any one tried using a a tool that analyzes verboseGC output of SUN JVM. If so can you give any pointer. I have read through GCPortal, but i havent fully deployed it.
    Java version is 1.5.0
    OS Windows 2k3
    Snippet of GC Output
    [GC [DefNew: 5208K->38K(5824K), 0.0072564 secs] 32049K->26879K(34636K), 0.0080451 secs]
    [GC [DefNew: 5222K->24K(5824K), 0.0070320 secs] 32063K->26868K(34636K), 0.0078097 secs]
    [GC [DefNew: 5208K->39K(5824K), 0.0082161 secs] 32052K->26883K(34636K), 0.0090173 secs]
    [GC [DefNew: 5223K->27K(5824K), 0.0080766 secs] 32067K->26874K(34636K), 0.0089273 secs]
    [GC [DefNew: 5211K->39K(5824K), 0.0071186 secs] 32058K->26886K(34636K), 0.0078970 secs]
    [GC [DefNew: 5223K->25K(5824K), 0.0070952 secs] 32070K->26875K(34636K), 0.0078766 secs]
    [GC [DefNew: 5209K->21K(5824K), 0.0069871 secs] 32059K->26872K(34636K), 0.0077657 secs]

  • OutOfMemoryError: unable to create native thread

    Why do I get OutOfMemory exceptions even if there is plently of Memory.
    JVM settings are -Xms256M and -Xmx1024M.
    Debug at runtime (Runtime.totalMemory()) shows that it never got above 260M. Why does the JVM not grab some more memory -instead of throwing OutOfMemory exception.
    I am creating quite a lot of threads 800+ within a few minutes
    Any ideas?

    I googled a bit and one thing i came across was
    "In those hypothetical configurations, the error java.lang.OutOfMemoryError: unable to create new native thread would begin to saturate the JRun logs. To clarify the error text, the error message means that no more native, or OS, threads can be created for the JVM process, causing the JVM to throw an exception. The exception type is java.lang.outOfMemoryError, but I find that to be rather misleading since the resource limitation on the OS thread count, not memory usage. "
    So it looks like you're looking for OS specific settings rather than anything pure java.
    Note that a thread per socket is not necessary, even when not using NIO:
    import java.io.BufferedReader;
    import java.io.IOException;
    import java.io.InputStreamReader;
    import java.io.Reader;
    import java.net.ServerSocket;
    import java.net.Socket;
    import java.util.HashMap;
    import java.util.LinkedList;
    import java.util.List;
    import java.util.Map;
    import java.util.concurrent.Executors;
    import java.util.concurrent.TimeUnit;
    public class ForumQuestion { 
        // i'm assuming character based input
        static final List<Reader> readers = new LinkedList<Reader>();
        static final Map<Reader,StringBuffer> buffers = new HashMap<Reader,StringBuffer>();
        static final Map<Reader,Socket> sockets = new HashMap<Reader,Socket>();
        public static void main( String[] args ) throws IOException {
            // using single thread (for simplicity) to handle all sockets
            // the main trick is making sure that your thread(s) doing the reading
            // don't sit and "spin" around the inputStreams when they have nothing
            // at all waiting... wasting CPU. Here i just make the worker sleep
            // for 1000 nanos between attempts where it hasn't read anything. I'm
            // sure you can do better!
            Executors.newScheduledThreadPool( 1 ).scheduleWithFixedDelay( new Runnable() {
                public void run() {
                    checkStreams();
            }, 1000, 1000, TimeUnit.NANOSECONDS );
            // create server socket and use main thread to block waiting for connections
            ServerSocket serverSock = new ServerSocket( 1138 );
            System.out.println( "Accepting connections on port 1138" );
            while( true ) {
                Socket s = serverSock.accept();
                synchronized( readers ) {
                    Reader r = new BufferedReader( new InputStreamReader( s.getInputStream() ) );
                    readers.add( r );
                    buffers.put( r, new StringBuffer() );
                    sockets.put( r, s );
                    System.out.printf( "Connection: %s%n", s );
        private static void checkStreams() {
            // i've been lazy (over zealous) with the synchronization for simplicity. you'd want to
            // Do something cleverer than blocking accepts() while work is being done
            synchronized( readers ) {
                if ( readers.size() == 0 ) {
                    return;
                // carry on until no work was done for any incoming sockets
                while( true ) {
                    boolean workDone = false;
                    for( Reader r : readers ) {
                        try {
                            StringBuffer buff = buffers.get( r );
                            while( r.ready() ) {
                                char c = (char)r.read();
                                buff.append( c );
                                checkBuffer( r, buff, c );
                                workDone = true;
                        } catch( IOException e ) {
                            // do something here, client prob dead
                    // if no work done (no sockets had anything) then rest the thread
                    if ( !workDone ) break;
        private static void checkBuffer( Reader r, StringBuffer buff, char last ) {
            if ( last == '\n' ) {
                System.out.printf( "Read \"%s\" from %s%n", buff.toString().trim(), sockets.get( r ) );
                buff.delete( 0, buff.length() );
    Accepting connections on port 1138
    Connection: Socket[addr=/127.0.0.1,port=1776,localport=1138]
    Connection: Socket[addr=/127.0.0.1,port=1777,localport=1138]
    Read "hello" from Socket[addr=/127.0.0.1,port=1776,localport=1138]
    Read "hi" from Socket[addr=/127.0.0.1,port=1777,localport=1138]
    Read "we're two sockets, but only using one thread to read from both of us!!" from Socket[addr=/127.0.0.1,port=1776,localport=1138]
    Read "Oh! YAY!!!!" from Socket[addr=/127.0.0.1,port=1777,localport=1138]It's massively inferior to using NIO, but better than having thousands of dedicated threads

  • Attach native thread to jvm takes much time

    Hello everyone,
    I attach a native thread to the jvm. It works but it takes about 10 seconds. I do not understand why and I would like to reduce this time to 1 or 2 seconds.
    I use a native thread to get keyboard events (a hook) to capture a screen area (with Robot class).
    Samples program :
    Abstract class used by the thread :
    class CATSrvThreadHandler
    public:
    CATSrvThreadHandler();
    enum
    enableCode = 1,
    updateCode = 2,
    disableCode = 3
    virtual ~CATSrvThreadHandler();
    virtual void doEnable() = 0;
    virtual void doUpdate() = 0;
    Herited class : class CATSrvScreenIndicator:public CATSrvThreadHandler
    CATSrvScreenIndicator CATSrvScreenIndicator::extract(JNIEnv env, jobject object)
    // Get field ID
    jfieldID l_handlerId = env->GetFieldID(env->GetObjectClass(object), "_handler", "I");
    // Get field
    CATSrvScreenIndicator l_handler = (CATSrvScreenIndicator )env->GetIntField(object, l_handlerId);
    return l_handler;
    // This method is called by Java code to activate the thread
    void CATSrvScreenIndicator::enable(JNIEnv *env)
    g_DesktopIndicatorThread.MakeSureThreadIsUp(env);
    // Takes too much time !!!! (about 5 seconds)
    while(!PostThreadMessage(g_DesktopIndicatorThread, WM_DESKTOPINDICATOR, enableCode, (LPARAM)this))
    Sleep(0);
    The thread class :
    CATSrvScreenCaptureThread::CATSrvScreenCaptureThread()
    m_env = NULL;
    m_thread = 0;
    m_vm = NULL;
    m_handlerCount = 0;
    void CATSrvScreenCaptureThread::MakeSureThreadIsUp(JNIEnv *env)
    if(!m_thread)
    // --> Get VM
    env->GetJavaVM(&m_vm);
    // --> Start "native" thread
    CreateThread(NULL, 0, ThreadProc, this, 0, &m_thread);
    DWORD WINAPI CATSrvScreenCaptureThread::ThreadProc(LPVOID lpParameter)
    CATSrvScreenCaptureThread l_this=(CATSrvScreenCaptureThread)lpParameter;
    // --> Attach the thread to the VM, takes too much time !!!! (about 5 seconds)
    l_this->m_vm->AttachCurrentThread((JNIEnv**)&l_this->m_env, NULL);
    MSG msg;
    while(GetMessage(&msg, NULL, 0, 0))
    Thanks for any information !

    It's ellapse time with no other application running
    between this method call and tray icon appearing int
    the taskbar.
    Now I am not sure I understand the question.
    To time how long a method call takes you must time the method - not just the code that the method runs in. And you need to use a timer and not just guess about it.

  • Green and Native Threads...

    How do I find whether green / native threads are used in my VM???
    Can I control whether to use green / native threads are used?
    I use 2 VM's, one for win NT and one for ISeries(as/400).
    Thanks in advance!

    I don't think green/native threads can be used on windows, but for example on linux, native threads are running in their own process, while green threads means they all run in the same process.
    You can use the flag -native and -green to specify whether it should run native or green threads (on linux at least).

Maybe you are looking for