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.

Replication stops after Error 6624

6 posts in Replication Last posting was on 2011-03-28 08:57:07.0Z
Tim Murfitt Posted on 2011-03-22 13:10:39.0Z
Reply-To: "Tim Murfitt" <tim@tmurfitt.co.uk>
From: "Tim Murfitt" <tim@tmurfitt.co.uk>
Newsgroups: Advantage.Replication
Subject: Replication stops after Error 6624
Date: Tue, 22 Mar 2011 13:10:39 -0000
Lines: 1
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.3502.922
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922
NNTP-Posting-Host: 82.70.207.190
Message-ID: <4d889fa8$1@solutions.advantagedatabase.com>
X-Trace: 22 Mar 2011 06:10:00 -0700, 82.70.207.190
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:446
Article PK: 1134299

ADS v10.1

I have a client replicating a database bi-directionally between two sites.
A few times now replication has stopped with the 6624 error (Help file: A
remote socket connection was closed by the server. This error will usually
be raised by client applications if the server is shut down when clients are
still connected.)

The only way we have been able to resolve the problem is by stopping and
restarting the servers. Unfortunately it is not clear which server is
causing the problem so we have been restarting both as the easiest way to
get operational again. A EXECUTE PROCEDURE sp_ProcessReplicationQueues( 1 )
does not restart the replication. It just generates another 6624 error.

Clearly I need to find out why the original 6624 error happened and stop the
problem at source but how can i get the replication to restart without
having to restart the servers?

Regards

Tim Murfitt


Tim Murfitt Posted on 2011-03-22 13:13:19.0Z
Reply-To: "Tim Murfitt" <tim@tmurfitt.co.uk>
From: "Tim Murfitt" <tim@tmurfitt.co.uk>
Newsgroups: Advantage.Replication
References: <4d889fa8$1@solutions.advantagedatabase.com>
In-Reply-To: <4d889fa8$1@solutions.advantagedatabase.com>
Subject: Re: Replication stops after Error 6624
Date: Tue, 22 Mar 2011 13:13:19 -0000
Lines: 1
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 15.4.3502.922
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922
NNTP-Posting-Host: 82.70.207.190
Message-ID: <4d88a049@solutions.advantagedatabase.com>
X-Trace: 22 Mar 2011 06:12:41 -0700, 82.70.207.190
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:447
Article PK: 1134300

A little bit of clarification. It is the ADS services that are being
restarted not the the servers themselves.



"Tim Murfitt" wrote in message
news:4d889fa8$1@solutions.advantagedatabase.com...

ADS v10.1

I have a client replicating a database bi-directionally between two sites.
A few times now replication has stopped with the 6624 error (Help file: A
remote socket connection was closed by the server. This error will usually
be raised by client applications if the server is shut down when clients are
still connected.)

The only way we have been able to resolve the problem is by stopping and
restarting the servers. Unfortunately it is not clear which server is
causing the problem so we have been restarting both as the easiest way to
get operational again. A EXECUTE PROCEDURE sp_ProcessReplicationQueues( 1 )
does not restart the replication. It just generates another 6624 error.

Clearly I need to find out why the original 6624 error happened and stop the
problem at source but how can i get the replication to restart without
having to restart the servers?

Regards

Tim Murfitt


Tim Murfitt Posted on 2011-03-24 18:44:21.0Z
Reply-To: "Tim Murfitt" <tim@tmurfitt.co.uk>
From: "Tim Murfitt" <tim@tmurfitt.co.uk>
Newsgroups: Advantage.Replication
References: <4d889fa8$1@solutions.advantagedatabase.com> <4d88a049@solutions.advantagedatabase.com>
In-Reply-To: <4d88a049@solutions.advantagedatabase.com>
Subject: Re: Replication stops after Error 6624
Date: Thu, 24 Mar 2011 18:44:21 -0000
Lines: 1
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 15.4.3502.922
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922
NNTP-Posting-Host: 82.70.207.190
Message-ID: <4d8b90cf@solutions.advantagedatabase.com>
X-Trace: 24 Mar 2011 11:43:27 -0700, 82.70.207.190
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:448
Article PK: 1134301

This issue has now been resolved with Advantage Technical Support. The
following is a summary of the answer in case it is of any help to other
users.

The 6624 error was caused by the internet connection being lost whilst in
the middle of processing a large replication queue. My application
detected that replication was not proceeding and automatically issued every
few seconds a EXECUTE PROCEDURE sp_ProcessReplicationQueues( 1 ) in an
attempt to restart the replication process. Every time that this procedure
ran it caused another 6624 error. The problem is that post a 6624 error it
would appear you need to leave about a minute before trying another
connection so that there is time for any invalid polled connections to be
released.

I have now changed the application so that it now only tries a restart every
two minutes. I have found that this has worked ok. My application will now
automatically restart the replication process after a lost internet
connection being recovered. Tech Support said that i might have to pause
the replication process (manually or using sp_ModifySubscriptionProperty)
for a minute to allow the 6624 problem to resolve. I have not found I have
needed to do this but have allowed for this possibility.

Hope this may be of some help.

Tim Murfitt


Mark Wilkins Posted on 2011-03-25 15:54:34.0Z
From: "Mark Wilkins" <a@b.c>
Newsgroups: Advantage.Replication
References: <4d889fa8$1@solutions.advantagedatabase.com> <4d88a049@solutions.advantagedatabase.com> <4d8b90cf@solutions.advantagedatabase.com>
In-Reply-To: <4d8b90cf@solutions.advantagedatabase.com>
Subject: Re: Replication stops after Error 6624
Date: Fri, 25 Mar 2011 09:54:34 -0600
Lines: 2
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: <4d8cba8a$1@solutions.advantagedatabase.com>
X-Trace: 25 Mar 2011 08:53:46 -0700, 10.6.199.122
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:449
Article PK: 1134302

Hi Tim,

Thanks for posting the update on this and everything you learned. We have
addressed this, and the bug fix will be in the next service update (EBF).
We have changed the logic such that when a 6000 class error is received on a
replication attempt, it discards that connection rather than replacing it in
the pool. A 6000 class error typically means the connection is no longer
usable, but we were treating those errors basically the same as other errors
(e.g., 7000 class errors).

Mark Wilkins
Advantage R&D

"Tim Murfitt" <tim@tmurfitt.co.uk> wrote in message
news:4d8b90cf@solutions.advantagedatabase.com...
> This issue has now been resolved with Advantage Technical Support. The
> following is a summary of the answer in case it is of any help to other
> users.
>
> The 6624 error was caused by the internet connection being lost whilst in
> the middle of processing a large replication queue. My application
> detected that replication was not proceeding and automatically issued
> every few seconds a EXECUTE PROCEDURE sp_ProcessReplicationQueues( 1 ) in
> an attempt to restart the replication process. Every time that this
> procedure ran it caused another 6624 error. The problem is that post a
> 6624 error it would appear you need to leave about a minute before trying
> another connection so that there is time for any invalid polled
> connections to be released.
>
> I have now changed the application so that it now only tries a restart
> every two minutes. I have found that this has worked ok. My application
> will now automatically restart the replication process after a lost
> internet connection being recovered. Tech Support said that i might have
> to pause the replication process (manually or using
> sp_ModifySubscriptionProperty) for a minute to allow the 6624 problem to
> resolve. I have not found I have needed to do this but have allowed for
> this possibility.
>
> Hope this may be of some help.
>
> Tim Murfitt


Tim Murfitt Posted on 2011-03-28 08:45:26.0Z
Reply-To: "Tim Murfitt" <tim@tmurfitt.co.uk>
From: "Tim Murfitt" <tim@tmurfitt.co.uk>
Newsgroups: Advantage.Replication
References: <4d889fa8$1@solutions.advantagedatabase.com> <4d88a049@solutions.advantagedatabase.com> <4d8b90cf@solutions.advantagedatabase.com> <4d8cba8a$1@solutions.advantagedatabase.com>
In-Reply-To: <4d8cba8a$1@solutions.advantagedatabase.com>
Subject: Re: Replication stops after Error 6624
Date: Mon, 28 Mar 2011 09:45:26 +0100
Lines: 1
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 15.4.3502.922
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922
NNTP-Posting-Host: 82.70.207.190
Message-ID: <4d904a67$1@solutions.advantagedatabase.com>
X-Trace: 28 Mar 2011 01:44:23 -0700, 82.70.207.190
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:450
Article PK: 1134304

Mark

Thanks for advising me of your bug fix. Can you please explain what you
mean by next service update (EBF)? Is this different to a new release (i
see 10.1 is just out) and if so how do i find out about them?

Thanks

Tim



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

Hi Tim,

Thanks for posting the update on this and everything you learned. We have
addressed this, and the bug fix will be in the next service update (EBF).
We have changed the logic such that when a 6000 class error is received on a
replication attempt, it discards that connection rather than replacing it in
the pool. A 6000 class error typically means the connection is no longer
usable, but we were treating those errors basically the same as other errors
(e.g., 7000 class errors).

Mark Wilkins
Advantage R&D

"Tim Murfitt" <tim@tmurfitt.co.uk> wrote in message
news:4d8b90cf@solutions.advantagedatabase.com...
> This issue has now been resolved with Advantage Technical Support. The
> following is a summary of the answer in case it is of any help to other
> users.
>
> The 6624 error was caused by the internet connection being lost whilst in
> the middle of processing a large replication queue. My application
> detected that replication was not proceeding and automatically issued
> every few seconds a EXECUTE PROCEDURE sp_ProcessReplicationQueues( 1 ) in
> an attempt to restart the replication process. Every time that this
> procedure ran it caused another 6624 error. The problem is that post a
> 6624 error it would appear you need to leave about a minute before trying
> another connection so that there is time for any invalid polled
> connections to be released.
>
> I have now changed the application so that it now only tries a restart
> every two minutes. I have found that this has worked ok. My application
> will now automatically restart the replication process after a lost
> internet connection being recovered. Tech Support said that i might have
> to pause the replication process (manually or using
> sp_ModifySubscriptionProperty) for a minute to allow the 6624 problem to
> resolve. I have not found I have needed to do this but have allowed for
> this possibility.
>
> Hope this may be of some help.
>
> Tim Murfitt


Joachim Duerr (ADS) Posted on 2011-03-28 08:57:07.0Z
From: "Joachim Duerr (ADS)" <jojo.duerr@gmx.de>
Subject: Re: Replication stops after Error 6624
Newsgroups: Advantage.Replication
References: <4d889fa8$1@solutions.advantagedatabase.com> <4d88a049@solutions.advantagedatabase.com> <4d8b90cf@solutions.advantagedatabase.com> <4d8cba8a$1@solutions.advantagedatabase.com> <4d904a67$1@solutions.advantagedatabase.com>
Date: Mon, 28 Mar 2011 10:57:07 +0200
User-Agent: XanaNews/1.19.1.269
X-Face: u2p+</,mb|Ah!x!/qxX5q0t:O~.<1&JzwNHYhSqcviY{~&|iDc"U.Je1A.ZeHR`d;;y#R
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 10.29.66.130
Message-ID: <4d904ca2$1@solutions.advantagedatabase.com>
X-Trace: 28 Mar 2011 01:53:54 -0700, 10.29.66.130
Lines: 16
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:451
Article PK: 1134303


Tim Murfitt wrote:

>Thanks for advising me of your bug fix. Can you please explain what
>you mean by next service update (EBF)? Is this different to a new
>release (i see 10.1 is just out) and if so how do i find out about
>them?

10.1 is a minor release, an EBF or service update get's a number like
10.1.0.6 (which is the latest). You'll get informed if you subscribe to
AdsAnnouncements News feed or by checking Advantage.Announcements on
this server.

--
Joachim Duerr, Advantage Presales
*** NEW *** Advantage Pocket Guide released *** NEW ***
http://pocketguide.jd-engineering.de