[michaeljseo]

We have no way to reproduce this, we tried some speculative fixes which did not work. So, we need more information - next 5.1 nightly build (2015-02-05) will have some additional logging added to SQLMetaData class and we'd appreciate if you could provide more detail log illustrating the issue.

In order to do that you must enable DEBUG level logging for two categories in log4j.isc.config.xml file:

<category name="com.isomorphic.sql.SQLConnectionManager">
  <priority value="DEBUG" />
</category>
<category name="com.isomorphic.sql.SQLMetaData">
  <priority value="DEBUG" />
</category>

Please make sure that log actually has new entries, i.e. SQLConnectionManager and SQLMetaData started to log their DEBUG info. Thanks for your help!

To clarify, I must wait for the Feb 5th build, which means to get you feedback on Friday the 6th.

[Isomorphic]

Yes, you must wait for the Feb 5th build, change log level, showcase this issue with new build and then report more detail log here for us to analyze.

[michaeljseo]

Yes, you must wait for the Feb 5th build, change log level, showcase this issue with new build and then report more detail log here for us to analyze.

I had to split up the logs into loadable sizes. Here are the 5 of 11

[michaeljseo]

Yes, you must wait for the Feb 5th build, change log level, showcase this issue with new build and then report more detail log here for us to analyze.

Here are 6 through 10

[michaeljseo]

Yes, you must wait for the Feb 5th build, change log level, showcase this issue with new build and then report more detail log here for us to analyze.

Here the last (11th) piece

[Isomorphic]

Thanks, we'll take a look.

As a note, if you revert your logging settings to the defaults we ship with the framework, then add the specific log categories we asked for, you'll have much much smaller log output and wouldn't end up posting 11 files; probably 2 at most.

[Isomorphic]

We think we know what's causing this issue, but since we can't reproduce it, we ask you to send us your logs one more time. We want to be 100% sure.

So, there is some additional debug info logged which will give us necessary details. You should download Feb 9 nightly build, showcase the issue using that build and send us your log.

Note that SQLConnectionManager and SQLMetaData need to be logged at DEBUG level, but the rest of the framework may stay at default log levels.

[michaeljseo]

We think we know what's causing this issue, but since we can't reproduce it, we ask you to send us your logs one more time. We want to be 100% sure.

So, there is some additional debug info logged which will give us necessary details. You should download Feb 9 nightly build, showcase the issue using that build and send us your log.

Note that SQLConnectionManager and SQLMetaData need to be logged at DEBUG level, but the rest of the framework may stay at default log levels.

I actually have captured two scenarios:

• The server seems to hang (loghang.txt attachment)

• The server has an exception (logExc.txt attachment)

BTW, I used a log4j config file from one of your sample so that the logs will be smaller. However, I still had to split them into many parts to be up loaded.

[michaeljseo]

We think we know what's causing this issue, but since we can't reproduce it, we ask you to send us your logs one more time. We want to be 100% sure.

So, there is some additional debug info logged which will give us necessary details. You should download Feb 9 nightly build, showcase the issue using that build and send us your log.

Note that SQLConnectionManager and SQLMetaData need to be logged at DEBUG level, but the rest of the framework may stay at default log levels.

Here is the next batch of attachments.

[michaeljseo]

We think we know what's causing this issue, but since we can't reproduce it, we ask you to send us your logs one more time. We want to be 100% sure.

So, there is some additional debug info logged which will give us necessary details. You should download Feb 9 nightly build, showcase the issue using that build and send us your log.

Note that SQLConnectionManager and SQLMetaData need to be logged at DEBUG level, but the rest of the framework may stay at default log levels.

Here is the next batch of attachments.

[michaeljseo]

We think we know what's causing this issue, but since we can't reproduce it, we ask you to send us your logs one more time. We want to be 100% sure.

So, there is some additional debug info logged which will give us necessary details. You should download Feb 9 nightly build, showcase the issue using that build and send us your log.

Note that SQLConnectionManager and SQLMetaData need to be logged at DEBUG level, but the rest of the framework may stay at default log levels.

Here is the last batch of attachments.

[Isomorphic]

This is fixed now. You may download nightly build from 2015-02-11 (today) and check it out. Exception must be gone, please confirm that and let us know if something is still not working.

Thank you for your cooperation.

[michaeljseo]

This is fixed now. You may download nightly build from 2015-02-11 (today) and check it out. Exception must be gone, please confirm that and let us know if something is still not working.

Thank you for your cooperation.

It works.

Thank you for your diligence!