[jcifs] OutOfMemoryError unable to create new native thread

Peter peter_zavadsky at symantec.com
Mon Mar 8 15:20:01 MST 2010

Michael B Allen <ioplex <at> gmail.com> writes:

> In particular the broadcasting is refered to as the 'BCAST' method. So
> again, set netbios.resolveOrder=DNS. If your customer is really
> actually using WINS then use netbios.resolveOrder=WINS,DNS. Whatever
> the case, just leave BCAST out of it.
> Basically you just have a name service problem.


Thanks for the explanation.
It seems that your suggestion would be an ideal solution. However it seems that
in our case only the BCAST option resolves the (server) name. If I leave it out
I get UnknownHostException.
While I could adjust our network configuration to by pass that, I can't force
our customers to do so. It seems that BCAST is a viable feature of JCIFS, and
it would be a pity to not support it.

> I think if you read the above link carefully, you should be able to
> solve your problem. Interrupting those QueryThreads is a very ugly
> solution to what is effectively a configuration issue. You just need
> to understand better what name service lookups are timing out and
> adjust the configuration to stop them.
> Mike

I am only trying to point out that there is temporarily a thread leak. Each
request leaves one thread around doing job which will be wasted.
That left-behind-thread leads to the OutOfMemoryError in a performance heavy
app like ours. If that is fixed, the BCAST option would work without


More information about the jCIFS mailing list