Given that ActiveMQ uses commons logging during its startup - its
gonna be hard to use ActiveMQ to log messages of ActiveMQ starting up
:). So there's clearly gonna be ordering & dependency issues gettings
started.
On 2/15/07, teryz <[EMAIL PROTECTED]> wrote:
Hello David i ran into the same
Hi Terys ...
I'm got the same problem configuring my log4j.properties with activemq
appender, this is my log config:
log4j.appender.A1=org.apache.activemq.util.JmsLogAppender
log4j.appender.A1.uri=tcp://localhost:61616
i don't know why!!!
Thanx!
On 2/15/07, teryz <[EMAIL PROTECTED]> wrote:
Hello David i ran into the same problem and i used an appender that I wrote
myself for log4J to send message in ActiveMQ and this class is based on the
ProducerTool example given with activeMQ (we don't have any app server).
I tried it on the 4.1, same error, i tried it a 4.2 snapshot still the s
Hi James ...
The version of active mq is the latest (apache-activemq-4.1.0-incubator),
and the activemq log seems normal (i think so ...):
2007-02-14 09:09:16,306 [main ] INFO
BrokerService - ActiveMQ 4.1.0-incubator JMS Message Broker
(localhost) is starting
2007-02-
Which version are you using? Also what appears in the broker's log
file - it seems the broker side is not responding properly
On 2/14/07, David Borja <[EMAIL PROTECTED]> wrote:
Hi activemq devs!!
I'm having a problem with activemq and log4j ...
this is my log4j.properties :
log4j.appender.A1=
