Your first problem is java1.4
Sun will have fixed version of jmxri.jar available soon.
If you want more info search the forums.
I don't think this stops the server working. It
just causes lots of exceptions and you can't use
Your second problem is that you aren't getting an
initial context. Can you check the contents of
JBOSS_DIST\conf\default\jndi.properties contents follow:
# Do NOT uncomment this line as it causes in VM calls to go over
That's the jndi.properties file you're referring to I presume. I haven't changed it since the install.
That's a weird one.
Have you changed the classpath? You might have a
jndi.properties somewhere else?
JBOSS_DIST = C:\jboss-3.0.0beta
There's the one jndi.properties I told you about, then another at jboss_dist\admin\client with the following contents:
J2EE_HOME = C:\j2sdkee1.3_01
-- does JBoss add this to it's classpath?
I've got one jndi.properties at J2EE_HOME\lib\classes with the following contents:
There are several other jndi.properties files, but they shouldn't be in the classpath. They are all from previous JBoss installations that I have sitting on my computer. I checked my static classpath and there are no jndi.properties files located anywhere in the static classpath.
Perhaps you could clue me in on what is weird, and what is normal... I just what to be like everyone else, man. ;)
I should throw in at this point that all the exceptions are gone, so the first problem (using JRE 1.4) was the root cause of all that. I'm presuming that you saw another issue that I was not aware of, but if that is not the case, then perhaps we're finished here.
There is only one remaining oddity that I'm aware of (besides my own application) and that is there are still some JAR files that could not be opened. I attached the system.log again so you can see which I'm referring to. And I'm still ironing out the wrinkles in my application so you can ignore the deployer exceptions.
Did you forget the attachment?
Don't worry about the cannot find errors.
These are third party jars. We provide the required
classes using a different mechanism.
Either the jars in lib and are loaded at boot time or
the classes are in a different jar to the one
specified in the manifest.