0 Replies Latest reply on Jun 15, 2009 6:32 PM by Ind Kon

    JMSAppender, jboss-log4j and jboss.

    Ind Kon Newbie

      This is my question, I have the following setup in the jboss-log4j.xml on a Jboss server:

      appender name="JMS" class="org.apache.log4j.net.JMSAppender
      errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"
      param name="InitialContextFactoryName" value="org.jnp.interfaces.NamingContextFactory"
      param name="URLPkgPrefixes" value="org.jboss.naming"/>
      param name="ProviderURL" value="jnp://myhost.mydomain.com:1099"
      param name="Threshold" value="DEBUG"
      param name="TopicConnectionFactoryBindingName" value="ConnectionFactory"
      param name="TopicBindingName" value="topic/testTopic"

      Now, when I bring up this jboss server, not neccessarily will the myhost.mydomain.com be listening on port 1099. There are times where it could be down. However, if this myhost.mydomain.com is down, then my jboss server will fail to deploy correctly reporting a " javax.naming.CommunicationException: Failed to connect to server myhost.mydomain.com:1099[Root exception is java.net.ConnectException: Connection refused]]

      How can I make it so that when my jboss server is starting up, and when it comes accross the JMS entry above in the jboss-log4j, it ignores it until that server myhost.mydomain.com:1099 is up? Any ideas?