cancel
Showing results for 
Search instead for 
Did you mean: 

Scheduled Job in NWA XAResource.end Exception

Former Member
0 Kudos

Hello,

I´ve developed a scheduled Job you can start in NWA. This job runs >1 hour, searches user defined instances and delete them.

Now, there is a Rollback (triggered from system, NOT triggered by the job), so actions are executed and at the end, all changes are going to be restored.

Why?

I get an error in NWA Developer Log (https: ... /nwa/logs).

What does the XARessource mean? Is this the responsible error?

Can you edit a value in NWA?

There are only two errors thrown, this above one and a common error about the job status as following log-entry.

After this error the Rollback is executed.

Thanks in advance.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Now I`ve got a new indication for this error.

I´ve deveoped a Simple Job with a break in it.


/**

* Message-Driven Bean implementation class for: HelloJob

*

*/

@MessageDriven(activationConfig = {

        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),

        @ActivationConfigProperty(propertyName = "messageSelector", propertyValue = "JobDefinition=\'HelloJob\' AND ApplicationName=\'sample.com/utils~job~hellojob~ear\'") })

public class HelloJob extends MDBJobImplementation {

    /**

     * Default constructor.

     */

    public HelloJob() {

        // TODO Auto-generated constructor stub

    }

    @Override

    public void onJob(JobContext jobContext) throws Exception {

        Logger log = jobContext.getLogger();

       

        JobParameter jp = jobContext.getJobParameter("TSleep");

       

        int time = Integer.valueOf(jp.toString());

       

        log.info("Hello Job 01 exec at " + (new Date()));

       

        Thread.sleep(time * 1000);

        log.info("Hello Job 02 exec at " + (new Date()));

    }

}

Using a sleeptime of 1000 seconds everything is well and no error appears.

Using a sleeptime of 2000 seconds the Error appears again.

The Job Status is "Completed" but for a restart, the Scheduler needs the status "STARTING".

So I think, there is a Timeout reached.

But what timeout is responsible for this error??


Thanks in advance.