[JNDI/Naming/Network] - JDNI Lookup - Naming Not Found with JBOSS 4.2.2
by senthilrajan.nitt
Hi,
I am trying to set my local environment in JBOSS 4.2.2 server for my project.
I have configured the Datasource to point to my local oracle instance. The JBOSS log shows up as follows.
19:29:13,031 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
19:29:13,984 INFO [A] Bound to JNDI name: queue/A
19:29:13,984 INFO [B] Bound to JNDI name: queue/B
19:29:14,000 INFO [C] Bound to JNDI name: queue/C
19:29:14,000 INFO [D] Bound to JNDI name: queue/D
19:29:14,000 INFO [ex] Bound to JNDI name: queue/ex
19:29:14,031 INFO [testTopic] Bound to JNDI name: topic/testTopic
19:29:14,031 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
19:29:14,046 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
19:29:14,046 INFO [testQueue] Bound to JNDI name: queue/testQueue
19:29:14,140 INFO [UILServerILService] JBossMQ UIL service available at : /127.
0.0.1:8093
19:29:14,203 INFO [DLQ] Bound to JNDI name: queue/DLQ
19:29:14,703 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
19:29:14,937 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=DataSourceBinding,name=OracleDS' to JNDI name 'java:OracleDS'
When i try to lookup for my Datasource i got NamenotFound Exception.
Context ctx = new InitialContext();
Object ds = ctx.lookup("java:OracleDS");
System.out.println("Got the object : "+ds)
But when i look the object by name : topic/testTopic i got the object.
Context ctx = new InitialContext();
Object ds = ctx.lookup("topic/testTopic");
System.out.println("Got the object : "+ds)
Could anybody please help me what i have to do to work properly?
Thanks,
Senthil
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145179#4145179
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145179
18 years, 3 months
[JBoss Messaging] - Re: Clustered server preference
by clebert.suconic@jboss.com
Andy wrote : So in answer to your question, you would need to use a singleton queue that all your consumers used and use the other node as a backup for fail over.
A Singleton Queue it the way JBossMQ decided to implement cluster, and that was as performant as having a single node.
If you need multiple clients sharing a single queue with JBossMessaging, and you can't have the localQueues behavior.. you should use a single node, and you could have other nodes as backup nodes. Another way is if you aways had your producer on the BackupNode and consumers on remote nodes, the load would be shared with your clients.
I believe we have the Singleton Queue option planned for JBM 2.
Notice that this is still correct according to the JMS specification as it doesn't state how cluster whould behave on clustered distributions. (this is something up to the implementation).
Just coming back to your Banking example, when you go to the bank the next cashier will get you.. you won't need to go to the other side of the city to get the next available teller. The local queue has this behavior... you get the next teller at the agency you are currently on which is the cheapest operation.
What we can do now is consider the Single option for a future release for users that don't need to scale up their queues. I'm sure you can find a way to work this out with JBM 1.4 if you want... but I'm not sure if this will satisfy your needs.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145172#4145172
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145172
18 years, 3 months
[JBoss Messaging] - Re: Clustered server preference
by ataylor
anonymous wrote : I certainly appreciate your taking the time to participate in this discussion. no problems.
In Jboss Messaging if a single queue has more than one Consumer, we will deliver to the first available. If multiple consumers are registered with the queue(with no message selectors) then we will round robin and send to the next available consumer. If there are no local consumers on the queue then we distribute to another node in the cluster to be consumed.
The problem is that both of your consumers are attached to different nodes, if they were both attached to the same node the load would be shared. Always routing to the local consumer is the most performant way to do this.
So in answer to your question, you would need to use a singleton queue that all your consumers used and use the other node as a backup for fail over.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145170#4145170
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145170
18 years, 3 months