Hi all.
I have someone seeing the following error under both 10.3.1.4 and 10.3.2.1:
java.lang.NullPointerException
at org.apache.derby.client.am.PreparedStatement.setIntX(Unknown Source)
at
org.apache.derby.client.am.CallableLocatorProcedures.blobGetLength(Unknown
Source)
I have a pretty basic Rails 2.0.2 using embedded derby that I am deploying
with warbler and goldspike 1.5. If I deploy the war and run the application
under tomcat on linux, it runs fine. If I deploy that same war on windows
with tomcat, I get periodic "can't connect to the database errors". I
This sounds great, Rick. FYI, there is also the CommunityOne event (May 5) a
day before JavaOne...I'll be giving a talk there about Derby. I believe
ComunityOne registration is free if some of you are going to be around at
that time:
http://developers.sun.com/events/communityone/
Plenty of places
For your scenario, use System.nanoTime() instead. This provides a time
value (in nanoseconds, so you'll have to scale it appropriately) which is
not tied to the system clock. It is only appropriate for calculating
elapsed time (not time relative to a fixed clock such as "wall time"), but
this is
the scenario is an automated exam where the questions are fetched from the
apache derby database server.
so i wanted to fetch the time also from the server so that the local client
local clock tampering will have no effect on the current time.
how do i do this.
regards.
please help.
Narayanan
Andrew Lawrenson wrote:
I've done some more experimentation & testing.
At the moment, when syscolumns is updated, if a sub-transction is done, the
update is done with an expicit no-wait on locks.
I've tried changing this so that it will use the same wait policy as the parent
transaction - when
I've done some more experimentation & testing.
At the moment, when syscolumns is updated, if a sub-transction is done, the
update is done with an expicit no-wait on locks.
I've tried changing this so that it will use the same wait policy as the parent
transaction - when this is done, I see none
