Hi, Hans,
Guido's approach works.
This occurs when you've started your WO application in the Java
Virtual Machine (JVM) from within Xcode and then the Xcode instance
that's monitoring it goes away (in your case, you Force Quit it). So
when you restart Xcode and try to restart your app, the original
(still running) instance of your app hijacks your output.
If you happen to have other Java apps running that you don't wish to
kill, you can do a "ps auxwww" command in the terminal, search for
JVM processes running and kill the appropriate ones rather than all
of them. However, use Guido's approach if you're not trying to keep
any other Java processes running.
Regards,
Jerry
On Feb 23, 2006, at 3:17 AM, Guido Neitzer wrote:
On 23.02.2006, at 9:06 Uhr, [EMAIL PROTECTED] wrote:
I had this several times. Something got corrupted deep down in the
system. I don't know what it is or why but I only fixed it by
doing a complete restart of the machine.
Quit Xcode. Open Terminal. Execute "killall java". Restart Xcode.
Have your log output back.
cug
--
PharmaLine, Essen, GERMANY
Software and Database Development
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/jerrywwalker%
40gmail.com
This email sent to [EMAIL PROTECTED]
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
[EMAIL PROTECTED]
203 278-4085 office
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
