Skip to main content


InvalidMethodException is described in the javadoc comments as:

Instances of this class are thrown by BCEL's class file verifier 'JustIce' when the verification of a method is requested that does not exist.
version: $Id:,v 2001/10/29 20:00:33 jvanzyl Exp $ author: Enver Haase

Where is this exception thrown?

Following, is a list of exception messages cross-referenced to the source code responsible for throwing them. Click on the method link to view the code and see how the exception is thrown.

How is this exception thrown?

The following sub-sections identify where this exception is thrown, and how (or why) the code is throwing the exception.

Any source code quoted in this section is subject to the Java Research License unless stated otherwise.

  * Pass 3a is the verification of static constraints of
  * JVM code (such as legal targets of branch instructions).
  * This is the part of pass 3 where you do not need data
  * flow analysis.
  * JustIce also delays the checks for a correct exception
  * table of a Code attribute and correct line number entries
  * in a LineNumberTable attribute of a Code attribute (which
  * conceptually belong to pass 2) to this pass. Also, most
  * of the check for valid local variable entries in a
  * LocalVariableTable attribute of a Code attribute is
  * delayed until this pass.
  * All these checks need access to the code array of the
  * Code attribute.
  * @throws InvalidMethodException if the method to verify does not exist.
public VerificationResult do_verify() {
    if (myOwner.doPass2().equals(VerificationResult.VR_OK)) {
        JavaClass jc = Repository.lookupClass(myOwner.getClassName());
        Method[] methods = jc.getMethods();
        if (method_no >= methods.length) {
            throw new InvalidMethodException('METHOD DOES NOT EXIST!');
        Method method = methods[method_no];
        code = method.getCode();
        if (method.isAbstract() || method.isNative()) {
            return VerificationResult.VR_OK;
        try {
            instructionList = new InstructionList(method.getCode().getCode());
        } catch (RuntimeException re) {
            return new VerificationResult(VerificationResult.VERIFIED_REJECTED, 'Bad bytecode in the code array of the Code attribute of method '' + method + ''.');
        VerificationResult vr = VerificationResult.VR_OK;
        try {
        } catch (ClassConstraintException cce) {
            vr = new VerificationResult(VerificationResult.VERIFIED_REJECTED, cce.getMessage());
            return vr;
        try {
        } catch (StaticCodeConstraintException scce) {
            vr = new VerificationResult(VerificationResult.VERIFIED_REJECTED, scce.getMessage());
        return vr;
    } else {
        return VerificationResult.VR_NOTYET;

Source: "Java SE Downloads: Java SE 6 JDK Source Code", at:


Popular posts from this blog

Connection refused: No available router to destination

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators.

The following exception occurs in WebLogic server logs. Most likely to occur during WebLogic server start-up, but similar exceptions may occur at other times. t3://myserver:8000: Destination unreachable; nested exception is: Connection refused: connect; No available router to destination] at weblogic.jndi.internal.ExceptionTranslator.toNamingException( at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException( at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext( at weblogic.jndi.Environment.getContext( at weblogic.jndi.Environment.getContext(
This message (Connection refused: connect; No available router to destination) is a kind of "catch…

BAD_CERTIFICATE - A corrupt or unuseable certificate...

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators.
In wls_utc, when trying to test a webservice using SSL, the following error message is received: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
If SSL debugging is enabled, the following error also appears in the logs: ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' <1254822672320>>
verification failed because RSA key public exponent [3] is too small
The certificate encryption is of a weaker strength than expected by newer versions of Java.
Add the flag "" to the server startup parameters.


WebLogic Admin Console

WebLogic Admin Console
The WebLogic Admin Console is a web-based, user interface used to configure and control a set of WebLogic servers or clusters (i.e. a "domain"). In any logical group of WebLogic servers there must exist one admin server, which hosts the WebLogic Admin Console application and manages the associated configuration files.
WebLogic Administrators will use the Administration Console for a number of tasks, including:
Starting and stopping WebLogic servers or entire clusters.Configuring server parameters, security, database connections and deployed applications.Viewing server status, health and metrics. Note: It is not strictly necessary to use the Weblogic Admin Console to perform these tasks, as they can be scripted using WLST (the WebLogic Scripting Tool).
Accessing the Admin Console
WebLogic Admin Console Url: http://hostname:port/console.
To access the WebLogic Administration Console, assuming the admin server has been started, goto the above url. Where hostname…