Skip to main content


StaticCodeInstructionConstraintException is described in the javadoc comments as:

Instances of this class are thrown by BCEL's class file verifier 'JustIce' when a class file to verify does not pass the verification pass 3 because of a violation of a static constraint as described in the Java Virtual Machine Specification, Second edition, 4.8.1, pages 133-137. The static constraints checking part of pass 3 is called pass 3a in JustIce. Static constraints on the instructions in the code array are checked early in pass 3a and are described on page 134 in the Java Virtual Machine Specification, Second Edition.
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.

  * These are the checks if constraints are satisfied which are described in the
  * Java Virtual Machine Specification, Second Edition as Static Constraints on
  * the instructions of Java Virtual Machine Code (chapter 4.8.1).
  * @throws StaticCodeConstraintException if the verification fails.
private void pass3StaticInstructionChecks() {
    if (!(code.getCode().length < 65536)) {
        throw new StaticCodeInstructionConstraintException('Code array in code attribute '' + code + '' too big: must be smaller than 65536 bytes.');
    InstructionHandle ih = instructionList.getStart();
    while (ih != null) {
        Instruction i = ih.getInstruction();
        if (i instanceof IMPDEP1) {
            throw new StaticCodeInstructionConstraintException('IMPDEP1 must not be in the code, it is an illegal instruction for _internal_ JVM use!');
        if (i instanceof IMPDEP2) {
            throw new StaticCodeInstructionConstraintException('IMPDEP2 must not be in the code, it is an illegal instruction for _internal_ JVM use!');
        if (i instanceof BREAKPOINT) {
            throw new StaticCodeInstructionConstraintException('BREAKPOINT must not be in the code, it is an illegal instruction for _internal_ JVM use!');
        ih = ih.getNext();
    Instruction last = instructionList.getEnd().getInstruction();
    if (!((last instanceof ReturnInstruction) || (last instanceof RET) || (last instanceof GotoInstruction) || (last instanceof ATHROW))) throw new StaticCodeInstructionConstraintException('Execution must not fall off the bottom of the code array. This constraint is enforced statically as some existing verifiers do - so it may be a false alarm if the last instruction is not reachable.');

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…