I’ve just started the AIX install of WebSphere 5.0 base using a response file generated by a Java class. This will be an interesting test… no X, trying again from an xterm. Interesting that silent install requires X connection. I guess it’s using JRE 1.3 without the AWT factored out.
The Sametime Java toolkit seems to be stuck at the 3.0 level. I’d like to see lots of improvements here especially a synchronous wrapper set suitable for exposure as web services.
2003/10/09 07:50:27:440 EDT [ERROR] HttpMethodBase - -I/O failure reading response body
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.io.FilterInputStream.read(FilterInputStream.java:125)
at java.io.PushbackInputStream.read(PushbackInputStream.java:175)
at java.io.FilterInputStream.read(FilterInputStream.java:125)
at org.apache.commons.httpclient.ContentLengthInputStream.read(ContentLengthInputStream.java:167)
at java.io.FilterInputStream.read(FilterInputStream.java:125)
at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:142)
at java.io.FilterInputStream.read(FilterInputStream.java:104)
at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:161)
at org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.java:685)
at org.apache.commons.httpclient.HttpMethodBase.getResponseBodyAsString(HttpMethodBase.java:734)
at asiwko.home.net.SiteCheckerThread.run(GetIp.java:455)
The java comm api works well on 2 Linux boxes but not on a third. While runinng the program to write to the serial port then read back the result I was able to read directly from /dev/ttyS0 the expected results even though the Java program did not. The Java code used the .available() method to get a byte count. It always came back 0. When the .read() method was used, a byte was returned. I guess I’ll have to rewrite the section of code which returns results to take an expected length rather than letting the comm input drive the result size.
I’m using the IBM JDK 1.4.1 on Red Hat 7 and 9. Its a COMPAQ machine with FIFO that has the problem.
setserial returns this:
/dev/ttyS0, UART: 16550A, Port: 0×03f8, IRQ: 4
on the working system and this:
/dev/ttyS0, UART: 16550A, Port: 0×03f8, IRQ: 4
on the non working system. I’ve got IBM JDK 1.3.0 on the working system and 1.4.1 on the non-working system. I do recall upgrading a long time ago from 1.3.0 to 1.3.1 and having the comms fail. I wonder whether the InputStream class ot the comm classes changed between 1.3.0 and 1.4.1.
Got hold of an AIX system to try out WebSphere 5 silent installs. unzip wasn’t there, got it here: http://aixpdslib.seas.ucla.edu/packages/unzip.html and stuck it in /bin.
I tried
\websphere\deploymentmanager\bin\wsadmin -port 8101 -c “$AdminConfig list Server”
on the deployment manager, node agent, jms app server and app server. I got this:
“WASX7022E: Problem running command “$AdminConfig list Server” — exception information: com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration service is not available.”
which is good.
So I’ve got the perfect omlette going, the color is good, the cheese is melting well, the ham and onion are just right. It’s a little runny, but I fold it anyway. All is going well. I flip it and it explodes with a rush of leaky cheese. Oh well, we all know that function’s far more important than form. Mmmm that’s good… what was I saying again?
You can’t earn your way into Heaven, but can you earn your way out of purgatory?
Failover / Replication items:
1. mysql - replication
2. web site - tar / rsync, maybe amanda
3. mail files - ?
4. cron tables - tar / rsync, maybe amanda, maybe cvs
5. DNS condifuration - rsync
6. sendmail configuration - rsync
7. tomcat webapps - tar / rsync / cvs
8. cvs - unknown, rsync?
web site should have DNS failover to remote site
mail server has backup MX already
maybe config files get tarred together?
need to consider hot backup when failover won’t work. think about job to modify NAT forwarding in case of failure.