JMS/JNDI introducing white spaces

Question

Hi.
I am having trouble getting the example at http://technet.oracle.com/docs/tech/java/oc4j/htdocs/OC4JExample.html to work. I finally started the client program that uses JMS with java Main instead of java -Djava.naming.security.credentials=<admin password> Main
Then I saw in a popup box that somewhere along the way there has been appended a single whitespace character after the login name "admin" was spelled "admin " and "ormi://localhost" was spelled "ormi://localhost ". My jndi.properties file did not include white spaces. Anyone seen this before?
-Christer

Answer 1

Hi
          Please find my answers below:
          Q1:
          It depends how you configured the JMSSevers.
          If both the JMSServers are targeted to the same MigratableTarget, then you do the migration only once, that will move both of them to the new active server.
          If not, you have to perform the migration once for each MT.
          Q2:
          No, you dont have to start the Managed Server II, unless otherwise you wanted it to be readily available for the migration next time.
          Q3:
          You can just repeat the migration process by specifying the destination as Maganged Server-I this time. You dont need change the configuration for this, since the MT, shall already have the Candidate servers M1 and M2 and both JMSServers are targeted to MT.
          Q4:
          Yes, as long as the CF is targeted to the cluster, your connection is valid. But your destinations references will become invalid after migration, so you have to have some logic in the exception listeners to reconnect again.
          Hope this helps.