RE: DB2 server not responding after short time using Slide 2.1 be ta

[Warwick Burrows <wa...@e2open.com>]

Hi Oliver,

I'm having this same DB2 problem trying to get the testsuite slide
configuration going too. ie. by adding two more stores alongside the
standard /files store: a /files_2 and a /files_secondCollection store as
required by the testsuite. The DB2 adapter hangs in a different statement
this time even though I do have the "sequential-mode" parameter set to
"full".

I've attached the Domain.xml file if you have any suggestions for what I'm
doing wrong configuring these extra stores. My Domain.xml is not too far
removed from the example Domain.xml of the 2.1 beta I've just substituted
the XML nodestore in each <store> definition with a jdbcstore implementation
instead. I reference the same jdbcstore in each <store> definition rather
than separate ones. I've also defined the sequence store as a reference to
the nodestore instead of using the FileSequenceStore in the beta Slide
Domain.xml.

Thanks,
Warwick


-----Original Message-----
From: Oliver Zeigermann [mailto:oliver@zeigermann.de] 
Sent: Monday, September 06, 2004 9:57 AM
To: Slide Users Mailing List
Subject: Re: DB2 server not responding after short time using Slide 2.1 beta


This can not be a deadlock as DB2 would resolve it automatically. Maybe 
there is another transaction running that holds locks on the concerned 
table. Maybe from the DB2 CLI? I'd suspect that...

And yes, actually if you switch on

             <parameter name="sequential-mode">full</parameter>

in Domain.xml as done by default in Slide 2.1, Slide will never 
deadlock. However, if you reuse your old Domain.xml from earlier 
releases my patch won't have any effect.

Oliver

James Mason wrote:

> Warwick,
> This sounds suspiciously like a deadlock condition to me. I ran into
> something similar with MySQL, and I *thought* that Oliver and I had made 
> changes that would ensure it couldn't happen, but maybe not.
> 
> If possible can you get a log of all the sql statements executed by
> Slide against the database? If your log includes a connection id look to 
> see if the connection id suddenly changes. That should help you pinpoint 
> the sql statement that's causing the problem .
> 
>  From looking at enumerateLocks() I don't see any way that statement
> could cause a deadlock. This makes me think the problem is probably 
> somewhere else and it's just surfacing when that statement runs.
> 
> -James
> 
> Warwick Burrows wrote:
> 
>> Hi,
>> I've run into a serious problem with the slide 2.1B1 server where the DB2
>> server hangs executing a select statement in the enumerateLocks() 
>> method of
>> the StandardRDBMSAdapter in the server. Once the DB server is hung it 
>> won't
>> even respond to simple select statements from the DB2 cli.  Though it 
>> will
>> respond to "list tables" commands. When I run a select from the DB2 
>> cli (eg.
>> select * from URI) and it hangs I can hit ctrl-C at the DB2 cli prompt 
>> and
>> it will cancel the request and return -- but no data comes back with 
>> it. Of
>> course the slide server will wait indefinitely for the sql request to 
>> come
>> back. Has anybody else had this problem with Slide 2.1B1 and DB2?  A 
>> new DB2
>> RDBMS adapter was introduced in 2.1B1 as well as a new DB2 schema. I 
>> didn't
>> see this problem with 2.1M1 but its happening frequently with 2.1B1. 
>> In fact
>> its such a problem my project no longer works and we're grounded until we
>> can find a fix.
>>  
>> Thanks,
>> Warwick
>>  
>>  
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org

Re: DB2 server not responding after short time using Slide 2.1 be ta

[Oliver Zeigermann <ol...@zeigermann.de>]

Hi Warwick,

if you have set the sequential-mode to full you can be very sure only a 
single request at a time can be executed. Thus it is very unlikely that 
it is a deadlock. I am afraid I can not check you configuration as I 
have no access to DB2. I can only recommend what most people do in such 
a scenario. Use a tool that displays all open connections and locks to 
find out what is going on. This is no fun, but the last resort, I guess. 
  I know Toad does a pretty good job for Oracle and MySQL, do not know 
if there is anything like that for DB2.

Sorry that there is nothing more I can do to help you :(

Good luck,

Oliver

Warwick Burrows wrote:
> Hi Oliver,
> 
> I'm having this same DB2 problem trying to get the testsuite slide
> configuration going too. ie. by adding two more stores alongside the
> standard /files store: a /files_2 and a /files_secondCollection store as
> required by the testsuite. The DB2 adapter hangs in a different statement
> this time even though I do have the "sequential-mode" parameter set to
> "full".
> 
> I've attached the Domain.xml file if you have any suggestions for what I'm
> doing wrong configuring these extra stores. My Domain.xml is not too far
> removed from the example Domain.xml of the 2.1 beta I've just substituted
> the XML nodestore in each <store> definition with a jdbcstore implementation
> instead. I reference the same jdbcstore in each <store> definition rather
> than separate ones. I've also defined the sequence store as a reference to
> the nodestore instead of using the FileSequenceStore in the beta Slide
> Domain.xml.
> 
> Thanks,
> Warwick
> 
> 
> -----Original Message-----
> From: Oliver Zeigermann [mailto:oliver@zeigermann.de] 
> Sent: Monday, September 06, 2004 9:57 AM
> To: Slide Users Mailing List
> Subject: Re: DB2 server not responding after short time using Slide 2.1 beta
> 
> 
> This can not be a deadlock as DB2 would resolve it automatically. Maybe 
> there is another transaction running that holds locks on the concerned 
> table. Maybe from the DB2 CLI? I'd suspect that...
> 
> And yes, actually if you switch on
> 
>              <parameter name="sequential-mode">full</parameter>
> 
> in Domain.xml as done by default in Slide 2.1, Slide will never 
> deadlock. However, if you reuse your old Domain.xml from earlier 
> releases my patch won't have any effect.
> 
> Oliver
> 
> James Mason wrote:
> 
> 
>>Warwick,
>>This sounds suspiciously like a deadlock condition to me. I ran into
>>something similar with MySQL, and I *thought* that Oliver and I had made 
>>changes that would ensure it couldn't happen, but maybe not.
>>
>>If possible can you get a log of all the sql statements executed by
>>Slide against the database? If your log includes a connection id look to 
>>see if the connection id suddenly changes. That should help you pinpoint 
>>the sql statement that's causing the problem .
>>
>> From looking at enumerateLocks() I don't see any way that statement
>>could cause a deadlock. This makes me think the problem is probably 
>>somewhere else and it's just surfacing when that statement runs.
>>
>>-James
>>
>>Warwick Burrows wrote:
>>
>>
>>>Hi,
>>>I've run into a serious problem with the slide 2.1B1 server where the DB2
>>>server hangs executing a select statement in the enumerateLocks() 
>>>method of
>>>the StandardRDBMSAdapter in the server. Once the DB server is hung it 
>>>won't
>>>even respond to simple select statements from the DB2 cli.  Though it 
>>>will
>>>respond to "list tables" commands. When I run a select from the DB2 
>>>cli (eg.
>>>select * from URI) and it hangs I can hit ctrl-C at the DB2 cli prompt 
>>>and
>>>it will cancel the request and return -- but no data comes back with 
>>>it. Of
>>>course the slide server will wait indefinitely for the sql request to 
>>>come
>>>back. Has anybody else had this problem with Slide 2.1B1 and DB2?  A 
>>>new DB2
>>>RDBMS adapter was introduced in 2.1B1 as well as a new DB2 schema. I 
>>>didn't
>>>see this problem with 2.1M1 but its happening frequently with 2.1B1. 
>>>In fact
>>>its such a problem my project no longer works and we're grounded until we
>>>can find a fix.
>>> 
>>>Thanks,
>>>Warwick
>>> 
>>> 
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: slide-user-help@jakarta.apache.org
>>
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org