Receiving exceptions from TAO with different minor codes...
How do I decipher what is the problem using these minor codes?
The explanation given in Wikipedia is a little confusing.
This is what is mentioned in Wikipedia:
Each standard CORBA exception includes a minor code to designate the subcategory of the exception. Minor exception codes are of type unsigned long and consist of a 20-bit “Vendor Minor Codeset ID” (VMCID), which occupies the high order 20 bits (in my case 0x49540) and the minor code proper which occupies the low order 12 bits (in one case decimal 770 and decimal 512 in the other)
Exception thrown by TAO:
EventIterator::destroy()-org.omg.CORBA.TRANSIENT: cannot establish binding
vmcid: 0x49540000 minor code: 770
But on converting the minor codes to Hex:
770 becomes 0x302 (0x06U Location Code + 0x2U Error Code)
0x06U means CORBA::COMM_FAILURE exception //According to TAO Developer's guide
0x2U means System File table is full //According to TAO Developer's guide
Another exception thrown by TAO:
org.omg.CORBA.COMM_FAILURE: vmcid: 0x49540000 minor code: 512
512 becomes 0x200 (0x04U Location Code + 0x0U Error Code)
0x04U means CORBA::TRANSIENT exception //According to TAO Developer's guide
0x0U means unspecified error code //According to TAO Developer's guide
Could anyone tell me if I am interpreting the minor codes in the wrong way?