Hello,
we have EJB 2.1 and 3.0 Beans on JBossAS 4.2.3 and EJB 2.1 on JBossAS 4.0.2.
Now our clients would like to set timeouts for their RMI-EJB-Calls. I can set a
timeout on the server side for all EJBs, but we have applications which are
used by frontend and backend systems. The Backends can w
Hello,
with JBoss 4.0.x we used the class
org.jboss.deployment.scanner.PrefixDeploymentSorter to get a deployment order
which was idependent of the file content. With JBoss 4.2.x the filename is the
first part of the global JNDI-Name. This is a very goog idea, because we have
the version numbe
No I don't have FD_SOCK next to FD. I saw the doubled node when the whole
cluster had a high load with lots of garbage collection runs. That was the
reason why I thought that the use of FD_SOCK will lessen the likelihood of the
problem, but it still can happen, especially when a node takes a GC
Thanks a lot. I played a little bit around and now I could generate a patch
which adds the attribute 'forceUidInNodeName' to
ClusterPartiton/ClusterPartitonMBean which is false per default, which means
that the behaviour is untouched and when its set to true the UID is used. But
to implement it
I added a bugreport for the logging issue, too. The added patch is a little bit
smaller, but I think the check if oldMembers is null, could be removed. Because
of the prior code, it can't be null, but the check is saver when the code
changes in future.
View the original post :
http://www.jboss
I posted two Bugreports:
JBAS-4313
JBAS-4314
But I found a minor bug in HAPartitionImpl. The debug output in method
viewAccepted doesn't log the old size, because the members-field changed during
the method. I changed 'this.memebers' to 'oldMembers' with some checking for
oldMembers == null.
Sure, but I haven't used JIRA yet, so I have some, maybe stupid, questions:
Should I use 'Bug' as issue type or 'Support Patch'? I would add it for project
'JBoss Clustering', is this ok? I can add a patch for both issues against JBoss
4.0.2. Would this be helpful?
View the original post :
htt
Hi everyone,
we have the problem that our cluster sometimes looses his master and only
restarting the 'right' node solves it. We are using jboss 4.0.2 but the code
which causes the problem is present up to 4.2.0.CR1. I can reproduce it as
follows:
cluster with two nodes: node_a, node_b, both j
Hi,
for all who may be interested, we found the reason for the described behaviour:
The problem was, that there were two clusters with different multicast addresse
etc., but the same partition name. And both cluster were accessed from the same
client for different services. When we installed the
Hi,
we get intermittent NameNotFound-Exceptions when a client makes a lookup
against our JBoss-4.0.2-Cluster. The client uses the HA-JNDI-Ports. When he
uses the non HA-JNDI-Ports we don't see the exceptions. At the same time
another client can make lookups without any problems. When the client
10 matches
Mail list logo
