activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Gies <andr...@soa-knowledge.net>
Subject Re: Please help:Again about ActiveMQ intigration with Websphere 6.1
Date Fri, 01 May 2009 12:39:46 GMT
Hi there,

sorry to say, but the IBM guy is kind of wrong. You can bind AMQ  
administered objects
in any JNDI store. This having said, the ActiveMQ JNDI implementation  
takes the information
from a file called jndi.properties on the classpath. You cannot  
programmatically bind objects
into the AMQ JNDI implementation. Find more infos here:

http://activemq.apache.org/jndi-support.html

This having said, I am convinced that AMQ can meet your messaging  
needs; but at the end of the
day you have to choose yourself.


Best regards
Andreas

On Apr 30, 2009, at 10:11 PM, Websphere and ActiveMQ wrote:

>
> Hi Andreas,
>
> I have created some queues on ActiveMQ and tested them using pure Java
> Client, they worked well.here I use JNDI.properties file.
>
> But as IBMer said, I have to create JNDI name space in ActiveMQ end,  
> or
> create JMS Administered Objects, I remembered I need to create it  
> when I
> used MQ before.
>
> So do you know how to create JMS Administered Objects(JNDI name  
> space) in
> ActiveMQ end??
>
> Now I'm choosing a suitable MQ to replace IBM MQ, if  
> ActiveMQ doesn‘t work,
> which one is better(cha 
> nge less code existing  
> in our system), JBoss M 
> essage
> or Open Message Queue(S 
> un).
>
> Thanks.
>
> Derrick
>
>
> Andreas Gies wrote:
>>
>> Hi there,
>>
>> it seems, that your Queue cannot be located in the JNDI store. On the
>> first
>> glance I find it unusual that in an AppServer context you are using  
>> the
>> ActiveMQ JNDI store.
>>
>> However, when you are using that, you must be sure, that the
>> jndi.properties
>> file where you have defined your JMS administered objects can be  
>> found
>> on
>> the classpath.
>>
>> This having said, I would find it more natural to use the JNDI store
>> that comes
>> with the app server. I don't know WebSphere from the top of my head,
>> but that
>> should be easy to find in the docs. You can either use a management  
>> GUI
>> to define those objects or use a small program, that creates the
>> ActiveMQ objects
>> on the fly and stores them in WebSphere JNDI.
>>
>> Hope that helps
>> Andreas
>>
>> On Apr 27, 2009, at 10:09 PM, Websphere and ActiveMQ wrote:
>>
>>>
>>> I have already configurated ActiveMQ in Websphere 6.1 as someone
>>> described
>>> here, but when I re-started websphere,  the following error is
>>> appeared:
>>> ####### error ##########
>>> Content: JndiLookupInfo: jndiName="MyReceiveQueue";
>>> providerURL="tcp://localhost:61616";
>>> initialContextFactory
>>> ="org.apache.activemq.jndi.ActiveMQInitialContextFactory"
>>> Address Type: IndirectJndiLookupAdditionalProperties
>>> AddressContents: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75
>>> 74 69 6c
>>> 2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a  ...
>>>
>>> Exception data follows:
>>> javax.naming.NameNotFoundException: MyReceiveQueue
>>> 	at
>>> org 
>>> .apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:
>>> 225)
>>> 	at javax.naming.InitialContext.lookup(InitialContext.java:363)
>>> 	at
>>> com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory
>>> $1.run(IndirectJndiLookupObjectFactory.java:375)
>>> 	at
>>> com
>>> .ibm
>>> .ws
>>> .security.util.AccessController.doPrivileged(AccessController.java:
>>> 118)
>>> 	at
>>> com
>>> .ibm
>>> .ws
>>> .naming
>>> .util
>>> .IndirectJndiLookupObjectFactory
>>> .getObjectInstanceExt(IndirectJndiLookupObjectFactory.java:221)
>>> 	at
>>> com
>>> .ibm
>>> .ws
>>> .naming
>>> .util.Helpers.processSerializedObjectForLookupExt(Helpers.java:893)
>>> 	at
>>> com
>>> .ibm
>>> .ws
>>> .naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:
>>> 705)
>>> 	at
>>> com
>>> .ibm
>>> .ws
>>> .naming
>>> .jndicos.CNContextImpl.processResolveResults(CNContextImpl.java: 
>>> 2093)
>>> 	at
>>> com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:
>>> 1947)
>>> 	at
>>> com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:
>>> 1862)
>>> 	at
>>> com 
>>> .ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:
>>> 1552)
>>> 	at
>>> com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:
>>> 1354)
>>> 	at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:172)
>>> 	at javax.naming.InitialContext.lookup(InitialContext.java:363)
>>> 	at
>>> com
>>> .ibm
>>> .ejs
>>> .jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:
>>> 235)
>>> 	at
>>> com
>>> .ibm
>>> .ejs 
>>> .jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:
>>> 727)
>>> 	at
>>> com
>>> .ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:
>>> 700)
>>> 	at
>>> com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:
>>> 1035)
>>> 	at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:90)
>>> 	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
>>> ###############################
>>> Could anyone tell me what's the error, do I need to do some extra
>>> work on
>>> ActiveMQ end or Websphere End.
>>> Thanks.
>>>
>>> -- 
>>> View this message in context:
>>> http://www.nabble.com/Please-help%3AAgain-about-ActiveMQ-intigration-with-Websphere-6.1-tp23263958p23263958.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>
>>
>>
>
> -- 
> View this message in context: http://www.nabble.com/Please-help%3AAgain-about-ActiveMQ-intigration-with-Websphere-6.1-tp23263958p23322601.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


Mime
View raw message