[Lift] Re: java.sql.SQLException | ERROR 07000

2009-10-13 Thread David Pollak
Please open a ticket at http://github.com/dpp/liftweb/issues with a
reproducible example.

On Tue, Oct 13, 2009 at 12:27 AM, Hannes  wrote:

>
> Hi Lifters,
>
> I encountered a problem after I started & tried to test my project today.
>
> I'm almost sure that this error didn't occured before..I also
> updated to 1.1-M6 but the error is still there. Do I've to do some other
> update? I think the problem is related to some actor stuff.???
>
> Here's some console output:
> -
>
> INFO - Service request (GET) /limitorder/list took 263 Milliseconds
> INFO - Service request (GET) /images/ajax-loader.gif took 2 Milliseconds
> INFO - Service request (GET) /user_mgt/logout took 21 Milliseconds
> INFO - The CometActor org.tobster.comet.mar...@221f81 Received Shutdown
> INFO - Service request (GET) / took 93 Milliseconds
> INFO - Service request (GET) /comet_request/1bebfbc2v6fa9/cometAjax.js
> took 3 Milliseconds
> INFO - Service request (GET) /images/ajax-loader.gif took 2 Milliseconds
> INFO - Service request (GET) /comet_request/85510940001/1bebfbc2v6fa9
> took 16 Milliseconds
> INFO - Service request (GET) /comet_request/60721905658/1bebfbc2v6fa9
> took 8714 Milliseconds
> INFO - Service request (GET) /user_mgt/sign_up took 794 Milliseconds
> INFO - Service request (GET) /images/ajax-loader.gif took 1 Milliseconds
> INFO - Service request (POST) /user_mgt/sign_up took 14 Milliseconds
> INFO - Service request (GET) / took 91 Milliseconds
> INFO - Service request (GET) /images/ajax-loader.gif took 1 Milliseconds
> INFO - Service request (GET) /comet_request/36437894169/1bebfbc2v6fa9
> took 8400 Milliseconds
> INFO - Service request (GET) /limitorder/create took 138 Milliseconds
> INFO - Service request (GET) /images/ajax-loader.gif took 3 Milliseconds
> INFO - Service request (POST) /limitorder/create took 32 Milliseconds
> java.sql.SQLException: At least one parameter to the current statement
> is uninitialized.
>at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
> Source)
>at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)
>at
>
> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
> Source)
>at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
> Source)
>at
> org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
>at
> org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
>at
> org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
>at
> org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown
> Source)
>at
> org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown
> Source)
>at
>
> net.liftweb.mapper.MetaMapper$$anonfun$14$$anonfun$15.apply(MetaMapper.scala:653)
>at
>
> net.liftweb.mapper.MetaMapper$$anonfun$14$$anonfun$15.apply(MetaMapper.scala:636)
>at
> net.liftweb.mapper.DB$$anonfun$runPreparedStatement$1.apply(DB.scala:375)
>at
> net.liftweb.mapper.DB$$anonfun$runPreparedStatement$1.apply(DB.scala:372)
>at net.liftweb.util.TimeHelpers$class.calcTime(TimeHelpers.scala:241)
>at net.liftweb.util.Helpers$.calcTime(Helpers.scala:29)
>at net.liftweb.mapper.DB$.runPreparedStatement(DB.scala:372)
>at net.liftweb.mapper.DB$.prepareStatement(DB.scala:316)
>at net.liftweb.mapper.MetaMapper$$anonfun$14.apply(MetaMapper.scala:635)
>at net.liftweb.mapper.MetaMapper$$anonfun$14.apply(MetaMapper.scala:630)
>at net.liftweb.mapper.DB$.use(DB.scala:389)
>at net.liftweb.mapper.MetaMapper$class.save(MetaMapper.scala:629)
>at org.tobster.model.LimitOrderMetaObj$.save(LimitOrder.scala:201)
>at net.liftweb.mapper.Mapper$$anonfun$save$1.apply(Mapper.scala:86)
>at net.liftweb.mapper.Mapper$$anonfun$save$1.apply(Mapper.scala:86)
>at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>at net.liftweb.mapper.Safe$.runSafe(Safe.scala:44)
>at net.liftweb.mapper.Mapper$class.runSafe(Mapper.scala:52)
>at org.tobster.model.LimitOrder.runSafe(LimitOrder.scala:21)
>at net.liftweb.mapper.Mapper$class.save(Mapper.scala:85)
>at org.tobster.model.LimitOrder.save(LimitOrder.scala:21)
>at
> org.tobster.comet.MarketServer$.doSecurityReservation(Market.scala:44)
>at
>
> org.tobster.comet.MarketServer$$anonfun$highPriority$1.apply(Market.scala:30)
>at
>
> org.tobster.comet.MarketServer$$anonfun$highPriority$1.apply(Market.scala:28)
>at scala.PartialFunction$$anon$1.apply(PartialFunction.scala:37)
>at scala.PartialFunction$$anon$1.apply(PartialFunction.scala:37)
>at scala.PartialFunction$$anon$1.apply(PartialFunction.scala:37)
>at scala.actors.Reaction.run(Reaction.scala:78)
>at scala.actors.FJTask$Wrap.run(Unknown Source)
>at scala.actors.FJTaskRunner.scanWhileIdling(Unknown Source)
>at scala.actors.FJTaskRunner.run(Unk

[Lift] Re: java.sql.SQLException | ERROR 07000

2009-10-13 Thread Richard Dallaway

On Tue, Oct 13, 2009 at 10:37 AM, Hannes  wrote:
>
> OK, thanks. I'll have a look!

Ah, it won't be that.  I've just seen the error I had documented here:

http://wiki.github.com/dpp/liftweb/10-11-possible-code-changes

...and it looks nothing like the error you're getting.

Sorry for the false lead.
Richard

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---



[Lift] Re: java.sql.SQLException | ERROR 07000

2009-10-13 Thread Hannes

OK, thanks. I'll have a look!

> On Tue, Oct 13, 2009 at 8:27 AM, Hannes  wrote:
>   
>> I'm almost sure that this error didn't occured before..I also
>> updated to 1.1-M6 but the error is still there. Do I've to do some other
>> update? I think the problem is related to some actor stuff.???
>> 
>
> This is a long shot,  but I think I saw something similar and it
> turned out I had an incorrect DB.addLogFunc in my Boot.   If you have
> one, maybe comment it out and see if you get the same behaviour.
>
> It doesn't really look related from the stack trace, but I thought I'd
> mention it just in case...
>
> Richard
>
> >
>   


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---



[Lift] Re: java.sql.SQLException | ERROR 07000

2009-10-13 Thread Richard Dallaway

On Tue, Oct 13, 2009 at 8:27 AM, Hannes  wrote:
> I'm almost sure that this error didn't occured before..I also
> updated to 1.1-M6 but the error is still there. Do I've to do some other
> update? I think the problem is related to some actor stuff.???

This is a long shot,  but I think I saw something similar and it
turned out I had an incorrect DB.addLogFunc in my Boot.   If you have
one, maybe comment it out and see if you get the same behaviour.

It doesn't really look related from the stack trace, but I thought I'd
mention it just in case...

Richard

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---