App won't load if remote app server isn't there

Question

I have an application that is using a connection factory to subscribe to a topic on a remote host. If that remote host is not up when i deploy my application, the application will not load. If the app is already running and the remote server goes down, it will just retry to connect to the remote server. My app can still run with out it. So how do I get my app to come up when the remote server is not up and running?? Thanks!

Answer 1

Hi! Thanks for replying back! Here is some more info:
Please provide more information, such as
The type of application, a mdb, servlet, session
bean, appclient .. ?For sake of keeping it simple, it is a MDB on one application server and a publisher on another app server.
How the connection factory is used in the application
?The connection factory is being used from the descriptor files. here is my descriptor file for the MDB (ejb-jar):
<message-driven>
            <ejb-name>ReplySubscriber</ejb-name>
            <ejb-class>com.mycompany.common.framework.ejb.mdb.ReplySubscriber</ejb-class>
            <transaction-type>Container</transaction-type>
            <message-driven-destination>
                <destination-type>javax.jms.Topic</destination-type>
                <subscription-durability>Durable</subscription-durability>
            </message-driven-destination>
            <env-entry>
                <env-entry-name>factoryLookup</env-entry-name>
                <env-entry-type>java.lang.String</env-entry-type>
                <env-entry-value>java:comp/env/jms/remoteTCF</env-entry-value>
            </env-entry>
            <env-entry>
                <env-entry-name>queryReplyTopic</env-entry-name>
                <env-entry-type>java.lang.String</env-entry-type>
                <env-entry-value>java:comp/env/jms/statusTopic</env-entry-value>
            </env-entry>
            <resource-ref>
                <res-ref-name>jms/remoteTCF</res-ref-name>
                <res-type>javax.jms.TopicConnectionFactory</res-type>
                <res-auth>Container</res-auth>
            </resource-ref>
            <resource-env-ref>
                <resource-env-ref-name>jms/statusTopic</resource-env-ref-name>
                <resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
            </resource-env-ref>
        </message-driven>-------end ejb-jar
here is the bean in the sun-ejb-jar:
<ejb>
            <ejb-name>ReplySubscriber</ejb-name>
            <jndi-name>jms/statusTopic</jndi-name>
            <resource-ref>
                <res-ref-name>jms/remoteTCF</res-ref-name>
                <jndi-name>jms/remoteTCF</jndi-name>
                <default-resource-principal>
                    <name>admin</name>
                    <password>admin</password>
                </default-resource-principal>
            </resource-ref>
            <resource-env-ref>
                <resource-env-ref-name>jms/statusTopic</resource-env-ref-name>
                <jndi-name>jms/statusTopic</jndi-name>
            </resource-env-ref>
            <mdb-connection-factory>
                <jndi-name>jms/remoteTCF</jndi-name>
                <default-resource-principal>
                    <name>admin</name>
                    <password>admin</password>
                </default-resource-principal>
            </mdb-connection-factory>
            <jms-durable-subscription-name>jms/durableSub</jms-durable-subscription-name>
        </ejb>------------------end sun-ejb-jar
so the container automatically sets up the subscription to the topic statusTopic. The TopicConnectionFactory remoteTCF has a imqBrokerHostName set to a remote host, not localhost. So it is subscribing to a topic using a remote broker through that connection factory.
What does the application do ?Again for simplicity sake, all it does is listen for a message to be published to the statusTopic on a remote machine (appserver). There is a publisher on the remote machine that publishes to that topic using a localTCF.
The application server version ?SunOne Application Server 7.0 platform edition (and Messaging Queue 3.01 platform)
Please elaborate on "subscribe to a topic on a remote
host"I think i did this above.
So when i deploy this application, the container sets up the durable subscription for me. Then the app waits for a message to be published.
Now, if the app server that contains the publisher is not running and i try to bring up the app server with the MDB (say after a restart), the MDB application will not load because it cannot connect to the remote host named by the connection factory.
How do I get around this? Thanks for the reply!
Andrew