David Brown - Java Projects Journal category

January catchup entry

Fri, 16 Jan 2009 23:00:00 GMT

This entry is post dated to back-fill the gaps in the monthly entries for '08 and '09 (see Dec '08).
I got the big RIF today from First American. In hindsight I knew it was coming and also in hindsight I now see all the extra activities I was doing at the request of the Systems' folks was an effort to justify my position but alas it did not prevail.
In addition to losing the mem sticks and the HDD I was hit with a trojan browser hijacking virus.
This piece-of-crap virus took a week and a lot of effort to rid the machine (local Windows box) of this pestilence.
As a result I have discovered TrendMicro does a poor job of real-time virus catching. I had to resort to TrendMicro hijackthis program to root out the culprits. I also found out the TrendMicro (nor anyother tool) will delete this type of virus. The virus is so nasty as to accomplish some type of unbreakable file permissions. The file permissions are unbreakable at least in terms of Windows tools.
At last I was able to delete the undeletable virus .DLLs by downloading and burning the sysresccd.org bootable Linux CD. The Linux CD boots up and then allows the user to mount the target disk partition and filesystem and viola! the good ol' /bin/rm works like a charm!
As a result I wound up installing Squid to help fend off the browser hijack attacks and if there is anything positive from this nasty virus attack is I am not able to re-direct my unsecured Pebble blog traffic to: http://www.davidwbrown.name/pebble without having to use the 8080 port. Additionally, I have installed ClamAV and if I can get the Samba module to work I will be able to drop TrendMicro.

Catchup entry

Mon, 01 Dec 2008 06:00:00 GMT

This is just a so-called "Catchup" entry since I lost my blog back at the end of the year.
The two original mem sticks in my HP ML 110 went to the weeds including the SCSI disk. The entire disaster was somewhat my fault as attempts to save the disk by installing a new disk and a new OS (CentOS) I inadvertently corrupted some of the partitions on the old disk.
Thankfully, I had made a backup of the blog as an exported .zip file. And, this what I am blogging on now. The only real information lost was the end-of-the-year and the beginning of '09.
It was back-to-back whammies: losing the memory and the HDD and then once I got back-on-my-feet I was hit by a very nasty trojan browser hijacking virus. It took a week and all of my concentration to rid the local Windows box of the worrisome pestilence. Only Windows has this type of problem: not Linux, not Mac, not the topten.org computers, juts Windows.
More on this in the January catchup entry.

Work Journal

Fri, 07 Nov 2008 23:00:00 GMT

Googled for: weblogic.rjvm.PeerGoneException with variations on this theme to no avail.
After talking to: BM I have decided to created a separate local client to test the Context and other possible issues.
I completed the separate test client (LookupEJB) and it is definitely connecting to WL via the input URL and getting the ResearchClerk method needed to execute the PendMoveProcess class. But, no solution to the first bullet above.

Work Journal

Fri, 07 Nov 2008 00:23:00 GMT

Got past the servicing.properties file issues: was using protocol http: instead of: t3: for the url.
Spent too much time creating a pendmove.dbf file but using the query in DBViz I was able to create a readable .dbf file for pendmove. When I read in the .dbf with the task_id I got an exception thrown. PendMove bailed on the getEJBHome lookup of the ResearchClerkHome.JNDI.

Work Journal

Thu, 06 Nov 2008 02:29:00 GMT

This and the last few entries refer to bugzilla: 15982.
Re-installed NB IDE on the Linux box and moved the PendMove project source files to the Linux box.
Successfull in getting the ResearchClerk code working with exposing the method(): updateResubmitPendedOrder().
I deployed the servicing-1.35 on the Linux box and 1.36 on the Windows box but firing up the PendMove 1.0 Swing app does not get past the: pjernigan/password1 login: Communication Exception: http://www.flooddata.com/sevicing-common: No known valid port for: 'Default http:null:-1:10.3.66.104:-1'; No available router to destination.