Query hangs indefinitely

Question

Our product uses ODP.NET to communicate with the Oracle instance for our clients. One particular client is on 11.2 and we are having trouble pulling back data for one particular table in their db. We are using Oracle Client 10.2 but have also tried 11.2.
Things to note are that this table uses a LONG datatype so we are setting InitialLongFetchSize to -1 so we can pull back all of the data. We ran wireshark to look at the network traffic when we encountered it and saw that we simply stopped receiving data from Oracle and it closed the connection on its end while the client sat there waiting.
We only get this issue when querying this table and we suspect it may be related to the LONG datatype the table has, since we don't see the issue with any other table that we query (and none of them use LONG).
Has anyone ever encountered anything like this before? Any ideas would be appreciated as we have been trying to trouble shoot this issue for a matter of weeks and have no been able to reproduce it anywhere else.
Thank you,
Steve

Answer 1

Here is what I have traced this issue back to. Note that both query and put document steps are working with the same container.
// 1. query
String xquery = "collection('2-201.dbxml')/cust";
XmlTransaction xmlTransaction = xmlManager.createTransaction();
XmlQueryContext queryContext = xmlManager.createQueryContext();
XmlResults results = xmlManager.query(xmlTransaction, xquery, queryContext);
// 2. open container
XmlContainerConfig config = new XmlContainerConfig();
config.setTransactional(true);
String containerName = "2-201.dbxml";
container = xmlManager.openContainer(xmlTransaction, containerName, config);
// 3. put document
XmlUpdateContext updateContext = xmlManager.createUpdateContext();
container.putDocument(txn, "uniqueId-123", "<foo>blah</foo>", updateContext);
Sequence:
1) query
2) open container
3) put document
results in hang in 3) although steps 1) and 2) work fine.
Sequence:
2) open container
1) query
3) put document
works fine all the way through.
I guess, I need to open the container before performing the query. It is not clear to me as to why it wouldn't fail in the query() step as opposed to failing when writing into this container later on.
Cheers.