Re: getting the socket?
Re: getting the socket?
- Subject: Re: getting the socket?
- From: Chuck Hill <email@hidden>
- Date: Wed, 5 Jul 2006 17:19:26 -0700
On Jul 5, 2006, at 3:55 PM, Jaime Magiera wrote:
Hello,
Every once in a while, there will be a crash that leaves my WO app
unable to restart (error: "Cannot bind to address"). Folks on the
Network Programming list suggested the SO_REUSEADDR and
SO_REUSEPORT UNIX commands as methods to avoid this. In Java, that
translates to ServerSocket.setReuseAddress().
I think you are following a dead end there. First you can't easily
get ahold of this. Second, that error probably means that some
remnant of the JVM is still running and has the port. I'd guess that
reusing it, if even possible, will lead to unhappy results.
Is there anything in the WO API for accessing the current socket so
that I might set this value?
You would have to scratch and RTTI pretty hard to get there.
Eventually, I'd like to debug the various code sections to prevent
these types of crashes overall. However, I'm using WO and QTJava,
which can be quirky.
Quirky. Yes, that is one word for it. Can you dump QT and use
something else? I have found QTJava terrible for app stability. I
have even gotten it to seg fault the JVM on a fairly regular basis.
Depending on what you are using it for, moving to AWT is relatively
painless.
Chuck
--
Coming sometime... - an introduction to web applications using
WebObjects and Xcode http://www.global-village.net/wointro
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden