Smalltalk › Instantiations

Debugging GLORP queries in Seaside App makes Image unresponsive to HTTP Requests

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

jtuchel

Debugging GLORP queries in Seaside App makes Image unresponsive to HTTP Requests

Hi,

not sure how I could describe it any better, but if I set a breakpoint in a callback method which issues an SQL statement via GLORP (Not sure if GLORP is the problem or VA Database classes) and step through or over a #readManyOf:where:, the image freezes completely.
You can still press the emergency button and get back to the debugger and work in the IDE, but the image will not answer any http requests any more until at least the WASstServerAdapter is stopped and removed and a new one started.

I have no idea what the exact reason for this behaviour is, but it is reproducible.

Any ideas?

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/vRU0Z2qPwsoJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

jtuchel

Re: Debugging GLORP queries in Seaside App makes Image unresponsive to HTTP Requests

Sorry,

VA Smalltalk 8.5 (haven't tried any other version) on Windows XP and Windows 7x64.

Joachim

Am Donnerstag, 3. Mai 2012 13:50:51 UTC+2 schrieb [hidden email]:

Hi,

not sure how I could describe it any better, but if I set a breakpoint in a callback method which issues an SQL statement via GLORP (Not sure if GLORP is the problem or VA Database classes) and step through or over a #readManyOf:where:, the image freezes completely.
You can still press the emergency button and get back to the debugger and work in the IDE, but the image will not answer any http requests any more until at least the WASstServerAdapter is stopped and removed and a new one started.

I have no idea what the exact reason for this behaviour is, but it is reproducible.

Any ideas?

Joachim

Am Donnerstag, 3. Mai 2012 13:50:51 UTC+2 schrieb [hidden email]:

Hi,

not sure how I could describe it any better, but if I set a breakpoint in a callback method which issues an SQL statement via GLORP (Not sure if GLORP is the problem or VA Database classes) and step through or over a #readManyOf:where:, the image freezes completely.
You can still press the emergency button and get back to the debugger and work in the IDE, but the image will not answer any http requests any more until at least the WASstServerAdapter is stopped and removed and a new one started.

I have no idea what the exact reason for this behaviour is, but it is reproducible.

Any ideas?

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/3HyMnecNut8J.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

jtuchel

Re: Debugging GLORP queries in Seaside App makes Image unresponsive to HTTP Requests

One more detail:

stopping the frozen WASstServerAdapter almost always brings up a debugger and a message box: failed attempt to add dead session to debugger. The debugger has no stack trace then.

Am Donnerstag, 3. Mai 2012 13:52:30 UTC+2 schrieb [hidden email]:

Sorry,

VA Smalltalk 8.5 (haven't tried any other version) on Windows XP and Windows 7x64.

Joachim

Am Donnerstag, 3. Mai 2012 13:50:51 UTC+2 schrieb [hidden email]:
Hi,

not sure how I could describe it any better, but if I set a breakpoint in a callback method which issues an SQL statement via GLORP (Not sure if GLORP is the problem or VA Database classes) and step through or over a #readManyOf:where:, the image freezes completely.
You can still press the emergency button and get back to the debugger and work in the IDE, but the image will not answer any http requests any more until at least the WASstServerAdapter is stopped and removed and a new one started.

I have no idea what the exact reason for this behaviour is, but it is reproducible.

Any ideas?

Joachim

Am Donnerstag, 3. Mai 2012 13:50:51 UTC+2 schrieb [hidden email]:
Hi,

not sure how I could describe it any better, but if I set a breakpoint in a callback method which issues an SQL statement via GLORP (Not sure if GLORP is the problem or VA Database classes) and step through or over a #readManyOf:where:, the image freezes completely.
You can still press the emergency button and get back to the debugger and work in the IDE, but the image will not answer any http requests any more until at least the WASstServerAdapter is stopped and removed and a new one started.

I have no idea what the exact reason for this behaviour is, but it is reproducible.

Any ideas?

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/G85y32R8Q98J.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

jtuchel

Re: Debugging GLORP queries in Seaside App makes Image unresponsive to HTTP Requests

Hi there,

I'd like to bring this issue up again, because it is time consuming and seems to make the image instable over time. Once I've had this a dozen times or so, VAST hangs completely.

Joachim

Am Donnerstag, 3. Mai 2012 14:17:42 UTC+2 schrieb [hidden email]:

One more detail:

stopping the frozen WASstServerAdapter almost always brings up a debugger and a message box: failed attempt to add dead session to debugger. The debugger has no stack trace then.

Am Donnerstag, 3. Mai 2012 13:52:30 UTC+2 schrieb [hidden email]:
Sorry,

VA Smalltalk 8.5 (haven't tried any other version) on Windows XP and Windows 7x64.

Joachim

Am Donnerstag, 3. Mai 2012 13:50:51 UTC+2 schrieb [hidden email]:
Hi,

not sure how I could describe it any better, but if I set a breakpoint in a callback method which issues an SQL statement via GLORP (Not sure if GLORP is the problem or VA Database classes) and step through or over a #readManyOf:where:, the image freezes completely.
You can still press the emergency button and get back to the debugger and work in the IDE, but the image will not answer any http requests any more until at least the WASstServerAdapter is stopped and removed and a new one started.

I have no idea what the exact reason for this behaviour is, but it is reproducible.

Any ideas?

Joachim

Am Donnerstag, 3. Mai 2012 13:50:51 UTC+2 schrieb [hidden email]:
Hi,

not sure how I could describe it any better, but if I set a breakpoint in a callback method which issues an SQL statement via GLORP (Not sure if GLORP is the problem or VA Database classes) and step through or over a #readManyOf:where:, the image freezes completely.
You can still press the emergency button and get back to the debugger and work in the IDE, but the image will not answer any http requests any more until at least the WASstServerAdapter is stopped and removed and a new one started.

I have no idea what the exact reason for this behaviour is, but it is reproducible.

Any ideas?

Joachim

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

jtuchel

Re: Debugging GLORP queries in Seaside App makes Image unresponsive to HTTP Requests

In reply to this post by jtuchel

HI there,

I'd like to bring this issue back up - Once I've had this problem maybe 5 times, the image often hangs completely and I have to use the task manager to kill VAST.

This is happening in at least since VAST 8.5.0 and is still happening in VAST 8.5.2 on bith XP SP3 and Win 7.

Joachim

Am Donnerstag, 3. Mai 2012 14:17:42 UTC+2 schrieb [hidden email]:

One more detail:

stopping the frozen WASstServerAdapter almost always brings up a debugger and a message box: failed attempt to add dead session to debugger. The debugger has no stack trace then.

Am Donnerstag, 3. Mai 2012 13:52:30 UTC+2 schrieb [hidden email]:
Sorry,

VA Smalltalk 8.5 (haven't tried any other version) on Windows XP and Windows 7x64.

Joachim

Am Donnerstag, 3. Mai 2012 13:50:51 UTC+2 schrieb [hidden email]:
Hi,

not sure how I could describe it any better, but if I set a breakpoint in a callback method which issues an SQL statement via GLORP (Not sure if GLORP is the problem or VA Database classes) and step through or over a #readManyOf:where:, the image freezes completely.
You can still press the emergency button and get back to the debugger and work in the IDE, but the image will not answer any http requests any more until at least the WASstServerAdapter is stopped and removed and a new one started.

I have no idea what the exact reason for this behaviour is, but it is reproducible.

Any ideas?

Joachim

Am Donnerstag, 3. Mai 2012 13:50:51 UTC+2 schrieb [hidden email]:
Hi,

not sure how I could describe it any better, but if I set a breakpoint in a callback method which issues an SQL statement via GLORP (Not sure if GLORP is the problem or VA Database classes) and step through or over a #readManyOf:where:, the image freezes completely.
You can still press the emergency button and get back to the debugger and work in the IDE, but the image will not answer any http requests any more until at least the WASstServerAdapter is stopped and removed and a new one started.

I have no idea what the exact reason for this behaviour is, but it is reproducible.

Any ideas?

Joachim