Andrew Siwko’s Blog #2

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.

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.

http://www.weeklystandard.com/Content/Public/Articles/000/000/003/220wytlz.asp

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.

I did a silent install of IHS 2.0.42 this morning. A few tweaks to the config and newton’s back on line. I’m trying the base silent install then will do the ND silent install. Scripting global security is the next big thing.

Base install took 24 minutes and installed the 1.3.26 admin service. It added plug-in lines tot he conf but left it the same otherwise.. IHS wouldn’t start:

The Apache service named  reported the following error:
>>> API module structure `ibm_app_server_http_module’ in file C:/WebSphere/AppServer/bin/mod_ibm_app_server_http.dll is garbled - perhaps this is not an Apache module DSO? 

With Kali’s input, I changed the LoadModule line to:

LoadModule was_ap20_module “C:\WebSphere\AppServer/bin/mod_was_ap20_http.dll”

which worked nicely. The last configuration error was in the port directive inserted by the WAS install:

The Apache service named  reported the following error:
>>> Port was replaced with Listen in Apache 2.0 

I removed the Port directive installed by WebSphere and the server started up fine (except the drive’s going nuts). On service stop apache GP faulted whe a memory write error. Interesting. It turns out that the http_plugin.log is full of these:

[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError

So maybe I need to turn the AFPA back on? Yes, that got it going. Here are the lines I uncommented:

#AfpaEnable
#AfpaCache on
AfpaPort  80
#AfpaLogFile “c:/WebSphere/IBMHTTPServer/logs/afpalog” V-ECLF

ND install took just over 28 minutes. netstat shows these ports:

  TCP    newton:8100            newton:0               LISTENING - cell ORB bootstrap
  TCP    newton:8101            newton:0               LISTENING - cell SOAP
  TCP    newton:8109            newton:0               LISTENING - cell discovery
  TCP    newton:8112            newton:0               LISTENING - cell http 2 (admin)
  TCP    newton:8113            newton:0               LISTENING - cell https 2
  TCP    newton:8114            newton:0               LISTENING - cell ORB listener
  TCP    newton:8120            newton:0               LISTENING - app bootstrap
  TCP    newton:8121            newton:0               LISTENING - app SOAP
  TCP    newton:8130            newton:0               LISTENING - app http 1
  TCP    newton:8131            newton:0               LISTENING - app https 1
  TCP    newton:8132            newton:0               LISTENING - app https 2 (admin)
  TCP    newton:8133            newton:0               LISTENING - app https 2

which seems to indicate that the customization worked. So, it’s time to federate. addNode dumps this out:

Usage: addNode cell_host [cell_port] [-conntype ] [-includeapps]
           [-startingport ] [-noagent] [-quiet] [-nowait] [-logfile
           ] [-replacelog] [-trace] [-username ] [-password
           ] [-help]

So it’s off to the infocenter: http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp where we find this writeup:
http://publib.boulder.ibm.com/infocenter/wasinfo/topic/com.ibm.websphere.base.doc/info/aes/ae/rxml_addnode.html?resultof=%22%61%64%64%4e%6f%64%65%22%20%22%61%64%64%6e%6f%64%22%20