Re: Connection issue

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi Siva,

The keepalive property should be in the HTTP Headers. You can have a
look at these headers when you install a tool to capture HTTP traffic,
like Ethereal or HTTPAnalyzer (http://www.ieinspector.com/
httpanalyzer/).

HTH,

*** Dijkstra

On Aug 24, 11:12 pm, Siva <s...@xxxxxxxxxxxxxxxxx> wrote:
Hi ***
I have a question.
Should the XML out put contains "KeepAlive" syntex, If I add the following
lines in the custom pipeline:
public Microsoft.BizTalk.Message.Interop.IBaseMessage
Execute(Microsoft.BizTalk.Component.Interop.IPipelineContext pc,
Microsoft.BizTalk.Message.Interop.IBaseMessage inmsg)
{

inmsg.Context.Write("KeepAlive","http://schemas.microsoft.com/BizTalk/2003/http-properties";, false);
return inmsg;
}

I am not getting "KeepAlive" syntext in the xml out put. I am not sure
whether this code is working or not.
--
Thank you,

Siva



"*** Dijkstra" wrote:
Hi Siva,

That's bad luck... You might try to run a sniffer and compare the
requests and responses of both your 2004 and 2006 environments and
compare them. Especially look at the http headers. I also found this,
you can have look at it:http://markitup.com/Posts/Post.aspx?postId=c98db0ca-f3a8-4f49-bb96-64...

HTH,

*** Dijkstra

On Aug 23, 11:46 pm, Siva <s...@xxxxxxxxxxxxxxxxx> wrote:
Hi,
Thank you ***. I called the microsoft and intalled this hotfix still NO
LUCK. The article u send me and the problem i am facing looks exactly same.
Still this hot fix couldnt solve the problem.
I think this is related to Keepalive but i dont know how to fix.
--
Thank you,

Siva

"*** Dijkstra" wrote:
Hi Siva,

No thanks, hope we both can solve your problem. Since posting most of
the messages works fine, it might be the KeepAlive problem you
describe. Have a look athttp://support.microsoft.com/kb/924638/en-us.
Maybe it works for you, I'd give it a try.

HTH,

*** Dijkstra

On Aug 22, 10:42 pm, Siva <s...@xxxxxxxxxxxxxxxxx> wrote:
Hi ***,
Thank you for helping me continueously.
I tried tracert from both server. I am getting same report. Partner said
they didn't make any changes on their server.
We used to sent xml from the server that have biztalk 2004. we never had
any connection closed issue in that server. I recently moved all the project
to new server which have biztalk 2006. After that we get this connection
close error. Almost 93% of transaction go through with out any failure. only
7% face this "connection closed" issue. This 7% make sequence issue and other
issues.

Do you think anything related to Biztalk 2006, such as .NET fram work, HTTP
port - KeepAlife, might be the reason for this issue? I dont have enough
knowladge about them.
--
Thank you,

Siva

"*** Dijkstra" wrote:
Could it be possible that the destination server is behind a firewall?
If so, can you check the settings on it?

*** Dijkstra

On 22 aug, 09:38, Dick Dijkstra <dickdijks...@xxxxxxxxxxx> wrote:
Hi Siva,

Can you try a traceroute to the URI from both servers and see if
there's a difference?

*** Dijkstra

On 21 aug, 22:44, Siva <s...@xxxxxxxxxxxxxxxxx> wrote:

Hi ***,
Thank you for your reply. We have exactly same firewall setting. The telnet
for that URI works fine from this BizTalk 2006 server.
Is there any response set up or anything might make this host close?
I could not find anything on google neither. Please help me to solve this
issue.

--
Thank you,

Siva

"*** Dijkstra" wrote:
Hi Siva,

Are the server behind the same firewall? If so, have someone verify
the settings on the firewall and find out whether the parameters for
both servers are equal. If you don't use a proxy, you can leave the
default settings on the send port (that is, if you specified that no
proxy should be used in the handler, under platform settings).

Have you tried to telnet to you destination URI?

HTH,

*** Dijkstra

On 21 aug, 15:38, Siva <s...@xxxxxxxxxxxxxxxxx> wrote:
Hi ***,
Thank you for your reply. Both server are behind the firewall. I could not
reach the URI through the internet explorer on both servers.
The server that works fine has BizTalk 2004 and otherone, the one fails to
post sometime, has BizTalk 2006. I noticed that BizTalk 2006 has some extra
HTTP setting under the HTTP Configuration in Biztalk Adminitrater - Sent
ports. Do I need to set anything there? I left as defualt so the http sent
port for this partner has "use Handler's default proxy configuration" as
defult. Should I have to change this to Not to use proxy? Because we set up
the HTTP Adater NOT to use proxy, which is under the BizTalk Administater -
Platform Setting - Adapters .

--
Thank you,

Siva

"*** Dijkstra" wrote:
Hi Siva,

Could it be that this server is behind a firewall? Can you reach the
URI when you type it in Internet Explorer? You can also use telnet to
find out if you can reach the destination URI (port 443 as you use
https). You might also check the proxy settings (proxycfg.exe) on your
server.

HTH,

*** Dijkstra

On Aug 20, 11:46 pm, Siva <s...@xxxxxxxxxxxxxxxxx> wrote:
Hi,
I am using HTTP adapter in the send port to send xml file to partner. I am
getting the following warnning msg in the event view so often.

The adapter failed to transmit message going to send port "SENDPORT_A_HTTP"
with URL "https://patnerURI";. It will be retransmitted after the retry
interval specified for this Send Port. Details:"The underlying connection was
closed: A connection that was expected to be kept alive was closed by the
server.".

We have exactly same send port in another server, it works fine with out any
warnning msg or any failures.
Why does the connection close in this server? How can I fix this?

--
Thank you,

Siva- Tekst uit oorspronkelijk bericht niet weergeven -

- Tekst uit oorspronkelijk bericht weergeven -- Tekst uit oorspronkelijk bericht niet weergeven -

- Tekst uit oorspronkelijk bericht weergeven -- Tekst uit oorspronkelijk bericht niet weergeven -

- Tekst uit oorspronkelijk bericht weergeven -- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -


.

Quantcast