axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 19836] - Exception in service constructor makes future SOAP calls hang
Date Mon, 21 Jul 2003 10:50:25 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19836>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19836

Exception in service constructor makes future SOAP calls hang





------- Additional Comments From james.casey@cern.ch  2003-07-21 10:50 -------
I had the same problem with an Application Scope service in 1.1rc2.  

I tracked it down to the lock object not being released, which was fixed in 1.1
final.

But using this, the service now returns 

FAIL : Tried to invoke method public java.lang.String
org.edg.data.rls.EdgLocalReplicaCatalogSoapBindingSkeleton.ping() throws
java.rmi.RemoteException with arguments .  The arguments do not match the
signature.; nested exception is:
        java.lang.IllegalArgumentException: object is not an instance of
declaring class


The full solution is to also delete the lock object from the Session when an
exception is thrown.  The combination of the patch already in 1.1final and this
one should fix the problem.

Mime
View raw message