Workflows - when exceeding 200 wfl tasks java application crasches

[Former Member]

Hi,

I have a portal web dynpro java application that tries to extract a list of workflow tasks from MDM.

When the number of workflows increases to over 200 the application crasches, due to OutOfMemory error.

In each case the application is running for a few minutes, eating memory and then the entire portal goes down.

I'm not sure if this is an MDM Java API problem, Java Portal memory issue or just a limitation in MDM regarding number of workflow tasks?

Besides the Data manager takes really long time to start up.

Do you have any idea what can be done?

We use MDM 5.5 SP5 patch 2

Example

Using the "old" MDM4j Java API, I get an OutOfMemoryError

Using the new JAVA API, also runs for a long time and currently I get java.lang.IllegalStateException: Previous send not yet complete.

Example code (New API):

public int GetWorkflowTasks() throws CommandException, Exception {
				

RetrieveWorkflowTasksCommand cmd = new RetrieveWorkflowTasksCommand(getConnections());

cmd.setTaskType(WorkflowTask.Type.AVAILABLE);

cmd.setTableId(getTableID("Products"));

cmd.setSession(getUserSessionId());

cmd.execute();

Example code (old API):

Task[] tasksAvailable = catalogWFLOwnerData.GetWorkflowTasks("Products", Task.AVAILABLE);
catalogWFLOwnerData.GetWorkflowTasks("Products", Task.AVAILABLE);

Regards

Olof

[Former Member]

Yes, thank you for your response.

I opened OSS and got the answer to upgrade to latest version of MDM SP06 or MDM 7.1.

Guess there is nothing else I can do.

Regards

Olof

[Former Member]

Hi,

Please open a ticket via the official channel, including all relevant information.

Regards,

Walter