| Title: | DCE Product Information |
| Notice: | Kit Info - See 2.*-4.* |
| Moderator: | TUXEDO::MAZZAFERRO |
| Created: | Fri Jun 26 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2269 |
| Total number of notes: | 10003 |
There seems to be a problem with the context rundown detection with DCE 2.0A (with and without the ECO1) on Digital Unix 4.0a. 1) The client makes threaded calls to the server using the same context handle. 2) The server, performs a pthread_cond_wait inside of the remote routine. This also happens if you make a call to pthread_delay_np as well. 3) If the client exits, then the server never receives the rundown. This worked under DCE 1.3 and Digital Unix 3.2x, as well as DCE 1.1C for Windows NT. Did something change between releases with either the handling of context rundowns or threads? The customer I'm dealing with requires a fix and is holding up deployment of a very critical application, not to mention sales of many Alphas. Also, I noticed that the same problem occurs if you build the IDL file with the trace all option and send the output to the terminal window. If you send the trace output to a file, then you get the context rundown but you don't get the rundown message in the log file. Maybe this is related? If you need the code to reproduce the problem let me know. garry
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2250.1 | TUXEDO::CHUBB | Thu May 15 1997 17:37 | 5 | ||
Yes, please make some code available. You can mail it to
[email protected] if that's convenient. (tarred, compressed,
uuencoded would be fine).
-- brandon
| |||||
| 2250.2 | threads changed | TUXEDO::ZEE | There you go. | Thu May 15 1997 18:49 | 17 |
> This worked under DCE 1.3 and Digital Unix 3.2x, as well as DCE 1.1C for > Windows NT. > > Did something change between releases with either the handling of context > rundowns or threads? Threads changed big time from Digital UNIX V3.2x to V4.0x. In V3.2x, pthreads Draft 4 was pretty much it. In V4.0x, the DECthreads folks implemented the pthreads standard as the default and layered a Draft 4 behavior library over it. However, signal handling changed, so there is a slight chance that an application using pthreads Draft 4 will need to be modified to run on DU V4.0x. I imagine you already know about using "cc -threads" on DU V4.0x or else you probably would have received some compile errors, or are you running an image built on V3.2x? --Roger | |||||
| 2250.3 | used the threads switch | FOUNDR::WOODRUFF | Fri May 16 1997 10:23 | 18 | |
> behavior library over it. However, signal handling changed, so > there is a slight chance that an application using pthreads Draft 4 > will need to be modified to run on DU V4.0x. I imagine you already > know about using "cc -threads" on DU V4.0x or else you probably would > have received some compile errors, or are you running an image built > on V3.2x? yes, used the switch. re: *.-2 i'll send you over the code later today. thanks garry | |||||