Websockets – failed subscription
-
Frantisek5 years ago #14915
Hi,
I have Simplifier application written in UI5, which uses Push Connector to receive data from SAP MII (MII post data to the connector).
Application normally works on mobile but I am trying to make it work also in normal browser.
However I have problems to receive any data. Websocket connection is correctly created but when subscribe frame is sent server always respond with failed subscription.Example communication:
send:{frameType: "subscribe", subscriptionKey: "dd2f9cda-f263-478a-b16f-ff898d83bfc4", json: {}}
recieve:{frameType: "termination", reason: "failed_subscription", subscriptionKey: "dd2f9cda-f263-478a-b16f-ff898d83bfc4"}
Could you give me some hints what can be wrong? Why it is not working in normal browser?
Thanks,
FrantisekKahnHas successfully completed the online course IntroductionHas successfully completed the online course Intermediate (200)Has successfully completed the online course Advanced (300)Frantisek5 years ago #14932::Hi,
sorry I forgot about that. So our simplifier instance is deployed on premise via docker. We are using version 3.5.74-LTS.98.
I checked logs from appserver.log, System.log, docker.log and in GUI, and there is nothing related (just in GUI it is shown that it was terminated without some reason).
I also tried to restart docker container multiple times and it did not help.
Are there some more log files to check (rest of *.log files inside simplifier/data/log/appserver/simplifierlog folder were basically empty or old)?
Edit:
I discovered that this is written to the log file(appserver.log) after failed_subscription frame, but still I do not think that it is cause of the problem:
2019-04-26 13:23:00 [DEBUG] BaseService: Connected WebSocket to event source Actor[akka://on-spray-can/user/StreamSupervisor-0/flow-17082-1-actorRefSource#-201183254] 2019-04-26 13:24:01 [WARN ] ActorSystemImpl: Illegal header: Illegal 'cookie' header: Unexpected end of input, expected ??? (line 1, column 2):
Thanks,
Frantisek
You must be logged in to reply to this topic.