Skip to main content


ForwardException is described in the javadoc comments as:


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.

public void handle(ObjectKey okey) {
    IOR newIOR = null;
    ServerLocationPerORB location;
    ObjectKeyTemplate oktemp = okey.getTemplate();
    int serverId = oktemp.getServerId();
    String orbId = oktemp.getORBId();
    try {
        ServerTableEntry entry = getEntry(serverId);
        location = locateServerForORB(entry, orbId, true);
        if (debug) System.out.println('ServerManagerImpl: handle called for server id' + serverId + '  orbid  ' + orbId);
        int clearPort = 0;
        EndPointInfo[] listenerPorts = location.ports;
        for (int i = 0; i < listenerPorts.length; i++) {
            if ((listenerPorts[i].endpointType).equals(IIOP_CLEAR_TEXT.value)) {
                clearPort = listenerPorts[i].port;
        IIOPAddress addr = IIOPFactories.makeIIOPAddress(orb, location.hostname, clearPort);
        IIOPProfileTemplate iptemp = IIOPFactories.makeIIOPProfileTemplate(orb, GIOPVersion.V1_2, addr);
        if (GIOPVersion.V1_2.supportsIORIIOPProfileComponents()) {
        IORTemplate iortemp = IORFactories.makeIORTemplate(oktemp);
        newIOR = iortemp.makeIOR(orb, 'IDL:org/omg/CORBA/Object:1.0', okey.getId());
    } catch (Exception e) {
        throw wrapper.errorInBadServerIdHandler(e);
    if (debug) System.out.println('ServerManagerImpl: handle ' + 'throws ForwardException');
    try {
    } catch (Exception e) {
        System.out.println('Exception = ' + e);
    throw new ForwardException(orb, newIOR);

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

public void invokeServerPIEndingPoint(ReplyMessage replyMessage) {
    if (!hasServerInterceptors) return;
    ServerRequestInfoImpl info = peekServerRequestInfoImplStack();
    if (!info.getAlreadyExecuted()) {
        int replyStatus = replyMessage.getReplyStatus();
        short piReplyStatus = REPLY_MESSAGE_TO_PI_REPLY_STATUS[replyStatus];
        if ((piReplyStatus == LOCATION_FORWARD.value) || (piReplyStatus == TRANSPORT_RETRY.value)) {
        Exception prevException = info.getException();
        if (!info.isDynamic() && (piReplyStatus == USER_EXCEPTION.value)) {
        short newPIReplyStatus = info.getReplyStatus();
        Exception newException = info.getException();
        if ((newPIReplyStatus == SYSTEM_EXCEPTION.value) && (newException != prevException)) {
            throw (SystemException) newException;
        if (newPIReplyStatus == LOCATION_FORWARD.value) {
            if (piReplyStatus != LOCATION_FORWARD.value) {
                IOR ior = info.getForwardRequestIOR();
                throw new ForwardException(orb, ior);
            } else if (info.isForwardRequestRaisedInEnding()) {

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

     * Handles exceptions for the starting and intermediate points for
     * server request interceptors.  This is common code that has been
     * factored out into this utility method.
     * This method will NOT work for ending points.
private void serverPIHandleExceptions(ServerRequestInfoImpl info) {
    int endingPointCall = info.getEndingPointCall();
    if (endingPointCall == ServerRequestInfoImpl.CALL_SEND_EXCEPTION) {
        throw (SystemException) info.getException();
    } else if ((endingPointCall == ServerRequestInfoImpl.CALL_SEND_OTHER) && (info.getForwardRequestException() != null)) {
        IOR ior = info.getForwardRequestIOR();
        throw new ForwardException(orb, ior);

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

public void getInvocationServant(OAInvocationInfo info) {
    try {
        if (debug) {
            ORBUtility.dprint(this, 'Calling getInvocationServant on poa ' + this);
        java.lang.Object servant = null;
        try {
            servant = mediator.getInvocationServant(, info.getOperation());
        } catch (ForwardRequest freq) {
            throw new ForwardException(getORB(), freq.forward_reference);
    } finally {
        if (debug) {
            ORBUtility.dprint(this, 'Exiting getInvocationServant on poa ' + this);

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…