Damian,
Sorry, please ignore the TupleLoaderBase remark. This is related to a
second problem that I have on MSSQL server with concurrent users (20).
[5/15/12 8:20:14:731 MDT] FFDC Exception:java.sql.SQLException
SourceId:com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.execute ProbeId:296
Reporter:com.ibm.ws.rsadapter.jdbc.WSJdbcStatement@38273827
java.sql.SQLException: There is already an object named '#NNodeQuads' in
the database.
at
net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
at
net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
at
net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
at
net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:723)
at net.sourceforge.jtds.jdbc.JtdsStatement.execute(JtdsStatement.java:1160)
at
net.sourceforge.jtds.jdbcx.proxy.StatementProxy.execute(StatementProxy.java:287)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.pmiExecute(WSJdbcStatement.java:1485)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.execute(WSJdbcStatement.java:632)
at com.hp.hpl.jena.sdb.sql.SDBConnection.execSilent(SDBConnection.java:203)
at
com.hp.hpl.jena.sdb.layout2.TupleLoaderBase.ensureTempTables2(TupleLoaderBase.java:364)
at
com.hp.hpl.jena.sdb.layout2.TupleLoaderBase.ensureTempTables(TupleLoaderBase.java:335)
at com.hp.hpl.jena.sdb.layout2.TupleLoaderBase.init(TupleLoaderBase.java:52)
at
com.hp.hpl.jena.sdb.layout2.TupleLoaderBase.<init>(TupleLoaderBase.java:45)
at
com.hp.hpl.jena.sdb.layout2.hash.TupleLoaderHashSQLServer.<init>(TupleLoaderHashSQLServer.java:17)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:45)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
at java.lang.reflect.Constructor.newInstance(Constructor.java:515)
at
com.hp.hpl.jena.sdb.layout2.LoaderTuplesNodes.updateOneTuple(LoaderTuplesNodes.java:267)
at
com.hp.hpl.jena.sdb.layout2.LoaderTuplesNodes.access$2(LoaderTuplesNodes.java:256)
at
com.hp.hpl.jena.sdb.layout2.LoaderTuplesNodes$Commiter.run(LoaderTuplesNodes.java:334)
at java.lang.Thread.run(Thread.java:735)
I tried to use Optimistic or Pessimistic ensureTempTablesX but it fails
within these two lines of code.
if (!TableUtils.hasTable(connection().getSqlConnection(), getNodeLoader()))
connection().execSilent(getCreateTempNodes());
Right now I'm investigating this problem but any help will be appreciated.
Regards,
Adrian
On Tue, May 15, 2012 at 9:16 PM, Adrian Paleacu <[email protected]>wrote:
> Hi Damian,
>
> My SDB version is ~1.1 and the DB is MSSQL 2008, comparing
> TupleLoaderBase reveal no differences.
> I could try to port some of the changes from the current dev into my
> codebase. But I need some directions :)
>
> Thank you for your quick response,
>
> Adrian
>
>
> On Tue, May 15, 2012 at 4:20 PM, Damian Steer <[email protected]>wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 15/05/12 06:35, Adrian Paleacu wrote:
>> > Hi everyone, I'm wonder if someone know about a possible deadlock
>> > in SDB with this scenario. I'm not sure if is my app fault of SDB.
>> > :)
>>
>> Which version of SDB are you using, and which database?
>>
>> > Process A has an exclusive lock on nodes and wants a share lock on
>> > quads Process B has an exclusive lock on quads and wants a share
>> > lock on nodes
>>
>> On some databases the loader now locks the node table on entry, but
>> I'm pretty sure that version hasn't been released yet. Could you try
>> the current SDB snapshot?
>>
>> (The jena issue is jena-118, but jira is unreachable for me at the moment)
>>
>> Thanks,
>>
>> Damian
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk+yWC4ACgkQAyLCB+mTtynm+wCg3kdkVRdNb8UwWZhptrrL23YR
>> HJgAoKPEXBQV1edAy87SmCpgwWRR2kbs
>> =RaMN
>> -----END PGP SIGNATURE-----
>>
>
>
