update-webMethods support is working on this. Their initial call is that it is a bug in the API. I’ll post results once I know more.

I also noticed the bizarre behavior of peekEvents function. I’m very glad you reported it to Support, I was about to do it myself.
But I observed something more. I run my program (very similar to yours - see code below) several times. Then my Broker started to crash - every time I called the destroy method, the awbroker process went down. Eventually, whole Broker disappeared! I couldn’t really believe it. The Broker Server was still in place, but Broker itself was gone. Neither WmBrokerAdmin nor broker_status reported its existence. So I created it again and now I’m trying to crash it again.

    cadmin = new BrokerAdminClient("localhost", "broker", null, "admin", "Test Admin Client", null); 

// Get the target client queue’s lock
qlock = cadmin.getClientQueueLock(“test__someTrigger”);

    events = qlock.peekEvents(0, 10, 10000); 

System.out.println(events.length); 

// Release the lock on the queue
boolean flag = qlock.releaseLock();
if (flag != true)
{
System.out.println ("Lock not released: " + flag);
}

    /* Clean up */ 
cadmin.destroy();

webMethods confirmed it was a bug in the API. They are in the process of working on a fix for the 6.1 version but not the 6.0.1 version which was okay for us.

Thanks, Mark.

BTW, I’m hearing great things about JMS and pure-Broker performance for the next release. Supposed to scream!

Mark

I received word from webMethods that Broker 6.1 sp3 has corrected this issue. I have not tested myself.

markg
http://darth.homelinux.net

SP3 solves the problem “Out of Range (221-1730)…”, I tested it. However, there is still an issue with crashing Broker Server. It happens only on Windows platforms. I reported this to webMethods support. They confirmed the bug and started working on it.