Scott:
I had some time to look at the problem last night. It turns out I was
having a conflict with some jars that were mistakenly moved into lib/ext
directory. These jars were removed when I downgraded my sdk. When Jboss
started working I assumed (incorrectly) that the 1.4.2 sdk was the
I'm
running W2K-pro service pack 4, JBoss-Jetty (3.2.2) - sun sdk
1.4.1-02.
I can
try to upgrade my java - otherwise it could be Tomcat !?
- Ren
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Dennis R.
GeskerSent: 17. juli 2003 00:49To:
Ren:
The problem appears to have been sdk 1.4.2. I downgraded to 1.4.1_02
and now run.bat executes just fine. I don't have a Windows server that
isn't patched to Service Pack 4 so I don't know if the problem was with
Windows or the 1.4.2 version of the SDK but I'm inclined to think the
SDK is
JDK1.4.2 is working fine with jboss-3.2.2RC1_tomcat-4.1.24 on an XPsp1 box:
C:\cvs\Releases\jboss-3.2.2RC1_tomcat-4.1.24\binset
JAVA_HOME=/usr/local/Java/j2sdk1.4.2
C:\cvs\Releases\jboss-3.2.2RC1_tomcat-4.1.24\binrun
