activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3764) JMSAppender cannot connect to activemq using failover
Date Thu, 29 Mar 2012 11:54:35 GMT

    [ https://issues.apache.org/jira/browse/AMQ-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241160#comment-13241160
] 

Gary Tully commented on AMQ-3764:
---------------------------------

The crux of this issue is hinted at in the [log4j-jms.properties file|http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/example/src/log4j-jms.properties],
to avoid a circular dependency, activemq cannot log to the jms appender:
{code}
## Be sure that ActiveMQ messages are not logged to 'jms' appender
log4j.logger.org.apache.activemq=INFO, stdout
{code} 
                
> JMSAppender cannot connect to activemq using failover
> -----------------------------------------------------
>
>                 Key: AMQ-3764
>                 URL: https://issues.apache.org/jira/browse/AMQ-3764
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.5.1
>         Environment: J2SE 1.5
> activemq-core-5.5.1.jar
> log4j-1.2.14.jar
> geronimo-jms_1.1_spec-1.1.1.jar
> geronimo-j2ee-management_1.1_spec-1.0.1.jar
> slf4j-api-1.5.11.jar
> slf4j-log4j12-1.5.11.jar
>            Reporter: LeeDW
>
> Hi All, 
> I tried to use Log4jJMSAppenderExample.java and set failover:(localhost:61616) property
ProvierURL in log4j.properties file.
> But I can not connect to activemq and stop below line.
>  log4j: Creating TopicSession, non-transactional, in AUTO_ACKNOWLEDGE mode.
> trace:
> log4j: Parsing appender named "jms".
> log4j: Setting property [initialContextFactoryName] to [org.apache.activemq.jndi.ActiveMQInitialContextFactory].
> log4j: Setting property [topicBindingName] to [logTopic].
> log4j: Setting property [topicConnectionFactoryBindingName] to [ConnectionFactory].
> log4j: Setting property [providerURL] to [failover:(tcp://localhost:61616)].
> log4j: Getting initial context.
> log4j: Looking up [ConnectionFactory]
> log4j: About to create TopicConnection.
> 2012-03-13 14:28:29,900 DEBUG org.apache.activemq.transport.failover.FailoverTransport
- Reconnect was triggered but transport is not started yet. Wait for start to connect the
transport.
> 2012-03-13 14:28:30,045 DEBUG org.apache.activemq.transport.failover.FailoverTransport
- Started.
> 2012-03-13 14:28:30,046 DEBUG org.apache.activemq.transport.failover.FailoverTransport
- Waking up reconnect task
> log4j: Creating TopicSession, non-transactional, in AUTO_ACKNOWLEDGE mode.
> log4j.properties:
> log4j.appender.jms=org.apache.log4j.net.JMSAppender
> log4j.appender.jms.InitialContextFactoryName=org.apache.activemq.jndi.ActiveMQInitialContextFactory
> log4j.appender.jms.ProviderURL=failover:(tcp://localhost:61616)
> log4j.appender.jms.TopicBindingName=logTopic
> log4j.appender.jms.TopicConnectionFactoryBindingName=ConnectionFactory
> Please help and any advise.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message