Re: Failure in JDBC tests on multiple pull requests

2017-08-09 Thread Weiqing Xu 
Hi Dave,

Sorry , Just now, I found it will still fail in some case in my env. I need
update it.

Weiqing

On Aug 9, 2017, at 23:14, Dave Birdsall <dave.birds...@esgyn.com> wrote:

I will look at it this morning.

Dave

-Original Message-
From: Weiqing Xu [mailto:xuweiqing...@gmail.com]
Sent: Tuesday, August 8, 2017 6:44 PM
To: dev@trafodion.incubator.apache.org
Subject: Re: Failure in JDBC tests on multiple pull requests

I have create a PR for this issue. And the regression has beed passed
twice. https://github.com/apache/incubator-trafodion/pull/1199

Does anyone can review and merge it?

On Aug 8, 2017, at 09:41, Weiqing Xu <xuweiqing...@gmail.com> wrote:

I'll check the JDBC regression test to make sure all unused statement will
be closed.

Best Regards,
Weiqing

On Tue, Aug 8, 2017 at 7:28 AM, Selva Govindarajan <
selva.govindara...@esgyn.com> wrote:

This error message is thrown if you have 14 or more statements active
in a single connection. Please reduce the number of open statements in
the connection. It is possible that the statement is not explicitly
closed in these tests.

Selva

-Original Message-
From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
Sent: Monday, August 7, 2017 3:09 PM
To: dev@trafodion.incubator.apache.org
Subject: Failure in JDBC tests on multiple pull requests

Hi,

I was looking at the outstanding pull requests today. I noticed that
some JDBC-related changes are getting the following failure:

2017-08-04 05:27:18 Batch Update Failed, See next exception for
details
2017-08-04 05:27:18 Invalid Parameter Value: VARCHAR data longer than
column length: 1
2017-08-04 05:27:30 Running testBatchInsertFKNotExist..
2017-08-04 05:27:51 *** ERROR[2026] Server Process $ZSM0 has reached
allowed depth for nowait operation from the process 0,15836.
[2017-08-04 05:27:51]
2017-08-04 05:28:12 Running testBatchUpsertDuplicate..
2017-08-04 05:28:27 Running testBatchInsertPkDuplicate..
2017-08-04 05:28:41 Running testBatchUpdateOverflow..
2017-08-04 05:28:48 Batch Update Failed, See next exception for
details
2017-08-04 05:28:48 Invalid Parameter Value: VARCHAR data longer than
column length: 1
2017-08-04 05:28:52 Running testBatchUpdatePkDuplicate..
2017-08-04 05:28:59 Batch Update Failed, See next exception for
details
2017-08-04 05:28:59 *** ERROR[8102] The operation is prevented by a
unique constraint. [2017-08-04 05:28:59]
2017-08-04 05:29:06 Running testBatchInsertPositive..
2017-08-04 05:29:14 Time consumption for batch inserting 1 rows is
1867 milli seconds
2017-08-04 05:31:00 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0,
Time
elapsed: 231.891 sec <<< FAILURE! - in BatchTest

I don't see anything in the pull requests themselves that should cause
this.

Does anyone have an idea what might be doing it? I hate to get into a
mode where we just repeatedly run tests until they pass without fixing
the underlying problem.

Thanks,

Dave

RE: Failure in JDBC tests on multiple pull requests

2017-08-09 Thread Dave Birdsall 
OK, thanks for letting me know.

Dave

-Original Message-
From: Weiqing Xu [mailto:xuweiqing...@gmail.com] 
Sent: Wednesday, August 9, 2017 8:24 AM
To: dev@trafodion.incubator.apache.org
Subject: Re: Failure in JDBC tests on multiple pull requests

Hi Dave,

Sorry, Just now, I found it will fail in some cases in my env. I need update it.

Weiqing
> On Aug 9, 2017, at 23:14, Dave Birdsall <dave.birds...@esgyn.com> wrote:
> 
> I will look at it this morning.
> 
> Dave
> 
> -Original Message-
> From: Weiqing Xu [mailto:xuweiqing...@gmail.com]
> Sent: Tuesday, August 8, 2017 6:44 PM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Failure in JDBC tests on multiple pull requests
> 
> I have create a PR for this issue. And the regression has beed passed 
> twice. https://github.com/apache/incubator-trafodion/pull/1199
> 
> Does anyone can review and merge it?
> 
> On Aug 8, 2017, at 09:41, Weiqing Xu <xuweiqing...@gmail.com> wrote:
> 
> I'll check the JDBC regression test to make sure all unused statement will be 
> closed.
> 
> Best Regards,
> Weiqing
> 
> On Tue, Aug 8, 2017 at 7:28 AM, Selva Govindarajan < 
> selva.govindara...@esgyn.com> wrote:
> 
>> This error message is thrown if you have 14 or more statements active 
>> in a single connection. Please reduce the number of open statements 
>> in the connection. It is possible that the statement is not 
>> explicitly closed in these tests.
>> 
>> Selva
>> 
>> -Original Message-
>> From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
>> Sent: Monday, August 7, 2017 3:09 PM
>> To: dev@trafodion.incubator.apache.org
>> Subject: Failure in JDBC tests on multiple pull requests
>> 
>> Hi,
>> 
>> I was looking at the outstanding pull requests today. I noticed that 
>> some JDBC-related changes are getting the following failure:
>> 
>> 2017-08-04 05:27:18 Batch Update Failed, See next exception for 
>> details
>> 2017-08-04 05:27:18 Invalid Parameter Value: VARCHAR data longer than 
>> column length: 1
>> 2017-08-04 05:27:30 Running testBatchInsertFKNotExist..
>> 2017-08-04 05:27:51 *** ERROR[2026] Server Process $ZSM0 has reached 
>> allowed depth for nowait operation from the process 0,15836.
>> [2017-08-04 05:27:51]
>> 2017-08-04 05:28:12 Running testBatchUpsertDuplicate..
>> 2017-08-04 05:28:27 Running testBatchInsertPkDuplicate..
>> 2017-08-04 05:28:41 Running testBatchUpdateOverflow..
>> 2017-08-04 05:28:48 Batch Update Failed, See next exception for 
>> details
>> 2017-08-04 05:28:48 Invalid Parameter Value: VARCHAR data longer than 
>> column length: 1
>> 2017-08-04 05:28:52 Running testBatchUpdatePkDuplicate..
>> 2017-08-04 05:28:59 Batch Update Failed, See next exception for 
>> details
>> 2017-08-04 05:28:59 *** ERROR[8102] The operation is prevented by a 
>> unique constraint. [2017-08-04 05:28:59]
>> 2017-08-04 05:29:06 Running testBatchInsertPositive..
>> 2017-08-04 05:29:14 Time consumption for batch inserting 1 rows 
>> is
>> 1867 milli seconds
>> 2017-08-04 05:31:00 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, 
>> Time
>> elapsed: 231.891 sec <<< FAILURE! - in BatchTest
>> 
>> I don't see anything in the pull requests themselves that should 
>> cause this.
>> 
>> Does anyone have an idea what might be doing it? I hate to get into a 
>> mode where we just repeatedly run tests until they pass without 
>> fixing the underlying problem.
>> 
>> Thanks,
>> 
>> Dave
>> 
>>

Re: Failure in JDBC tests on multiple pull requests

2017-08-09 Thread Weiqing Xu 
Hi Dave,

Sorry, Just now, I found it will fail in some cases in my env. I need update it.

Weiqing
> On Aug 9, 2017, at 23:14, Dave Birdsall <dave.birds...@esgyn.com> wrote:
> 
> I will look at it this morning.
> 
> Dave
> 
> -Original Message-
> From: Weiqing Xu [mailto:xuweiqing...@gmail.com] 
> Sent: Tuesday, August 8, 2017 6:44 PM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Failure in JDBC tests on multiple pull requests
> 
> I have create a PR for this issue. And the regression has beed passed twice. 
> https://github.com/apache/incubator-trafodion/pull/1199
> 
> Does anyone can review and merge it?
> 
> On Aug 8, 2017, at 09:41, Weiqing Xu <xuweiqing...@gmail.com> wrote:
> 
> I'll check the JDBC regression test to make sure all unused statement will be 
> closed.
> 
> Best Regards,
> Weiqing
> 
> On Tue, Aug 8, 2017 at 7:28 AM, Selva Govindarajan < 
> selva.govindara...@esgyn.com> wrote:
> 
>> This error message is thrown if you have 14 or more statements active 
>> in a single connection. Please reduce the number of open statements in 
>> the connection. It is possible that the statement is not explicitly 
>> closed in these tests.
>> 
>> Selva
>> 
>> -Original Message-
>> From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
>> Sent: Monday, August 7, 2017 3:09 PM
>> To: dev@trafodion.incubator.apache.org
>> Subject: Failure in JDBC tests on multiple pull requests
>> 
>> Hi,
>> 
>> I was looking at the outstanding pull requests today. I noticed that 
>> some JDBC-related changes are getting the following failure:
>> 
>> 2017-08-04 05:27:18 Batch Update Failed, See next exception for 
>> details
>> 2017-08-04 05:27:18 Invalid Parameter Value: VARCHAR data longer than 
>> column length: 1
>> 2017-08-04 05:27:30 Running testBatchInsertFKNotExist..
>> 2017-08-04 05:27:51 *** ERROR[2026] Server Process $ZSM0 has reached 
>> allowed depth for nowait operation from the process 0,15836. 
>> [2017-08-04 05:27:51]
>> 2017-08-04 05:28:12 Running testBatchUpsertDuplicate..
>> 2017-08-04 05:28:27 Running testBatchInsertPkDuplicate..
>> 2017-08-04 05:28:41 Running testBatchUpdateOverflow..
>> 2017-08-04 05:28:48 Batch Update Failed, See next exception for 
>> details
>> 2017-08-04 05:28:48 Invalid Parameter Value: VARCHAR data longer than 
>> column length: 1
>> 2017-08-04 05:28:52 Running testBatchUpdatePkDuplicate..
>> 2017-08-04 05:28:59 Batch Update Failed, See next exception for 
>> details
>> 2017-08-04 05:28:59 *** ERROR[8102] The operation is prevented by a 
>> unique constraint. [2017-08-04 05:28:59]
>> 2017-08-04 05:29:06 Running testBatchInsertPositive..
>> 2017-08-04 05:29:14 Time consumption for batch inserting 1 rows is
>> 1867 milli seconds
>> 2017-08-04 05:31:00 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, 
>> Time
>> elapsed: 231.891 sec <<< FAILURE! - in BatchTest
>> 
>> I don't see anything in the pull requests themselves that should cause 
>> this.
>> 
>> Does anyone have an idea what might be doing it? I hate to get into a 
>> mode where we just repeatedly run tests until they pass without fixing 
>> the underlying problem.
>> 
>> Thanks,
>> 
>> Dave
>> 
>>

Re: Failure in JDBC tests on multiple pull requests

2017-08-08 Thread Weiqing Xu 
I have create a PR for this issue. And the regression has beed passed
twice. https://github.com/apache/incubator-trafodion/pull/1199

Does anyone can review and merge it?

On Aug 8, 2017, at 09:41, Weiqing Xu  wrote:

I'll check the JDBC regression test to make sure all unused statement will
be closed.

Best Regards,
Weiqing

On Tue, Aug 8, 2017 at 7:28 AM, Selva Govindarajan <
selva.govindara...@esgyn.com> wrote:

> This error message is thrown if you have 14 or more statements active in a
> single connection. Please reduce the number of open statements in the
> connection. It is possible that the statement is not explicitly closed in
> these tests.
>
> Selva
>
> -Original Message-
> From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
> Sent: Monday, August 7, 2017 3:09 PM
> To: dev@trafodion.incubator.apache.org
> Subject: Failure in JDBC tests on multiple pull requests
>
> Hi,
>
> I was looking at the outstanding pull requests today. I noticed that some
> JDBC-related changes are getting the following failure:
>
> 2017-08-04 05:27:18 Batch Update Failed, See next exception for details
> 2017-08-04 05:27:18 Invalid Parameter Value: VARCHAR data longer than
> column length: 1
> 2017-08-04 05:27:30 Running testBatchInsertFKNotExist..
> 2017-08-04 05:27:51 *** ERROR[2026] Server Process $ZSM0 has reached
> allowed depth for nowait operation from the process 0,15836. [2017-08-04
> 05:27:51]
> 2017-08-04 05:28:12 Running testBatchUpsertDuplicate..
> 2017-08-04 05:28:27 Running testBatchInsertPkDuplicate..
> 2017-08-04 05:28:41 Running testBatchUpdateOverflow..
> 2017-08-04 05:28:48 Batch Update Failed, See next exception for details
> 2017-08-04 05:28:48 Invalid Parameter Value: VARCHAR data longer than
> column length: 1
> 2017-08-04 05:28:52 Running testBatchUpdatePkDuplicate..
> 2017-08-04 05:28:59 Batch Update Failed, See next exception for details
> 2017-08-04 05:28:59 *** ERROR[8102] The operation is prevented by a unique
> constraint. [2017-08-04 05:28:59]
> 2017-08-04 05:29:06 Running testBatchInsertPositive..
> 2017-08-04 05:29:14 Time consumption for batch inserting 1 rows is
> 1867 milli seconds
> 2017-08-04 05:31:00 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed: 231.891 sec <<< FAILURE! - in BatchTest
>
> I don't see anything in the pull requests themselves that should cause
> this.
>
> Does anyone have an idea what might be doing it? I hate to get into a mode
> where we just repeatedly run tests until they pass without fixing the
> underlying problem.
>
> Thanks,
>
> Dave
>
>

Re: Failure in JDBC tests on multiple pull requests

2017-08-07 Thread Weiqing Xu 
I'll check the JDBC regression test to make sure all unused statement will
be closed.

Best Regards,
Weiqing

On Tue, Aug 8, 2017 at 7:28 AM, Selva Govindarajan <
selva.govindara...@esgyn.com> wrote:

> This error message is thrown if you have 14 or more statements active in a
> single connection. Please reduce the number of open statements in the
> connection. It is possible that the statement is not explicitly closed in
> these tests.
>
> Selva
>
> -Original Message-
> From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
> Sent: Monday, August 7, 2017 3:09 PM
> To: dev@trafodion.incubator.apache.org
> Subject: Failure in JDBC tests on multiple pull requests
>
> Hi,
>
> I was looking at the outstanding pull requests today. I noticed that some
> JDBC-related changes are getting the following failure:
>
> 2017-08-04 05:27:18 Batch Update Failed, See next exception for details
> 2017-08-04 05:27:18 Invalid Parameter Value: VARCHAR data longer than
> column length: 1
> 2017-08-04 05:27:30 Running testBatchInsertFKNotExist..
> 2017-08-04 05:27:51 *** ERROR[2026] Server Process $ZSM0 has reached
> allowed depth for nowait operation from the process 0,15836. [2017-08-04
> 05:27:51]
> 2017-08-04 05:28:12 Running testBatchUpsertDuplicate..
> 2017-08-04 05:28:27 Running testBatchInsertPkDuplicate..
> 2017-08-04 05:28:41 Running testBatchUpdateOverflow..
> 2017-08-04 05:28:48 Batch Update Failed, See next exception for details
> 2017-08-04 05:28:48 Invalid Parameter Value: VARCHAR data longer than
> column length: 1
> 2017-08-04 05:28:52 Running testBatchUpdatePkDuplicate..
> 2017-08-04 05:28:59 Batch Update Failed, See next exception for details
> 2017-08-04 05:28:59 *** ERROR[8102] The operation is prevented by a unique
> constraint. [2017-08-04 05:28:59]
> 2017-08-04 05:29:06 Running testBatchInsertPositive..
> 2017-08-04 05:29:14 Time consumption for batch inserting 1 rows is
> 1867 milli seconds
> 2017-08-04 05:31:00 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed: 231.891 sec <<< FAILURE! - in BatchTest
>
> I don't see anything in the pull requests themselves that should cause
> this.
>
> Does anyone have an idea what might be doing it? I hate to get into a mode
> where we just repeatedly run tests until they pass without fixing the
> underlying problem.
>
> Thanks,
>
> Dave
>
>

RE: Failure in JDBC tests on multiple pull requests

2017-08-07 Thread Selva Govindarajan 
This error message is thrown if you have 14 or more statements active in a 
single connection. Please reduce the number of open statements in the 
connection. It is possible that the statement is not explicitly closed in these 
tests.

Selva

-Original Message-
From: Dave Birdsall [mailto:dave.birds...@esgyn.com] 
Sent: Monday, August 7, 2017 3:09 PM
To: dev@trafodion.incubator.apache.org
Subject: Failure in JDBC tests on multiple pull requests

Hi,

I was looking at the outstanding pull requests today. I noticed that some 
JDBC-related changes are getting the following failure:

2017-08-04 05:27:18 Batch Update Failed, See next exception for details
2017-08-04 05:27:18 Invalid Parameter Value: VARCHAR data longer than column 
length: 1
2017-08-04 05:27:30 Running testBatchInsertFKNotExist..
2017-08-04 05:27:51 *** ERROR[2026] Server Process $ZSM0 has reached allowed 
depth for nowait operation from the process 0,15836. [2017-08-04 05:27:51]
2017-08-04 05:28:12 Running testBatchUpsertDuplicate..
2017-08-04 05:28:27 Running testBatchInsertPkDuplicate..
2017-08-04 05:28:41 Running testBatchUpdateOverflow..
2017-08-04 05:28:48 Batch Update Failed, See next exception for details
2017-08-04 05:28:48 Invalid Parameter Value: VARCHAR data longer than column 
length: 1
2017-08-04 05:28:52 Running testBatchUpdatePkDuplicate..
2017-08-04 05:28:59 Batch Update Failed, See next exception for details
2017-08-04 05:28:59 *** ERROR[8102] The operation is prevented by a unique 
constraint. [2017-08-04 05:28:59]
2017-08-04 05:29:06 Running testBatchInsertPositive..
2017-08-04 05:29:14 Time consumption for batch inserting 1 rows is 1867 
milli seconds
2017-08-04 05:31:00 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time 
elapsed: 231.891 sec <<< FAILURE! - in BatchTest

I don't see anything in the pull requests themselves that should cause this.

Does anyone have an idea what might be doing it? I hate to get into a mode 
where we just repeatedly run tests until they pass without fixing the 
underlying problem.

Thanks,

Dave