| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem with events blocking a connector |
« View previous topic :: View next topic » |
| Author |
Message
|
| fponcet |
 Posted: Thu Dec 15, 2005 9:38 am Post subject: Problem with events blocking a connector |
 |
|
Acolyte
Joined: 20 Oct 2005
Posts: 55
|
Hi,
Sometimes it looks like a single event blocks a connector (synchronous request). From that event on, no other events got processed. Only right after deleting a lot of tables it continues (CXSTATELOG, CXTRANSBLOBS, CXWIPBLOBS, ...).
Is there any property in the connector or in the collaboration to specify that one event error cannot block that connector?
Thanks. |
|
| Back to top |
|
 |
| Ratan |
| Posted: Thu Dec 15, 2005 9:42 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I believe the property you are looking for is the 'Blocking Property' in Collaboration Object properties.
_________________
-Ratan |
|
| Back to top |
|
|
| recallsunny |
| Posted: Thu Dec 15, 2005 12:48 pm Post subject: |
|
|
Disciple
Joined: 15 Jun 2005
Posts: 163
Location: Massachusetts
|
"Blocking Type" is meant to be used in conjunction with Max event capacity to control the no. of events in memory queue. Donot mistake this with the problem described in "Blocking event" topic, which talks about a single Error (unless ur max event capacity is 1 !!!).
Check for the key's of the business objects which are getting blocked by the single event which you've mentioned. Looks like its a Event sequence paradox. When all the new events have a similar event key as the Blocked event and your event sequencing is "turned On", you observe this kind of event blocking.... |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
