theCamel's blog

To trace a java thread from a thread dump to the corresponding thread on Solaris 10, you can find the LWP using pstack by converting the NID (which corresponds to the LWP ID on Solaris) and matching it up in the pstack output, or by finding the TID listed in the pstack output.

For example, I ran a thread dump and I want to trace this thread from the dump:

"ExecuteThread: '2' for queue: 'weblogic.kernel.System'" daemon prio=5 tid=0x00880588 nid=0x35 in Object.wait() [aba7f000..aba7fc30]
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:429)

I was recently setting up a site hosted by bluehost and running drupal.

Before you transfer DNS authority to bluehost, they give you a temporary URL to allow you to get the site up and running and tested before you make it live. The URL is in this format:

http:<IP>/~<username>
or
http://69.89.31.189/~camelrch

I installed Drupal using 'fantastico', which is available from the bluehost control panel. But to get Drupal to recognize this 'test' URL, you have to change two things.

Ever since I set up the forums on this site a few weeks ago, I have been inundated with spam posts on them. I didn't want to require users to register, or answer a question prior to posting, so I installed the spam module. It's not a bad module for a simple implementation, and actually did block the majority of spam-bot posts, but it's not very granular (and understandably so... it walks a fine line of being easy to use and still effective, and does a pretty good job), and it was sort of hit and miss and there were many posts still getting though (even after tuning the custom filters for a few weeks), so I finally found the cure:

Cronolog provides a solution to the age-old problem of tomcat's catalina.out log file not rotating and growing so large that the server must be stopped to deal with it.

First, install cronolog, which can be downloaded from here.

the cronolog command works like this:

cronolog [OPTIONS] logfile-spec

First, I made a few modifications to the nodemanager start/stop scripts:

(on weblogic 8.1)

in startNodeManager.sh, I added a -D tag to be able to easily spot the nodemanager process when doing a 'ps' by adding this line:

----------------------------------------------------------------------------
JAVA_OPTIONS="${JAVA_OPTIONS} -Dnodemanager"
----------------------------------------------------------------------------

and then in the actual java start commands, adding ${JAVA_OPTIONS} to each line that calls nodemanager:

I bought the professional version of Komodo 4, the multi-language Web-Dev IDE. I bought the personal version of 3.5 and actually started using it, so I decided to buy the professional version of 4 while ActiveState was offering me a big discount. I'm happy with it, but I spent a few hundred dollars on it before I realized this:

the Gui builder toolkit (previously present only in the pro version) has been removed from pro 4... and is now available for free here.

This is where the magic happens...

I finally got my CoCo working. After all the adapters and switchboxes and modulators, it just turned out that the TV I drug out of the closet didn't work anymore... So the final (and easy) combination was a simple RCA cable out of the CoCo's "to TV" jack, into an RCA to COAX adapter, and into the COAX input of my TV, and after a very silent power-on (no moving parts) I was greeted with this:

I got a wild hair and have been trying to decide the best way to go about parsing java thread dumps with python. After a few failed attempts, Paul McGuire, author of the pyparsing python module, came to my rescue. Pyparsing is a fairly simple to use (considering what it is doing) parsing module, that makes quick work out of cryptic log files...

I compiled 2 different versions of apache 2.2.4 on Solaris 10 (06/06, on a crappy U10, but...) one using the prefork MPM (compile --with-mpm=prefork) and the other using the worker MPM (compile --with-mpm=worker). Prefork is supposed to generally be better for single or dual cpu systems, and worker is supposed to be generally better for multi-CPU systems. The following are the Apache Bench results run against each build on an old Sun Ultra 10 with a single 440mhz CPU and 512m RAM. The server isn't impressive, but it works for bench-testing the MPMs...