I have a JmsQueueAppender that logs messages to an ActiveMQ broker on a given
queue.
I also have a jndi.properties file in which I do NOT specify the
provider.url value, because that value can vary depending on a flag.
In my JmsQueueAppender, the jndi context is initialized using the default
the
PROVIDER_URL?
Joe
Free ActiveMQ user guide @ http://www.ttmsolutions.com
selezovikj wrote:
I have a JmsQueueAppender that logs messages to an ActiveMQ broker on a
given queue.
I also have a jndi.properties file in which I do NOT specify the
provider.url value, because that value
I am logging messages using log4j to a queue on an ActiveMQBroker.
Now, I want dependent on whether a flag is on to be able to log to a broker
specified by let's say: java.naming.provider.url = tcp://machineA:61616, and
if it is off to log to java.naming.provider.url = tcp://machineB:61616
When
I am using log4j to send logging events to a topic on an ActiveMQ broker.
I use the failover transport to specify a secondary host and automatic
reconnection.
When the commons-logging.jar is in the classpath the failover transport is
blocking.
Has anyone experienced this ?
Does commons-logging
Yes, I am using the JMS appender and in the jndi.properties file I specify
failover:(tcp://localhost:61617) as the value for the providerURL.
I have a simple client logging messages using the JMS appender.
Commons-logging is logging to a jms appender when I am NOT using the
failover transport.
If so, does this mean that by default, with the failover transport
commons-logging logs to where it tries to connect ?
James.Strachan wrote:
2008/11/4 selezovikj [EMAIL PROTECTED]:
So failover tries to log that it is connected, but it cannot log since it
is
not connected.
But, my
://www.scriptinginjava.net
selezovikj wrote:
I am not sending ActiveMQ logging information to the JMS appender.
__
Logger messageLogger = Logger.getLogger(MSGSTATS);
messageLogger.info(Client logs to 61617
System.out.println(before declaration);
final Log log = LogFactory.getLog(MSGSTATS);
System.out.println(after declaration);
after declaration is never printed out.
So commons-logging initializes a Log, which initializes log4j by reading the
log4j.properties file, then in the log4j.properties
information to the JMS
appender right? Otherwise its catch 22; you can't connect until you've
logged and can't log until you've connected.
2008/11/4 selezovikj [EMAIL PROTECTED]:
Yes, I am using the JMS appender and in the jndi.properties file I
specify
failover:(tcp://localhost:61617) as the value
and removing of jar files, I saw that the problem causing
this is the commons-logging-1.1.jar file.
When I add that jar file the failover transport is useless.
Any idea why this is so ?
selezovikj wrote:
Jconsole shows the following stack trace:
Name: main
State: BLOCKED on [EMAIL
YES, I am using the log4j JMS appender. That is mentioned in my first
message for this thread.
In my simple client, I am using the log4j JMS appender, which appends
messages to a JMS topic and it WORKS !
It doesn't give any problems. The problem occurs once I include the
commons-logging JAR.
I saw that in the Apache ActiveMq 5.2 release the default
ActiveMQConnectionFactory brokerUrl uses the failover transport.
Is this going to solve my problem ?
I tried running my application on different machines and it is giving the
same error. Can anyone suggest anything ?
selezovikj
- get a free ActiveMQ user guide
selezovikj wrote:
Even only:
failover://tcp://localhost:61617
does not work
selezovikj wrote:
I have a jms appender sending logging events to active mq broker. In the
jndi.properties I have the following provider url
Jconsole shows the following stack trace:
Name: main
State: BLOCKED on [EMAIL PROTECTED] owned by: ActiveMQ Task
Total blocked: 1 Total waited: 1
Stack trace:
org.apache.activemq.transport.failover.FailoverTransport.start(FailoverTransport.java:228)
selezovikj wrote:
I am getting
I have a jms appender sending logging events to active mq broker. In the
jndi.properties I have the following provider url:
java.naming.provider.url =
failover:(tcp://localhost:61617,tcp://localhost:61616)?initialReconnectDelay=20maxReconnectDelay=1000randomize=falsemaxReconnectAttempts=10
Even only:
failover://tcp://localhost:61617
does not work
selezovikj wrote:
I have a jms appender sending logging events to active mq broker. In the
jndi.properties I have the following provider url:
java.naming.provider.url =
failover:(tcp://localhost:61617,tcp://localhost:61616
Peer did not send his wire format ...
Did anyone find with a solution for this problem ?
I have the same problem
javadevel wrote:
We are trying to create a distributed logging service using Log4J and JMS
appender to an ActiveMQ topic. However, we keep getting an error Wire
format
17 matches
Mail list logo
