-
1. Re: *could not start deployment* during first start
adrian.brock Apr 2, 2003 5:57 PM (in response to chaloupka)This is a bug in the IBM 1.4 compiler.
If you compile it with another compiler
it works and it will run on 1.4 VM.
The IBM VM has another bug that stops it
running JBoss.
Workarounds have been determined,
they should be available in the jboss3.2.0 and
jboss3.0.7 releases available soon.
You could try 3.2 from cvs...
Regards,
Adrian -
2. Re: *could not start deployment* during first start
chaloupka Apr 3, 2003 1:29 AM (in response to chaloupka)Thanks ...
Jiri -
3. Re: *could not start deployment* during first start
sblezard Jan 12, 2004 7:43 AM (in response to chaloupka)Hi,
I am currently trying to build the Jboss 2.3.2 source against the Linux 1.4.1 IBM JDK. It does not build, I get this error:
[javac] Compiling 491 source files to /home/sean/jboss-3.2.3-src/jmx/output/classes
error: IO exception sun.io.MalformedInputException
error: IO exception sun.io.MalformedInputException
error: IO exception sun.io.MalformedInputException
/home/sean/jboss-3.2.3-src/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.java:70: cannot access org.jboss.mx.capability.OptimizedMBeanDispatcher
bad class file: /home/sean/jboss-3.2.3-src/jmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.java
file does not contain class org.jboss.mx.capability.OptimizedMBeanDispatcher
Please remove or make sure it appears in the correct subdirectory of the classpath.
dispatcher = OptimizedMBeanDispatcher.create(info, resource /*, parent classloader */);
^
4 errors
Basically, I can't do anything useful with Jboss and the IBM JDK - which I need to use in our AIX environment. Is Jboss and AIX a non-starter? I am trying to move the company away from Jrun towards Jboss but a lot of our customers have AIX so it could be a non-starter for now.
Sean.