session lock denied

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

session lock denied

SeanTAllen
So...

running normal code, nothing special. works on 2 systems. doesnt work
on the 3rd.

when trying to render a particular page we get:

topaz 1> topaz 1> WAGsSwazooAdaptor Server started on port 9009
----------- Lock not acquired - retrying LOG ENTRY: Session lock
denied: 2075-----------
----------- Lock not acquired - retrying LOG ENTRY: Session lock
denied: 2075-----------
----------- Lock not acquired - retrying LOG ENTRY: Session lock
denied: 2075-----------
----------- Lock not acquired - retrying LOG ENTRY: Session lock
denied: 2075-----------
----------- Lock not acquired - retrying LOG ENTRY: Session lock
denied: 2075-----------
----------- Lock not acquired - retrying LOG ENTRY: Session lock
denied: 2075-----------
----------- Lock not acquired - retrying LOG ENTRY: Session lock
denied: 2075-----------
----------- Lock not acquired - retrying LOG ENTRY: Session lock
denied: 2075-----------
----------- Lock not acquired - retrying LOG ENTRY: Session lock
denied: 2075-----------
----------- Lock not acquired - retrying LOG ENTRY: Session lock
denied: 2075-----------
----------- Internal Swazoo ERROR Encountered: 2010-05-20T07:20:48-07:00
Too many retries: 11
1 GRGemStonePlatform >> logError:title: @2 line 4  [GsMethod OOP 124136961]
2 WAGsSwazooAdaptor >> internalServerErrorFor:message: @10 line 12
[GsMethod OOP 148484865]
3 ComplexBlock in GRGemStonePlatform >>
seasideProcessRequest:adaptor:resultBlock: @17 line 14  [GsMethod OOP
150105857]
4 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
5 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
6 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
7 GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @25
line 16  [GsMethod OOP 150105857]
8 WAGsSwazooAdaptor >> process: @4 line 4  [GsMethod OOP 148485121]
9 WAPluggableSite >> answerTo: @2 line 2  [GsMethod OOP 130287617]
10 WAPluggableSite >> helpResolve: @7 line 3  [GsMethod OOP 130287105]
11 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
12 ComplexBlock in URIResolution >> visitChildrenOf:advancing: @10
line 7  [GsMethod OOP 130667009]
13 Collection >> do: @5 line 10  [GsMethod OOP 1544961]
14 URIResolution >> visitChildrenOf:advancing: @15 line 5  [GsMethod
OOP 130667009]
15 URIResolution >> resolveTransparentComposite: @2 line 2  [GsMethod
OOP 130670337]
16 URIResolution >> resolveServerRoot: @1 line 2  [GsMethod OOP 130668289]
17 ServerRootComposite >> helpResolve: @1 line 2  [GsMethod OOP 131127041]
18 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
19 URIResolution class >> resolveRequest:startingAt: @3 line 2
[GsMethod OOP 130223617]
20 HTTPServer >> answerTo: @3 line 3  [GsMethod OOP 130320897]
21 ComplexBlock in HTTPConnection >> produceResponseFor: @9 line 5
[GsMethod OOP 130933761]
22 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
23 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
24 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
25 HTTPConnection >> produceResponseFor: @23 line 6  [GsMethod OOP 130933761]
26 HTTPConnection >> getAndDispatchMessages @9 line 9  [GsMethod OOP 130934529]
27 ComplexBlock in HTTPConnection >> interact @7 line 6  [GsMethod OOP
130934785]
28 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
29 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
30 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
31 ComplexVCBlock in HTTPConnection >> interact @12 line 9  [GsMethod
OOP 130934785]
32 ComplexBlock in ExecutableBlock >> ifCurtailed: @4 line 6
[GsMethod OOP 67997953]
33 ComplexBlock in ExecutableBlock >> ensure: @4 line 11  [GsMethod OOP 2305281]
34 ComplexBlock in ExecutableBlock >> ensure: @6 line 11  [GsMethod OOP 2305281]
35 ComplexVCBlock in ExecutableBlock >> ifCurtailed: @8 line 8
[GsMethod OOP 67997953]
36 ComplexVCBlock in HTTPConnection >> interact @19 line 13  [GsMethod
OOP 130934785]
37 HTTPConnection >> interact @26 line 18  [GsMethod OOP 130934785]
38 HTTPServer >> acceptConnection @15 line 11  [GsMethod OOP 148109313]
39 ComplexBlock in HTTPServer >> start @13 line 6  [GsMethod OOP 130321921]
40 ComplexBlock in BlockClosure >> repeat @3 line 5  [GsMethod OOP 18247425]
41 ComplexVCBlock in HTTPServer >> start @14 line 6  [GsMethod OOP 130321921]
42 GsProcess >> _startPart2 @15 line 17  [GsMethod OOP 4503553]
43 GsProcess >> _start @1 line 9  [GsMethod OOP 4504065]

any idea what might cause that. we arent opening a new browser window
so the session isnt being duplicated.
Reply | Threaded
Open this post in threaded view
|

Re: session lock denied

Dale Henrichs
Sean Allen wrote:

> So...
>
> running normal code, nothing special. works on 2 systems. doesnt work
> on the 3rd.
>
> when trying to render a particular page we get:
>
> topaz 1> topaz 1> WAGsSwazooAdaptor Server started on port 9009
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Internal Swazoo ERROR Encountered: 2010-05-20T07:20:48-07:00
> Too many retries: 11
> 1 GRGemStonePlatform >> logError:title: @2 line 4  [GsMethod OOP 124136961]
> 2 WAGsSwazooAdaptor >> internalServerErrorFor:message: @10 line 12
> [GsMethod OOP 148484865]
> 3 ComplexBlock in GRGemStonePlatform >>
> seasideProcessRequest:adaptor:resultBlock: @17 line 14  [GsMethod OOP
> 150105857]
> 4 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
> 5 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
> 6 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
> 7 GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @25
> line 16  [GsMethod OOP 150105857]
> 8 WAGsSwazooAdaptor >> process: @4 line 4  [GsMethod OOP 148485121]
> 9 WAPluggableSite >> answerTo: @2 line 2  [GsMethod OOP 130287617]
> 10 WAPluggableSite >> helpResolve: @7 line 3  [GsMethod OOP 130287105]
> 11 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
> 12 ComplexBlock in URIResolution >> visitChildrenOf:advancing: @10
> line 7  [GsMethod OOP 130667009]
> 13 Collection >> do: @5 line 10  [GsMethod OOP 1544961]
> 14 URIResolution >> visitChildrenOf:advancing: @15 line 5  [GsMethod
> OOP 130667009]
> 15 URIResolution >> resolveTransparentComposite: @2 line 2  [GsMethod
> OOP 130670337]
> 16 URIResolution >> resolveServerRoot: @1 line 2  [GsMethod OOP 130668289]
> 17 ServerRootComposite >> helpResolve: @1 line 2  [GsMethod OOP 131127041]
> 18 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
> 19 URIResolution class >> resolveRequest:startingAt: @3 line 2
> [GsMethod OOP 130223617]
> 20 HTTPServer >> answerTo: @3 line 3  [GsMethod OOP 130320897]
> 21 ComplexBlock in HTTPConnection >> produceResponseFor: @9 line 5
> [GsMethod OOP 130933761]
> 22 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
> 23 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
> 24 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
> 25 HTTPConnection >> produceResponseFor: @23 line 6  [GsMethod OOP 130933761]
> 26 HTTPConnection >> getAndDispatchMessages @9 line 9  [GsMethod OOP 130934529]
> 27 ComplexBlock in HTTPConnection >> interact @7 line 6  [GsMethod OOP
> 130934785]
> 28 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
> 29 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
> 30 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
> 31 ComplexVCBlock in HTTPConnection >> interact @12 line 9  [GsMethod
> OOP 130934785]
> 32 ComplexBlock in ExecutableBlock >> ifCurtailed: @4 line 6
> [GsMethod OOP 67997953]
> 33 ComplexBlock in ExecutableBlock >> ensure: @4 line 11  [GsMethod OOP 2305281]
> 34 ComplexBlock in ExecutableBlock >> ensure: @6 line 11  [GsMethod OOP 2305281]
> 35 ComplexVCBlock in ExecutableBlock >> ifCurtailed: @8 line 8
> [GsMethod OOP 67997953]
> 36 ComplexVCBlock in HTTPConnection >> interact @19 line 13  [GsMethod
> OOP 130934785]
> 37 HTTPConnection >> interact @26 line 18  [GsMethod OOP 130934785]
> 38 HTTPServer >> acceptConnection @15 line 11  [GsMethod OOP 148109313]
> 39 ComplexBlock in HTTPServer >> start @13 line 6  [GsMethod OOP 130321921]
> 40 ComplexBlock in BlockClosure >> repeat @3 line 5  [GsMethod OOP 18247425]
> 41 ComplexVCBlock in HTTPServer >> start @14 line 6  [GsMethod OOP 130321921]
> 42 GsProcess >> _startPart2 @15 line 17  [GsMethod OOP 4503553]
> 43 GsProcess >> _start @1 line 9  [GsMethod OOP 4504065]
>
> any idea what might cause that. we arent opening a new browser window
> so the session isnt being duplicated.

It is likely that asynchronous javacscript callbacks are causing the
retry ... although the too many retries must be something else, although
I don't know how many concurrent requests are being sent by javascript
... It seems that Gerhard had noticed a problem in one of the javascript
libraries and even had a workaround...I'll have to dig through the
archives to find it (new mail system with vmware, so I'm experiencing a
major discontinuity in my work flow using a new mail system ...
fortunate that is the only complatnt so far:)

Dale
Reply | Threaded
Open this post in threaded view
|

Re: session lock denied

SeanTAllen
In reply to this post by SeanTAllen
So for posterity...

we had code that was taking too long to execute and then, the front
end server tried proxying to another
swazoo and we got the error.

is there a way to set the timeout with swazoo so after say 60 seconds,
we can free up the session?

On Thu, May 20, 2010 at 10:26 AM, Sean Allen
<[hidden email]> wrote:

> So...
>
> running normal code, nothing special. works on 2 systems. doesnt work
> on the 3rd.
>
> when trying to render a particular page we get:
>
> topaz 1> topaz 1> WAGsSwazooAdaptor Server started on port 9009
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Internal Swazoo ERROR Encountered: 2010-05-20T07:20:48-07:00
> Too many retries: 11
> 1 GRGemStonePlatform >> logError:title: @2 line 4  [GsMethod OOP 124136961]
> 2 WAGsSwazooAdaptor >> internalServerErrorFor:message: @10 line 12
> [GsMethod OOP 148484865]
> 3 ComplexBlock in GRGemStonePlatform >>
> seasideProcessRequest:adaptor:resultBlock: @17 line 14  [GsMethod OOP
> 150105857]
> 4 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
> 5 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
> 6 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
> 7 GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @25
> line 16  [GsMethod OOP 150105857]
> 8 WAGsSwazooAdaptor >> process: @4 line 4  [GsMethod OOP 148485121]
> 9 WAPluggableSite >> answerTo: @2 line 2  [GsMethod OOP 130287617]
> 10 WAPluggableSite >> helpResolve: @7 line 3  [GsMethod OOP 130287105]
> 11 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
> 12 ComplexBlock in URIResolution >> visitChildrenOf:advancing: @10
> line 7  [GsMethod OOP 130667009]
> 13 Collection >> do: @5 line 10  [GsMethod OOP 1544961]
> 14 URIResolution >> visitChildrenOf:advancing: @15 line 5  [GsMethod
> OOP 130667009]
> 15 URIResolution >> resolveTransparentComposite: @2 line 2  [GsMethod
> OOP 130670337]
> 16 URIResolution >> resolveServerRoot: @1 line 2  [GsMethod OOP 130668289]
> 17 ServerRootComposite >> helpResolve: @1 line 2  [GsMethod OOP 131127041]
> 18 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
> 19 URIResolution class >> resolveRequest:startingAt: @3 line 2
> [GsMethod OOP 130223617]
> 20 HTTPServer >> answerTo: @3 line 3  [GsMethod OOP 130320897]
> 21 ComplexBlock in HTTPConnection >> produceResponseFor: @9 line 5
> [GsMethod OOP 130933761]
> 22 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
> 23 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
> 24 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
> 25 HTTPConnection >> produceResponseFor: @23 line 6  [GsMethod OOP 130933761]
> 26 HTTPConnection >> getAndDispatchMessages @9 line 9  [GsMethod OOP 130934529]
> 27 ComplexBlock in HTTPConnection >> interact @7 line 6  [GsMethod OOP
> 130934785]
> 28 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
> 29 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
> 30 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
> 31 ComplexVCBlock in HTTPConnection >> interact @12 line 9  [GsMethod
> OOP 130934785]
> 32 ComplexBlock in ExecutableBlock >> ifCurtailed: @4 line 6
> [GsMethod OOP 67997953]
> 33 ComplexBlock in ExecutableBlock >> ensure: @4 line 11  [GsMethod OOP 2305281]
> 34 ComplexBlock in ExecutableBlock >> ensure: @6 line 11  [GsMethod OOP 2305281]
> 35 ComplexVCBlock in ExecutableBlock >> ifCurtailed: @8 line 8
> [GsMethod OOP 67997953]
> 36 ComplexVCBlock in HTTPConnection >> interact @19 line 13  [GsMethod
> OOP 130934785]
> 37 HTTPConnection >> interact @26 line 18  [GsMethod OOP 130934785]
> 38 HTTPServer >> acceptConnection @15 line 11  [GsMethod OOP 148109313]
> 39 ComplexBlock in HTTPServer >> start @13 line 6  [GsMethod OOP 130321921]
> 40 ComplexBlock in BlockClosure >> repeat @3 line 5  [GsMethod OOP 18247425]
> 41 ComplexVCBlock in HTTPServer >> start @14 line 6  [GsMethod OOP 130321921]
> 42 GsProcess >> _startPart2 @15 line 17  [GsMethod OOP 4503553]
> 43 GsProcess >> _start @1 line 9  [GsMethod OOP 4504065]
>
> any idea what might cause that. we arent opening a new browser window
> so the session isnt being duplicated.
>
Reply | Threaded
Open this post in threaded view
|

Re: session lock denied

Ryan Simmons-2
We have had similar problems with session locks.

Ours were caused by code taking a while to execute and the user clicking on the link again or on another link before the system had a chance to respond.

We worked around it by bringing up a lightbox effect whenever an anchor or button is clicked
Sent via my BlackBerry from Vodacom - let your email find you!

-----Original Message-----
From: Sean Allen <[hidden email]>
Date: Thu, 20 May 2010 15:17:46
To: GemStone Seaside beta discussion<[hidden email]>
Subject: Re: [GS/SS Beta] session lock denied

So for posterity...

we had code that was taking too long to execute and then, the front
end server tried proxying to another
swazoo and we got the error.

is there a way to set the timeout with swazoo so after say 60 seconds,
we can free up the session?

On Thu, May 20, 2010 at 10:26 AM, Sean Allen
<[hidden email]> wrote:

> So...
>
> running normal code, nothing special. works on 2 systems. doesnt work
> on the 3rd.
>
> when trying to render a particular page we get:
>
> topaz 1> topaz 1> WAGsSwazooAdaptor Server started on port 9009
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
> denied: 2075-----------
> ----------- Internal Swazoo ERROR Encountered: 2010-05-20T07:20:48-07:00
> Too many retries: 11
> 1 GRGemStonePlatform >> logError:title: @2 line 4  [GsMethod OOP 124136961]
> 2 WAGsSwazooAdaptor >> internalServerErrorFor:message: @10 line 12
> [GsMethod OOP 148484865]
> 3 ComplexBlock in GRGemStonePlatform >>
> seasideProcessRequest:adaptor:resultBlock: @17 line 14  [GsMethod OOP
> 150105857]
> 4 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
> 5 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
> 6 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
> 7 GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @25
> line 16  [GsMethod OOP 150105857]
> 8 WAGsSwazooAdaptor >> process: @4 line 4  [GsMethod OOP 148485121]
> 9 WAPluggableSite >> answerTo: @2 line 2  [GsMethod OOP 130287617]
> 10 WAPluggableSite >> helpResolve: @7 line 3  [GsMethod OOP 130287105]
> 11 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
> 12 ComplexBlock in URIResolution >> visitChildrenOf:advancing: @10
> line 7  [GsMethod OOP 130667009]
> 13 Collection >> do: @5 line 10  [GsMethod OOP 1544961]
> 14 URIResolution >> visitChildrenOf:advancing: @15 line 5  [GsMethod
> OOP 130667009]
> 15 URIResolution >> resolveTransparentComposite: @2 line 2  [GsMethod
> OOP 130670337]
> 16 URIResolution >> resolveServerRoot: @1 line 2  [GsMethod OOP 130668289]
> 17 ServerRootComposite >> helpResolve: @1 line 2  [GsMethod OOP 131127041]
> 18 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
> 19 URIResolution class >> resolveRequest:startingAt: @3 line 2
> [GsMethod OOP 130223617]
> 20 HTTPServer >> answerTo: @3 line 3  [GsMethod OOP 130320897]
> 21 ComplexBlock in HTTPConnection >> produceResponseFor: @9 line 5
> [GsMethod OOP 130933761]
> 22 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
> 23 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
> 24 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
> 25 HTTPConnection >> produceResponseFor: @23 line 6  [GsMethod OOP 130933761]
> 26 HTTPConnection >> getAndDispatchMessages @9 line 9  [GsMethod OOP 130934529]
> 27 ComplexBlock in HTTPConnection >> interact @7 line 6  [GsMethod OOP
> 130934785]
> 28 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
> 29 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
> 30 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
> 31 ComplexVCBlock in HTTPConnection >> interact @12 line 9  [GsMethod
> OOP 130934785]
> 32 ComplexBlock in ExecutableBlock >> ifCurtailed: @4 line 6
> [GsMethod OOP 67997953]
> 33 ComplexBlock in ExecutableBlock >> ensure: @4 line 11  [GsMethod OOP 2305281]
> 34 ComplexBlock in ExecutableBlock >> ensure: @6 line 11  [GsMethod OOP 2305281]
> 35 ComplexVCBlock in ExecutableBlock >> ifCurtailed: @8 line 8
> [GsMethod OOP 67997953]
> 36 ComplexVCBlock in HTTPConnection >> interact @19 line 13  [GsMethod
> OOP 130934785]
> 37 HTTPConnection >> interact @26 line 18  [GsMethod OOP 130934785]
> 38 HTTPServer >> acceptConnection @15 line 11  [GsMethod OOP 148109313]
> 39 ComplexBlock in HTTPServer >> start @13 line 6  [GsMethod OOP 130321921]
> 40 ComplexBlock in BlockClosure >> repeat @3 line 5  [GsMethod OOP 18247425]
> 41 ComplexVCBlock in HTTPServer >> start @14 line 6  [GsMethod OOP 130321921]
> 42 GsProcess >>_startPart2 @15 line 17  [GsMethod OOP 4503553]
> 43 GsProcess >>_start @1 line 9  [GsMethod OOP 4504065]
>
> any idea what might cause that. we arent opening a new browser window
> so the session isnt being duplicated.
>
Reply | Threaded
Open this post in threaded view
|

Re: session lock denied

Dale Henrichs
In reply to this post by SeanTAllen
Sean Allen wrote:
> So for posterity...
>
> we had code that was taking too long to execute and then, the front
> end server tried proxying to another
> swazoo and we got the error.

"front end server" is that Apache? Can't you tell the "front-end server"
to wait longer before trying again or better yet to not timeout at all?

>
> is there a way to set the timeout with swazoo so after say 60 seconds,
> we can free up the session?

I don't like timeouts because they tend to start firing off when things
  are actually working, but just taking longer than usual (like on a
loaded machine)...then you end up increasing the timeout to the point
where it never fires off:)

I'm not sure what problem the "try again after timeout" is trying to
solve, but I would imagine that there is a more direct solution to the
problem that doesn't involve timeouts.

Dale
Reply | Threaded
Open this post in threaded view
|

Re: session lock denied

SeanTAllen
In reply to this post by Ryan Simmons-2
I'm seeing the same sort of thing.

Biggest problem is that the session lock issue is bringing down the swazoo.

The double click and session lock beyond that would appear to be a real issue.
Not sure how to address as using a lightbox just doesnt work in all cases.

On Thu, May 20, 2010 at 4:08 PM,  <[hidden email]> wrote:

> We have had similar problems with session locks.
>
> Ours were caused by code taking a while to execute and the user clicking on the link again or on another link before the system had a chance to respond.
>
> We worked around it by bringing up a lightbox effect whenever an anchor or button is clicked
> Sent via my BlackBerry from Vodacom - let your email find you!
>
> -----Original Message-----
> From: Sean Allen <[hidden email]>
> Date: Thu, 20 May 2010 15:17:46
> To: GemStone Seaside beta discussion<[hidden email]>
> Subject: Re: [GS/SS Beta] session lock denied
>
> So for posterity...
>
> we had code that was taking too long to execute and then, the front
> end server tried proxying to another
> swazoo and we got the error.
>
> is there a way to set the timeout with swazoo so after say 60 seconds,
> we can free up the session?
>
> On Thu, May 20, 2010 at 10:26 AM, Sean Allen
> <[hidden email]> wrote:
>> So...
>>
>> running normal code, nothing special. works on 2 systems. doesnt work
>> on the 3rd.
>>
>> when trying to render a particular page we get:
>>
>> topaz 1> topaz 1> WAGsSwazooAdaptor Server started on port 9009
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Internal Swazoo ERROR Encountered: 2010-05-20T07:20:48-07:00
>> Too many retries: 11
>> 1 GRGemStonePlatform >> logError:title: @2 line 4  [GsMethod OOP 124136961]
>> 2 WAGsSwazooAdaptor >> internalServerErrorFor:message: @10 line 12
>> [GsMethod OOP 148484865]
>> 3 ComplexBlock in GRGemStonePlatform >>
>> seasideProcessRequest:adaptor:resultBlock: @17 line 14  [GsMethod OOP
>> 150105857]
>> 4 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
>> 5 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
>> 6 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
>> 7 GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @25
>> line 16  [GsMethod OOP 150105857]
>> 8 WAGsSwazooAdaptor >> process: @4 line 4  [GsMethod OOP 148485121]
>> 9 WAPluggableSite >> answerTo: @2 line 2  [GsMethod OOP 130287617]
>> 10 WAPluggableSite >> helpResolve: @7 line 3  [GsMethod OOP 130287105]
>> 11 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
>> 12 ComplexBlock in URIResolution >> visitChildrenOf:advancing: @10
>> line 7  [GsMethod OOP 130667009]
>> 13 Collection >> do: @5 line 10  [GsMethod OOP 1544961]
>> 14 URIResolution >> visitChildrenOf:advancing: @15 line 5  [GsMethod
>> OOP 130667009]
>> 15 URIResolution >> resolveTransparentComposite: @2 line 2  [GsMethod
>> OOP 130670337]
>> 16 URIResolution >> resolveServerRoot: @1 line 2  [GsMethod OOP 130668289]
>> 17 ServerRootComposite >> helpResolve: @1 line 2  [GsMethod OOP 131127041]
>> 18 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
>> 19 URIResolution class >> resolveRequest:startingAt: @3 line 2
>> [GsMethod OOP 130223617]
>> 20 HTTPServer >> answerTo: @3 line 3  [GsMethod OOP 130320897]
>> 21 ComplexBlock in HTTPConnection >> produceResponseFor: @9 line 5
>> [GsMethod OOP 130933761]
>> 22 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
>> 23 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
>> 24 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
>> 25 HTTPConnection >> produceResponseFor: @23 line 6  [GsMethod OOP 130933761]
>> 26 HTTPConnection >> getAndDispatchMessages @9 line 9  [GsMethod OOP 130934529]
>> 27 ComplexBlock in HTTPConnection >> interact @7 line 6  [GsMethod OOP
>> 130934785]
>> 28 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
>> 29 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
>> 30 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
>> 31 ComplexVCBlock in HTTPConnection >> interact @12 line 9  [GsMethod
>> OOP 130934785]
>> 32 ComplexBlock in ExecutableBlock >> ifCurtailed: @4 line 6
>> [GsMethod OOP 67997953]
>> 33 ComplexBlock in ExecutableBlock >> ensure: @4 line 11  [GsMethod OOP 2305281]
>> 34 ComplexBlock in ExecutableBlock >> ensure: @6 line 11  [GsMethod OOP 2305281]
>> 35 ComplexVCBlock in ExecutableBlock >> ifCurtailed: @8 line 8
>> [GsMethod OOP 67997953]
>> 36 ComplexVCBlock in HTTPConnection >> interact @19 line 13  [GsMethod
>> OOP 130934785]
>> 37 HTTPConnection >> interact @26 line 18  [GsMethod OOP 130934785]
>> 38 HTTPServer >> acceptConnection @15 line 11  [GsMethod OOP 148109313]
>> 39 ComplexBlock in HTTPServer >> start @13 line 6  [GsMethod OOP 130321921]
>> 40 ComplexBlock in BlockClosure >> repeat @3 line 5  [GsMethod OOP 18247425]
>> 41 ComplexVCBlock in HTTPServer >> start @14 line 6  [GsMethod OOP 130321921]
>> 42 GsProcess >>_startPart2 @15 line 17  [GsMethod OOP 4503553]
>> 43 GsProcess >>_start @1 line 9  [GsMethod OOP 4504065]
>>
>> any idea what might cause that. we arent opening a new browser window
>> so the session isnt being duplicated.
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: session lock denied

SeanTAllen
Correction, the gem is still running but the swazoo becomes entirely
unresponsive.

On Fri, May 21, 2010 at 10:04 AM, Sean Allen
<[hidden email]> wrote:

> I'm seeing the same sort of thing.
>
> Biggest problem is that the session lock issue is bringing down the swazoo.
>
> The double click and session lock beyond that would appear to be a real issue.
> Not sure how to address as using a lightbox just doesnt work in all cases.
>
> On Thu, May 20, 2010 at 4:08 PM,  <[hidden email]> wrote:
>> We have had similar problems with session locks.
>>
>> Ours were caused by code taking a while to execute and the user clicking on the link again or on another link before the system had a chance to respond.
>>
>> We worked around it by bringing up a lightbox effect whenever an anchor or button is clicked
>> Sent via my BlackBerry from Vodacom - let your email find you!
>>
>> -----Original Message-----
>> From: Sean Allen <[hidden email]>
>> Date: Thu, 20 May 2010 15:17:46
>> To: GemStone Seaside beta discussion<[hidden email]>
>> Subject: Re: [GS/SS Beta] session lock denied
>>
>> So for posterity...
>>
>> we had code that was taking too long to execute and then, the front
>> end server tried proxying to another
>> swazoo and we got the error.
>>
>> is there a way to set the timeout with swazoo so after say 60 seconds,
>> we can free up the session?
>>
>> On Thu, May 20, 2010 at 10:26 AM, Sean Allen
>> <[hidden email]> wrote:
>>> So...
>>>
>>> running normal code, nothing special. works on 2 systems. doesnt work
>>> on the 3rd.
>>>
>>> when trying to render a particular page we get:
>>>
>>> topaz 1> topaz 1> WAGsSwazooAdaptor Server started on port 9009
>>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>>> denied: 2075-----------
>>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>>> denied: 2075-----------
>>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>>> denied: 2075-----------
>>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>>> denied: 2075-----------
>>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>>> denied: 2075-----------
>>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>>> denied: 2075-----------
>>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>>> denied: 2075-----------
>>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>>> denied: 2075-----------
>>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>>> denied: 2075-----------
>>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>>> denied: 2075-----------
>>> ----------- Internal Swazoo ERROR Encountered: 2010-05-20T07:20:48-07:00
>>> Too many retries: 11
>>> 1 GRGemStonePlatform >> logError:title: @2 line 4  [GsMethod OOP 124136961]
>>> 2 WAGsSwazooAdaptor >> internalServerErrorFor:message: @10 line 12
>>> [GsMethod OOP 148484865]
>>> 3 ComplexBlock in GRGemStonePlatform >>
>>> seasideProcessRequest:adaptor:resultBlock: @17 line 14  [GsMethod OOP
>>> 150105857]
>>> 4 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
>>> 5 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
>>> 6 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
>>> 7 GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @25
>>> line 16  [GsMethod OOP 150105857]
>>> 8 WAGsSwazooAdaptor >> process: @4 line 4  [GsMethod OOP 148485121]
>>> 9 WAPluggableSite >> answerTo: @2 line 2  [GsMethod OOP 130287617]
>>> 10 WAPluggableSite >> helpResolve: @7 line 3  [GsMethod OOP 130287105]
>>> 11 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
>>> 12 ComplexBlock in URIResolution >> visitChildrenOf:advancing: @10
>>> line 7  [GsMethod OOP 130667009]
>>> 13 Collection >> do: @5 line 10  [GsMethod OOP 1544961]
>>> 14 URIResolution >> visitChildrenOf:advancing: @15 line 5  [GsMethod
>>> OOP 130667009]
>>> 15 URIResolution >> resolveTransparentComposite: @2 line 2  [GsMethod
>>> OOP 130670337]
>>> 16 URIResolution >> resolveServerRoot: @1 line 2  [GsMethod OOP 130668289]
>>> 17 ServerRootComposite >> helpResolve: @1 line 2  [GsMethod OOP 131127041]
>>> 18 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
>>> 19 URIResolution class >> resolveRequest:startingAt: @3 line 2
>>> [GsMethod OOP 130223617]
>>> 20 HTTPServer >> answerTo: @3 line 3  [GsMethod OOP 130320897]
>>> 21 ComplexBlock in HTTPConnection >> produceResponseFor: @9 line 5
>>> [GsMethod OOP 130933761]
>>> 22 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
>>> 23 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
>>> 24 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
>>> 25 HTTPConnection >> produceResponseFor: @23 line 6  [GsMethod OOP 130933761]
>>> 26 HTTPConnection >> getAndDispatchMessages @9 line 9  [GsMethod OOP 130934529]
>>> 27 ComplexBlock in HTTPConnection >> interact @7 line 6  [GsMethod OOP
>>> 130934785]
>>> 28 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
>>> 29 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
>>> 30 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP 9449985]
>>> 31 ComplexVCBlock in HTTPConnection >> interact @12 line 9  [GsMethod
>>> OOP 130934785]
>>> 32 ComplexBlock in ExecutableBlock >> ifCurtailed: @4 line 6
>>> [GsMethod OOP 67997953]
>>> 33 ComplexBlock in ExecutableBlock >> ensure: @4 line 11  [GsMethod OOP 2305281]
>>> 34 ComplexBlock in ExecutableBlock >> ensure: @6 line 11  [GsMethod OOP 2305281]
>>> 35 ComplexVCBlock in ExecutableBlock >> ifCurtailed: @8 line 8
>>> [GsMethod OOP 67997953]
>>> 36 ComplexVCBlock in HTTPConnection >> interact @19 line 13  [GsMethod
>>> OOP 130934785]
>>> 37 HTTPConnection >> interact @26 line 18  [GsMethod OOP 130934785]
>>> 38 HTTPServer >> acceptConnection @15 line 11  [GsMethod OOP 148109313]
>>> 39 ComplexBlock in HTTPServer >> start @13 line 6  [GsMethod OOP 130321921]
>>> 40 ComplexBlock in BlockClosure >> repeat @3 line 5  [GsMethod OOP 18247425]
>>> 41 ComplexVCBlock in HTTPServer >> start @14 line 6  [GsMethod OOP 130321921]
>>> 42 GsProcess >>_startPart2 @15 line 17  [GsMethod OOP 4503553]
>>> 43 GsProcess >>_start @1 line 9  [GsMethod OOP 4504065]
>>>
>>> any idea what might cause that. we arent opening a new browser window
>>> so the session isnt being duplicated.
>>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: session lock denied

SeanTAllen
In reply to this post by Dale Henrichs
I've tracked this back on our end to processes taking a bit and people
click click clicking.
O those impatient people.

On Thu, May 20, 2010 at 12:45 PM, Dale Henrichs <[hidden email]> wrote:

> Sean Allen wrote:
>>
>> So...
>>
>> running normal code, nothing special. works on 2 systems. doesnt work
>> on the 3rd.
>>
>> when trying to render a particular page we get:
>>
>> topaz 1> topaz 1> WAGsSwazooAdaptor Server started on port 9009
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Lock not acquired - retrying LOG ENTRY: Session lock
>> denied: 2075-----------
>> ----------- Internal Swazoo ERROR Encountered: 2010-05-20T07:20:48-07:00
>> Too many retries: 11
>> 1 GRGemStonePlatform >> logError:title: @2 line 4  [GsMethod OOP
>> 124136961]
>> 2 WAGsSwazooAdaptor >> internalServerErrorFor:message: @10 line 12
>> [GsMethod OOP 148484865]
>> 3 ComplexBlock in GRGemStonePlatform >>
>> seasideProcessRequest:adaptor:resultBlock: @17 line 14  [GsMethod OOP
>> 150105857]
>> 4 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
>> 5 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
>> 6 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP
>> 9449985]
>> 7 GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @25
>> line 16  [GsMethod OOP 150105857]
>> 8 WAGsSwazooAdaptor >> process: @4 line 4  [GsMethod OOP 148485121]
>> 9 WAPluggableSite >> answerTo: @2 line 2  [GsMethod OOP 130287617]
>> 10 WAPluggableSite >> helpResolve: @7 line 3  [GsMethod OOP 130287105]
>> 11 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
>> 12 ComplexBlock in URIResolution >> visitChildrenOf:advancing: @10
>> line 7  [GsMethod OOP 130667009]
>> 13 Collection >> do: @5 line 10  [GsMethod OOP 1544961]
>> 14 URIResolution >> visitChildrenOf:advancing: @15 line 5  [GsMethod
>> OOP 130667009]
>> 15 URIResolution >> resolveTransparentComposite: @2 line 2  [GsMethod
>> OOP 130670337]
>> 16 URIResolution >> resolveServerRoot: @1 line 2  [GsMethod OOP 130668289]
>> 17 ServerRootComposite >> helpResolve: @1 line 2  [GsMethod OOP 131127041]
>> 18 URIResolution >> visitResource: @1 line 2  [GsMethod OOP 130668545]
>> 19 URIResolution class >> resolveRequest:startingAt: @3 line 2
>> [GsMethod OOP 130223617]
>> 20 HTTPServer >> answerTo: @3 line 3  [GsMethod OOP 130320897]
>> 21 ComplexBlock in HTTPConnection >> produceResponseFor: @9 line 5
>> [GsMethod OOP 130933761]
>> 22 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
>> 23 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
>> 24 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP
>> 9449985]
>> 25 HTTPConnection >> produceResponseFor: @23 line 6  [GsMethod OOP
>> 130933761]
>> 26 HTTPConnection >> getAndDispatchMessages @9 line 9  [GsMethod OOP
>> 130934529]
>> 27 ComplexBlock in HTTPConnection >> interact @7 line 6  [GsMethod OOP
>> 130934785]
>> 28 ExceptionHandler >> doTryBlock: @9 line 7  [GsMethod OOP 11916289]
>> 29 ExceptionHandler >> try:on:do: @15 line 18  [GsMethod OOP 11913985]
>> 30 ComplexBlock in ExecutableBlock >> on:do: @2 line 8  [GsMethod OOP
>> 9449985]
>> 31 ComplexVCBlock in HTTPConnection >> interact @12 line 9  [GsMethod
>> OOP 130934785]
>> 32 ComplexBlock in ExecutableBlock >> ifCurtailed: @4 line 6
>> [GsMethod OOP 67997953]
>> 33 ComplexBlock in ExecutableBlock >> ensure: @4 line 11  [GsMethod OOP
>> 2305281]
>> 34 ComplexBlock in ExecutableBlock >> ensure: @6 line 11  [GsMethod OOP
>> 2305281]
>> 35 ComplexVCBlock in ExecutableBlock >> ifCurtailed: @8 line 8
>> [GsMethod OOP 67997953]
>> 36 ComplexVCBlock in HTTPConnection >> interact @19 line 13  [GsMethod
>> OOP 130934785]
>> 37 HTTPConnection >> interact @26 line 18  [GsMethod OOP 130934785]
>> 38 HTTPServer >> acceptConnection @15 line 11  [GsMethod OOP 148109313]
>> 39 ComplexBlock in HTTPServer >> start @13 line 6  [GsMethod OOP
>> 130321921]
>> 40 ComplexBlock in BlockClosure >> repeat @3 line 5  [GsMethod OOP
>> 18247425]
>> 41 ComplexVCBlock in HTTPServer >> start @14 line 6  [GsMethod OOP
>> 130321921]
>> 42 GsProcess >> _startPart2 @15 line 17  [GsMethod OOP 4503553]
>> 43 GsProcess >> _start @1 line 9  [GsMethod OOP 4504065]
>>
>> any idea what might cause that. we arent opening a new browser window
>> so the session isnt being duplicated.
>
> It is likely that asynchronous javacscript callbacks are causing the retry
> ... although the too many retries must be something else, although I don't
> know how many concurrent requests are being sent by javascript ... It seems
> that Gerhard had noticed a problem in one of the javascript libraries and
> even had a workaround...I'll have to dig through the archives to find it
> (new mail system with vmware, so I'm experiencing a major discontinuity in
> my work flow using a new mail system ... fortunate that is the only
> complatnt so far:)
>
> Dale
>
Reply | Threaded
Open this post in threaded view
|

Re: session lock denied

SeanTAllen
In reply to this post by Dale Henrichs
On Thu, May 20, 2010 at 7:22 PM, Dale Henrichs <[hidden email]> wrote:

> Sean Allen wrote:
>>
>> So for posterity...
>>
>> we had code that was taking too long to execute and then, the front
>> end server tried proxying to another
>> swazoo and we got the error.
>
> "front end server" is that Apache? Can't you tell the "front-end server" to
> wait longer before trying again or better yet to not timeout at all?

i should be more clear on that for posterity.

user clicks on link. it takes a long time, gem has session locked.
user gets antsy, clicks again.
nginx proxies to a different gem ( as the one that has the session is busy )
second gem hits the session lock error.