java bad magic number error

Hello All, When i'm running configurator executable in the system, I'm getting the bad magic number error and it it coming out, Could some body help me out as how to solve this problem. The error details are as follows:

Starting Configurator run [Date : Wed Aug 1 08:43:59 EDT 2007]
------------------------------------------------------------------

Found executable /opt/java1.4/bin/java
Found executable /usr/bin/dirname
Executing the java code

INTERNAL com.aol.revenue.brd.config.Main.main(Main.java:118) BRD configurator v 1.2 build 0025
Argument = /home/qa38/brd/apps/config/BRD.properties File exist and readable
Argument = PD_MF_PRICE_PLAN.xml.v94_r120 File exist and readable
Exception in thread "main" java.lang.ClassFormatError: com/aol/revenue/brd/config/handler/pd_element_id/PD_ELEMENT_ID (Bad magic number)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:250)
at java.net.URLClassLoader.access$100(URLClassLoader.java:54)
at java.net.URLClassLoader$1.run(URLClassLoader.java:193)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:265)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at com.aol.revenue.brd.config.handler.HandlerService.createHandlerForElement(HandlerService.java:90)
at com.aol.revenue.brd.config.handler.HandlerService.getConfigHandle(HandlerService.java:40)
at com.aol.revenue.brd.config.Main.processXMLData(Main.java:92)
at com.aol.revenue.brd.config.Main.main(Main.java:138)
Configurator return code: 1
ERROR*** Configurator error


The java installation details on my machine are as follow:

java version "1.4.1.01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.01-030304-15:40)
Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.01-030304-17:08-PA_RISC2.0 PA2.0, mixed mode)

--Thanks
Subramanya

Perhaps you are using teh wrong version of Java for the application?

Magic Number, sounds like some sort of prefix in the class file used to identify something, probably a library or JVM version.

Just a random guess, could be totally wrong, but I would check I had the right versions of libraries and JVM's

*shrugs*
G

The magic number is always CAFE BABE in hexadecimal. This does not vary between Java versions. If you had the wrong version of Java, you would get a very specific message telling you that. Therefore, you can discount Java version as the reason for your problem.

Here are some things that might be wrong: -

You're trying to read, as a class file, a file that was never a class file. Review what you are doing, to see if that could have happened.

A class file, or maybe a Jar that it's in, has got corrupted. See whether there's another copy of your software, to compare.

Your class file is intended to be read through a special ClassLoader, which does something to the data in the file, before trying to defineClass() with it. This can be associated with security measures. If so, and you legitimately have rights to the class, then consult with appropriate people as to what the security measures are. If you're trying to crack something you don't have rights to, then you deserve to fail - in everything, not just this.

[ August 02, 2007: Message edited by: Peter Chase ]

If this is happening to java programmers that use modules, then you must read the binary .class module file.

Example:

Instead of this:

 ModuleDescriptor.read(new FileInputStream("module-info.java"));

You have to write this:

 ModuleDescrptor.read(new FileInputStream("module-info.class"));
The .class file in intellij is normally located in \out\production\ package in the root module.

Welcome to the Ranch I hop the original poster (=OP) isn't still struggling with this problem after thirteen years.