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.

AIMs not working after Impact 5.5.1 upgrade

4 posts in General Discussion Last posting was on 2010-02-17 19:47:31.0Z
Jan Ross Posted on 2010-02-03 15:36:10.0Z
Sender: 21cf.4b69907e.1804289383@sybase.com
From: Jan Ross
Newsgroups: sybase.public.impact
Subject: AIMs not working after Impact 5.5.1 upgrade
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4b6997ea.228e.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 3 Feb 2010 07:36:10 -0800
X-Trace: forums-1-dub 1265211370 10.22.241.41 (3 Feb 2010 07:36:10 -0800)
X-Original-Trace: 3 Feb 2010 07:36:10 -0800, 10.22.241.41
Lines: 11
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.impact:2225
Article PK: 230302

We've had some AIMs that worked fine in version 5.4.6 but
stopped working correctly after upgrading to 5.5.1.
According to our end point vendors, it is due to timing
issues.
For example, some of the delivery AIMs were not waiting long
enough for an Ack to be received before resending the
message, and eventually they time out. We use a generic
delivery AIM, so we are puzzled as to why some AIMs work ok
and some do not. Weve
had a similar issue with acquisition AIMs. Has anyone else
experienced this problem?


chris Posted on 2010-02-03 17:56:25.0Z
Sender: 5907.4b67488a.1804289383@sybase.com
From: Chris
Newsgroups: sybase.public.impact
Subject: Re: AIMs not working after Impact 5.5.1 upgrade
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4b69b8c9.2641.1681692777@sybase.com>
References: <4b6997ea.228e.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 3 Feb 2010 09:56:25 -0800
X-Trace: forums-1-dub 1265219785 10.22.241.41 (3 Feb 2010 09:56:25 -0800)
X-Original-Trace: 3 Feb 2010 09:56:25 -0800, 10.22.241.41
Lines: 29
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.impact:2226
Article PK: 230301

The timers that were there before - should still be there..
not sure why they would not wait long enough now
unless previously they were timing out prematurely and the
engine recovered in a better way..
--
what is the main issue..
are the transactions queueing up in SFM and need
intervention?
are the same messages being sent twice?
are the timers in your AIM configurable or hard-coded?
can you send me your AIM code?

celm
at
first choice professionals
(dot com)

> We've had some AIMs that worked fine in version 5.4.6 but
> stopped working correctly after upgrading to 5.5.1.
> According to our end point vendors, it is due to timing
> issues.
> For example, some of the delivery AIMs were not waiting
> long enough for an Ack to be received before resending the
> message, and eventually they time out. We use a generic
> delivery AIM, so we are puzzled as to why some AIMs work
> ok and some do not. Weve
> had a similar issue with acquisition AIMs. Has anyone else
> experienced this problem?


jl Posted on 2010-02-11 17:16:34.0Z
Sender: 1f77.4b743a67.1804289383@sybase.com
From: JL
Newsgroups: sybase.public.impact
Subject: Re: AIMs not working after Impact 5.5.1 upgrade
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4b743b72.1fae.1681692777@sybase.com>
References: <4b6997ea.228e.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 11 Feb 2010 09:16:34 -0800
X-Trace: forums-1-dub 1265908594 10.22.241.41 (11 Feb 2010 09:16:34 -0800)
X-Original-Trace: 11 Feb 2010 09:16:34 -0800, 10.22.241.41
Lines: 19
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.impact:2228
Article PK: 230306

Apply the 5.5.3 EBF.
5.5.3 fixed several tcp/ip issues especially on AIX.

Anybody upgrading from 5.4 or below should not even consider
anything but 5.5.3.

> We've had some AIMs that worked fine in version 5.4.6 but
> stopped working correctly after upgrading to 5.5.1.
> According to our end point vendors, it is due to timing
> issues.
> For example, some of the delivery AIMs were not waiting
> long enough for an Ack to be received before resending the
> message, and eventually they time out. We use a generic
> delivery AIM, so we are puzzled as to why some AIMs work
> ok and some do not. Weve
> had a similar issue with acquisition AIMs. Has anyone else
> experienced this problem?