| Author |
Message |
 Topic: HTTPRequest node: BIP3161 socket exception |
Hoshi
Replies: 14
Views: 12947
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Mon May 23, 2016 8:53 am Subject: HTTPRequest node: BIP3161 socket exception |
We've set 1 second on the Broker side and 2 seconds on the Web Server side.
Although I strongly suggest you capture and analyze the traffic in your environment, since I believe there may be many dif ... |
| Topic: HTTPRequest node: BIP3161 socket exception |
Hoshi
Replies: 14
Views: 12947
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun May 22, 2016 11:44 am Subject: HTTPRequest node: BIP3161 socket exception |
| It's a Web Server configuration for persistent (keep-alive) connections. We didn't have to find it out in our case, since server admins just told us what they configured. |
| Topic: HTTPRequest node: BIP3161 socket exception |
Hoshi
Replies: 14
Views: 12947
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 19, 2016 12:35 pm Subject: HTTPRequest node: BIP3161 socket exception |
Hi vinod,
I don't really have information about the server software since it's a 3rd party. And for the second question - I'm pretty certain a firewall can close idle connections too.
Anyway the ... |
| Topic: HTTPRequest node: BIP3161 socket exception |
Hoshi
Replies: 14
Views: 12947
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Apr 21, 2016 10:34 pm Subject: HTTPRequest node: BIP3161 socket exception |
It looks like we were able to figure out what was causing the error in our case.
The HTTPRequest node in our flow is configured to use persistent connections with HTTP 1.1 keep-alive over TLS protoco ... |
| Topic: HTTPRequest node: BIP3161 socket exception |
Hoshi
Replies: 14
Views: 12947
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Apr 21, 2016 4:09 am Subject: HTTPRequest node: BIP3161 socket exception |
| Yes, I do. But thanks for the reminder! |
| Topic: HTTPRequest node: BIP3161 socket exception |
Hoshi
Replies: 14
Views: 12947
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Apr 21, 2016 12:45 am Subject: HTTPRequest node: BIP3161 socket exception |
Hello, Sanjoo,
Were you able to identify the root cause for the error above?
We are facing a similar situation. We have a simple message flow performing requests to an HTTPS endpoint. The flow is ... |
| Topic: Setting additional header in HTTP Request Node |
Hoshi
Replies: 12
Views: 9353
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Feb 03, 2016 1:59 am Subject: Setting additional header in HTTP Request Node |
| Actually it's quite the contrary. If you set the mode to "Message" then LocalEnvironment and ExceptionList will be unmodifiable and will be the same as in the input message. If you set the m ... |
| Topic: Setting additional header in HTTP Request Node |
Hoshi
Replies: 12
Views: 9353
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 02, 2016 12:18 pm Subject: Setting additional header in HTTP Request Node |
| Oh, that was my bad. Of course I meant one should set compute mode to "Message" on the Compute node, so that LocalEnvironment is not lost, but I did not mention it. |
| Topic: Setting additional header in HTTP Request Node |
Hoshi
Replies: 12
Views: 9353
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 02, 2016 9:48 am Subject: Setting additional header in HTTP Request Node |
That depends on specific requirements for the flow.
If you need the original message enriched with the data you get from HTTP Request, then you can, for example, store it in the Environment tree be ... |
| Topic: Setting additional header in HTTP Request Node |
Hoshi
Replies: 12
Views: 9353
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 02, 2016 12:51 am Subject: Setting additional header in HTTP Request Node |
It's been almost a year now but still if someone is struggling with the same issue:
source-http (ServiceGatewayFSH_80): Request processing failed: Get Or Head with Content-Length,
the malformed h ... |
