Bug 1567 - PullConsumer with "pull()" locks CosEvent_Service
Summary: PullConsumer with "pull()" locks CosEvent_Service
Status: ASSIGNED
Alias: None
Product: TAO
Classification: Unclassified
Component: CosEvent Service (show other bugs)
Version: 1.3
Hardware: x86 Linux
: P3 major
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 2003-08-10 19:05 CDT by Robert Whitney
Modified: 2003-08-28 09:08 CDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Whitney 2003-08-10 19:05:39 CDT 
I've modified the tutorial for CosEvents by changing the Stock_Consumer to a
PullConsumer.  The "try_pull()" works fine, but the "pull()" method call seems
to lock up the CosEvent_Servce, and subsequently the supplier.

There is a reference to this bug via a google search but I can't located it in
this bugzilla service:

http://groups.yahoo.com/group/tao-bugs/message/514

Is there a known work-around or fix?

Many thanks, Rob.
Comment 1 pradeep 2003-08-16 14:02:28 CDT 
This version of the EC was written by Carlos. reassigning to tao-support for 
now.
Comment 2 Nanbor Wang 2003-08-24 19:35:26 CDT 
Aceepting bug for tao-suport

Rob, if you want this problem badly fixed, I would recommend you to contact OCI 
or Johnny Willemsen <jwillemsen@remedy.nl>. The doc_group is swamped with other 
projects and it would be hard for us to allote time to this.
Comment 3 Carlos O'Ryan 2003-08-25 09:06:48 CDT 
I assume you are using the CosEvent in thread-per-connection mode?  The
documentation may not say so, but pull() does not work reliably otherwise.

BTW, this is a perfect use-case for AMH in TAO.  Maybe a new DOC group member
can learn a bit by implementing pull() using AMH?
Comment 4 Robert Whitney 2003-08-27 18:58:04 CDT 
Thanks Carlos - I've set the threading model appropriately, and all works fine...

static Server_Strategy_Factory "-ORBConcurrency thread-per-connection"

What's the best way to get the documentation updated to reflect this requirement?

Should I close (resolve) this?
Comment 5 Steve Totten 2003-08-28 09:08:57 CDT 
I've added a note about this to the CosEvent Service chapter of OCI's TAO
Developer's Guide.  It will appear in the next revision due out later this fall.

Thanks!
Steve Totten