December 30th, 2005
I have written a multithreaded hash table framework. You can put multiple tasks to do work for you with a simple “put” with a key,Then when it completes you can do a “get” to return the data worked on. The “get” will block until that requested thread is finished working.
Read the rest of this entry »
Posted in Code Examples, Performance, multithreading | No Comments »
December 29th, 2005
Here is a small example of a simple text file reader.
TextFileReader.java
Posted in Code Examples | No Comments »
December 27th, 2005
I recently tried to get a container managed transaction message bean to read from a MQ queue then read from an oracle database. I got an error indicating that I did not have XA Transactions turned on in my MQ queue. Then I dug a little deeper….
Read the rest of this entry »
Posted in J2EE, Performance | No Comments »
December 16th, 2005
I wanted to profile an ATG Dynamo 6.4 app, so I down loaded a 10 day trial version of Optimizeit 6.0, but it only came with instructions for configuring ATG Dynamo 4.5.
So here are the instructions for configuring Optimizeit with ATG Dynamo 6.4
Read the rest of this entry »
Posted in Performance | No Comments »
December 15th, 2005
Earlier in the week I did some testing of MQ with message beans.
This is what I got.
10,000 very small messages of 10 bytes going through 1 queue with persistence turned on takes about 37 seconds.
10,000 large messages of 10,000 bytes through 1 queue with persistence turned on takes about 90 seconds
Technorati Tags: Java, ATG, Performance, Optimizeit , Dynamo
Posted in J2EE, Performance | No Comments »
December 12th, 2005
I used JMSAdmin as my service provider for inserting objects into the queue.
QueueIBMTest.java uses websphere 6.0 as my service provider to insert items in an MQ queue using JMS.
Posted in J2EE | No Comments »
December 12th, 2005
If you have ever tried to get a Message Bean working in Rational Software Development Platform 6.0 and Websphere MQ 5.3, you would know why this tutorial is needed good luck….
As you go through this tutorial there are things to keep in hand
- Queue Manager Name : QM_headley (default on my machine)
- Queue Manager Port :1414 (default)
- Queue name: headleyqueue (created this under QM_headley in MQ explorer )
- File System url : file:/C:/JNDI-Directory/mq
- File System JNDI Connection Factory name : headleyCF
- File System JNDI Queue name : headleyq
- Websphere Provider Connection Factory name: jms/headleyCF
- Websphere Provider Queue name: jms/headleyq
- Listener port name: headleyListener
- Test Java code: QueueTest.java QueuePut.java
Read the rest of this entry »
Posted in J2EE | 1 Comment »
