Kbase P122059: CGI messenger fails when the MsgrTrace logging is turned on when QUERY_STRING is very long
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/30/2011 |
|
Status: Verified
SYMPTOM(s):
CGI messenger fails when the MsgrTrace logging is turned on when QUERY_STRING is very long
In UNIX, the errors 6402, 6397 and 6400 are apparent in the WebSpeed Server log file:
WTA: WebSendMessage() Could not connect to WTB: npp_connect() failed with error: -2. (6402)
WTA: WebSendMessage() Could not connect to WTB: npp_connect() failed with error: . (6402)
WTA: npp_send()failed while sending terminate message! Error: -70. (6397)
WTA: npp_send() failed while sending terminate message! Error: . (6397)
WTA: Failed to notify broker of state information! (6400)
In Windows, the error 6275 is apparent
find_Section of %DLC%\properties\ubroker.properties for section NameServer.XXXXXXXXXXXXXXXXXXX failed: WebSpeed error 10004, System error 0, Specified Service Name does not exist (6275)
<opname> failed: WebSpeed error <ws_error>, System error <errno>, <errordesc> (6275)
Where XXXXXXXXXXXXXXXXXX is part of the query string
FACT(s) (Environment):
OpenEdge 10.1A
OpenEdge 10.1B
All Supported Operating Systems
The size of QUERY_STRING causes the messenger to fail is around 1024 characters or higher
CAUSE:
Bug# OE00145584
FIX:
Upgrade to OE10.1B01 or later
Or,
If an upgrade is not possible, turn-off the MsgrTrace:2 logging under the WebSpeed messenger by removing it from the Logging Entry Types section under the Messenger Logging Setting.
note:This is a viable work around except if the Messenger is WSISA, in that case , the issue is not tied to logging and an upgrade is the only option.