Can you post the row handler you are using.
Larry
On Sat, Mar 15, 2008 at 1:14 PM, nch <[EMAIL PROTECTED]> wrote:
>
>
> Hi, Nathan.
> I did so, but I'm still having the same issue. Perhaps I'm not using it
> correctly?
> See my last post to this forum entry:
>
> http://forum.compass-project.org/
I *think* Webpshere 6.x will call rollback on the connection if you return
it to the pool without calling commit or rollback yourself. (Check your
SystemOut.log for warnings) Also, I remember looking into this six months
ago and found that when you call setAutoCommit(true), for example, before
re
Hi, Nathan.
I did so, but I'm still having the same issue. Perhaps I'm not using it
correctly?
See my last post to this forum entry:
http://forum.compass-project.org/thread.jspa?threadID=215278
See the stack trace:
MemoryError: Java heap space:
java.lang.OutOfMemoryError: Java heap space
this is only my 2 cents but I would throw that class out. Write your own
implementation which uses a row handler. This is the type of situation in
which a row handler could really help. almost no memory would be used.
On Thu, Mar 13, 2008 at 4:57 PM, nch <[EMAIL PROTECTED]> wrote:
>
> Yes, I
In eclipse you should not edit the .classpath file directly. You should
edit the launch configuration through the UI. The menu option is something
like "Run->External Tools...", this will present you with a dialog where you
can find your Ant launches and set the classpath appropriately. Assuming
We are setting up our application to use Websphere's JDBC connection.
When we setup this in Websphere in version 5.1 we needed to add the
commitRequired=true to get it to work.
Although in our Websphere 6.1 server we didn't have to add this.
Would it be a good idea to use this?
Do most
