Skip to main content

AddressingDispositionException

com.sun.corba.se.impl.protocol.AddressingDispositionException

AddressingDispositionException is described in the javadoc comments as:

This exception is thrown while reading GIOP 1.2 Request, LocateRequest to indicate that a TargetAddress disposition is unacceptable. If this exception is caught explicitly, this need to be rethrown. This is eventually handled within RequestPRocessor and an appropriate reply is sent back to the client. GIOP 1.2 allows three dispositions : KeyAddr (ObjectKey), ProfileAddr (ior profile), IORAddressingInfo (IOR). If the ORB does not support the disposition contained in the GIOP Request / LocateRequest 1.2 message, then it sends a Reply / LocateReply indicating the correct disposition, which the client ORB shall use to transparently retry the request with the correct disposition.

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.

com.sun.corba.se.impl.protocol.giopmsgheaders.MessageBase.extractObjectKey(TargetAddress, ORB)

/**
     * Extract the object key from TargetAddress.
     * @return ObjectKey the object key.
     */
static ObjectKey extractObjectKey(TargetAddress target, ORB orb) {
    short orbTargetAddrPref = orb.getORBData().getGIOPTargetAddressPreference();
    short reqAddrDisp = target.discriminator();
    switch(orbTargetAddrPref) {
        case ORBConstants.ADDR_DISP_OBJKEY:
            if (reqAddrDisp != KeyAddr.value) {
                throw new AddressingDispositionException(KeyAddr.value);
            }
            break;
        case ORBConstants.ADDR_DISP_PROFILE:
            if (reqAddrDisp != ProfileAddr.value) {
                throw new AddressingDispositionException(ProfileAddr.value);
            }
            break;
        case ORBConstants.ADDR_DISP_IOR:
            if (reqAddrDisp != ReferenceAddr.value) {
                throw new AddressingDispositionException(ReferenceAddr.value);
            }
            break;
        case ORBConstants.ADDR_DISP_HANDLE_ALL:
            break;
        default:
            throw wrapper.orbTargetAddrPreferenceInExtractObjectkeyInvalid();
    }
    try {
        switch(reqAddrDisp) {
            case KeyAddr.value:
                byte[] objKey = target.object_key();
                if (objKey != null) {
                    ObjectKey objectKey = orb.getObjectKeyFactory().create(objKey);
                    if (objectKey != null) {
                        return objectKey;
                    }
                }
                break;
            case ProfileAddr.value:
                IIOPProfile iiopProfile = null;
                TaggedProfile profile = target.profile();
                if (profile != null) {
                    iiopProfile = IIOPFactories.makeIIOPProfile(orb, profile);
                    ObjectKey objectKey = iiopProfile.getObjectKey();
                    if (objectKey != null) {
                        return objectKey;
                    }
                }
                break;
            case ReferenceAddr.value:
                IORAddressingInfo iorInfo = target.ior();
                if (iorInfo != null) {
                    profile = iorInfo.ior.profiles[iorInfo.selected_profile_index];
                    iiopProfile = IIOPFactories.makeIIOPProfile(orb, profile);
                    ObjectKey objectKey = iiopProfile.getObjectKey();
                    if (objectKey != null) {
                        return objectKey;
                    }
                }
                break;
            default:
                break;
        }
    } catch (Exception e) {
    }
    throw wrapper.invalidObjectKey();
}

Source: "Java SE Downloads: Java SE 6 JDK Source Code", at: http://www.oracle.com/technetwork/java/javase/downloads/index.html

Comments

Popular posts from this blog

NullPointerException

java.lang.NullPointerException NullPointerException is described in the javadoc comments as: Thrown when an application attempts to use null in a case where an object is required. These include: Calling the instance method of a null object. Accessing or modifying the field of a null object. Taking the length of null as if it were an array. Accessing or modifying the slots of null as if it were an array. Throwing null as if it were a Throwable value. Applications should throw instances of this class to indicate other illegal uses of the null object. author: unascribed version: 1.19, 12/19/03 since: JDK1.0 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. The message ' java.lang.NullPointerException: ' is thrown within the method: com.sun.corba.se.impl.interceptors.ClientRequestInfoImpl.get_r

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. Symptom 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. java.net.ConnectException: t3://myserver:8000: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused: connect; No available router to destination] at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:49) at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:363) at weblogic.jndi.Environment.getContext(Environment.java:307) at weblogic.jndi.Environment.getContext(Environment.java:277) Cause This message (Connection refused: connect; No available

SocketException

java.net.SocketException SocketException is described in the javadoc comments as: Thrown to indicate that there is an error in the underlying protocol, such as a TCP error. author: Jonathan Payne version: 1.17, 12/19/03 since: JDK1.0 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. The message ' java.net.SocketException: ... ' is thrown within the method: java.net.ServerSocket.createImpl() The message ' java.net.SocketException: ... ' is thrown within the method: java.net.Socket.createImpl(boolean) The message ' java.net.SocketException: ... ' is thrown within the method: java.net.SocksSocketImpl.connect(SocketAddress, int) The message ' java.net.SocketException: ... ' is thrown within the method: java.net.SocksSocketImpl.socksBind(InetSocketAddress) The message