[JBoss-dev] Naming service startup problem...

[Luke Taylor]

I've got a problem with my Maven build. I've pretty much build a replica 
of the JBoss server as it stands with the current build, but during 
startup, the naming service appears to be trying to use tyrex classes 
instead of the jnp ones and I've no idea where it's getting the idea 
from. The jndi.properties file is in the conf directory (I assume that's 
where it bootstraps from) but I get the following exception in the log 
during startup (and things naturally screw up from then on):

<log>
2003-06-18 19:06:35,218 DEBUG [org.jboss.system.ServiceController] 
starting service jboss:service=Naming
2003-06-18 19:06:35,218 INFO  [org.jboss.naming.NamingService] Starting
2003-06-18 19:06:35,265 DEBUG [org.jboss.naming.NamingService] 
System.setProperty, key=java.naming.factory.initial, 
value=tyrex.naming.MemoryContextFactory
2003-06-18 19:06:35,281 DEBUG [org.jboss.naming.NamingService] 
System.setProperty, key=java.naming.provider.url, value=
2003-06-18 19:06:35,281 DEBUG [org.jboss.naming.NamingService] 
System.setProperty, key=java.naming.factory.url.pkgs, value=tyrex.naming
2003-06-18 19:06:35,281 INFO  [org.jboss.naming.NamingService] Starting 
jnp server
2003-06-18 19:06:35,531 DEBUG [org.jboss.naming.NamingService] 
NamingServer stub: org.jnp.server.NamingServer_Stub[RemoteStub [ref: 
[endpoint:[217.39.46.22:1978](local),objID:[0]]]]
2003-06-18 19:06:35,703 INFO  [org.jboss.naming.NamingService] Started 
jnpPort=1099, rmiPort=0, backlog=50, bindAddress=null, Client 
SocketFactory=null, Server SocketFactory=null
2003-06-18 19:06:35,859 DEBUG [org.jboss.naming.NamingService] 
InitialContext Environment:
2003-06-18 19:06:35,859 DEBUG [org.jboss.naming.NamingService] 
key=java.naming.factory.initial, value=tyrex.naming.MemoryContextFactory
2003-06-18 19:06:35,859 DEBUG [org.jboss.naming.NamingService] 
key=java.naming.provider.url, value=
2003-06-18 19:06:35,875 DEBUG [org.jboss.naming.NamingService] 
key=java.naming.factory.url.pkgs, 
value=tyrex.naming:tyrex.naming:org.jboss.naming:org.jnp.interfaces
2003-06-18 19:06:35,875 WARN  [org.jboss.naming.NamingService] 
Context.PROVIDER_URL in server jndi.properties, url=
2003-06-18 19:06:36,140 ERROR [org.jboss.naming.NamingService] Starting 
failed: javax.naming.OperationNotSupportedException: Context is read-only
2003-06-18 19:06:36,156 WARN  [org.jboss.system.ServiceController] 
Problem starting service jboss:service=Naming
javax.naming.OperationNotSupportedException: Context is read-only
	at tyrex.naming.EnvContext.rebind(EnvContext.java:345)
	at org.jboss.naming.NamingService.startService(NamingService.java:189)
	at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:233)

</log>

Anyone any ideas why it would be picking up the wrong classes?

Luke.

--
 Luke Taylor.                      Monkey Machine Ltd.
 PGP Key ID: 0x57E9523C            http://www.monkeymachine.ltd.uk




-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development