could well be.
depends on your setup...
>
> WARNING: Unable to asynchronously send session with
> id=[88798A041EC3F104045E5C22B47ADE77.jvm1-1151322148155] - message will
> be ignored. java.net.Connect
On Mon, 26 Jun 2006 11:46:43 +0100
Pid <[EMAIL PROTECTED]> wrote:
>
>
> Sean O'Reilly wrote:
>
> > Still having some problems with load balancing and state replication
> > neither of which appear to be working. If i shutdown tomcat on the
> > main server i can still get to the application direc
Sean O'Reilly wrote:
> Still having some problems with load balancing and state replication
> neither of which appear to be working. If i shutdown tomcat on the
> main server i can still get to the application directory from one of
> the other servers but get a 503 error if i try to run any of
(I've manually configured the tcpListenAddress to be the node's main IP.
Obviously it's not 000.000.000.00.)
I've specified JvmRouteBinderValve, JvmRouteSessionIDBinderListener and
ClusterSessionListener.
Sean O'Reilly wrote:
> On Fri, 23 Jun 200
On Fri, 23 Jun 2006 16:43:16 +0100
Pid <[EMAIL PROTECTED]> wrote:
>
>
> Sean O'Reilly wrote:
> > On Fri, 23 Jun 2006 09:05:18 -0500
> > Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> > I am sure it would be easier to use mod_proxy_balancer and
> > mod_proxy_ajp but can't find any documenta
Sean O'Reilly wrote:
> On Fri, 23 Jun 2006 09:05:18 -0500
> Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> I am sure it would be easier to use mod_proxy_balancer and
> mod_proxy_ajp but can't find any documentation anywhere.
My servers didn't have their clocks synchronised, check that.
Als
How are you defining the cluster in your server.xml?
I did this recently, and had a bunch of small problems.
E.g. my server clocks weren't sync'd.
I found that enabling just the SimpleTcpCluster element (without all the
rest) helped me get up and running.
Sean O'Reilly wrote:
> On Fri, 23 Jun 2
Sean O'Reilly wrote:
On Fri, 23 Jun 2006 10:00:36 -0500
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Sean O'Reilly wrote:
On Fri, 23 Jun 2006 09:05:18 -0500
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Hi Guys,
I appear to be finally getting somewhere with the
On Fri, 23 Jun 2006 10:00:36 -0500
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> Sean O'Reilly wrote:
> > On Fri, 23 Jun 2006 09:05:18 -0500
> > Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> >
> >
> >>> Hi Guys,
> >>>
> >>> I appear to be finally getting somewhere with the in-memo
Sean O'Reilly wrote:
On Fri, 23 Jun 2006 09:05:18 -0500
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Hi Guys,
I appear to be finally getting somewhere with the in-memory state
replication but am now getting the following error when starting up
my tomcat instances/
WARNING: Manager [/
On Fri, 23 Jun 2006 09:05:18 -0500
Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
>
> > Hi Guys,
> >
> > I appear to be finally getting somewhere with the in-memory state
> > replication but am now getting the following error when starting up
> > my tomcat instances/
> >
> > WARNING: Manager
Hi Guys,
I appear to be finally getting somewhere with the in-memory state
replication but am now getting the following error when starting up my
tomcat instances/
WARNING: Manager [/jsp-examples], requesting session state from
org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.4.121:
On Thu, 22 Jun 2006 15:39:09 +0100
Pid <[EMAIL PROTECTED]> wrote:
> In each case it's the ROOT context, so is it appending "" where
> there's no Context name/path: ie
>
> SEVERE: Context manager doesn't exist:host1+context1
>
> where context1=""
> ?
>
> It would still seem that the name parame
In each case it's the ROOT context, so is it appending "" where there's
no Context name/path: ie
SEVERE: Context manager doesn't exist:host1+context1
where context1=""
?
It would still seem that the name parameter supplied to the
getManagerName is carrying over it's previous value, and appendin
Makes sense, can we please ask you to open up a bug for us,
http://issues.apache.org/bugzilla/
thanks
Filip
Pid wrote:
OK,
I'm probably being dense here.
(There's only 1 context in each host, the ROOT context)
If I take the Host/Context offline in one node and restart it, the logs
on that no
OK,
I'm probably being dense here.
(There's only 1 context in each host, the ROOT context)
If I take the Host/Context offline in one node and restart it, the logs
on that node start showing the following:
SEVERE: Context manager doesn't exist:host1
As the Context doesn't exist, which is the sa
Hmm,
look at o.a.c.cluster.tcp.SimpleTcpCluster
L 626ff
private String getManagerName(String name, Manager manager) {
String clusterName = name ;
if(getContainer() instanceof Engine) {
Container context = manager.getContainer() ;
if(context != null &&
Filip Hanik - Dev Lists wrote:
> if the cluster is put in the engine element, the context names are
> prefixed with the engine name, since you can have multiple contexts with
> the same name in different host
> when reloading a context, you'll get these errors cause the context is
> not available
if the cluster is put in the engine element, the context names are
prefixed with the engine name, since you can have multiple contexts with
the same name in different host
when reloading a context, you'll get these errors cause the context is
not available during the reload
this will be fixed w
I'm seeing an issue on 5.5.17 with a 2 node cluster config.
When a context is reloaded, it sends the context node name incorrectly
to the cluster.
E.g. context is called "website1"
SEVERE: Context manager doesn't exist:website1website1
The config I'm using is exactly the same as the default from
20 matches
Mail list logo
