javavmwrapper messes up amavisd-new

[Jiawei Ye]

On Mon, 6 Dec 2004 15:13:39 +0100, Herve Quiroz
<herve.quiroz at esil.univ-mrs.fr> wrote:
> Do you have any JAVA* variable defined? Please try unsetting all of them
> (JAVA_VERSION, JAVA_HOME, JAVAVM...). The error you reported should only
> be raised if some criteria is specified regarding the JVM and a suitable
> JVM cannot be found. When nothing is specified, any JVM would fit and
> thus javavmwrapper will raise no error.
> 
> OTOH, maybe you just have javavmwrapper installed and no JDK, and thus
> there is a 'java' executable with no JDK to run on the other side (thus
> no suitable JVM, as there's no JVM at all). But I doubt this is the
> case.
> 
> Herve
I have a valid JDK with no JAVA_* set in the environment. Running
'java' in a normal shell gives normal results. My guess is that
amavisd-new runs 'java' with an incorrect search path which is later
passed to the javavmwrapper executable. Any thoughts on how to verify
that point?

Jiawei


-- 
"Without the userland, the kernel is useless."
               --inspired by The Tao of Programming