RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Hi! You are the first one to get this :( I also got this one on beta3 but it works fine for me on beta1 :) beta4 is just out, I will try again... Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de John Menke Envoyé : vendredi 11 mai 2001 2:04 À : [EMAIL PROTECTED] Objet : RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Maybe the -nonaming is not getting executed then? (if it fixed your problem). I am using Catalina from within the Turbine TDK which contains a schell script startup.sh which calls the catalina.sh script. I have added the -nonaming to this line so it reads $BASEDIR/catalina.sh start -nonaming $@ This should turn naming off, but I still get the errors when I start the program this way. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone Sent: Thursday, May 10, 2001 6:42 PM To: '[EMAIL PROTECTED]' Subject: R: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Hey John Yes, I have tried that, and I still get the error. (It seems like it has no effect) Do you have this configuration working? Not exactly. I'm using Catalina with another server application that has its own Naming service, and at the beginning I got the same error on startup, but it went away with the -nonaming option. We then have other problems with this jndi: protocol, also from previous discussions it seems to me a Catalina bug: with us, every class loaded from web-inf/classes or web-inf/lib has a codebase like jndi:/WEB-INF/classes/ or jar:jndi:/WEB-INF/lib/xxx.jar!/, so that if objects of these classes are passed as arguments to any rmi method invocation, on the other side the class annotation is taken from the stream, but of course the classloader cannot understand the Catalina-specific jndi: protocol. The context class loader should take care of that probably, but I did not figured it out yet why it doesn't. I miss Rickard ! Will live, will see. Cheers Simon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone Sent: Thursday, May 10, 2001 6:15 PM To: '[EMAIL PROTECTED]' Subject: R: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Do you start Catalina with the -nonaming option, so that from it you connect to JBoss' Naming service ? Simon -Messaggio originale- Da: John Menke [mailto:[EMAIL PROTECTED]] Inviato: mercoledì 9 maggio 2001 23:30 A: jboss Oggetto: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error This error is produced when I try to get an initial JNDI context. The error is: javax.naming.CommunicationException[Root exeption is java.rmi.ServerException: RemoteException occured in server thread; nested exception is java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is java.net.MalformedURL exception: unknown protocol: jndi I can get InitalContext in Tomcat 3.2, but Catalina produces the error. Is there a workaround? ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Vincent, my mistake I am using Beta 1 and I'm gettting the error. Not Beta 3 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Vincent Harcq Sent: Friday, May 11, 2001 3:58 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Hi! You are the first one to get this :( I also got this one on beta3 but it works fine for me on beta1 :) beta4 is just out, I will try again... Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de John Menke Envoyé : vendredi 11 mai 2001 2:04 À : [EMAIL PROTECTED] Objet : RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Maybe the -nonaming is not getting executed then? (if it fixed your problem). I am using Catalina from within the Turbine TDK which contains a schell script startup.sh which calls the catalina.sh script. I have added the -nonaming to this line so it reads $BASEDIR/catalina.sh start -nonaming $@ This should turn naming off, but I still get the errors when I start the program this way. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone Sent: Thursday, May 10, 2001 6:42 PM To: '[EMAIL PROTECTED]' Subject: R: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Hey John Yes, I have tried that, and I still get the error. (It seems like it has no effect) Do you have this configuration working? Not exactly. I'm using Catalina with another server application that has its own Naming service, and at the beginning I got the same error on startup, but it went away with the -nonaming option. We then have other problems with this jndi: protocol, also from previous discussions it seems to me a Catalina bug: with us, every class loaded from web-inf/classes or web-inf/lib has a codebase like jndi:/WEB-INF/classes/ or jar:jndi:/WEB-INF/lib/xxx.jar!/, so that if objects of these classes are passed as arguments to any rmi method invocation, on the other side the class annotation is taken from the stream, but of course the classloader cannot understand the Catalina-specific jndi: protocol. The context class loader should take care of that probably, but I did not figured it out yet why it doesn't. I miss Rickard ! Will live, will see. Cheers Simon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone Sent: Thursday, May 10, 2001 6:15 PM To: '[EMAIL PROTECTED]' Subject: R: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Do you start Catalina with the -nonaming option, so that from it you connect to JBoss' Naming service ? Simon -Messaggio originale- Da: John Menke [mailto:[EMAIL PROTECTED]] Inviato: mercoledì 9 maggio 2001 23:30 A: jboss Oggetto: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error This error is produced when I try to get an initial JNDI context. The error is: javax.naming.CommunicationException[Root exeption is java.rmi.ServerException: RemoteException occured in server thread; nested exception is java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is java.net.MalformedURL exception: unknown protocol: jndi I can get InitalContext in Tomcat 3.2, but Catalina produces the error. Is there a workaround? ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists
RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Vincent, you were able to get 4.0 beta 1 and JBoss 2.2.1 working? I am running Turbine TDK Catalina 4.0 beta 1 - provided by Turbine TDK JBoss2.2.1 Catalina and JBoss are running in seperate VM's -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Vincent Harcq Sent: Friday, May 11, 2001 5:01 AM To: Dev JBoss; [EMAIL PROTECTED] Subject: RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Nope. Scott, my gentle jndi guru, does it make sense to change NamingContext so that it can understand jndi:, then use for java.naming.provider.url something like jndi://localhost:1099 to avoid this problem with catalina ? Or is it Catalina the source of the problem ? javax.naming.CommunicationException[Root exeption is java.rmi.ServerException: RemoteException occured in server thread; nested exception is java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is java.net.MalformedURL exception: unknown protocol: jndi Vincent Hi! You are the first one to get this :( I also got this one on beta3 but it works fine for me on beta1 :) beta4 is just out, I will try again... Vincent. Maybe the -nonaming is not getting executed then? (if it fixed your problem). I am using Catalina from within the Turbine TDK which contains a schell script startup.sh which calls the catalina.sh script. I have added the -nonaming to this line so it reads $BASEDIR/catalina.sh start -nonaming $@ This should turn naming off, but I still get the errors when I start the program this way. Hey John Yes, I have tried that, and I still get the error. (It seems like it has no effect) Do you have this configuration working? Not exactly. I'm using Catalina with another server application that has its own Naming service, and at the beginning I got the same error on startup, but it went away with the -nonaming option. We then have other problems with this jndi: protocol, also from previous discussions it seems to me a Catalina bug: with us, every class loaded from web-inf/classes or web-inf/lib has a codebase like jndi:/WEB-INF/classes/ or jar:jndi:/WEB-INF/lib/xxx.jar!/, so that if objects of these classes are passed as arguments to any rmi method invocation, on the other side the class annotation is taken from the stream, but of course the classloader cannot understand the Catalina-specific jndi: protocol. The context class loader should take care of that probably, but I did not figured it out yet why it doesn't. I miss Rickard ! Will live, will see. Cheers Simon Do you start Catalina with the -nonaming option, so that from it you connect to JBoss' Naming service ? Simon -Messaggio originale- Da: John Menke [mailto:[EMAIL PROTECTED]] Inviato: mercoledì 9 maggio 2001 23:30 A: jboss Oggetto: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error This error is produced when I try to get an initial JNDI context. The error is: javax.naming.CommunicationException[Root exeption is java.rmi.ServerException: RemoteException occured in server thread; nested exception is java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is java.net.MalformedURL exception: unknown protocol: jndi I can get InitalContext in Tomcat 3.2, but Catalina produces the error. Is there a workaround? _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Vincent, I finally got Catalina started with -nonaming... I had catalina.sh
start -nonaming and it was not working. You must use catalina.sh
run -nonaming to get a Standalone version to run. That being said, I STILL
GET THE SAME ERROR. I have copied ALL the jar files from the JBoss client
directory into my WEB-INF/lib folder. I am using the Turbine TDK so there
are extra jar files in the directory from what you may have. Possibly this
is creating the problem?
Here is a list of the .jar files in the directory: Can you give a list of
your jar files so I can compare?
WEB-INF/lib
TestBeanClient.jar
activation-1.01.jar
connector.jar
deploy.jar
ecs-1.4.1.jar
ejb.jar
hsql.jar
jaas.jar
jakarta-regexp-1.3-dev.jar
jboss-client.jar
jbossmq-client.jar
jbosssx-client.jar
jdbc-se2.0.jar
jdbc2_0-stdext.jar
jndi.jar
jnp-client.jar
jta-spec1_0_1.jar
jta1.0.1.jar
junit-3.2.jar
log4j-1.0.4.jar
mail-1.2.jar
mm.mysql-2.0.4.jar
postgresql.jar
stop.jar
turbine-2.1-dev-unrealeased.jar
velocity-1.0b2-dev.jar
village-1.5.1-dev.jar
xalan-1.2.1.jar
xerces-1.3.0.jar
xmlrpc.jar
Here is the code that creates the error:
try {
// Set up the naming provider. This may not always be necessary,
// depending on how your Java system is configured.
System.setProperty(java.naming.factory.initial,
org.jnp.interfaces.NamingContextFactory);
System.setProperty(java.naming.provider.url,
localhost:1099);
// Get a naming context
InitialContext jndiContext = new InitialContext();
// Get a reference to the Interest Bean
Object ref = jndiContext.lookup(interest/Interest);
// Get a reference from this to the Bean's Home interface
InterestHome home = (InterestHome)
PortableRemoteObject.narrow (ref, InterestHome.class);
// Create an Interest object from the Home interface
m_interest = home.create();
} catch(Exception e) {
out.println(LIContext failed: + e);
}
This code works great in 3.2
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Vincent
Harcq
Sent: Friday, May 11, 2001 9:06 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Yes, no problem with -nonaming : catalina.bat run -nonaming.
server.xml :
Context path= docBase=E:\Projects\web debug=0 reloadable=true/
And all JBoss client JAR files in E:\Projects\web\WEB-INF\lib
Nothing else changed to catalina installation directory
Oh yes, another one,
jndi.properties is not read (if I remember well) so I have to manually
System.setProperty java.naming... just before calling new
InitialContext()
Vincent.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]De la part de John Menke
Envoyé : vendredi 11 mai 2001 15:10
À : [EMAIL PROTECTED]
Objet : RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Vincent, you were able to get 4.0 beta 1 and JBoss 2.2.1 working?
I am running
Turbine TDK
Catalina 4.0 beta 1 - provided by Turbine TDK
JBoss2.2.1
Catalina and JBoss are running in seperate VM's
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Vincent
Harcq
Sent: Friday, May 11, 2001 5:01 AM
To: Dev JBoss; [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Nope.
Scott, my gentle jndi guru, does it make sense to change NamingContext
so that it can understand jndi:, then use for
java.naming.provider.url
something like jndi://localhost:1099 to avoid this problem with
catalina ?
Or is it Catalina the source of the problem ?
javax.naming.CommunicationException[Root exeption is
java.rmi.ServerException: RemoteException occured
in server
thread; nested
exception is java.rmi.UnmarshalException: error
unmarshalling
arguments;
nested exception is java.net.MalformedURL
exception: unknown
protocol: jndi
Vincent
Hi!
You are the first one to get this :(
I also got this one on beta3 but it works fine for me on beta1 :)
beta4 is just out, I will try again...
Vincent.
Maybe the -nonaming is not getting executed then? (if it
fixed your
problem). I am using Catalina from within the Turbine TDK which
contains a
schell script startup.sh which calls the catalina.sh script. I
have added
the -nonaming to this line so it reads
$BASEDIR/catalina.sh start -nonaming $@
This should turn naming off, but I still get the errors when
I start the
program this way.
Hey John
Yes
Re: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Yes, no problem with -nonaming : catalina.bat run -nonaming. server.xml : Context path= docBase=E:\Projects\web debug=0 reloadable=true/ And all JBoss client JAR files in E:\Projects\web\WEB-INF\lib Nothing else changed to catalina installation directory Oh yes, another one, jndi.properties is not read (if I remember well) so I have to manually System.setProperty java.naming... just before calling new InitialContext() Hi! I'm using catalina in combination with the turbine framework and jbossMQ. I also get exactly these communication errors when trying to get an initial context. Which jar files exactly do you put in your web-inf\lib?? I tried your suggestions (using jbossmq-client.jar) but the error stays the same regards Chris ... ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Hi! Please note that I am using a 2.3 beta version so maybe there was some changes in between. But here are the jars I have 1. In Tomcat E:\Projects\p1\tomcat4b1dir /s *.jar Directory of E:\Projects\p1\tomcat4b1\bin 06/01/2001 05:18 24.776 bootstrap.jar 06/01/2001 05:18 98.496 jndi.jar 06/01/2001 05:18 23.514 naming.jar 06/01/2001 05:18 74.753 servlet.jar Directory of E:\Projects\p1\tomcat4b1\lib 06/01/2001 05:18 188.406 crimson.jar 06/01/2001 05:18 272.734 jasper.jar 06/01/2001 05:18 11.809 jaxp.jar 23/02/2001 10:47 85.237 jdom.jar 06/01/2001 05:183.724 namingfactory.jar Directory of E:\Projects\p1\tomcat4b1\server 06/01/2001 05:18 490.878 catalina.jar 06/01/2001 05:18 188.406 crimson.jar 06/01/2001 05:18 29.809 jakarta-regexp-1.2.jar 06/01/2001 05:18 11.809 jaxp.jar 06/01/2001 05:18 31.416 warp.jar 2. In WEB-INF\lib E:\Projects\VMI\main\UltraDevdir /s *.jar Directory of E:\Projects\p1\main\web\WEB-INF\lib 18/02/2001 01:10 175.666 hsql.jar 07/05/2001 09:49 88.843 jboss-client.jar 03/05/2001 16:18 58.461 jboss-j2ee.jar 03/05/2001 16:18 133.040 jbossmq-client.jar 04/05/2001 09:51 22.976 jbosssx-client.jar 04/05/2001 09:51 15.110 jnp-client.jar 25/02/2001 00:14 128.006 log4j.jar Total Files Listed: 7 File(s)622.102 bytes 0 Dir(s) 5.701.087.232 bytes free -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Rettig Christoph Envoyé : vendredi 11 mai 2001 16:30 À : [EMAIL PROTECTED] Objet : Re: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Yes, no problem with -nonaming : catalina.bat run -nonaming. server.xml : Context path= docBase=E:\Projects\web debug=0 reloadable=true/ And all JBoss client JAR files in E:\Projects\web\WEB-INF\lib Nothing else changed to catalina installation directory Oh yes, another one, jndi.properties is not read (if I remember well) so I have to manually System.setProperty java.naming... just before calling new InitialContext() Hi! I'm using catalina in combination with the turbine framework and jbossMQ. I also get exactly these communication errors when trying to get an initial context. Which jar files exactly do you put in your web-inf\lib?? I tried your suggestions (using jbossmq-client.jar) but the error stays the same regards Chris ... ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
IT WORKED I DELETED jndi.jar from my WEB-INF-lib and then it worked THANK YOU! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Vincent Harcq Sent: Friday, May 11, 2001 11:27 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Hi! Please note that I am using a 2.3 beta version so maybe there was some changes in between. But here are the jars I have 1. In Tomcat E:\Projects\p1\tomcat4b1dir /s *.jar Directory of E:\Projects\p1\tomcat4b1\bin 06/01/2001 05:18 24.776 bootstrap.jar 06/01/2001 05:18 98.496 jndi.jar 06/01/2001 05:18 23.514 naming.jar 06/01/2001 05:18 74.753 servlet.jar Directory of E:\Projects\p1\tomcat4b1\lib 06/01/2001 05:18 188.406 crimson.jar 06/01/2001 05:18 272.734 jasper.jar 06/01/2001 05:18 11.809 jaxp.jar 23/02/2001 10:47 85.237 jdom.jar 06/01/2001 05:183.724 namingfactory.jar Directory of E:\Projects\p1\tomcat4b1\server 06/01/2001 05:18 490.878 catalina.jar 06/01/2001 05:18 188.406 crimson.jar 06/01/2001 05:18 29.809 jakarta-regexp-1.2.jar 06/01/2001 05:18 11.809 jaxp.jar 06/01/2001 05:18 31.416 warp.jar 2. In WEB-INF\lib E:\Projects\VMI\main\UltraDevdir /s *.jar Directory of E:\Projects\p1\main\web\WEB-INF\lib 18/02/2001 01:10 175.666 hsql.jar 07/05/2001 09:49 88.843 jboss-client.jar 03/05/2001 16:18 58.461 jboss-j2ee.jar 03/05/2001 16:18 133.040 jbossmq-client.jar 04/05/2001 09:51 22.976 jbosssx-client.jar 04/05/2001 09:51 15.110 jnp-client.jar 25/02/2001 00:14 128.006 log4j.jar Total Files Listed: 7 File(s)622.102 bytes 0 Dir(s) 5.701.087.232 bytes free -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Rettig Christoph Envoyé : vendredi 11 mai 2001 16:30 À : [EMAIL PROTECTED] Objet : Re: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Yes, no problem with -nonaming : catalina.bat run -nonaming. server.xml : Context path= docBase=E:\Projects\web debug=0 reloadable=true/ And all JBoss client JAR files in E:\Projects\web\WEB-INF\lib Nothing else changed to catalina installation directory Oh yes, another one, jndi.properties is not read (if I remember well) so I have to manually System.setProperty java.naming... just before calling new InitialContext() Hi! I'm using catalina in combination with the turbine framework and jbossMQ. I also get exactly these communication errors when trying to get an initial context. Which jar files exactly do you put in your web-inf\lib?? I tried your suggestions (using jbossmq-client.jar) but the error stays the same regards Chris ... ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Yes, I have tried that, and I still get the error. (It seems like it has no effect) Do you have this configuration working? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone Sent: Thursday, May 10, 2001 6:15 PM To: '[EMAIL PROTECTED]' Subject: R: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Do you start Catalina with the -nonaming option, so that from it you connect to JBoss' Naming service ? Simon -Messaggio originale- Da: John Menke [mailto:[EMAIL PROTECTED]] Inviato: mercoledì 9 maggio 2001 23:30 A: jboss Oggetto: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error This error is produced when I try to get an initial JNDI context. The error is: javax.naming.CommunicationException[Root exeption is java.rmi.ServerException: RemoteException occured in server thread; nested exception is java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is java.net.MalformedURL exception: unknown protocol: jndi I can get InitalContext in Tomcat 3.2, but Catalina produces the error. Is there a workaround? ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error
Maybe the -nonaming is not getting executed then? (if it fixed your problem). I am using Catalina from within the Turbine TDK which contains a schell script startup.sh which calls the catalina.sh script. I have added the -nonaming to this line so it reads $BASEDIR/catalina.sh start -nonaming $@ This should turn naming off, but I still get the errors when I start the program this way. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone Sent: Thursday, May 10, 2001 6:42 PM To: '[EMAIL PROTECTED]' Subject: R: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Hey John Yes, I have tried that, and I still get the error. (It seems like it has no effect) Do you have this configuration working? Not exactly. I'm using Catalina with another server application that has its own Naming service, and at the beginning I got the same error on startup, but it went away with the -nonaming option. We then have other problems with this jndi: protocol, also from previous discussions it seems to me a Catalina bug: with us, every class loaded from web-inf/classes or web-inf/lib has a codebase like jndi:/WEB-INF/classes/ or jar:jndi:/WEB-INF/lib/xxx.jar!/, so that if objects of these classes are passed as arguments to any rmi method invocation, on the other side the class annotation is taken from the stream, but of course the classloader cannot understand the Catalina-specific jndi: protocol. The context class loader should take care of that probably, but I did not figured it out yet why it doesn't. I miss Rickard ! Will live, will see. Cheers Simon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone Sent: Thursday, May 10, 2001 6:15 PM To: '[EMAIL PROTECTED]' Subject: R: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error Do you start Catalina with the -nonaming option, so that from it you connect to JBoss' Naming service ? Simon -Messaggio originale- Da: John Menke [mailto:[EMAIL PROTECTED]] Inviato: mercoledì 9 maggio 2001 23:30 A: jboss Oggetto: [JBoss-user] Catalina and Jboss2.2.1 InitialContext error This error is produced when I try to get an initial JNDI context. The error is: javax.naming.CommunicationException[Root exeption is java.rmi.ServerException: RemoteException occured in server thread; nested exception is java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is java.net.MalformedURL exception: unknown protocol: jndi I can get InitalContext in Tomcat 3.2, but Catalina produces the error. Is there a workaround? ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
