Getting error "URI index 0 is not valid" in Oracle Service Bus

Question

Dear Friends,
I am receiving an error "URI index 0 is not valid" while executing Customization File in Oracle Service Bus. I am not able to figure out why it is happening. Please help.
Thank you.
Regards,
Palak Mathur

Answer 1

AbhishekJ wrote:
Change the:
<xt:value>
<tableElement xmlns:tran="http://www.bea.com/wli/sb/transports">
<URI>http://app-1ip-alsb-01.corp.intranet/ServiceAddressV1Proxy</URI>
<weight>1</weight>
</tableElement>
</xt:value>Section to:
<xt:value>
<tran:tableElement xmlns:tran="http://www.bea.com/wli/sb/transports">
<tran:URI>http://app-1ip-alsb-01.corp.intranet/ServiceAddressV1Proxy</tran:URI>
<tran:weight>1</tran:weight>
</tran:tableElement>
</xt:value>in your Customization File and try again.Hi Abhishek,
I did the same thing. Actually, the deployment team was getting this error and they called me up to find out. I analyzed and sent the following response:-
I was going through the Customization file. I removed all the elements from the file and started with only 1 envValueAssignments:-
+<cus:envValueAssignments>+
+<xt:envValueType>Service URI Weight</xt:envValueType>+
+<xt:location>0</xt:location>+
+<xt:owner>+
+<xt:type>BusinessService</xt:type>+
+<xt:path>CommonServices/Business Services/ServiceAddressV1RS</xt:path>+
+</xt:owner>+
+<xt:value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">0</xt:value>+
+</cus:envValueAssignments>+
The customization file got executed perfectly. Then I added another envValueAssignments and it worked fine as well.
Now, when I added
+<cus:envValueAssignments>+
+<xt:envValueType>Service URI Table</xt:envValueType>+
+<xt:location xsi:nil="true"/>+
+<xt:owner>+
+<xt:type>BusinessService</xt:type>+
+<xt:path>CommonServices/Business Services/ServiceAddressV1RS</xt:path>+
+</xt:owner>+
+<xt:value>+
+<tableElement xmlns:tran="http://www.bea.com/wli/sb/transports">+
+<URI>http://app-1ip-alsb-01.corp.intranet/ServiceAddressV1Proxy</URI>+
+<weight>0</weight>+
+</tableElement>+
+</xt:value>+
+</cus:envValueAssignments>+
+, I got the above error, ie URI index 0 is not valid. If you check each element then you will know that tableElement defines a namespace as xmlns:tran="http://www.bea.com/wli/sb/transports" which is neither being used by the node nor its child elements. Also the error in server logs was:-com.bea.wli.sb.transports.TransportException: URI index 0 is not valid.+
It stuck that we were doing something wrong here. I checked other elements in the same file and found that some of them were starting the node as <tableElement xmlns="http://www.bea.com/wli/sb/transports">. So, tableElements should be qualified with this namespace:-http://www.bea.com/wli/sb/transports. It was clear there was issue with qualified name of the element and hence I added the prefix "tran" and made entry as:-
+<tran:tableElement xmlns:tran="http://www.bea.com/wli/sb/transports">+
+<tran:URI>http://app-1ip-alsb-01.corp.intranet/ServiceAddressV1Proxy</tran:URI>+
+<tran:weight>0</tran:weight>+
+</tran:tableElement>+
When I executed the changed customization file it worked. I checked with few more elements and they all worked making me sure that this was the error.
So, the issue was that the OSB was not able to find any URI and for index 0 there was no URI available. Hence we were getting a weird error which was not at all user friendly. However, while making the OSb they must have thought that no one will make any manual changes (by hand in the file) and this error would be sufficient to tell that there is something wrong with the customization and we must regenerate the customization file.
Only solution that we do not receive this error in future is rather than making changes to the customization file manually we should use OSB console or scripts to replace the properties. Otherwise we need to be very careful while touching the Customization file.
Hope this helps.