WPS – Using esAdmin.sh to unlock the locked messages in the event sequencing queue

Sometimes, WPS event sequencing works not very well, and some messages are locked there and blocked the other messages to continue to process, using the esAdmin.sh to unlock or delete locks

Usage: esAdmin [-h hostname] [-p soapPortNumber] method parameters where hostname=’localhost’ and soapPortNumber=8880 by default.
Available methods are :
listAll
listLocks moduleName
listLocks moduleName componentName
listLocks moduleName componentName methodName
deleteLocks moduleName
unlock lockId

listAll is used to list all locked messages
unlock lockId will be used to unlock one locked messages. lockId can be acquired using listAll command.
deleteLocks is used to delete all lockes related to one module. remember that the application need to be stopped before using deleteLocks. the module name is SCA module name, not application name.

for example: esAdmin.sh deleteLocks moduleName

About this entry

You’re currently reading “WPS – Using esAdmin.sh to unlock the locked messages in the event sequencing queue,” an entry on WebSphere Cloud

Published:: December 21, 2010 / 4:12 PM

Category:: Uncategorized

Tags:

About

I am a guy who worked for IBM for 2 years and now I am working for a telecomunication corporation in Toronto, Ontario. My daily jobs are to administrate WPS/WAS and part of MQ servers. This blog writes down some experience I acquired during my job.

Hope it will be helpful for anyone who also works on WPS/WAS. Welcome your feedback.

karthikeyan 7.27.11 / 8am

you site is very useful
my prayers for you.

i have some questions.

1. when i try to restart or stop websphere in aix using stopServer.sh , sometimes i am unable to
stop it or restart it.
How do i find out what is wrong and why it went wrong ?
How do i restart or stop or start it when some process inside websphere is hanging or locked?
Is there any log files or commands that i should issue to kill the process that is hanging
because of which i am unable to stop or start or restart the application server.

2. if i want to deploy and run java web application directly from eclipse ide
how do i do that ? i see websphere version up to 6 only inside eclipse.
i want to use was 7.

3. when i read an article which says how to connect to was and application and node and other details
i found that ,
“To connect to websphere from java code , use websphere java runtime and not sun java”
while excuting the code mentioned in posts here which uses websphere jar class files.
my question is how do i change the runtime while im inside eclipse ide-inside a mvc project.

PLEASE REPLY TO MY MAIL IF POSSIBLE , PLEASE

WebSphere 7.28.11 / 1pm

Hi Karthikeyan

1. if you can not stop/start the server, check the SystemOut.log file to see what happened. that’s the first step to check.
2. yes, we can deploy and run the java webapplication from eclipse ide, you have to create an server and configure it to point to Websphere Application Server, and then deploy the module to WAs server, note: eclipse and WAS server should be on same server.
3. some unix servers were equiped with java 1.4 or java 1.5. when you work with WAS, you better to use the java application in the directory /IBM/Websphere/AppServer/java/bin

Bjoern Wittke 8.8.11 / 9am

Hi,

do you know, if there’s an API for java running esAdmin commands?

We are using MBeans via AdminService to run wsAdmin commands. I expected finding some samples in an analogous manner but I didn’t find anything by google or IBM Infocenter. Maybe, there’s no API for esAdmin so that we need to run a script on our server started through the java application. But first of all I would prefer an API way.

Kind regards
Bjoern

WebSphere 8.12.11 / 9pm

Hi Bjoern:

I checked the API documents and I did not find the API for esAdmin

Checking esAdmin.sh, we can see the script is calling com.ibm.wbiserver.sequencing.service.management.client.EsAdmin,but I did not find it in the API

you can open an PMR to IBM to see if they can give you some advices.

I found a way to use api call esAdmin functions

after you connect to Webspere process instance using AdminClient, you can call EsServiceManager mbean then execute the functions, for example:

ObjectName queryName=new ObjectName(“WebSphere:type=EsServiceManager,process=server1”)

through this way, you can call the function “deleteLocks” or “unlock”, etc.

Bjoern Wittke 8.15.11 / 8am

thank your very much!

As soon as I have some time, I’m going to implement the call function we need for our requirement.
I’ll give you a feedback then.

Best regards
Bjoern

WebSphere Cloud

WPS – Using esAdmin.sh to unlock the locked messages in the event sequencing queue

About this entry

6 Comments

Leave a reply to WebSphere Cancel reply

Recent Posts

Archives

Categories

About

WebSphere Cloud

WPS – Using esAdmin.sh to unlock the locked messages in the event sequencing queue

Share this:

Related

About this entry

6 Comments

Leave a reply to WebSphere Cancel reply

Recent Posts

Archives

Categories

About

Share this:

Related