Problems on setting server-side concurrency model

[alexan]

I have the following CORBA (Orbacus) application (and java):
One Corba Server(AuthServer) exporting two method :
1)Session Login (username, password);
2)void logout (Session mySession);

Then, a generic client may access the server using the Login method and
release the server invoking the Logout method.

The problem I have regards Orbacus concurrency model.
What I do is to register on the Name Service the AuthServer object.

The System works fine when I Login to the server simultaneously from different clients (connections) and all the Login methods are successfully .But if for any reason a Login fails and the AuthServer blocks then all the system blocks itself and in not possible to invoke from a client any other Login or Logut.

I think it was due to the setting of the server-side concurrency model by means of the system variable ooc.orb.oa.conc_model, which on my system is set to "threaded". So I changed its value to "thred_per_client" but the system keeps on not working.

Any Idea how to get the system working?

Thanks

 

[Cagliostro]

Create a server side login factory. For each user try to connect the login factory should create a separate login object and to start for each a separate thread.

Ion Filipski

filipski@excite.com