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.

Multiple updates not commited from appeon 6

2 posts in Appeon (partner product) Last posting was on 2008-09-04 01:15:14.0Z
diasroshan Posted on 2008-08-30 12:57:38.0Z
From: diasroshan@gmail.com
Newsgroups: sybase.public.appeon
Subject: Multiple updates not commited from appeon 6
Date: Sat, 30 Aug 2008 05:57:38 -0700 (PDT)
Organization: http://groups.google.com
Lines: 35
Message-ID: <14589d46-19bb-4169-8bf7-b31956057fc7@m73g2000hsh.googlegroups.com>
NNTP-Posting-Host: 168.187.78.193
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1220101059 6041 127.0.0.1 (30 Aug 2008 12:57:39 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 30 Aug 2008 12:57:39 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: m73g2000hsh.googlegroups.com; posting-host=168.187.78.193; posting-account=E8Js2goAAACVqO-x2AEsT-bsYEPkNrs_
User-Agent: G2/1.0
X-HTTP-Via: 1.0 KWISA
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30),gzip(gfe),gzip(gfe)
Path: forums-1-dub!forums-master!newssvr.sybase.com!news-sj-1.sprintlink.net!news-peer1.sprintlink.net!nntp1.phx1.gblx.net!nntp.gblx.net!nntp.gblx.net!border2.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!m73g2000hsh.googlegroups.com!not-for-mail
Xref: forums-1-dub sybase.public.appeon:2215
Article PK: 13334

Hi,

i have recently upgraded from appeon 5.1 to appeon 6

The issue is as follows,
The major show stopping issue faced right now is database locking.

Using PB 10.5/Appeon 6/ Sybase 12.5

If I have multiple datawindows updated and a final Commit in a window.
The commit, only commits the last datawindow and leaves the other 2
uncommited and hence causes a database lock.

Example.
Dw_1.Update()
Dw_2.Update()
Dw_3.Update()
Commit;

The above only commits dw_3 and causes a lock on the tables for dw_1
and dw_2


Also note,
Dw_1.Update()
Commit;
Dw_2.Update()
Commit;
Dw_3.Update()
Commit;

The above works fine but isn’t practical.

Cheers,
Rosh


steven.yang Posted on 2008-09-04 01:15:14.0Z
Sender: 44bb.48bf3467.1804289383@sybase.com
From: steven.yang
Newsgroups: sybase.public.appeon
Subject: Re: Multiple updates not commited from appeon 6
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <48bf36a2.4509.1681692777@sybase.com>
References: <14589d46-19bb-4169-8bf7-b31956057fc7@m73g2000hsh.googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 3 Sep 2008 18:15:14 -0700
X-Trace: forums-1-dub 1220490914 10.22.241.41 (3 Sep 2008 18:15:14 -0700)
X-Original-Trace: 3 Sep 2008 18:15:14 -0700, 10.22.241.41
Lines: 35
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:2216
Article PK: 13336

Hi Rosh,

For this issue, the error may occur in the Update function,
which can cause the deadlock of database. We recommend that
you judge the return value of the DataWindow Update first,
and then use Commit or Rollback statement. When doing these
operation, please make sure the related information below is
correct:
a) Your data source setting and the JDBC driver type are
consistent with that which Appeon can support, or else, the
web application cannot work normally. For details, please
refer to Appeon Help | Appeon Server Configuration Guide |
Database Connection Setup | Setting up Appeon Server data
sources\connection caches.
b) The configuration items of DataSource is correct,
especially note the configuration of DataBase URL is
correct.
c) If your EAServer is 6.0, please try to modify the Commit
Protocol property of DataSource.The specific operation
method is: Log on to the EAServer Console, go to Resources |
Data Sources, select the DataSource you used, and then set
Commit Protocol to optimistic in General page, and then
restart EAServer.
If our solution can't resolve your issue, please send us the
following files so that we can look further into this issue
and debug it:
a) AppeonServer.log(Note you need to go to AEM and set the
Log mode to debug and then reproduce the problem)
b) AppeonError.log;
c) EAServer log(êServer6%\logs\EAServer_instance.log);
d) Test case. (This is important. If we can reproduce in our
environment, we can resolve this issue ASAP.)

Regards,
Steven