Hi,
As code, you can directly use a connection factory that you create in
JBoss. Then your code directly uses the JMS API.
It's also to use MDB the same way (via connection factory).
You can find some details here:
https://access.redhat.com/documentation/en-us/jboss_enterprise_application_platf
hello
Installed apache-activemq-5.8.0-bin.tar.gz and using jboss 6
how to make jboss to talk to activemq which is running separately
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
ext.lookup("activemq/TopicConnectionFactory");
and factory is null
--
View this message in context:
http://old.nabble.com/JBOSS-and-activeMQ---JNDI-lookup-tp26576681p26577811.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
jms.Topic
> name="Properties">PhysicalName=topic/RawDataTopic
>
> ...
>
> and connection factoies are configured with:
>
> false
>
> context is configured as:
>
>
> props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.apache.activemq.jndi.ActiveM
on factoies are configured with:
false
context is configured as:
props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.apache.activemq.jndi.ActiveMQInitialContextFactory");
props.setProperty(Context.PROVIDER_URL,"tcp://hostname:61616");
What is missing?
Thank you and regards
--
g.xml that enables http transport?
It's not correctly described from documentation...
Regards
Marco
--
View this message in context:
http://old.nabble.com/JBOSS-and-ActiveMQ---enable-http-transport-tp26576232p26576232.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
exceptions.
What is the meaning of this error message ? What am I doing wrong ? Is this
a activemq bug ? Is it a problem of JBoss ?
Thank you very much!
--
View this message in context:
http://www.nabble.com/Deployment-failure-with-JBoss-and-ActiveMQ-5.3-tp25531099p25531099.html
Sent from th
2009/8/7 An An :
>
> Hi James,
> Thanks for the reply.
> I have set the JBoss jndi properties already.
> So I do this in the code :-
> <<
> Properties props = new Properties();
>
> props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.apache.activemq.jndi.ActiveMQInitialContextFactory");
>
rg/jndi-support.html
>>>
>>
>> Is that possible when ActiveMQ runs embedded within JBoss? How?
>
> The ActiveMQ JNDI provider is purely local to the JMS client - it
> doesn't matter where the broker is.
>
> For more background see this FAQ entry:
> http:/
2008/4/29 Alex Soto :
> James Strachan wrote:
>>
>> 2008/4/29 Alex Soto :
>>
>>>
>>> I also have the same problem.
>>> The suggestions I've seen is to instantiate ActiveMQConnectionFactory
>>> instead of getting it from JNDI. As a workaround it is satisfactory but
>>> this solution does not go ve
>> ConnectionFactories should be located in the "java:" namespace.
>> This namespace is local to the jvm and has no visibility to
>> external clients./"
>>
>> Is it true ? I'm not sure. How other application server do ?
>>
>> Ph
et this running on JBoss. How to I get JBoss to start up ActiveMQ
so that it works the same as the TomCat version?
TIA
David
--
View this message in context:
http://www.nabble.com/JBoss-and-ActiveMQ-tp22296006p22296006.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
If that is true, how is it possible that the JBossMQ connection
factory is available to remote clients?
I think is against the purpose of the standard if a change in the
implementation causes the clients to stop working.
Alex Soto
[EMAIL PROTECTED]
-
Amicus Plato, sed magis amica veritas.
JBoss answer
"/The connection factories provided by a Resource Adapter (RA) are
typically not available for use by clients that are outside of the
application server. That is, the JCA specification is intended to
provided resources to the application server, and relies upon behavior
on the par
Thank you Philippe, It's good to know.
Alex Soto
[EMAIL PROTECTED]
-
Amicus Plato, sed magis amica veritas.
On Apr 30, 2008, at 10:51 AM, Philippe P. wrote:
I find the bug, not the solution now.
The remote JNDI register a
org.apache.activemq.ra.ActiveMQManagedConnectionFactory.
When a re
I find the bug, not the solution now.
The remote JNDI register a
org.apache.activemq.ra.ActiveMQManagedConnectionFactory.
When a remote lookup is done, the remote JNDI server must serialize this
instance to send to the client.
This instance is connected to an ActiveMQResourceAdapter.
This inst
James Strachan wrote:
2008/4/29 Alex Soto <[EMAIL PROTECTED]>:
I also have the same problem.
The suggestions I've seen is to instantiate ActiveMQConnectionFactory
instead of getting it from JNDI. As a workaround it is satisfactory but
this solution does not go very far. Certainly it does no
2008/4/29 Alex Soto <[EMAIL PROTECTED]>:
> I also have the same problem.
> The suggestions I've seen is to instantiate ActiveMQConnectionFactory
> instead of getting it from JNDI. As a workaround it is satisfactory but
> this solution does not go very far. Certainly it does not help if the client
I also have the same problem.
The suggestions I've seen is to instantiate ActiveMQConnectionFactory
instead of getting it from JNDI. As a workaround it is satisfactory but
this solution does not go very far. Certainly it does not help if the
client code is not available for modification.
Do
in context:
http://www.nabble.com/JBoss-and-ActiveMQ-with-remote-JNDI-tp16961289s2354p16961289.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
20 matches
Mail list logo
