Article View: borland.public.jbuilder.java.language
Article #14823Re: Console window under NT crashes, what can it be?
From: Rich Wilkman
Date: Wed, 28 Jul 1999 00:00
Date: Wed, 28 Jul 1999 00:00
75 lines
3498 bytes
3498 bytes
Gabriel: Well, the trace is a monitor dump (you can get them from consoles via Shift+F1 if memory serves) telling you that there was a deadlock. What you are supposed to do is try to figure out what two items were locked (unless it's the type where every thread is simply saying "you go first") and relate it to your code. Since I have to guess, I'd start with making sure that nothing from your JDK 1.1 world can be seen (no JFC 1.03 libraries, etc.) on the classpath for your 1.2 app. -Rich Gabriel Lima wrote: > > Hi. > I work in a NT4 environment, and just upgraded from JB2 to JB3. > I have converted an existing project that used swing 1.0.3 to use the > new swing package path with the package migration wizard. > That seemed to work allright, and I can work without problems in the > IDE, use the UI designer and compile the project. > > A problem does however whenever I execute my compiled java apps. > After closing the swing GUI, when I try to close the DOS console window, > > several Java exceptions occur, displaying cryptic messages on stdout. > I would like to know if this is a common problem, if it is specific to > NT, or if it is a local anomaly with my configuration. > Another thing, I suspect that this also happens if I run the application > > with the JDK 1.2.2 outside JBuilder. > Please help, and thanks in advance. > Gabriel > > P.S. I have pasted some of the messages below. > > Waiting to be notified: > "Reference Handler" (0x8efdc0) > sun.awt.PostEventQueue@19E70B8/1A27960: <unowned> > Waiting to be notified: > "SunToolkit.PostEventQueue-0" (0x9ac730) > javax.swing.TimerQueue@19D4950/1AA2850: <unowned> > Waiting to be notified: > "TimerQueue" (0xa0b830) > Registered Monitor Dump: > Invoker change lock: <unowned> > utf8 hash table: <unowned> > JNI pinning lock: <unowned> > JNI global reference lock: <unowned> > BinClass lock: <unowned> > Class linking lock: <unowned> > System class loader lock: <unowned> > Code rewrite lock: <unowned> > Heap lock: <unowned> > Monitor cache lock: owner "Signal dispatcher" (0x8ef560) 1 entry > Thread queue lock: owner "Signal dispatcher" (0x8ef560) 1 entry > Waiting to be notified: > "Thread-0" (0xa861d0) > Monitor registry: owner "Signal dispatcher" (0x8ef560) 1 entry -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rich Wilkman Quality Assurance Manager Borland JBuilder Team If you see something that looks like an opinion up there, it's mine and mine alone. Mail sent to me from the newsgroups won't bounce but will be ignored. If I have time, I'll respond, but you have a better chance if you confine your posts to the newsgroups =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Technical Details
Message-ID:
<379F2205.1C7D1E9@inprise.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<379F9F6A.4900C619@enea.se>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f74b3,c55d5a64addeb59f X-Google-Attributes: gidf74b3,public From: Rich Wilkman <rwilkman@inprise.com> Subject: Re: Console window under NT crashes, what can it be? Date: 1999/07/28 Message-ID: <379F2205.1C7D1E9@inprise.com> X-Deja-AN: 506223526 Content-Transfer-Encoding: 7bit References: <379F9F6A.4900C619@enea.se> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: Another Netscape Collabra Server User Mime-Version: 1.0 Newsgroups: borland.public.jbuilder.java.language