I have tried the latest version - apache-activemq-4.2-20070328.130210-35, but
the same error still exists. With what are you going to substitute activeio?
Thank you!
Dingwen Yuan
2007-04-10
发件人: James Strachan
发送时间: 2007-04-03 15:49:52
收件人: users@activemq.apache.org
抄送:
主题: Re: Shared Fil
@ WALLACE
Yes i have successfully implemented the jms thing rom core java
application.
if u use
Properties Initialcontext_props = null;
queueName = "example.MyQueue";
Initialcontext_props = new Properties(
@ WALLACE
Yes i have successfully implemented the jms thing rom core java
application.
if u use
Properties Initialcontext_props = null;
queueName = "example.MyQueue";
Initialcontext_props = new Properties(
hi all
I need to know that is there any way to authenticate JMS clients to a
firewall or proxy on the client side ..
if yes then Can some one please guide me to it .
Any help will be Appreciated.
Thanks in advance .
--
View this message in context:
http://www.nabble.com/Help-with-JMS-client
i am planning to use spring to start a in-vm activemq broker in tomcat. But
when i start the tomcat, i get the error messages below in the log file
which means that i don't create a table for activemq,
nested exception is java.io.IOException: Failed to get last broker
message id: java.sql.SQLE
Dear all,
I set up the REST/AJAX examples following the instruction:
http://activemq.apache.org/web-samples.html
and ran the simple HTTP GET / POST via regular web browser technology
(hyperlinks and HTML forms), by posting messages with the html form:
http://myserver:8080/activemq-web-de
Hello,
This is a first try at configuring pure master slave topology with
ActiveMQ 4.1.
Test message is successfully consumed, however errors reported in both
master and slave logs.
I am keeping activemq.xml very simple and include both configurations
below error messages. What am I missing?
Thanks for response.
This works for me too. But it is a very big limitation to require the client
to hard code the physical queue name (in your example, example.MyQueue). It
defeats the purpose of jndi. The client should only need to know the jndi
name. So no code change is necessary when the se
Thanks for response.
This works for me too. But it is a very big limitation to require the client
to hard code the physical queue name (in your example, example.MyQueue). It
defeats the purpose of jndi. The client should only need to know the jndi
name. So no code change is necessary when the se
Thanks for response.
This works for me too. But it is a very big limitation to require the client
to hard code the physical queue name (in your example, example.MyQueue). It
defeats the purpose of jndi. The client should only need to know the jndi
name. So no code change is necessary when the se
Hi All,
I'll be writing a process that uses parallel grid processing to process
message groups. I'm new to Active MQ and could use some help in finding
documentation or examples.
I'll be running in the following environment
Java 1.6
JBoss 4
Active MQ 4.1.1
RHEL4
I know I will be performing
I am trying to figure out what the various configuration options are and what
they do but I seemed to be handicapped by an old XML reference. I have found
two versions:
http://activemq.apache.org/xml-reference.html
http://activemq.apache.org/xbean-xml-reference-41.html
The second one seems to be
Actually I think I figured it out. The second link does have everything
documented...some are documented as a XML element and some just as
properties until another element. I was searching for all of them with the
"<" on the front so i wasn't finding them all.
Although even the elements that are
I've managed to get Spring to load the .xml by fully installing XBean
into my project (including using it to load my Spring app context).
However, my IDE (IntelliJ IDEA 6.0.5) gives me the red error highlight
on the amq:journaledJDBC element, so either the .xsd doesn't define it
for amq:persis
well u can get them from user at run time . like ome sort of preferences or
key - value pair properties file.
wallace wrote:
>
> Thanks for response.
>
> This works for me too. But it is a very big limitation to require the
> client to hard code the physical queue name (in your example,
> exa
Refer to this: http://activemq.apache.org/wildcards.html
mjparme wrote:
Actually I think I figured it out. The second link does have everything
documented...some are documented as a XML element and some just as
properties until another element. I was searching for all of them with the
"<" on the
16 matches
Mail list logo