Four Js Development Tools Forum

Discussions by product => GWS => Topic started by: . on July 26, 2012, 12:01:46 pm



Title: Infinite gwsproxy error log file with POOL (V. 2.32.15)
Post by: . on July 26, 2012, 12:01:46 pm
I'm observing a strange behaviour when starting a webservice through fastcgidispatch.
I have a configuration file my_service.xcf like this one:
    ...
    <ENVIRONMENT_VARIABLE Id="FGLWSDEBUG">1</ENVIRONMENT_VARIABLE>
    <PATH>/my_path/bin</PATH>
    <MODULE>Ws_test.42r</MODULE>
    <POOL>
        <START>2</START>
        <MIN_AVAILABLE>1</MIN_AVAILABLE>
        <MAX_AVAILABLE>2</MAX_AVAILABLE>
    </POOL>
    ...

When the service is invoked (by example querying for a wsdl) the gwsproxy start two instances of Ws_test.42r and they appears to be correctly working.
But the logfile gwsproxy-Ws_test.log grows unwieldy with repeated error messages:
...
09:11:10.927951 "ERROR-8454262"
WS-DEBUG (IO ERROR)
Class: TCPConnection::atomicReceive()
Msg: TCP input stream shut down.
Code: 75
WS-DEBUG END
WS-DEBUG (HTTP ERROR)
Class: HTTPServerAsImpl::beginRequest()
Msg: Connection to As is closed, unable to process request.
WS-DEBUG END
...

This does not happens if i turn off the debugger as well as if I set START,MIN & MAX parameters to "1" in POOL section of config file.
IMPORTANT: I have omitted the FGLAPPSERVER environment variable as per Genero manuals for deployment environment to avoid conflict on used tcp port.

There seems to be also a conflict between instantiated DVM.
In this situation is impossible to debug a webservice in deployment environment.
Is there anybody having the same behaviour or some suggestion about workaround ?

Thanks for your attention.
Enrico.




Title: Re: Infinite gwsproxy error log file with POOL (V. 2.32.15)
Post by: Sisavanh S. on July 26, 2012, 02:30:06 pm
Hi,

It is support question. I suggest that you contact your local support center.
Provide them with a test program to replicate your issue or a GAS detailed log, see FAQ https://4js.com/en/support/faq/index.php?c=16&highlight=detailed%20log#7.

Thanks.
Many regards,