You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-user@db.apache.org by Bryce Nesbitt <br...@obviously.com> on 2006/02/16 17:48:29 UTC
What are possible causes of: IDBroker ... does not support transactions.
This application used to work on this machine. Has worked on other
machines for years. On other machines it works fine on table types that
don't even support transactions. Yet now have spent 10+ hours on this
error message which appeared on an otherwise working server after a data
source upgrade:::
$ tail -f stderr.log
srun listening to 127.0.0.1:6809
http listening to *:8080
9624 [tcpConnection-6809-0] INFO action.RequestProcessor - Processing a
'POST' for path '/member/login'
9758 [Thread-1] DEBUG oid.IDBroker - IDBroker thread was started.
9839 [tcpConnection-6809-0] WARN oid.IDBroker - IDBroker is being used
with db 'default', which does not support transactions. IDBroker
attempts to use transactions to limit the possibility of duplicate key
generation. Without transactions, duplicate key generation is possible
if multiple JVMs are used or other means are used to write to the database.
9876 [tcpConnection-6809-0] WARN action.RequestProcessor - Unhandled
Exception thrown: class java.lang.NullPointerException
$ cat torque.properties
# T O R Q U E P R O P E R T I E S
#
# -------------------------------------------------------------------
# These are your database settings. Look in the
# org.apache.torque.pool.* packages for more information.
#
# The parameters to connect to the default database. You MUST
# configure these properly.
# -------------------------------------------------------------------
torque.database.default=default_stupid_thing
torque.database.default.adapter=mysql
## Using Jdbc2Pool
torque.dsfactory.default.factory=\
org.apache.torque.dsfactory.Jdbc2PoolDataSourceFactory
torque.dsfactory.default.pool.defaultMaxActive = 10
torque.dsfactory.default.pool.testOnBorrow = true
torque.dsfactory.default.pool.validationQuery = SELECT 1
torque.dsfactory.default.connection.driver = com.mysql.jdbc.Driver
torque.dsfactory.default.connection.url =
jdbc:mysql://localhost:3306/ccs
torque.dsfactory.default.connection.user = xxx
torque.dsfactory.default.connection.password = xxxxxxxx
$ ls WEB-INF/*/to*
WEB-INF/lib/torque-3.0-b4.jar
$ mysql --version
mysql Ver 12.22 Distrib 4.0.17, for pc-linux (i686)
$ mysql -u xxx -p
> SHOW TABLE STATUS;
...
| ASSET_TABLE | InnoDB | Dynamic | 218129 | 93 | 20496384
...
$ telnet localhost 3306
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
0
4.0.17-standard
$ startserver
command-line: /usr/java/j2sdk1.4.2_06/bin/java -Xms1536m -Xmx1536m
-Dresin.home=/opt/resin-2.1.12 com.caucho.server.http.HttpServer -conf
resun-xxxxxxx.conf -stdout stdout.log -stderr stderr.log
We're confused by the use of the term 'default' in the DB error message,
among other things. Is there a way to get a more verbose or useful
error message?
What are typical causes of this type of failure to find a datasource?
And no, this application has run for years, upgrading all the versions
is not an option, sorry.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
Re: What are possible causes of: IDBroker ... does not support transactions.
Posted by Bryce Nesbitt <br...@obviously.com>.
Thomas Fischer wrote:
> This message is really cryptic, sorry for that. This usually means that you
> cannot connect to the database for some reason. The IdBroker is the first
> thing which connects to the database, so the error appears there first.
> Reasons may be wring configuration, wrong, nonexistentor badly installed
> database driver, firewall....
>
> Thomas
>
Does the fact that it says:
IDBroker is being used with db 'default'
Have any significance? We don't have a db named 'default'.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
Re: What are possible causes of: IDBroker ... does not support transactions.
Posted by Bryce Nesbitt <br...@obviously.com>.
Thomas Fischer wrote:
> This message is really cryptic, sorry for that. This usually means that you
> cannot connect to the database for some reason. The IdBroker is the first
> thing which connects to the database, so the error appears there first.
> Reasons may be wring configuration, wrong, nonexistentor badly installed
> database driver, firewall....
>
> Thomas
>
Cryptic I don't mind. But is there a way to get more data? Like what
error it encountered.
Or what port it used. Or... well.. anything. Everything we can do (see
the logs) shows the DB
is fine and, of course, transaction safe.
-Bryce
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
RE: What are possible causes of: IDBroker ... does not support transactions.
Posted by Thomas Fischer <fi...@seitenbau.net>.
This message is really cryptic, sorry for that. This usually means that you
cannot connect to the database for some reason. The IdBroker is the first
thing which connects to the database, so the error appears there first.
Reasons may be wring configuration, wrong, nonexistentor badly installed
database driver, firewall....
Thomas
Bryce Nesbitt <br...@obviously.com> schrieb am 16.02.2006 17:48:29:
> This application used to work on this machine. Has worked on other
> machines for years. On other machines it works fine on table types that
> don't even support transactions. Yet now have spent 10+ hours on this
> error message which appeared on an otherwise working server after a data
> source upgrade:::
>
>
> $ tail -f stderr.log
> srun listening to 127.0.0.1:6809
> http listening to *:8080
> 9624 [tcpConnection-6809-0] INFO action.RequestProcessor - Processing a
> 'POST' for path '/member/login'
> 9758 [Thread-1] DEBUG oid.IDBroker - IDBroker thread was started.
> 9839 [tcpConnection-6809-0] WARN oid.IDBroker - IDBroker is being used
> with db 'default', which does not support transactions. IDBroker
> attempts to use transactions to limit the possibility of duplicate key
> generation. Without transactions, duplicate key generation is possible
> if multiple JVMs are used or other means are used to write to the
database.
> 9876 [tcpConnection-6809-0] WARN action.RequestProcessor - Unhandled
> Exception thrown: class java.lang.NullPointerException
>
>
> $ cat torque.properties
>
> # T O R Q U E P R O P E R T I E S
> #
> # -------------------------------------------------------------------
> # These are your database settings. Look in the
> # org.apache.torque.pool.* packages for more information.
> #
> # The parameters to connect to the default database. You MUST
> # configure these properly.
> # -------------------------------------------------------------------
>
> torque.database.default=default_stupid_thing
> torque.database.default.adapter=mysql
>
> ## Using Jdbc2Pool
> torque.dsfactory.default.factory=\
> org.apache.torque.dsfactory.Jdbc2PoolDataSourceFactory
> torque.dsfactory.default.pool.defaultMaxActive = 10
> torque.dsfactory.default.pool.testOnBorrow = true
> torque.dsfactory.default.pool.validationQuery = SELECT 1
> torque.dsfactory.default.connection.driver = com.mysql.jdbc.Driver
> torque.dsfactory.default.connection.url =
> jdbc:mysql://localhost:3306/ccs
> torque.dsfactory.default.connection.user = xxx
> torque.dsfactory.default.connection.password = xxxxxxxx
>
>
> $ ls WEB-INF/*/to*
> WEB-INF/lib/torque-3.0-b4.jar
>
> $ mysql --version
> mysql Ver 12.22 Distrib 4.0.17, for pc-linux (i686)
> $ mysql -u xxx -p
> > SHOW TABLE STATUS;
> ...
> | ASSET_TABLE | InnoDB | Dynamic | 218129 | 93 |
20496384
> ...
>
> $ telnet localhost 3306
> Trying 127.0.0.1...
> Connected to localhost.localdomain (127.0.0.1).
> Escape character is '^]'.
> 0
> 4.0.17-standard
>
> $ startserver
> command-line: /usr/java/j2sdk1.4.2_06/bin/java -Xms1536m -Xmx1536m
> -Dresin.home=/opt/resin-2.1.12 com.caucho.server.http.HttpServer -conf
> resun-xxxxxxx.conf -stdout stdout.log -stderr stderr.log
>
>
>
> We're confused by the use of the term 'default' in the DB error message,
> among other things. Is there a way to get a more verbose or useful
> error message?
> What are typical causes of this type of failure to find a datasource?
> And no, this application has run for years, upgrading all the versions
> is not an option, sorry.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org