sessions not being pushed out to all nodes in the
cluster (I've pressed logout but I'm still logged in - posted about this
before).
Any help would be greatly appreciated.
rgds,
Richard
Richard Grantham
Development
---
rgrant...@limehousesoftware.co.uk
Limehouse Software
:47
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Cluster sessions don't expire
On Dec 4, 2008, at 9:31 AM, Richard Grantham wrote:
Yes, the logout code calls session.invalidate() and it works fine. I
have some application logic
not expire after the configured period of inactivity.
I'm using Resin-Pro 3.1.7a in a three-node cluster.
Is this a known issue or am I able to configure my way out of it?
rgds,
Richard
Richard Grantham
Development
---
[EMAIL PROTECTED]
Limehouse Software Ltd
DDI: (020
for the Resin application server
Subject: Re: [Resin-interest] Cluster sessions don't expire
On Dec 4, 2008, at 2:43 AM, Richard Grantham wrote:
My woes with clustered sessions and Resin never seem to end!
We switched from database-backed sessions to clustered sessions due to
issue whereby
it.
Richard Grantham
Development
---
[EMAIL PROTECTED]
Limehouse Software Ltd
DDI: (020) 7566 3336
Main: (020) 7566 3320
Fax: (020) 7566 3321
Limehouse Software Ltd
Bridewell Gate
9 Bridewell Place
London
EC4V 6AW
Manchester Office:
3rd Floor, The Triangle, Exchange Square
0 Oct 15 02:04
access.log.20081015.0204
-rw-r--r-- 1 resin apache 0 Oct 15 02:06
access.log.20081015.0206
-rw-r--r-- 1 resin apache 0 Oct 15 02:08
access.log.20081015.0208
Richard Grantham
Development
---
[EMAIL PROTECTED]
Limehouse Software
problem. I am using db persisted sessions, so I am see
the number of sessions in the db verses the number of sessions reported
by resin using jmx.
Richard Grantham wrote:
Hi list,
I recently upgraded to Resin Professional 3.1.7a in the hope
that the
issues I
this namespace declaration.
I guess this is an bug with Resin's streaming XML implementation. By
configuring Resin to use STaX instead I solved the issue I was having.
Is this a known issue or should I log it?
rgds,
Richard
Richard Grantham
Development
---
[EMAIL
(new
ByteArrayInputStream(xml.getBytes(UTF-8)), UTF-8);
transformer.transform(new StreamSource(reader), new
StreamResult(writer));
return writer.toString();
Any ideas why upgrading Resin would break transformations?
rgds,
Richard
Richard Grantham
Development
and solve this would be very much
appreciated. For now I have removed the page element.
rgds,
Richard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard Grantham
Sent: 18 June 2008 12:47
To: General Discussion for the Resin application server
Subject
respected.
Little help?
rgds,
Richard
PS. I am loath to switch (back) to using clustered sessions as I've had
issues with random logouts and loads of timeout errors in the logs
related to the internal Resin session store.
Richard Grantham
Development
---
[EMAIL
Thanks Sam. I'll give it a go.
Richard Grantham
Development
---
[EMAIL PROTECTED]
Limehouse Software Ltd
DDI: (020) 7566 3336
Main: (020) 7566 3320
Fax: (020) 7566 3321
Limehouse Software Ltd
4th Floor
1 London Bridge
London
SE1 9BG
Manchester Office:
3rd Floor
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard Grantham
Sent: 14 January 2008 16:54
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Resin clustered session store
Thanks for the response Scott. We did some firewall
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Ferguson
Sent: 14 January 2008 16:45
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Resin clustered session store
On Jan 10, 2008, at 4:19 AM, Richard Grantham wrote:
Hi
application server
Subject: Re: [Resin-interest] Resin clustered session store
On Mon, Jan 14, 2008 at 04:54:19PM -, Richard Grantham wrote:
Thanks for the response Scott. We did some firewall reconfiguration
with regards to connections and sessions and the issue appears to have
gone away
concerned as to what's causing the above error. The
(hardware) load balancer has been reporting that it has reached it's
maximum number of sessions. Could this be playing a part?
Any assistance would be appreciated.
rgds,
Richard
Richard Grantham
Development
for the 3.0 branch or am I doing something wrong?
I've seen the bug logged at http://bugs.caucho.com/view.php?id=1897 but
I can't run the 3.1 branch as it has issue with XFire.
rgds,
Richard
Richard Grantham
Development
---
[EMAIL PROTECTED]
Limehouse Software Ltd
17 matches
Mail list logo