What happened with the simple cli (any exception, or you just didn't see the job stop)? It won't be using a shared database by default, so it's no surprise if you haven't changed the database configuration.
For your original problem, the -stop flag was never supported in Batch 2.0, and you mentioned you had been using 2.0.4, so I would check very carefully that you don't have older versions on the jars on your classpath by mistake.
I invoke the batch process from gui by click of a button .
The Control Moves from Spring Controller-Quartzs Scheduler-then the batch process gets invoked form Quartz -Execute method invokes batch process ,
I am using WebSphere as application server ,
Can any one help me in deriving a solution to stop the batch process through screens(gui).
I was able to see job stopping using the Junit test case .. where job will be stopped after few seconds ..
But when i use a command prompt to stop a job .
I see an Error saying thier is no job running for the joblauncher job1.
As i digged log :
Found that when i run a job using a test case in the job parameter list it shows the job running id and excutes the job ..
But when i use a command prompt in job parmeter is empy ..
is their any changes i have to make to the command so that it can take jobparemeters id ?
I am using the same db which has been used in example.