Synapse received a response But a callback is not registered

View: New views
2 Messages — Rating Filter:   Alert me  

Synapse received a response But a callback is not registered

by mysurf mail :: Rate this Message:

| View Threaded | Show Only this Message

I am receiving an error when the synapse server is trying to route a message to my application. this are the to lines in the log : 

[*] I have deleted some string for security reasons and replaced them with [myString]

    <20120430-07:11:19, FIX.4.4:p.[myComp]->[theFarComputer], incoming>(8=FIX.4.49=29135=849=[theFarComputer]56=p.[MyString]34=270369=4652=20120430-07:11:38128=[MyString]1=[MyString]6=011=[MyString]14=015=USD17= [MyString]31=032=037=[MyString]38=131239=040=244=11.2454=155=OGZD150=0151=1312198=[MyString]526=[MyString]527=[MyString]10=087)  

    2012-04-30 10:11:19,843 [-] [FIX-Worker-8]  WARN SynapseCallbackReceiver Synapse received a response for the request with message Id : urn:uuid:683fd846-8c55-424d-8e2c-8f6e641bfdc4 But a callback is not registered (anymore) to process this response <20120430-07:11:19, FIX.4.4:p.[MyString]->p.ord.ul.ldn.LCE, incoming> 

another finding I have is that in the day before (end of day) I have a message - closing a callback with the same UUID. It doesnt seem to make sense because those are new messages sent in another day but the fact that thats the same UUID is weird.

    2012-04-28 18:01:32,218 [-] [Timer-1]  WARN TimeoutHandler Expiring message ID : urn:uuid:683fd846-8c55-424d-8e2c-8f6e641bfdc4; dropping message after global timeout of : 86400 seconds


  


Re: Synapse received a response But a callback is not registered

by Hiranya Jayathilaka-3 :: Rate this Message:

| View Threaded | Show Only this Message



On Mon, Apr 30, 2012 at 2:08 PM, Mysurf Mail <stammailbox@...> wrote:
I am receiving an error when the synapse server is trying to route a message to my application. this are the to lines in the log : 

What is your sequence/proxy configuration?
 

[*] I have deleted some string for security reasons and replaced them with [myString]

    <20120430-07:11:19, FIX.4.4:p.[myComp]->[theFarComputer], incoming>(8=FIX.4.49=29135=849=[theFarComputer]56=p.[MyString]34=270369=4652=20120430-07:11:38128=[MyString]1=[MyString]6=011=[MyString]14=015=USD17= [MyString]31=032=037=[MyString]38=131239=040=244=11.2454=155=OGZD150=0151=1312198=[MyString]526=[MyString]527=[MyString]10=087)  

    2012-04-30 10:11:19,843 [-] [FIX-Worker-8]  WARN SynapseCallbackReceiver Synapse received a response for the request with message Id : urn:uuid:683fd846-8c55-424d-8e2c-8f6e641bfdc4 But a callback is not registered (anymore) to process this response <20120430-07:11:19, FIX.4.4:p.[MyString]->p.ord.ul.ldn.LCE, incoming> 

another finding I have is that in the day before (end of day) I have a message - closing a callback with the same UUID. It doesnt seem to make sense because those are new messages sent in another day but the fact that thats the same UUID is weird.

    2012-04-28 18:01:32,218 [-] [Timer-1]  WARN TimeoutHandler Expiring message ID : urn:uuid:683fd846-8c55-424d-8e2c-8f6e641bfdc4; dropping message after global timeout of : 86400 seconds

Synapse holds on to all callbacks for 24 hours. This means a message for which Synapse was expecting a response never showed up. After 24 hours, Synapse prints the above log and drops the pending callbacks.

Thanks,
Hiranya
 


  




--
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hiranya@...;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com