DB2 server not responding after short time using Slide 2.1 beta

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

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
 
 

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

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

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 beta

[James Mason <ma...@apache.org>]

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