Is there a way to have a "stack dump" response in Zinc?
#debugMode is good for development, but I'm having an "Internal Error:
4", that I don't know how to trace.
GET /web HTTP/1.1
Host: x.y.z:8090
User-Agent: curl/7.58.0
Accept: /
< HTTP/1.1 500 Internal Server Error
< Content-Length: 512
< Content-Type: text/plain;charset=utf-8
< Server: Zinc HTTP Components 1.0 (Pharo/8.0)
< Date: Mon, 26 Jul 2021 00:45:39 GMT
<
Regards!
Esteban A. Maringolo
Hi Esteban,
On 26 Jul 2021, at 02:47, Esteban Maringolo emaringolo@gmail.com wrote:
Is there a way to have a "stack dump" response in Zinc?
#debugMode is good for development, but I'm having an "Internal Error:
4", that I don't know how to trace.
GET /web HTTP/1.1
Host: x.y.z:8090
User-Agent: curl/7.58.0
Accept: /
< HTTP/1.1 500 Internal Server Error
< Content-Length: 512
< Content-Type: text/plain;charset=utf-8
< Server: Zinc HTTP Components 1.0 (Pharo/8.0)
< Date: Mon, 26 Jul 2021 00:45:39 GMT
<
Regards!
Esteban A. Maringolo
Searching the source code of my image, I only find 'Internal Error' in WAExceptionHandler/WAResponseGenerator, not in Zn code. Furthermore, printing 4 there would be weird (as it is the exception message).
Is this a plain Zn response or a Seaside response ?
I know that Seaside has more logging options.
Zn does not have an exception logging mechanism that dumps a stack trace, only the debugMode for interactive development. I see you used curl, can't you fire the request against your dev image then ?
Sven
Hi Sven,
That's what I wanted to know, I made a quick change to it and pushed
it to the staging server (where I'm having the error), but I forgot to
simply search for the string, and now I confirm this is returned by
Seaside's response generator in the exception handler.
I don't know where the 4 comes from, and it only happens in
production, but replacing it with another exception handler gives me a
better understanding of what might be going on. It seems there was a
change in some dependency (seems like Glorp) that's affecting my
staging server.
Thanks!
Esteban A. Maringolo
On Mon, Jul 26, 2021 at 3:16 AM Sven Van Caekenberghe sven@stfx.eu wrote:
Hi Esteban,
On 26 Jul 2021, at 02:47, Esteban Maringolo emaringolo@gmail.com wrote:
Is there a way to have a "stack dump" response in Zinc?
#debugMode is good for development, but I'm having an "Internal Error:
4", that I don't know how to trace.
- Trying 167.71.182.110...
- TCP_NODELAY set
- Connected to fore.base.golf (167.71.182.110) port 8090 (#0)
GET /web HTTP/1.1
Host: x.y.z:8090
User-Agent: curl/7.58.0
Accept: /< HTTP/1.1 500 Internal Server Error
< Content-Length: 512
< Content-Type: text/plain;charset=utf-8
< Server: Zinc HTTP Components 1.0 (Pharo/8.0)
< Date: Mon, 26 Jul 2021 00:45:39 GMT
<
- Connection #0 to host x.y.z left intact
Internal Error: 4Regards!
Esteban A. Maringolo
Searching the source code of my image, I only find 'Internal Error' in WAExceptionHandler/WAResponseGenerator, not in Zn code. Furthermore, printing 4 there would be weird (as it is the exception message).
Is this a plain Zn response or a Seaside response ?
I know that Seaside has more logging options.
Zn does not have an exception logging mechanism that dumps a stack trace, only the debugMode for interactive development. I see you used curl, can't you fire the request against your dev image then ?
Sven
maybe
ex signalerContext errorReportOn: aStream
can show you more info
El lun, 26 jul 2021 a las 13:56, Esteban Maringolo (emaringolo@gmail.com)
escribió:
Hi Sven,
That's what I wanted to know, I made a quick change to it and pushed
it to the staging server (where I'm having the error), but I forgot to
simply search for the string, and now I confirm this is returned by
Seaside's response generator in the exception handler.
I don't know where the 4 comes from, and it only happens in
production, but replacing it with another exception handler gives me a
better understanding of what might be going on. It seems there was a
change in some dependency (seems like Glorp) that's affecting my
staging server.
Thanks!
Esteban A. Maringolo
On Mon, Jul 26, 2021 at 3:16 AM Sven Van Caekenberghe sven@stfx.eu
wrote:
wrote:
Is there a way to have a "stack dump" response in Zinc?
#debugMode is good for development, but I'm having an "Internal Error:
4", that I don't know how to trace.
GET /web HTTP/1.1
Host: x.y.z:8090
User-Agent: curl/7.58.0
Accept: /
< HTTP/1.1 500 Internal Server Error
< Content-Length: 512
< Content-Type: text/plain;charset=utf-8
< Server: Zinc HTTP Components 1.0 (Pharo/8.0)
< Date: Mon, 26 Jul 2021 00:45:39 GMT
<
Regards!
Esteban A. Maringolo
Searching the source code of my image, I only find 'Internal Error' in
WAExceptionHandler/WAResponseGenerator, not in Zn code. Furthermore,
printing 4 there would be weird (as it is the exception message).
Is this a plain Zn response or a Seaside response ?
I know that Seaside has more logging options.
Zn does not have an exception logging mechanism that dumps a stack
trace, only the debugMode for interactive development. I see you used curl,
can't you fire the request against your dev image then ?
Sven