- This topic has 1 reply, 1 voice, and was last updated 9 years, 9 months ago by
.
-
Posts
-
-
Hi,
We are currently looking to implement our first solution that makes use of the WSE 2.0 adapter in BizTalk 2004 and have encountered a problem.
The solution I have created receives a file from a directory which then starts an orchestration. This orchestration loads some options from a file, invokes a map and then, using a WSE Send Port, calls a web service from which it expects a response.
We have a number of environments – Dev, Test, Pseudo and Live – and so far we have released this solution to our deploment Dev server and the Test server where everything has worked ok.
We have now released to our Pseudo environment in preparation for going Live and have encountered a problem where-by the web service is not being called.
There are no entries in the event log.
Within HAT the message is marked as Active, “Delivered, Not Consumed”, and is listed against the WSE send port.
To me this indicates that BizTalk is aware of where the message should go but for some reason it is not being processed. All my efforts to google this issue have not readily turned up any obviously helpful lines of enquiry.
I am at a loss as to what to try next and thought some helpful soul might be able to come up with a useful suggestion.
Cheers
Stu.
-
Hello again, After much head scratching and installs on difefrent servers in the same domain, we have managed to get the send port to send. Using the technique on this web page: http://www.traceofthought.net/PermaLink,guid,273a4374-40fc-4fe4-bbe6-833aa3c84022.aspx we seem to have fixed the issue. The implication therefore is that the problem was with the way the WSE Adapter is handling threads and using the thread pool – the WSE Adapter didn’t have a ’free thread’ to process the response from the service.I had read the MSMQ article (linked above) a few days ago and had discounted it from our inquiries on the basis that the processes in question were the only thing running on the host in question (where there is a single WSE Send Port), there is only one receive location involved and we need only submit a single instruction to replicate the issue (in test we successfully tested the Web Service with 100 at once). This had led to a little confusion on my part – given the fact that there was unlikely to be any other threads using the WSE Adapter why did this happen, and why did it only affect Psuedo (we do not need these entries in Dev/Test)? Does anyone know if the fact that the Pseudo box is the first physical server (Dev and Test being virtual) is the best suspect for the difference in how the threads behaved, causing the need for these changes? CheersStu.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.