You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2002/12/27 01:08:17 UTC
RE: JDK 1.3.0 problem with latest James.
The problem is with Phoenix 4.0.1 and JVM 1.3.0, not with James, per se. I
don't know what specifically causes the exception, but Phoenix never gets to
James code. It dies internally first.
--- Noel
-----Original Message-----
From: Harmeet Bedi [mailto:harmeet@kodemuse.com]
Sent: Thursday, December 26, 2002 21:24
To: James Developers List
Subject: JDK 1.3.0 problem with latest James.
Latest James distribution does not work on Windows JDK 1.3.0. Phoenix seems
to break with JDK 1.3. I believe, Noel had reported this issue to Avalon
folks for Linux earlier. Danny had also talked about this earlier.
I am almost sure that the earlier 2.1 versions(post Phoenix) upgrade worked
with JDK 1.3.0 but the latest does not.
Upgrading to JDK 1.3.1 fixes this.
Thinking of changing readme etc. to reflect this unless someone has an
insight into making James work with JDK 1.3.
Harmeet
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: JDK 1.3.0 problem with latest James.
Posted by "Noel J. Bergman" <no...@devtech.com>.
> It maybe something to do with the way Phoenix has been compiled. Maybe a
> JDK1.3 compilation would fix things.
Perhaps. But that is something that the Avalon folks ought to deal with. I
really don't want to see us taking over the build process for included
platform code.
--- Noel
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JDK 1.3.0 problem with latest James.
Posted by Harmeet Bedi <ha...@kodemuse.com>.
----- Original Message -----
From: "Noel J. Bergman" <no...@devtech.com>
> The problem is with Phoenix 4.0.1 and JVM 1.3.0, not with James, per se.
There is a Phoenix README.txt in the distribution that says it support JDK
1.3 or higer. Should change this to 1.3.1 or higher if we can't get Phoenix
to work with JDK 1.3.0.
> I
> don't know what specifically causes the exception, but Phoenix never gets
to
> James code. It dies internally first.
It maybe something to do with the way Phoenix has been compiled. Maybe a
JDK1.3 compilation would fix things.
One interesting thing is that Phoenix breaks in different places with JDK
1.3 Hotspot and classic VM.
Harmeet
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>