Thanks, yes we had ruled out JDBC and Merovingian on this.
We have only seen this on the recent build we took (2008-04-21 nightly=current) of v5.5.0 We did not experience it on earlier versions.
On Wednesday 23 April 2008 14:11:29 Fabian Groffen wrote:
On 23-04-2008 13:30:18 -0400, McKennirey.Matthew wrote:
Our application includes multiple services that independently connect to the database. When each service connects it reads the database metadata to discover the column names, many services may start at about the same time.
We are getting the following error:
java.sql.SQLException: TypeException:user.s7172_2[262]:'io.stdout' undefined in: _416:any MALException:opt.remap:no implementation present
Something goes horribly wrong deep down in the engine.
When we stop and restart the merovingian demon, the problem goes away, but may reoccur the next time we try and start multiple services in short succession.
Isn't stopping and starting the BUSINESS database enough to get it running again? Essentially, restarting merovingian is the same, but if you'd have more databases it could be a bit disruptive, I guess.
MSG merovingian[12454]: starting database 'BUSINESS', up min/avg/max: 121/43165/92925, crash average: 0.00 0.30 0.10 (7-4=3) MSG BUSINESS[12459]: executing '/monetdb/bin/mserver5' for database 'BUSINESS' MSG BUSINESS[12459]: # MonetDB server v5.5.0, based on kernel v1.23.0 MSG BUSINESS[12459]: # Serving database 'BUSINESS' MSG BUSINESS[12459]: # Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
JDBC Driver 1.7 (Canephora_p2 20080418 based on MCL v1.3)
JDBC and Merovingian unrelated, my bet is concurrency is your enemy here.