Philip, Are you running the server in failsafe mode or regular standalone mode? Could make a difference. I'm trying to debug a similar problem. Scott Stirling Allaire Corporation http://www.allaire.com/developer/jrunreferencedesk/ > -----Original Message----- > From: Rhodes, Phillip C. [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 14, 2000 4:07 PM > To: '[EMAIL PROTECTED]' > Subject: Closing context does not prevent exceeded connections error? > > > > On my developer desktop, I have the dev version of Jrun. Limited to > 3 concurrent requests. > > I have an ejbclient invoked via a main method. This ejbclient gets a > Context and looks up a home. It then invokes a couple of methods on > the home and then 1) closes context 2) sets context to null. > > I follow what I see in the example programs. However, after 3 > invocations, I get an error that I exceeded connections. I have > validated that I am calling close on the context. Shouldn't calling > close on a context free it up? > > Thanks > Phillip > > java.rmi.RemoteException: System exception/error caught by container; > nested exc > eption is: > java.lang.RuntimeException: Number of client connections > exceeded the al > lowed limit > java.lang.RuntimeException: Number of client connections exceeded the > allowed li > mit > <<no stack trace available>> > closing context > > Phillip Rhodes ------------------------------------------------------------------------------ Archives: http://www.egroups.com/group/jrun-interest/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
