Hi Christopher,
sorry, if my response to your question concerning message expiration might
have been misleading, but expiration handling did not change from 4.0.1 to
4.0.2. You should see the behaviour I described with AMQ 4.0.1 as well.
Regards,
Holger
Christopher_Ong wrote:
>
> Hello, is a
[ https://issues.apache.org/activemq/browse/AMQ-979?page=all ]
Rob Davies updated AMQ-979:
---
Description:
Network connections are generally one way - with messages only flowing out from
the broker that made the network connection.
In order to support WAN hub/s
Hi Jason,
I just created a jira for this: http://issues.apache.org/activemq/
browse/AMQ-979
On 16 Oct 2006, at 05:40, Jason Dillon wrote:
How then do I setup a hub/spoke network where the hub does not know
about all of the spokes, and where the spokes may be behind
firewalls, only allowin
Allow NetworkConnections to bi-directional
--
Key: AMQ-979
URL: https://issues.apache.org/activemq/browse/AMQ-979
Project: ActiveMQ
Issue Type: New Feature
Components: Broker
Repo
Hello, is anyone can clarify my doubt? Thanks in advance.
Christopher_Ong wrote:
>
> May I know when is the projected official release of Activemq 4.0.2
> (because I prefer it's feature of auto remove of expired message where
> 4.0.1 can't do that)? Thanks
>
--
View this message in context:
Hi guys, I was just writing a simple GShell command to start up a
BrokerService, and when I enable useJmx=true, I get the rather nasty
looking DEBUG message below.
Anyone know why this is?
It appears that the broker is still functional... and I can still
peek at the jmx details with jconso
I would enable both of them.. and fix the comments in the file that
indicate that only the file appender is used.
--jason
On Oct 15, 2006, at 8:55 AM, Hiram Chirino (JIRA) wrote:
[ https://issues.apache.org/activemq/browse/AMQ-927?
page=comments#action_37186 ]
Hiram Chirino commented
No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java
JMS Producer/Consumer
---
Key: AMQ-978
URL: https://issues.apache.org/activemq/browse/AMQ
Topic destination created for channel:// destination name
-
Key: AMQ-977
URL: https://issues.apache.org/activemq/browse/AMQ-977
Project: ActiveMQ
Issue Type: Bug
Reporter: E