Hi Peter,
I should point out all the configuration works with messaging 1.2 in JBoss
4.0.5.
The client code is stand alone. It call lookup all pre-configured
destination coming with the package of 1.3.
The topicName was passed as an arguement to the method, which was set as a
sta
Sorry mbean should look like:
|
| jboss.messaging:service=ServerPeer
| jboss.messaging:service=PostOffice
| true
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052296#4052296
Reply to the post :
http://www.jboss.co
Here is what I see in JNDIView:
| +- topic (class: org.jnp.interfaces.NamingContext)
| | +- testDurableTopic (class: org.jboss.jms.destination.JBossTopic)
| | +- TopicWithOwnRedeliveryDelay (class:
org.jboss.jms.destination.JBossTopic)
| | +- xCacheInvalidationTopic (class:
I am using JBoss AS 4.2.0.GA. Yes I started server every time I made change on
any of config files.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052273#4052273
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052273
__
Sorry, my mistake. My topic does show up in JNDI view but cannot find by
jndi.lookup.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052271#4052271
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052271
___
Thanks Peter, I did look at the Global JNDI Namespace in JNDIView, my topic is
not there. My understanding is that by adding a destination in
destination-service.xml, name service should be able pick it up in JNDI space.
View the original post :
http://www.jboss.com/index.html?module=bb&op=view
Add a topic in destination-service.xml and got NameNotFoundException for that
topic. It was working with 1.2 and I can also find all pre-configured
destinations. I set up JBM in Jboss AS 4.2.0.GA. Is there any change about
destination configuration in 1.3? Or I missed anything. Thansks
View the
Any one here can help me to setup a HA MySql working with JBoss Messaging?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043976#4043976
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043976
_
I know that configuring HA-JNDI in JBOSS cluster requires partition. Since JBM
doesn't use partition, is there any other way to config JBM with HA-JNDI. Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039107#4039107
Reply to the post :
http://www.jboss
Hi Tim,
Could you please tell me where I can get the fixed copy of code? Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038922#4038922
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038922
_
Thanks Tim,
When will the fixed code release? Is it just another
jboss-messaging-client.jar?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036412#4036412
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036412
___
Hi Clebert,
Do you have ETA about the fix? Thanks.
xkong
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035817#4035817
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode
Thanks Clebert.
It is a good news for us if failover doesn't throw exception to exception
listener.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035070#4035070
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035070
_
I deployed an JBoss Messaging cluster with two nodes. When the node a jms
client connected crashed and topic was failed over to another node smoothly.
But at the same time a JMSException was also sent to Exception listener. Could
any one here help me to differentiate this exception from other J
I used jboss-messaging-clients.jar of 1.2.0.GA to call configuration of
1.2.0SP1 and I got following error.
2007-04-03 10:08:41,318 ERROR
[org.jboss.remoting.transport.socket.ServerThread] - Worker thread
initialization failure
| java.io.IOException: Can not read data for version 22. Supporte
To update to a new release of JBoss Messaging we are required to update
jboss-messaging-clients.jar on client sides for every new release. For my case,
I have near 100 client applications subscribe to topics on my jms server. It is
very difficult to update client side configuration each time. I
Looks like it is a JNDI related issue. Where are you running AS? Make sure
java.naming.provider.url points to the right ip address your AS is running. You
can find it in etc/jndi.properties.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030286#4030286
Reply
Since the systems I am going to deploy JBM cluster don't support UDP. Any one
here have used TCP for Postoffice config? Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030281#4030281
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=pos
I deployed two messaging nodes over separate systems. One on a Windows XP
professional and another on CentOS (linux). I removed the bind_addr from
postoffice config in clustered-mysql-persistence-service.xml. Then I ran the
sample code for queue_faiover. Half times I got sucess: I received Helo1
I have the same problem. Any one has a solutions? Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028426#4028426
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028426
_
Thanks Time for clarifying it. So every time a JMS provider is updated we need
update client side config also.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025279#4025279
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p
Hi,
We are in process to migrate our JMS servers from JBossMQ to JBoss
messaging. I know from user the guide that we need replace jbossmq-client.jar
with jboss-messaing-client.jar in clients' classpathes. The problem we are
facing is that we have many clients which are very difficult to updat
22 matches
Mail list logo