Andrew Siwko’s Blog #2

How many cells / nodes / app servers per system? ./WebSphere1, ./WebSphere2 and ./WebSphereN/AppServer1, etc or keep the numbering in the subdirectories? z/OS will have bunches of them and it may make sense to keep the nodes in the directories with the deployment manager or at least grouped together. So, what happens if the node changes cells? It might make more sense to federate in a new cell, clone into the new cell directory and destroy the original.

Why is the backup mail server being used?
Is the backup mail server more susceptible to SPAM?

I had to compress stuff on the AIX box to free up space, but the install seems to be proceeding well…
It took 41 minutes and completed succesfully, now it’s time to federate.

Ended up disabling the mq install for now. Trying to federate to newton for kicks, will redo tomorrow. Oops, I configured the host name wrong. TIme to rerun the install.

(Oct 9, 2003 8:13:20 PM), Setup.product.install, com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1, higherVersionFoundPasses: false
(Oct 9, 2003 8:13:20 PM), Setup.product.install, com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1, defaultEvalResult: false
(Oct 9, 2003 8:13:21 PM), Setup.product.install, com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1, checkOnlyCurrentVersion: true
(Oct 9, 2003 8:13:36 PM), Setup.product.install, com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1, higherVersionFoundPasses: false
(Oct 9, 2003 8:13:36 PM), Setup.product.install, com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1, defaultEvalResult: false
(Oct 9, 2003 8:13:36 PM), Setup.product.install, com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1, checkOnlyCurrentVersion: false
(Oct 9, 2003 8:13:58 PM), Setup.product.install, com.ibm.ws.install.actions.LogMessageAction, msg1, INST0051E: Unable to create user.
(Oct 9, 2003 8:13:58 PM), Setup.product.install, com.ibm.ws.install.actions.LogMessageAction, msg1, INST0058E: The install failed or did not complete due to one or more errors.

FileZilla won’t let me store my password any more. I may have to go back to an older version!

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 java.net.SocketTimeoutException: Read timed out
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.