Bill,
I work on the security team, and we have been discussing this issue internally with the jsse and performance teams. It looks like your app is exceeding the maximum number of connections allowed by the orb, and that when the orb tries to "reclaim" a connection for use by your app, that it tries to reclaim a connection that had previously been used for SSL (which results in a problem).
I have offered to pass on some suggestions.
one suggestion is to change the maximum connections configured for the orb. This may not fix the problem, and it might even amplify problems relating to resource consumption, but is something that you might want to try. You can do this using the admin console to change the max-connections (see Configuration -> ORB -< total connections).
you should also create a bug, and it would be most helpful, if you could upload your application so that we can use it to reproduce the problem. It would also help if you could attach your domain.xml, and a description of any orb specific configuration (if you have done any).
if you cannot send us (a version of) your app, you might try reducing the value of max-connections, hopefully to cause the problem to occur sooner. It may also be helpful if you could run your application while having corba transport debug enabled (-Dcom.sun.CORBA.ORBDebug="transport") and then send us the relevant part of the server.log.
thanks
Ron
[Message sent by forum member 'monzillo' (monzillo)]
http://forums.java.net/jive/thread.jspa?messageID=254524