Hi Everyone,
OMG. I've seen this problem inflicted on quite a number of pple with the
JNDI. 1099 seems to be a favourite of some sort among java developers. Can't
we change the Jboss naming service to another port that is very seldom used?
Minimises headaches.
Lionel
PS : anyway, it should have given an error response if it was connectring to
the wrong port when attempting lookup(bad code for cloudscape?) and also
during the start up sequence for Jboss.
----- Original Message -----
From: "Anatoly Akkerman" <[EMAIL PROTECTED]>
To: "jboss-user mailing list" <[EMAIL PROTECTED]>;
"JBoss-Dev" <[EMAIL PROTECTED]>
Sent: Tuesday, February 27, 2001 5:29 AM
Subject: RE: jndiView.jar hangs while JNDIView MBean works OK. (was
RE:[jBoss-User] How to setup JNDI in stand-alone TomCat not started asMBean)
>
> I've resolved the issue. It turns out that Cloudscape database was using
> the default port of 1099, so I had to reconfigure JBoss' naming service to
> use a different port.
>
> There really should be a way for JBoss' Naming service to check if the
> port is already in use and throw an exception.
>
> Thanks to everybody who attempted to help me out.
>
> Anatoly.
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
