-
1. Re: Partition name not respected with client lookup
darranl Jul 22, 2003 1:56 AM (in response to chiefcujo)When you obtain the initial context do you also specify the address of a JBoss installation to use in addition to the jnp.partitionName?
-
2. Re: Partition name not respected with client lookup
slaboure Jul 27, 2003 10:46 AM (in response to chiefcujo)yes, how do you assign/use jnp.partitionName?
-
3. Re: Partition name not respected with client lookup
chiefcujo Jul 31, 2003 2:39 PM (in response to chiefcujo)Gents,
As per the example test class
org.jboss.test.naming.test.SimpleUnitTestCase
env.setPropertyContext.PROVIDER_URL, "jnp://localhost:65535/");
env.setProperty"jnp.partitionName", "DefaultPartition");
Of course the partition name is what we are using in the server.
If we don't supply the bogus URL the connection is forced to localhost (Always) no matter what the partitionname. If no server on localhost, then it takes any available server with no regard to the partition name.
If we supply the bogus URL it times out and connect to the specified partition and ignores localhost if it is not a member of the partition.
If we supply an empty string for the URL, a NoSuchElementException org.jnp.interfaces.NamingContext.removeServer(Name).
So as you can see we are at a loss and still debugging trying to resolve this issue.
One other point, even using the bogus URL, if a client is up and the partition goes away. The HARMIClient will NEVER reconnect to the partition when a member is restarted unless that member is on the localhost.
Any help resolving this will be greatly appreciated.
Cheers -
4. Re: Partition name not respected with client lookup
slaboure Aug 19, 2003 12:10 PM (in response to chiefcujo)Can you please try again with a fresh checkout from Branch_3_2 (or use a snapshot: http://jboss.sf.net/snapshots/ )
If it doesn't work create a bug report on http://sf.net/projects/jboss and assign to me aka "slaboure"
Cheers,
sacha