This content has been marked as final.
Show 3 replies
-
1. Re: java.lang.IllegalStateException: cluster 'X' is already connected to singleton transport
smitha.nair Jun 28, 2010 1:09 AM (in response to smitha.nair)Missed to mention that we use jbosscache-core 3.2.2.GA.
Thanks
Smitha
-
2. Re: java.lang.IllegalStateException: cluster 'X' is already connected to singleton transport
smitha.nair Jul 8, 2010 9:11 AM (in response to smitha.nair)Hi,
I was able to resolve this issue by giving different singleton_names( for cluster config <UDP>) in each of the wars.
But both wars will be using the same cache config and same cluster name.
So both the wars are sharing the same cache.
Is that an ideal solution?
Does it have any side effects.
can any body please suggest.
Thanks
Smitha -
3. Re: java.lang.IllegalStateException: cluster 'X' is already connected to singleton transport
smitha.nair Jul 9, 2010 2:23 AM (in response to smitha.nair)Can anyone please comment on this
Two wars on jboss 5 clustered nodes use same cache configuration and same cluster name .
But each of these wars uses different shared transport(ie. different singleton_name in UDP config)
Does this has any performance issue?
We use jboss 5.
Thanks
Smitha