|
Known Faults
These are faults identified in the release version of WebPublisher Studio. As faults are cleared we'll move them into an archive.
| Fault |
OS Affected: |
Mac OS 10.3 - 10.5 |
Date: |
30/10/2008 |
OPEN |
| Platform: |
Studio V3.2.1 - 4.3.1 |
| Manifestation: |
WebPublisher Studio Server listener goes dead after being quit and rebooted on Macintosh OSX.
Under conditions where a WebPublisher Studio Server running Omnis Studio 3.2.1 and later under Mac OS 10.3-10.5 receives requests the following may occur:
- Omnis Studio crashes the Server unexpectedly.
(Intel Macs only with Omnis Studio 3.2.1 running both Server and Client on a single machine).
The exception generated in the Console log refers to the OpenTransport TCP/IP layer.
- Quitting and rebooting the Server reveals the Administration Service Port is inactive.
- Attempts to reconnect to the server from the Client or a browser on that Port will be unsuccessful.
- Inspecting the Web Error log on the server will reveal an entry for the affected Port:
Web Enabler TCPBind error -3247: "
Web Enabler: Open Transport: Address already in use".
This error is generated when an attempt is made to bind a new listening socket using TCPBind during the boot cycle (these logs can also be read with a text editor and are located in the /logs/weberr folder in the Server directory).
|
| Notes: |
This problem should only affect development work on Macs.
Typically a production WebPublisher Studio server instance should only crash if the entire server collapses (eg. a power outage). If the machine is rebooted then all sockets are automatically released and the server will startup with all ports active. We have no evidence of WebPublisher Studio spontaneously crashing in the Mac or Windows environments.
-
This problem is due to a conflict between Web Enabler and OpenTransport closing open sockets.
- We suspect that running two copies of Omnis Studio on one Macintosh causes this socketing conflict.
- This fault will not stop the Server running once booted. It only occurs after the server quits and reboots.
- All versions of Omnis Studio V4 exhibit the problem on all Macs (PowerPC & Intel).
- The Omnis Studio crashes only seem to occur on Intel Macs (ie. running in Rosetta).
- PowerPC Macs (G3, G4, G5) do not crash but do exhibit the socketing fault after restart.
- The problem can also be produced on Intel Macs (10.4) running Omnis Studio 3.2.1 & 3.3 .
It does not occur on PowerPC Macs running this OS and either Omnis Studio version.
- HTTP requests are less likely to cause the problem but Client sessions always produce the fault. |
| Solution: |
1. If you are running the WebPublisher Studio Client you should quit this instance of Omnis Studio.
2.
Quitting and rebooting the WebPublisher Studio Server will usually release the affected socket.
3. In addition, rebooting the Macintosh will always flush sockets.
4. Alternatively, if you have more than one Service Port assigned you can connect from a different Port using the Client then reactivate the failed Service Port. Your normal Administration Port can then be restored from within the Client. Doing this will avoid having to reboot the Server and also works if the Client is already loaded whilst the Server is restarted.
(Note:
We've written a patch that attempts to close all sockets on exit but, because the Omnis Studio externals don't realise the socket isn't closed, it is usually unable to release them. We've also patched the boot sequence to attempt to clear any open sockets but this suffers the same problem) |
|
Home
