[ebxmlms-general] Re: Enquiry - problem with Hermes

[Michal S. <sa...@se...>]

Patrick
Apart from watching output of client, I was watching output of MSH servlet
as well, and that's what made me think there was a problem with delivering
messages. This is what I got:

-------------  Client output -------------------------------------
Sending message
msg_1056646109774@http://localhost:8080/msh/_to_http://localhost:8080/msh/
...
Sent OK.
Message C:\Documents and
Settings\michal.DELL01\IdeaProjects\HEMP\src\koko.txt sent.
Message CAME :
msg_1056646109774@http://localhost:8080/msh/_to_http://localhost:8080/msh/
-----------------------------------------------------------------

Everything seems OK so far - Mesage sent, message received.

But, when you look on servlet output you get :
-------------  MSH servlet -------------------------------------
[MessageServiceHandler] Received request to send message

[MessageServer] Final sequence number in store: -10000
[DirectoryManager] getRepositoryFileName return:
R0000\h4BT2JjQ4W+7S9LzGIt5Mg==
[MessageServer] Insert into messagestore database
[MessageProcessor] Send... try #1
[MessageServer] Current: 'Started Sending' specified: 'Retrying #1'
[MessageServer] Update state to become 'Retrying #1'

[MessageServiceHandler] Receiving incoming message
[MessageServiceHandler] Validating incoming ebXML Message
[MessageServiceHandler] Validation of incoming message completed.
[DeliveryRecord] Adding sequence number: 0 as 0
[MessageServiceHandler] Message has an AckReq
[MessageServiceHandler] Message has not been received before
[MessageServiceHandler] Deliver to application
[MessageServer] Final sequence number in store: 0
[DirectoryManager] getRepositoryFileName return:
R0000\8Cm-3mEihOySNEZS3A83Tw==
[MessageServer] Loopback message; update messagestore table
[MessageServiceHandler] New message id:
[20030626-164836274-Some_CPA_ID.urn:oasis:names:tc:ebxml-msg:service.Acknowl
edgment.1@200.200.200.93]
[MessageServiceHandler] RefTo message id:
[msg_1056646109774@http://localhost:8080/msh/_to_http://localhost:8080/msh/]
[MessageServer] Final sequence number in store: -9999
[DirectoryManager] getRepositoryFileName return:
R0000\j3LbMhl-AoPkq4xDZTzyVA==
[MessageServer] Insert into reftomessage database
[MessageServer] Insert into messagestore database
[MessageServiceHandler] Ack sent
[MessageServiceHandler] No content is sent back
[MessageProcessor] Send... try #1
[MessageServer] Current: 'Started Sending' specified: 'Retrying #1'
[MessageServer] Update state to become 'Retrying #1'
[MessageServiceHandler] Receiving incoming message
[MessageServiceHandler] Missing MIME boundary in received message
[MessageServiceHandler] Validating incoming ebXML Message
[MessageServiceHandler] Validation of incoming message completed.
[MessageServiceHandler] Message is an Acknowledgement, referring to
[msg_1056646109774@http://localhost:8080/msh/_to_http://localhost:8080/msh/]
[DirectoryManager] getRepositoryFileName return:
R0000\vSh0Qq5XA3BZvbTUZIerxg==
[MessageServer] Insert into reftomessage database
[MessageServer] Loopback message; update messagestore table
[MessageServer] Update the acknowledgment record to set state = -7 and
acknowledged record to -6
[MessageServiceHandler] No content is sent back
[MessageServer] Current: 'Received' specified: 'Sent'
[MessageServer] Update state to become 'Sent and Received (loopback
message)'
[MessageServiceHandler] Undelivered file: R0000\8Cm-3mEihOySNEZS3A83Tw==
-----------------------------------------------------------------

The last line seems to me like that there was something not delivered and
thus delivery failed. Am I worng ? And if so, what does that message mean ?

After seeing this output, my conclusion was that message couln't be
delivered and thus was returned to client and then written out by client's
(not server's) onMessage(). That's what I meant by messages being returned
as undelivered.

Thanks
Michal



> Michal,
> If you want to use onMessage(), return null in getClientUrl() is the right
way. I'm not sure what you mean by returned all messages as undelivered. I
inspected your code, normally you send message using sendMessage(), and the
message will come in from onMessage().
>
> Regards, -Patrick
>
>
> Michal Sankot wrote:
>
> Hi Patrick,
> I tried to change code so that there is only one program running but it
> still didn't help.
> HempClient now implements MessageListener and creates request with itself
as
> a listener. But it still throws RequestException when I try to create that
> request.
>
> Problem arises when I change getClientUrl() from returning null to
returning
> a path to a local folder.
>
> I tried running it with getClientUrl() returning null sending messages to
> itself and it returned all messages as undelivered. I'd guess it was
caused
> by getClientUrl() returning null. Source files of both Client and
> MessageListener are attached.
>
> Michal
>