I have experienced the same problem, currently with jboss-4.2.3.GA.
And for me, the problem is even worse because the timers expire at a time the
server is not yet completely started and not all required services are started.
This results in failures and eventually I have to restart the
There is a post in a different forum about this:
http://www.jboss.org/index.html?module=bbop=viewtopict=139076
And a bug in JIRA:
https://jira.jboss.org/jira/browse/JBAS-5779
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4252981#4252981
Reply to the post :
This bug has been reverified on jbossws-native-3.1.1.
See https://jira.jboss.org/jira/browse/JBWS-2637
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227832#4227832
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227832
It looks like there is a problem with the namespace for web faults when this is
not the same as the namespace of the service. The type definition of the web
faults has the correct namespace, but the reference to the type from the
messsage elements uses the name space of the service instead.
As far as I understand, the documentation on clustering always assumes one is
clustering to handle more messages over the same number of queues, that is, to
scale the number of messages.
My question is if clustering is also helpful when the number of messages per
queue remains the same, but
Is there a way to have failover without clustering? I know about the
ha-singleton setup, but this would place the jms server only at one of the
nodes in the cluster. And I do want to distribute the load of the growing
number of clients over multiple instances.
View the original post :
timfox wrote : Yes you can have failover without clustering, but it's not
automatic. You need to catch the exception from the ExceptionListener and
recreate your connection on the new node.
This is failover of the connection, right? What about the queue? Is there a way
to have it also moved
wolfc wrote : This is a bug in AS 4.2.2 where if it can't find the name in
JNDI and there is no cluster active it will give a NPE instead of
NameNotFoundException.
|
| Fixed in AS 5.0.
Is this fixed in JBAS 4.2 also?
Can you point us to a JIRA issue number?
TIA,
Bart.
View the original
This problem appeared to have something to do with how the run.sh script works:
my kill was killing the run.sh script, but the jboss server kept running.
(I was using kill instead of plainly hitting Ctrl-C because the latter shuts
down jboss cleanly, so there is no cluster instance failure
The setup:
- two clustered jboss 4.2.1.GA nodes,
- a clustered topic with a durable subscriber on each node
- a remote client using clustered connection factory.
When the client starts posting messages on the topic, the first node (probably
the one the connection factory created a connection
Can @WebFault and @XmlType be used on the same element? I have an application
exception with additional information. The exception gets defined in the .wsdl
as a complex type, but the @XmlType annotation information does not seem to be
taken into account: the type is defined in the wrong
Has a JIRA issue been created for this? It is still there in JBoss 4.2--more
than one year later.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062381#4062381
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4062381
bartvh wrote : Has a JIRA issue been created for this? It is still there in
JBoss 4.2--more than one year later.
Ok, found the JIRA bug : http://jira.jboss.com/jira/browse/JBAS-3383. And I see
no 'Fix Version' has been filled in...
View the original post :
http://www.jboss.com/index.html
Setup:A two node cluster JBoss 4.2 with JBM 1.3.0 serverMySQL persistenceA
distributed topic on both nodesAn MDB with a durable subscription and client
ID, installed on both nodes
During tests, I have been starting and stopping the nodes one after the other
and also together, but now I have
timfox wrote : Have you configured each node to have a unique server id?
yes, I have server peer id 0 and 2.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4059155#4059155
Reply to the post :
It is rather big. Here's a subselect:
mysql select * from JBM_POSTOFFICE where JBM_POSTOFFICE.QUEUE_NAME =
'TraceListener.TraceListener';
|
+-+-+-++--++---+
| | POSTOFFICE_NAME | NODE_ID |
I did a delete of JBM_POSTOFFICE, JBM_MSG and JBM_MSGREF. And then:
Start up the two nodes, wait until both are started.kill -9 the first node and
start it up againwait until the first node is started again
Now I have the the situation like in the select statement above. If I now stop
the two
waynebaylor wrote : sounds like your modifying a collection while iterating
over it.
This is indeed what I was trying to make clear to the JBoss AOP developers...
A JIRA issue has been created at http://jira.jboss.com/jira/browse/JBAOP-430.
View the original post :
I am running some custom jmx beans inside a jboss-4.2 running on jdk1.5. With
load time weaving enabled, I get to see the following exception:
java.util.ConcurrentModificationException
| at
java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:365)
| at
I too have a situation where the 4.2.0 with loadtime weaving server fails to
start from time to time. It does not occur every time. I am running on Linux,
using sun jdk 1.5.
I did a stack trace (kill -3) of the java process and these two interesting
parts are printed:
main prio=1
I have a remote client connecting to a clustered jboss-messaging server, using
jboss 4.2.0. The JBM version is 1.3.0.GA. Because of some experimentation I
frequently had restarted my client application. After a number of restarts, I
get into a situation where the client is unable to reconnect
I want to add that when is problem occurs, shutting down the server hangs. I
did a stack trace dump and it shows:
JBoss Shutdown Hook daemon prio=1 tid=0x08abc388 nid=0x2d94 waiting for
monitor entry [0x85adb000..0x85adf030]
| at
Using JBoss Messaging 1.3.0.GA server, still seeing this ClassCastException
when RoundRobin is enabled.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4053421#4053421
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053421
This error log is indeed very annoying. But to me, the fact that a generic
CreateException is thrown is even more problematic. How do I distinguish this
from some other failure in the database? I would hope I do not need to
interpret the exeception's message to distinguish.
Shouldn't this code
I recently upgraded from jboss-3.2.3 jboss.net to jboss-3.2.8SP1 jboss.net, and
now I discovered an incompatibility between the latter and apache axis (1.4)
clients. In apache axis, user exceptions thrown in the service methods do not
have a 'message' element, while they do have this element in
25 matches
Mail list logo
