Adam,
The following change was made to the code in CVS regarding this issue.
Thanks again for providing the technique of locking the service class rather
than the servlet context.
Scott Nichol
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 11
-
From: "Adam Moore" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 11, 2002 10:29 AM
Subject: RE: Constructor Deadlock
> Scenario: We have a class that implements a SOAP service. Service scope
is
> set to "application". In the construc
: "Adam Moore" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 11, 2002 10:29 AM
Subject: RE: Constructor Deadlock
> Scenario: We have a class that implements a SOAP service. Service scope
is
> set to "application". In the constructor of that
Scenario: We have a class that implements a SOAP service. Service scope is
set to "application". In the constructor of that class we make a call to a
different service that is running on the same machine. Since these are
different services with different service ids everything should run fine,
D]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, July 09, 2002 3:32 PM
Subject: Re: Constructor Deadlock
> Adam:
>
> If individual calls from client fail then why would java Call have more
success?
> If possible could you provide
> 1)Specific services you are executing on Server
Adam:
If individual calls from client fail then why would java Call have more success?If possible could you provide 1)Specific services you are executing on Server (are they registered)2)Specific client call to the server code(in code)danke,Martin
>
>
>I have a class that implements a SOAP
Title: RE: Constructor Deadlock
I run into a similar problem when deploying a service using application scope. After reviewing the code, I think that the problem is in:
org.apache.soap.server.http.ServerHTTPUtils.getTargetObject
The scopeLock is obtained using the servlet context. I
Adam,
If you are using Application or Session scope for your services, this
behavior is by design. Creation of an instance of a service object is
synchronized on the app or session in those cases to ensure that only one
instance is created per application or session.
Scott Nichol
- Origina
