RE: Application Deployment Process
- From: dogirard@xxxxxxxxxxxxxxxxxxxx (Doug Girard [MSFT])
- Date: Tue, 12 Sep 2006 17:55:42 GMT
If a previous version of the BizTalk artifact is already deployed and
running in a host instance, deploying an updated version will not take
effect in the runtime until the host instance is restarted. Instead, the
cached version of the DLL will be held and used by the app domain -- this
is just how .NET works. The application domain is not recycled on a
deployment event by default, only when bouncing the service. There is a
warning that you will see about this in your Build Errors/Warning frame of
VS.
However, there is an option in the Deployment properties of a VS project
that will automatically restart all host instances on the local box after a
successful deployment. This will ensure the latest version is being
executed by the runtime. This is fine for testing on the local box, but if
you are troubleshooting on multi-machine topologies, just be sure to GAC
and restart the appropriate host instances on the other remote machines in
the group as well.
There is more about this in the Deployment whitepaper:
http://www.microsoft.com/biztalk/techinfo/whitepapers/bts2006_appdepwp.mspx
HTH,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
Thread-Topic: Application Deployment Processsituation
thread-index: AcbWfItNNXu/dp+1QKKg1QpKQH12Tg==
X-WBNR-Posting-Host: 194.75.37.250
From: =?Utf-8?B?TWlrZQ==?= <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Application Deployment Process
Date: Tue, 12 Sep 2006 08:03:02 -0700
Lines: 24
Message-ID: <8143625C-ECAF-4AC0-A3B9-3535912EFF34@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.biztalk.general
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:40714
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.biztalk.general
I had a situation which made me think i slightly understood the deployment
process incorrectly when deploying a BizTalk 2006 application. The
was
1. I changed an orchestration to include an expression shape which was
writing out to the event log a message
2. I ran my automated build/deployment which does the following:
a. Stop the application
b. Delete the application
c. Create the application
d. Deploy all of the bizTalk artifacts
e. Start the application
f. Run bizunit tests against the application
the expression shape never wrote to the event log, and when i used the
orchestration debugger it always skipped the expression shape.
I found that if i stopped then started the bizTalk windows service
everything worked fine. My previous understanding was that BizTalk
applications were in some ways similar to an iis application pool in that
they sand boxed processing and stopping the application would release all
resources it had held. Obviously this doesnt seem to be the case.
Just wondering if anyone had thoughts or comments on this?
.
- Prev by Date: Re: BizTalk eating up SQL Server (Virii Behaviour)
- Next by Date: Re: Custom functoid fails when orchestration deployed
- Previous by thread: BizTalk eating up SQL Server (Virii Behaviour)
- Next by thread: Re: Application Deployment Process
- Index(es):
Relevant Pages
|
