[ 
https://issues.apache.org/jira/browse/SANDESHA2-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574387#action_12574387
 ] 

Michael Schick commented on SANDESHA2-68:
-----------------------------------------

Hi David,

thanks. I'll give it a try. 

regards,

Michael

----- Ursprüngliche Mail ----
Von: David Illsley (JIRA) <[EMAIL PROTECTED]>
An: [EMAIL PROTECTED]
Gesendet: Sonntag, den 2. März 2008, 22:26:50 Uhr
Betreff: [jira] Resolved: (SANDESHA2-68) soapenv:Header is sometimes not filled 
for the CreateSequence request


     [ 
https://issues.apache.org/jira/browse/SANDESHA2-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Illsley resolved SANDESHA2-68.
------------------------------------

    Resolution: Cannot Reproduce

So much has changed since Sandesha2 1.0, it's really unlikely this problem 
still exists in the same form.
Please reopen if you can reproduce on Sandesha2 1.3 or a recent nightly.
Apologies for the long silence...
David


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.






      Lesen Sie Ihre E-Mails auf dem Handy.
www.yahoo.de/go


> soapenv:Header is sometimes not filled for the CreateSequence request
> ---------------------------------------------------------------------
>
>                 Key: SANDESHA2-68
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-68
>             Project: Sandesha2
>          Issue Type: Bug
>         Environment: Sun Solaris 2.9, Java 5, Axis2 (1.1.1), Sandesha2 (1.0)
>            Reporter: Michael Schick
>         Attachments: Client.zip
>
>
> From time to time I observe the failure "Operation not found EPR is   and WSA 
> = null". 
> If this error happens, then the first "createSequence" call does not seem to 
> have any details in the soap header !
> Re-running exactly the same client without change works suddenly again.
> I see this error however more often, when log4j logging is set to ALL.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to