Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

ace32

5 posts in Networking Last posting was on 2011-11-29 21:11:52.0Z
Filip Fransen Posted on 2011-11-22 21:56:17.0Z
From: "Filip Fransen" <filip_666@hotmail.com>
Newsgroups: Advantage.Networking
Subject: ace32
Date: Tue, 22 Nov 2011 22:56:17 +0100
Lines: 2
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 15.4.3538.513
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513
NNTP-Posting-Host: 81.82.227.183
Message-ID: <4ecdd494$1@solutions.advantagedatabase.com>
X-Trace: 23 Nov 2011 21:22:28 -0700, 81.82.227.183
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:979
Article PK: 1132389

I'm having issues with transaction sinds ADS v10.
I'm using the api AdsBeginTransaction and AdsCommitTransaction. This has
allways worked fine until v10.
After a while a transaction is started but the AdsCommitTransaction doesn't
work anymore. The result is that all changes are lost because the only
option is closing my app. After changing the ace32 version back to v9
everything is working as expected. The server version is still v10. The API
adsintransaction is false even when the transaction is still active when i
happens!
Any thoughts ?

Tx
Filip


Mark Wilkins Posted on 2011-11-28 23:28:55.0Z
From: "Mark Wilkins" <a@b.c>
Newsgroups: Advantage.Networking
References: <4ecdd494$1@solutions.advantagedatabase.com>
In-Reply-To: <4ecdd494$1@solutions.advantagedatabase.com>
Subject: Re: ace32
Date: Mon, 28 Nov 2011 16:28:55 -0700
Lines: 1
Organization: Sybase
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
NNTP-Posting-Host: 10.6.199.122
Message-ID: <4ed4190e$1@solutions.advantagedatabase.com>
X-Trace: 28 Nov 2011 15:28:14 -0700, 10.6.199.122
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:980
Article PK: 1132390

Hi,

Can you post a simple example that shows the problem?

One thing that changed with transactions is that v10 supports nested
transactions. So if there are two calls to AdsBeginTransaction then it
requires two calls to AdsCommitTransaction to commit it.

With v9.x, a second call to AdsBeginTransaction would return a 5047 error.
With v10, it will succeed and then require the additional commit call.

Mark Wilkins
Advantage R&D

"Filip Fransen" <filip_666@hotmail.com> wrote in message
news:4ecdd494$1@solutions.advantagedatabase.com...
> I'm having issues with transaction sinds ADS v10.
> I'm using the api AdsBeginTransaction and AdsCommitTransaction. This has
> allways worked fine until v10.
> After a while a transaction is started but the AdsCommitTransaction
> doesn't work anymore. The result is that all changes are lost because the
> only option is closing my app. After changing the ace32 version back to v9
> everything is working as expected. The server version is still v10. The
> API adsintransaction is false even when the transaction is still active
> when i happens!
> Any thoughts ?
>
> Tx
> Filip
>


devzone.advantagedatabase.com Posted on 2011-11-29 07:45:33.0Z
From: "devzone.advantagedatabase.com" <filip@datasupport.be>
Newsgroups: Advantage.Networking
References: <4ecdd494$1@solutions.advantagedatabase.com> <4ed4190e$1@solutions.advantagedatabase.com>
In-Reply-To: <4ed4190e$1@solutions.advantagedatabase.com>
Subject: Re: ace32
Date: Tue, 29 Nov 2011 08:45:33 +0100
Lines: 1
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 15.4.3538.513
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513
NNTP-Posting-Host: 84.199.84.252
Message-ID: <4ed48d74$1@solutions.advantagedatabase.com>
X-Trace: 28 Nov 2011 23:44:52 -0700, 84.199.84.252
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:981
Article PK: 1132391

Hi Marc,

This is happening in a large application.Sometimes after days sometimes
after a few hours. I didn't manage to reproduce a simple and small sample.
Is this nested transaction behaviour depended on which version of ace32 is
loaded ( v9 vs v10 ) targetting the same v10 server ?

Tx
Filip

"Mark Wilkins" wrote in message
news:4ed4190e$1@solutions.advantagedatabase.com...

Hi,

Can you post a simple example that shows the problem?

One thing that changed with transactions is that v10 supports nested
transactions. So if there are two calls to AdsBeginTransaction then it
requires two calls to AdsCommitTransaction to commit it.

With v9.x, a second call to AdsBeginTransaction would return a 5047 error.
With v10, it will succeed and then require the additional commit call.

Mark Wilkins
Advantage R&D

"Filip Fransen" <filip_666@hotmail.com> wrote in message
news:4ecdd494$1@solutions.advantagedatabase.com...
> I'm having issues with transaction sinds ADS v10.
> I'm using the api AdsBeginTransaction and AdsCommitTransaction. This has
> allways worked fine until v10.
> After a while a transaction is started but the AdsCommitTransaction
> doesn't work anymore. The result is that all changes are lost because the
> only option is closing my app. After changing the ace32 version back to v9
> everything is working as expected. The server version is still v10. The
> API adsintransaction is false even when the transaction is still active
> when i happens!
> Any thoughts ?
>
> Tx
> Filip
>


Mark Wilkins Posted on 2011-11-29 21:11:52.0Z
From: "Mark Wilkins" <a@b.c>
Newsgroups: Advantage.Networking
References: <4ecdd494$1@solutions.advantagedatabase.com> <4ed4190e$1@solutions.advantagedatabase.com> <4ed48d74$1@solutions.advantagedatabase.com>
In-Reply-To: <4ed48d74$1@solutions.advantagedatabase.com>
Subject: Re: ace32
Date: Tue, 29 Nov 2011 14:11:52 -0700
Lines: 1
Organization: Sybase
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
NNTP-Posting-Host: 10.6.199.122
Message-ID: <4ed54a6c@solutions.advantagedatabase.com>
X-Trace: 29 Nov 2011 13:11:08 -0700, 10.6.199.122
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:983
Article PK: 1132393

It does depend on the version of ACE32.DLL that is loaded. With v9 of
ACE32, it will not allow a nested transaction. AdsBeginTransaction will
return a 5047 error if it is called while a transaction is active. So if
the application makes a call to AdsBeginTransaction somewhere while a
transaction is already active and it ignores the error, then it could result
in this behavior. With v9, it would essentially be a no-op. With v10,
though, it would start the nested transaction and thus require an additional
commit.

You could check for this situation by calling AdsGetTransactionCount to see
if if the nested transaction exists. If, prior to the AdsCommitTransaction
call, it returns a value greater than 1, then it indicates that it is
nested.

Mark Wilkins
Advantage R&D

"devzone.advantagedatabase.com" <filip@datasupport.be> wrote in message
news:4ed48d74$1@solutions.advantagedatabase.com...
> Hi Marc,
>
> This is happening in a large application.Sometimes after days sometimes
> after a few hours. I didn't manage to reproduce a simple and small sample.
> Is this nested transaction behaviour depended on which version of ace32 is
> loaded ( v9 vs v10 ) targetting the same v10 server ?
>
> Tx
> Filip
>
> "Mark Wilkins" wrote in message
> news:4ed4190e$1@solutions.advantagedatabase.com...
>
> Hi,
>
> Can you post a simple example that shows the problem?
>
> One thing that changed with transactions is that v10 supports nested
> transactions. So if there are two calls to AdsBeginTransaction then it
> requires two calls to AdsCommitTransaction to commit it.
>
> With v9.x, a second call to AdsBeginTransaction would return a 5047 error.
> With v10, it will succeed and then require the additional commit call.
>
> Mark Wilkins
> Advantage R&D
>
>
> "Filip Fransen" <filip_666@hotmail.com> wrote in message
> news:4ecdd494$1@solutions.advantagedatabase.com...
>> I'm having issues with transaction sinds ADS v10.
>> I'm using the api AdsBeginTransaction and AdsCommitTransaction. This has
>> allways worked fine until v10.
>> After a while a transaction is started but the AdsCommitTransaction
>> doesn't work anymore. The result is that all changes are lost because the
>> only option is closing my app. After changing the ace32 version back to
>> v9 everything is working as expected. The server version is still v10.
>> The API adsintransaction is false even when the transaction is still
>> active when i happens!
>> Any thoughts ?
>>
>> Tx
>> Filip
>>
>


devzone.advantagedatabase.com Posted on 2011-11-29 07:45:38.0Z
From: "devzone.advantagedatabase.com" <filip@datasupport.be>
Newsgroups: Advantage.Networking
References: <4ecdd494$1@solutions.advantagedatabase.com> <4ed4190e$1@solutions.advantagedatabase.com>
In-Reply-To: <4ed4190e$1@solutions.advantagedatabase.com>
Subject: Re: ace32
Date: Tue, 29 Nov 2011 08:45:38 +0100
Lines: 1
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 15.4.3538.513
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513
NNTP-Posting-Host: 84.199.84.252
Message-ID: <4ed48d7a$1@solutions.advantagedatabase.com>
X-Trace: 28 Nov 2011 23:44:58 -0700, 84.199.84.252
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:982
Article PK: 1132392

Hi Marc,

This is happening in a large application.Sometimes after days sometimes
after a few hours. I didn't manage to reproduce a simple and small sample.
Is this nested transaction behaviour depended on which version of ace32 is
loaded ( v9 vs v10 ) targetting the same v10 server ?

Tx
Filip

"Mark Wilkins" wrote in message
news:4ed4190e$1@solutions.advantagedatabase.com...

Hi,

Can you post a simple example that shows the problem?

One thing that changed with transactions is that v10 supports nested
transactions. So if there are two calls to AdsBeginTransaction then it
requires two calls to AdsCommitTransaction to commit it.

With v9.x, a second call to AdsBeginTransaction would return a 5047 error.
With v10, it will succeed and then require the additional commit call.

Mark Wilkins
Advantage R&D

"Filip Fransen" <filip_666@hotmail.com> wrote in message
news:4ecdd494$1@solutions.advantagedatabase.com...
> I'm having issues with transaction sinds ADS v10.
> I'm using the api AdsBeginTransaction and AdsCommitTransaction. This has
> allways worked fine until v10.
> After a while a transaction is started but the AdsCommitTransaction
> doesn't work anymore. The result is that all changes are lost because the
> only option is closing my app. After changing the ace32 version back to v9
> everything is working as expected. The server version is still v10. The
> API adsintransaction is false even when the transaction is still active
> when i happens!
> Any thoughts ?
>
> Tx
> Filip
>