multithreading - using asynchbeans instead of native jdk threads -
are there performance limitations using ibm's asynchbeans? apps jvm core dumps showing numerous occurences of orphaned threads. im using native jdk unmanaged threads. worth changing on managed threads?
in perspective asynchbeans workaround create threads inside websphere j2ee server. far good, websphere lets create pool of "worker" threads, controlling way maximum number of threads, typical j2ee scalability concern.
i had problems using asynchbeans inside websphere on "unmanaged" threads (hacked callbacks jms listener via "outlawed" setmessagelistener). "asking it" not using mdbs in first place, have requisites not feet mdb way.
Comments
Post a Comment