This only gives more info about the problem. I cannot get the system to recognize
my jndi.properties file. Here is my classpath:
c:\jonas_jdk1.2;c:\jonas_jdk1.2\examples\src;\clients\myclient\code\product\mb;\clients\myclient\code\product\mb\gen;\lang\idb\classes\idb.jar;\lang\idb\classes\idbexmpl.jar;\lang\idb\classes\idbf.jar;\lang\ejb\classes12.zip;\lang\ejb\jndi.jar;\lang\ejb\providerutil.jar;\lang\ejb\rmiregistry.jar;\lang\ejb\jta-spec1_0_1.jar;\lang\ejb\jdbc2_0-stdext.jar;c:\jonas_jdk1.2\lib\RMI_jonas.jar;c:\jonas_jdk1.2\lib\ejb.jar
and the jndi.properties file is in c:\jonas_jdk1.2...
Maybe I am not seeing the problem in the classpath, everything else works, and
when I use jonas1.6 all my beans deploy and work with this classpath.
For now, I will just define the 'java.naming.factory.initial' on the java commnad
line. But I really would like to figure out what is going on here.
Thanks for any help,
Chris
Philippe Coq wrote:
> Timothy Rogers wrote:
> >
> > Hello,
> >
> > When I try to start up the Jonas server, I get:
> > JOnAS: Cannot start Naming Manager
> > java.lang.NullPointerException
> > at org.objectweb.jonas.naming.NamingManager.
> > <init>(NamingManager.java:75)
> > at org.objectweb.jonas.server.Server.main(Server.java:78)
> >
> > The reason I get this is that my naming service is screwed up. But also,
> > around line 75 in the NamingManager class, there is the following code:
> > try {
> > ictx = new InitialContext();
> > myEnv = ictx.getEnvironment();
> > } catch (NamingException n) {
> > Throwable t = n.getRootCause();
> > if (t.getMessage().startsWith("Connection refused to host:")) {
> > Trace.errln("NamingManager: rmi registry not started ?");
> > throw n;
> > } else if (t.getMessage().startsWith("error during remote
> > invocation")) {
> > Trace.errln("NamingManager: jrmi registry not started ?");
> > throw n;
> > } else {
> > Trace.errln("NamingManager: "+t.getMessage());
> > throw n;
> > }
> > }
> >
> > The bug is where you call the getRootCause() method of the NamingException
> > n. Sun's documentation says that getRootCause() "Returns the possibly null
> > exception that caused this naming exception. If null, it means no root cause
> > has been set for this naming exception."
> >
> > In my case, there is no root cause and the expression "Throwable t =
> > n.getRootCause()" returns a null Throwable t. In the next line, you ask the
> > Throwable t to get its message. Since the Throwable t is null, you get a
> > NullPointerException.
> >
> > This can be fixed by adding the lines:
> > if( t == null )
> > t = n;
> > after line 75:
> > Throwable t = n.getRootCause();
> >
> > Then, people like me would be able to actually get a meaningful message from
> > the NamingManager class and be able to move on to debug the naming service
> > problem.
> >
> > --Timothy Rogers
>
> Thank you Rogers,
> there is actually a bug in the NamingManager.
> It is fixed in the current CVS tree
> Best regards,
> --
> Philippe
>
> Philippe Coq Groupe Bulll/BullSoft/OpenMaster Phone: (33) 04 76 29 78
> 49
> Bull S.A - 1 rue de Provence - 38432 Echirolles Cedex France
> [EMAIL PROTECTED] http://www-frec.bull.com
> Download our EJBServer at http://www.bullsoft.com/ejb
> ----
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body of the message "unsubscribe jonas-users".
> For general help, send email to [EMAIL PROTECTED] and
> include in the body of the message "help".
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
