Re: BizTalk 2006: FTP Adapter Stops Polling
- From: "McGeeky" <anon@xxxxxxxx>
- Date: Fri, 2 Mar 2007 05:41:55 -0000
Is BizTalk stuck in the "connect" method? I opened a support incident with
Microsoft months ago, and through a BizTalk hang dump/stack trace, we got as
far as identifying that the FTP adapter was "hanging" in some low level
Connect method. It simply never returned. I requested Microsoft implement a
timeout on this method but got no joy from them.
If you have got one stage further and are being issued with a fix then I
congratulate you!
Which version of BizTalk is it, 2004 or 2006?
--
McGeeky
http://mcgeeky.blogspot.com
"falk0069" <falk0069@xxxxxxxxx> wrote in message
news:1172781618.000338.120700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 22, 11:14 am, Andreas <andr...@xxxxxxxxxxxxxx> wrote:relates
Hi,
Can't find if this problem relates to BTS2004 or BTS2006... If this
patchto BTS2004 it sounds like you guys haven't applied the .Net Framework
searchthat fixes the Timer-functionality. Can't remember the KB-number but
for .Net and Timer and you should find it.
/andreas
I'm having the same problem :-(
FTP-Location doesn't poll anymore, but is still enabled.
Disable/Enable helps.
I'm not quite sure if the polling stopped after a hostprocess restart
!?
trying to gather further infos!
KR
"Tao Zhang[MSFT]" wrote:
Hi! Craig
Have you raised the support request for this? I am handlingFTP
adaptertesting. I wonder whether I understand your correctly or
not:
You useFTPadapterto get file from UNIX system, and it will
automatically stop by iteself from time to time, and you can not see
anything in the event log when this is happened. Am I right?
--------------------
<AC9BA52F-CC6B-4BAA-A67C-EE54028A7...@xxxxxxxxxxxxx>From: "Jeff Lynch" <jeff.ly...@xxxxxxxxxxxxxxxx>
References: <Xns98BD8C3A27A62beukerccommunityn...@xxxxxxxxxxxxx>
<Xns98C183B449AA2beukerccommunityn...@xxxxxxxxxxxxx>
In-Reply-To: <Xns98C183B449AA2beukerccommunityn...@xxxxxxxxxxxxx>
Subject: Re:BizTalk2006:FTPAdapterStops Polling
Date: Thu, 25 Jan 2007 15:12:39 -0600
Lines: 79
Message-ID: <7E5A0B9A-B1E3-4482-9378-6D01DE99C...@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="Windows-1252";
reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
X-MS-CommunityGroup-PostID: {7E5A0B9A-B1E3-4482-9378-6D01DE99C082}
X-MS-CommunityGroup-ThreadID: 6CB8F239-BAEC-4FF0-A94C-542E1A8628ED
X-MS-CommunityGroup-ParentID: 58884A6A-42A1-402E-B07E-3DD96A311799
Newsgroups: microsoft.public.biztalk.general
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.biztalk.general:1856
NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
X-Tomcat-NG: microsoft.public.biztalk.general
Craig,
That's pretty strange behavior. When this happens to me it's
because the file can't be parsed (incorrect format) and isn't
deleted from the server
by
theadapter. If you're running a version of Unix supported by
BTS2006,
I'd
recommend opening a support case.
-- Best regards,
Jeff Lynch
MVP Windows Server System - Commerce Server
http://codebetter.com/blogs/jeff.lynch
"Craig Beuker" <beuk...@xxxxxxxxxxxxxxxx> wrote in message
news:Xns98C183B449AA2beukerccommunitynosp@xxxxxxxxxxxxxxxx
"Jeff Lynch" <jeff.ly...@xxxxxxxxxxxxxxxx> wrote in
news:AC9BA52F-CC6B-4BAA-A67C-EE54028A7B5C@xxxxxxxxxxxxx:
Craig,
Two things to check. Make sure the account you are using has
read, write and delete permissions on your Unix server. If one of
the files you are getting does not parse correctly, theFTP
adapterwill not issue the final delete command and from your
log, I don't see the files being deleted from your Unix server.
Checklist:
1) File Permissions: This is already set up and working. Smaller
files for fine. I haven't seem the thing stop on small files.
2) Files parse properly if I open them in IE or FireFox. Valid
XML.
You are correct that you don't see the files being deleted from
the UNIX server. TheFTPadapterjusthangsat the point after
receiving one of the files. Basically what I have done when I
encounter this situation
is
as follows:
1) Stop theFTPReceive location (It is in an enabled state when
the
problem occurs)
2) Set logging on theFTPReceive location
3) Start the location (problem persists)
Now, I have taken the following steps to try and deduce what is
going on
following step 3
4) Stop the receive location again.
5) Copy files out of the polled location to some other folder
6) Start theFTPReceive location, place 10 files in the folder.
7) First 10 went through
8) Place next 10 in folder
9) Receive location hung after receiving one of the larger files
(860K
around)
10) Restart the Receive location, Place 5 files in. Processed no
problems. Lather, rince, repeat for rest of files. No problems
Now, that seemed to work for a couple of days then the problem re-
appeared. This next time I did the following:
1) Stop the Receive Location
2) Modify the "Batch - Maximim files", set the value to 5 from 0.
3) Start theFTPlocation, all files are processed. No problems
About 3 days later, it happened again, theFTPReceive location
just
hung
or something, files weren't getting picked up and processed. I
did the
following:
1) Stop the Receive Location
2) Modify the "Batch - Maximim files", set the value to 1 from 5.
3) Start theFTPlocation, all files are processed. No problems
I haven't encountered the issue yet and it's been about a week
now..
Is there some additional logging which is easy to turn on?
Thanks in advance.
Craig B.- Hide quoted text -
- Show quoted text -
Craig,
We have a similar problem, but it is due to an over utilized network
connection between BizTalk and the FTP Server. It appears that
BizTalk does not have a timeout setting in its adapter if a connection
runs too long. The only way to reset it is to restart the FTP adapter
host. The real problem is packets are dropped by routers and BizTalk
is none the wiser and just continues to wait for a reply from the
server which will never happen. We currently have a support ticket
open with Microsoft for this issue (SRZ070110002735) and it sounds
likely they will be providing us with a private fix soon. So if you
believe you might have a bad connection between you two machines this
might be the same issue. It could also be the .NET/Timer bug, too,
that Andeas mentioned. Unfortunately that didn't solve it for us.
Good luck
--Andy
.
- Follow-Ups:
- Re: BizTalk 2006: FTP Adapter Stops Polling
- From: Craig Beuker
- Re: BizTalk 2006: FTP Adapter Stops Polling
- References:
- Re: BizTalk 2006: FTP Adapter Stops Polling
- From: falk0069
- Re: BizTalk 2006: FTP Adapter Stops Polling
- Prev by Date: Deploy issues for biztalk 2006
- Next by Date: RE: WSDL issues
- Previous by thread: Re: BizTalk 2006: FTP Adapter Stops Polling
- Next by thread: Re: BizTalk 2006: FTP Adapter Stops Polling
- Index(es):
Relevant Pages
|