[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

1601.0. "XInputArrival - IM window hangs using help" by LAVETA::DICKERSON () Fri Oct 04 1991 13:29

Below is a note posted in the Decwindows conference along with my reply to that
note indicating that we have a customer problem here at the Colorado CSC that is
identical.

Any assistance in troubleshooting direction/solutions to the problem will be
appreciated.

I have a fax of the DECW$SERVER_0_ERROR.LOG that I could send along but I 
hesitate to transcribe it here unless someone requests it (I'm a lousy typist).

Thanks
Doug Dickerson




             <<< BULOVA::DOCD$:[NOTES$LIBRARY]DECWINDOWS.NOTE;1 >>>
                                -< DECWINDOWS >-
================================================================================
Note 1713.0             _XInputArrival information again!                1 reply
COMICS::FISCHER "I'm not from Bushey"                25 lines   4-OCT-1991 03:50
--------------------------------------------------------------------------------
A few months ago, I put a note out asking if anyone knew what 
the internal Xlib error _XInputArrival means. I got no response
other than to submit a QAR. I felt submitting a QAR aty the time
somewhat pointless as I have no reproducer code from the customer.

Anyway, to refresh your memories, the error was from XtOpenDisplay
on VMS v5.4.

_XInputArrival - input buffer pointer not empty during
processing
state:2     flags: 0     stop depth: 0

%SYSTEM-F-BADPARAM, bad parameter value


This happens intermittently. What I really need to know, quite desparately
is what does this error mean? Or is there any way I can find out what this
error means? It doesn't appear in any documentation. Is there an official
channel I can use to get this information? The customer is getting rather
irate saying that surely we MUST be able to give him an answer.


Thanks

Ian 
================================================================================
Note 1713.1             _XInputArrival information again!                 1 of 1
LAVETA::DICKERSON                                    20 lines   4-OCT-1991 11:08
                       -< We have this problem as well >-
--------------------------------------------------------------------------------
We have an identical problem with DECmcc reported by one of our customers.

In addition to the "_XInputArrival - input buffer pointer not empty"
we have also seen "X Toolkit Warning: BadIDChoice - invalid resource id for this
connection".

In the DECW$SERVER_0_ERROR.LOG we see two "MEMMGR/XREALLOC - zero amount is
requested" messages followed by the connection being closed and a "..ddx layer
returns bad status(-1)" and a "..Dispatcher close down connection".

I second your request for some direction in troubleshooting this problem.  I
suspect it is a resource exhaustion or conflict problem.  But, which resource?
How do I find it?  I have fixed the "X Toolkit Warning: BadIDChoice - invalid
resource id for this connection" by blindly boosting BYTLM to a ludicrous 
number.  

Any help is greatly appreciated.

Doug Dickerson

T.RTitleUserPersonal
Name
DateLines
1601.1VERNA::V_GILBERTFri Oct 04 1991 14:039
Although Xlib routines are supposed to be re-entrant, some of them are not.

For V1.2, we have put jackets around several X routines. Since then, we have
not seen XInputArrival error, although we still see XToolkit errors, so we
probably still need to jacket more X calls.

Hope this helps a little.

Verna