Any ideas on this? I'm still stumped...
Alex_ynr wrote:
Bear with me cause this might be a total misconfiguration on my part but I
can't seem to figure it out
I am running Fuse 3.3 but with the latest svn trunk version of activeMQ to
solve the duplex=true bug i mentioned in a
Hey folks,
i really dont understand the following code-snippet from the original
AMQ-config-file:
!-- Use the following if you wish to configure the journal with JDBC
--
!--
persistenceAdapter
journaledJDBC journalLogFiles=5
dataDirectory=${activemq.base}/activemq-data
On 15/10/2007, j0llyr0g3r [EMAIL PROTECTED] wrote:
Hey folks,
i really dont understand the following code-snippet from the original
AMQ-config-file:
!-- Use the following if you wish to configure the journal with JDBC
--
!--
persistenceAdapter
journaledJDBC
Some extra points i would like to make to my previous post.
- After i enabled the debug logging I saw that every time activemq adds a
consumer via the stomp client, the log shows these lines (obvioulsy with
different time and port number):
2007-10-15 11:29:02,982 [/127.0.0.1:2121] TRACE
What version of ActiveMQ are you using. If its a 5.0 snapshot I saw
this same behavior from one of last weeks snapshots. I grabbed the Oct
10th version an it worked much better for stomp.
This is the one I grabbed that worked.
Ok guys,
thanks for the explanation
rajdavies wrote:
You can use the file based journal and a database together - it can
make sense where the database is local to the message broker using it
(embedded) - and for 4.x this is the default configuration - using
Apache derby as
Hey ho,
when i start an activemq-broker with the provided example configuration file
i get an
Initialization of bean failed; nested exception is
org.springframework.beans.InvalidPropertyException: Invalid property
'memoryUsage' of bean class [org.apache.activemq.xbean.XBeanBrokerService]:
No
Ok folks,
i didn't see the solution because this xml-scheme is HUGE.
If i get it right, instead of declaring something like
memoryManager
usageManager id=memory-manager limit=20 MB/
/memoryManager
within the broker -scope you have to declare something like
memoryUsage
Hi Jim,
I am most concerned with the first type of failure, where the client
has a problem with the network connection, but the server is still
running properly. What I did was take your modified amq.js (from link
in my previous message) and then added the following to line 111 in
As you know, none of the javascript rewrite has made it into HEAD. Perhaps
James or a committer on the project can weigh in on the patch I submitted.
If it is in HEAD then it can be improved upon and have these new features
added. Not to say, we can't evolve the code outside of that process, but
On 4.1.1, the fanout transport works as expected. My producer is fanning out
message sends (queues) to two unrelated message brokers and clients
connected to both those brokers get the messages.
However, when I run the same exact test under 5.0 (the 10/10 SNAPSHOT),
fanout no longer works as
Hi
I am simulating some issues which we are facing. One such issue is login -
subscribe-unsubscribe to topic.
I am trying to initiate a TopicSession. After a few minutes, I try to close
the session. It seems I am unable to close the TopicSession when i try to
once again create a new topic
Hi!
I've been trying to start activemq with zeroconf. I'm using the latest
5.0 SNAPSHOT. I downloaded the source and copied the
receiver-zeroconf.xml to
apache-activemq-5.0-SNAPSHOT/bin
and tried to start activemq by typing
activemq xbean:receiver-zeroconf.xml
But I get this exception.
13 matches
Mail list logo
