Forgot to mention, I am also running AS 5.1.0 GA with the JbossMessaging that
came with it (I believe it is 1.4.3).
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252949#4252949
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=re
It appears that I, too, am facing the same issue as described by venkadesan.
the messages are sent to two queues in round robin (say out of 10 messages, 5
goes to node1 and 5 goes to node 2). When we try to consume, consumer pointing
to node1 can consume only 5 from node 1 and nothing from node2
The clustering seems to work okay in a local setting.
But the CacheMarshaller200 class is in the jbosscache-core.jar
(jbosscache-core.jar MANIFEST shows version 3.1.0.GA).
Should it be in this jar? I am using the jar that came with JBoss AS 5.1.0.
| jar -tvf jbosscache-core.jar | grep Cache
Application server: JBoss AS 5.1.0
I am upgrading from JBoss 4.0.5 to JBoss 5.1.0.
When I deploy a second node in my parititon I am getting an error during
SessionCache start up. It occurs during state transfer. The stack trace is
posted below.
I am using udp and the standard-session-cache.
I am trying to deploy distributed caching for a single entity. I am running
JBoss AS 5.1.0 with jdk 1.5. I have two nodes running on two separate servers
in a single partition.
I see the caching work fine on each single node but the cache does not
replicate/invalidate between the two nodes (I
Thanks for the reply.
I have two separate clusters (partitions), each with one node. One cluster
named AppPartition, one cluster named BatchPartition. The JMS server is
running on the single node in BatchPartition. The single node in AppPartition
is unable to send a JMS message from within t
I am getting a NullPointerException when trying to open a session for sending a
JMS message.
I have two clusters, each with one node started up. I run into the error when
trying to send a message from within the server that is not running the JMS
server (I removed the deploy/messaging folder
This forum thread may be of interest to you when you do decide to upgrade.
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=149505&start=0
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232310#4232310
Reply to the post :
http://www.jboss.org/index.ht
Did you ever find a solution to this problem?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232037#4232037
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232037
___
jboss-us
Yeah, I saw that jira issue and a posting
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=147180. I figured
that it was likely the same issue but was not sure.
Here is a simple example I made that runs in the server. It will be easier
than posting all the related code pertaining to t
I am upgrading from JBoss AS 4.05 to JBoss 5.01. The code mentioned below
works fine in JBoss 4.05.
I have a quartz job that is unable to get a remote access to a deployed EJB. I
know that the EJB is deployed because I see it in the JMX console.
Additionally, I wrote a client program that u
You can make the MDB depend upon that which must be deployed before the MDB is
deployed. This can be set using the @Depends class-level annotation.
For example, if there are two session beans that must be deployed prior to the
MDB then add the following annotation.
| @Depends({
|
"jboss.
I have two clustered JMS servers running JBoss [Zion] 4.0.4.GA (build:
CVSTag=JBoss_4_0_4_GA date=200605151000); the servers run linux (debian). JMS
data is persisted to a postgres8.1 database; each server has the same
configuration (same JMS destinations; same datasource for the JMS persistence
One other thing to note:
When the server is restarted (say when node1 is restarted in Step 5) and the
exceptions begin to pour out the MDBs deployed on that server (and the other
one for that matter) are consuming messages.
View the original post :
http://www.jboss.com/index.html?module=bb&op=v
I have two clustered JMS servers running JBoss [Zion] 4.0.4.GA (build:
CVSTag=JBoss_4_0_4_GA date=200605151000); the servers run linux (debian). JMS
data is persisted to a postgres8.1 database; each server has the same
configuration (same JMS destinations; same datasource for the JMS persisten
15 matches
Mail list logo
