| Andy Platt 2004-03-27, 7:34 am |
| Hey Srini,
I don't think WAS 4 supports corbaloc  What error do you get? When I try a
simple test I get:
javax.naming.ConfigurationException:
URLToObjectFacility.badProtocolcorbaloc:iiop@localhost:2809
However, can't you just connect to the cluster with one iiop address instead
of trying to set up connections to each of them? The cluster maintains the
state of which are active and inactive.
Failing that you could probably just copy Dave's release two code! ;)
Andy.
--
I'm not really here, it's just your warped imagination
"Srinivas Chennamaraja" <schennamaraja@yahoo.com> wrote in message
news:ab482581.0403261731.5936ac64@posting.google.com...
> Hi,
>
> I have an EJB client running in Websphere (4.0.5) communicating with
> Websphere App. Server (version 5.0.1). The App Server is clustered (2
> Nodes and 4 app. srver clones). I am trying to use corbaloc to
> connect to the app servers for fail over, some how I am getting
> Naming Exception.... here is the code....
>
> Hashtable p= new Hashtable();
>
p.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialCo
ntextFactory")
>
>
p.put(Context.PROVIDER_URL,"corbaloc::myhost.com:9811,:myhost.com:9812,:myho
st1.com:9811.:myhost1.com:9812")
>
> InitialContext ic = new InitialContext(p)
> Object objref = ic.lookup("myEJBHome");
>
>
> any thoughts?, does webspherer 4.0 work with corbaloc??
>
> thanks,
> Srini
|