Bugs item #679705, was opened at 2003-02-03 10:40
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=679705&group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Stefan Kuehnel (skuehnel)
Assigned to: Scott M Stark (starksm)
Summary: 3.0.6 fails to start with AbstractMethodError on IBM 1.4 VM

Initial Comment:
TestingJBoss 3.0.6 with an IBM 1.4 VM on Linux I get an
AbstractMethodError on startup for
AbstractDeploymentScanner.scan() when starting the
URLDeploymentScanner.  This happens both if JBoss was
compiled with a Sun as well as an IBM JDK.

System info:

19:01:34,499 INFO  [ServerInfo] Java version: 1.4.0,IBM
Corporation
19:01:34,500 INFO  [ServerInfo] Java VM: Classic VM
1.4.0,IBM Corporation
19:01:34,526 INFO  [ServerInfo] OS-System: Linux
2.4.18-17.7.x,x86

Exception:

2003-02-03 19:01:45,294 INFO 
[org.jboss.deployment.scanner.URLDeploymentScanner]
Starting
2003-02-03 19:01:45,301 ERROR
[org.jboss.deployment.MainDeployer] could not start
deployment:
file:/home/stefan/tools/jboss/jboss-3.0.6-src-IBM/build/output/jboss-3.0.6/server/all/conf/jboss-service.xml
java.lang.AbstractMethodError:
org/jboss/deployment/scanner/AbstractDeploymentScanner.scan
        at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
        at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
        at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown
Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
        at java.lang.reflect.Method.invoke(Method.java:335)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
        at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
        at $Proxy0.start(Unknown Source)
        at
org.jboss.system.ServiceController.start(ServiceController.java:413)
        at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
        at java.lang.reflect.Method.invoke(Method.java:335)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
        at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
        at $Proxy2.start(Unknown Source)
        at
org.jboss.deployment.SARDeployer.start(SARDeployer.java:230)
        at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
        at java.lang.reflect.Method.invoke(Method.java:335)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
        at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325)
        at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:222)
        at org.jboss.Main.boot(Main.java:148)
        at org.jboss.Main$1.run(Main.java:381)
        at java.lang.Thread.run(Thread.java:566)
2003-02-03 19:01:45,468 DEBUG
[org.jboss.util.NestedThrowable]
org.jboss.util.NestedThrowable.parentTraceEnabled=true
2003-02-03 19:01:45,470 DEBUG
[org.jboss.util.NestedThrowable]
org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2003-02-03 19:01:45,470 DEBUG
[org.jboss.util.NestedThrowable]
org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2003-02-03 19:01:45,471 ERROR
[org.jboss.system.server.Server] start failed
org.jboss.deployment.DeploymentException: Could not
create deployment:
file:/home/stefan/tools/jboss/jboss-3.0.6-src-IBM/build/output/jboss-3.0.6/server/all/conf/jboss-service.xml;
- nested throwable: (java.lang.AbstractMethodError:
org/jboss/deployment/scanner/AbstractDeploymentScanner.scan)
        at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:835)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
        at java.lang.reflect.Method.invoke(Method.java:335)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
        at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325)
        at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:222)
        at org.jboss.Main.boot(Main.java:148)
        at org.jboss.Main$1.run(Main.java:381)
        at java.lang.Thread.run(Thread.java:566)
Caused by: java.lang.AbstractMethodError:
org/jboss/deployment/scanner/AbstractDeploymentScanner.scan
        at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
        at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
        at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown
Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
        at java.lang.reflect.Method.invoke(Method.java:335)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
        at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
        at $Proxy0.start(Unknown Source)
        at
org.jboss.system.ServiceController.start(ServiceController.java:413)
        at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
        at java.lang.reflect.Method.invoke(Method.java:335)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
        at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
        at $Proxy2.start(Unknown Source)
        at
org.jboss.deployment.SARDeployer.start(SARDeployer.java:230)
        at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
        ... 14 more
2003-02-03 19:01:45,486 ERROR [STDERR]
org.jboss.deployment.DeploymentException: Could not
create deployment:
file:/home/stefan/tools/jboss/jboss-3.0.6-src-IBM/build/output/jboss-3.0.6/server/all/conf/jboss-service.xml;
- nested throwable: (java.lang.AbstractMethodError:
org/jboss/deployment/scanner/AbstractDeploymentScanner.scan)
2003-02-03 19:01:45,486 ERROR [STDERR]  at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:835)
2003-02-03 19:01:45,487 ERROR [STDERR]  at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
2003-02-03 19:01:45,487 ERROR [STDERR]  at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
2003-02-03 19:01:45,487 ERROR [STDERR]  at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
2003-02-03 19:01:45,487 ERROR [STDERR]  at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2003-02-03 19:01:45,488 ERROR [STDERR]  at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
2003-02-03 19:01:45,488 ERROR [STDERR]  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
2003-02-03 19:01:45,488 ERROR [STDERR]  at
java.lang.reflect.Method.invoke(Method.java:335)
2003-02-03 19:01:45,491 ERROR [STDERR]  at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
2003-02-03 19:01:45,492 ERROR [STDERR]  at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
2003-02-03 19:01:45,492 ERROR [STDERR]  at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325)
2003-02-03 19:01:45,493 ERROR [STDERR]  at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:222)
2003-02-03 19:01:45,493 ERROR [STDERR]  at
org.jboss.Main.boot(Main.java:148)
2003-02-03 19:01:45,493 ERROR [STDERR]  at
org.jboss.Main$1.run(Main.java:381)
2003-02-03 19:01:45,493 ERROR [STDERR]  at
java.lang.Thread.run(Thread.java:566)
2003-02-03 19:01:45,493 ERROR [STDERR] Caused by:
java.lang.AbstractMethodError:
org/jboss/deployment/scanner/AbstractDeploymentScanner.scan
2003-02-03 19:01:45,494 ERROR [STDERR]  at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
2003-02-03 19:01:45,494 ERROR [STDERR]  at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
2003-02-03 19:01:45,494 ERROR [STDERR]  at
sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
2003-02-03 19:01:45,494 ERROR [STDERR]  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
2003-02-03 19:01:45,495 ERROR [STDERR]  at
java.lang.reflect.Method.invoke(Method.java:335)
2003-02-03 19:01:45,495 ERROR [STDERR]  at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
2003-02-03 19:01:45,495 ERROR [STDERR]  at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
2003-02-03 19:01:45,495 ERROR [STDERR]  at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
2003-02-03 19:01:45,496 ERROR [STDERR]  at
$Proxy0.start(Unknown Source)
2003-02-03 19:01:45,496 ERROR [STDERR]  at
org.jboss.system.ServiceController.start(ServiceController.java:413)
2003-02-03 19:01:45,496 ERROR [STDERR]  at
sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
2003-02-03 19:01:45,496 ERROR [STDERR]  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
2003-02-03 19:01:45,496 ERROR [STDERR]  at
java.lang.reflect.Method.invoke(Method.java:335)
2003-02-03 19:01:45,497 ERROR [STDERR]  at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
2003-02-03 19:01:45,497 ERROR [STDERR]  at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
2003-02-03 19:01:45,497 ERROR [STDERR]  at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
2003-02-03 19:01:45,497 ERROR [STDERR]  at
$Proxy2.start(Unknown Source)
2003-02-03 19:01:45,498 ERROR [STDERR]  at
org.jboss.deployment.SARDeployer.start(SARDeployer.java:230)
2003-02-03 19:01:45,498 ERROR [STDERR]  at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
2003-02-03 19:01:45,498 ERROR [STDERR]  ... 14 more


----------------------------------------------------------------------

>Comment By: Scott M Stark (starksm)
Date: 2003-03-31 14:57

Message:
Logged In: YES 
user_id=175228

The hack of explicitly declaring an abstract scan() method
in the AbstractDeploymentScanner has been tested as a
workaround for this problem. This change will be in the
3.0.7 and 3.2.0 releases.

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2003-03-24 15:54

Message:
Logged In: YES 
user_id=175228

It builds because the class is declared abstract. That this
addition causes it to work points to a bug in the IBM compiler.

----------------------------------------------------------------------

Comment By: Marko Strukelj (mstruk)
Date: 2003-03-23 09:12

Message:
Logged In: YES 
user_id=625403

Here is how you fix this:

go to $jboss_src/system/src/main/org/jboss/deployment/scanner/

and open AbstractDeploymentScanner.java

Go to the very end just before the final curly slash and
insert this line:

public abstract void scan() throws Exception;


Rebuild sources, deploy in the newly built jboss  et Voila !


Beats me how AbstractDeploymentScanner even gets built
without this method. Must be some build magic jboss uses or
the compilers are all broken.

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2003-03-07 08:05

Message:
Logged In: YES 
user_id=175228

I can't even compile the 3.0.6 code on my RedHat 8 box with
wither the IBM 1.4 or 1.3.1 JDKs because they both are 
puking
on something in the jmx module:

[EMAIL PROTECTED] build]$ export 
JAVA_HOME=~/Java/IBMJava2-14
[EMAIL PROTECTED] build]$ 
PATH=$JAVA_HOME/bin:$PATH
[EMAIL PROTECTED] build]$ java -version
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 
1.4.0)
Classic VM (build 1.4.0, J2RE 1.4.0 IBM build cxia32140-
20020917a (JIT enabled: jitc))

[EMAIL PROTECTED] build]$ ./build.sh      
Searching for build.xml ...
Buildfile: /home/starksm/JBoss/jboss-3.0.6-src/build/build.xml
...
compile-classes:
    [mkdir] Created dir: /home/starksm/JBoss/jboss-3.0.6-
src/jmx/output/classes
    [javac] Compiling 455 source files 
to /home/starksm/JBoss/jboss-3.0.6-src/jmx/output/classes
[execmodules] error: IO exception 
sun.io.MalformedInputException
[execmodules] error: IO exception 
sun.io.MalformedInputException
[execmodules] /home/starksm/JBoss/jboss-3.0.6-
src/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.j
ava:70: cannot resolve symbol
[execmodules] symbol  : method create  
(javax.management.MBeanInfo,java.lang.Object)
[execmodules] location: class 
org.jboss.mx.capability.OptimizedMBeanDispatcher
[execmodules]          dispatcher = 
OptimizedMBeanDispatcher.create(info, resource /*, parent 
classloader */);
[execmodules]                                               ^
[execmodules] /home/starksm/JBoss/jboss-3.0.6-
src/jmx/src/main/org/jboss/mx/logging/log4j/Log4jAdapter.java
:58: warning: getPriority() in org.apache.log4j.Category has 
been deprecated


[EMAIL PROTECTED] build]$ export 
JAVA_HOME=~/Java/IBMJava2-131
[EMAIL PROTECTED] build]$ 
PATH=$JAVA_HOME/bin:$PATH
[EMAIL PROTECTED] build]$ java -version
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 
1.3.1)
Classic VM (build 1.3.1, J2RE 1.3.1 IBM build cxia32131-
20021102 (JIT enabled: jitc))


[EMAIL PROTECTED] build]$ ./build.sh      
Searching for build.xml ...
Buildfile: /home/starksm/JBoss/jboss-3.0.6-src/build/build.xml
...
compile-classes:
    [mkdir] Created dir: /home/starksm/JBoss/jboss-3.0.6-
src/jmx/output/classes
    [javac] Compiling 455 source files 
to /home/starksm/JBoss/jboss-3.0.6-src/jmx/output/classes
[execmodules] error: The encoding null is not supported
[execmodules] error: The encoding null is not supported
[execmodules] /home/starksm/JBoss/jboss-3.0.6-
src/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.j
ava:70: cannot resolve symbol
[execmodules] symbol  : method create  
(javax.management.MBeanInfo,java.lang.Object)
[execmodules] location: class 
org.jboss.mx.capability.OptimizedMBeanDispatcher
[execmodules]          dispatcher = 
OptimizedMBeanDispatcher.create(info, resource /*, parent 
classloader */);
[execmodules]                                  


If I run with the IBM 1.4.0 VM using a binary compiled with 
the Sun 1.3.1_05
JDK it starts up just fine:

[EMAIL PROTECTED] bin]$ ./run.sh
============================================
====================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /home/starksm/JBoss/jboss-3.0.6

  JAVA: /home/starksm/Java/IBMJava2-14/bin/java

  JAVA_OPTS:  -Dprogram.name=run.sh

  CLASSPATH: /home/starksm/JBoss/jboss-
3.0.6/bin/run.jar:/home/starksm/Java/IBMJava2-14/lib/tools.jar
...
08:10:08,581 INFO  [MainDeployer] Deployed package: 
file:/home/starksm/JBoss/jboss-
3.0.6/server/default/conf/jboss-service.xml
08:10:08,585 INFO  [Server] JBoss (MX MicroKernel) [3.0.6 
(CVSTag=JBoss_3_0_6 Date=200302230935)] Started in 
0m:33s:220ms


----------------------------------------------------------------------

Comment By: Stefan Kuehnel (skuehnel)
Date: 2003-03-07 05:11

Message:
Logged In: YES 
user_id=596644

Before submitting this bug I had already tried that and 
recompiled from source with the IBM 1.4.0 SDK, but it didn't 
make a difference, the error remained the same.  When 
compiling with IBM 1.3.1 the above error doesn't appear.  But 
then when using the 1.3 compiled JBoss on 1.4. one runs into 
the AFAIK well known problem that JBossRMIClassLoader can't 
be found during boot.




So the final word here is: Forget about the IBM 1.4 JVM, JBoss 
doesn't support it?




----------------------------------------------------------------------

Comment By: Juha Lindfors (juhalindfors)
Date: 2003-03-06 03:27

Message:
Logged In: YES 
user_id=175239

I think this is a byte code incompatibility with SUN compiler 
and IBM virtual machine. Try recompiling from the source 
using IBM's compiler.


----------------------------------------------------------------------

Comment By: Frederic Lachasse (flachasse)
Date: 2003-03-04 12:35

Message:
Logged In: YES 
user_id=496388

I got the same exception using IBM JDK 1.3.0 and 1.3.1 on 
AIX. Using AIX, I am stuck with the IBM JDK, so this is a 
huge problem for me.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=679705&group_id=22866


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to