[jcifs] Any other way to create new Transport thread except mentioning SSN_LIMIT=1?

Michael B Allen ioplex at gmail.com
Wed Aug 20 16:09:16 GMT 2008

On Wed, Aug 20, 2008 at 4:04 AM, Arnab <arnab84 at gmail.com> wrote:
> Hi
> I have one application where I have to use SSN_LIMIT=1 so that jcifs creates new
> Transport thread for each Session. This is required to handle more than one pipe
> simultaneously.
> However I know there is only one place where I require multithreading and rest
> of the application can work with single Transport thread. So is there anyway
> other than having SSN_LIMIT=1 for multithreading because putting SSN_LIMIT=1
> creates more than one Transport thread, just a waste of resource.
> I would also like to suggest that if there is no external control other than
> mentioning SSN_LIMIT=1, then lets pass a flag into method parameter for creating
> new Transport thread.

There is no such logic and I'm not interested in adding it.

But I would be interested in hearing why you need to use ssnLimit=1 in
the first place. When you speak of pipes are you referring to named
pipes? I don't think you should have to set ssnLimit to 1 so if you
can describe the problem better perhaps we can come up with a fix.

Also, you could create a separate instance of JCIFS using a separate
class loader.


Michael B Allen
PHP Active Directory SPNEGO SSO

More information about the jcifs mailing list