[prasad]

Hi,

We are seeing this integration error more often. This happens whenever we upload order release information via integration.

Has anyone seen this before? Any recommendations for fixing this?

Thanks,
Prasad.

[james_foran]

Hello Prasad,

See that error quite often in agents. Generally, it will occur when two agents are trying to access the same Java Bean, ie, an Order or Shipment.

After 300 seconds waiting for the Java Bean, OTM will throw this error.

The first place I would be looking at would be the Agents that are triggered when an Order Release is created (agents that listen to the event Order Release - Created). You should really only have one agent listening to this event. If you have two, I would look at consolidating them, or triggering one from the other.

Let me know what you find.

Regards,

James Foran
Toll Solutions
TOLL Group - Logistics and Transport in Australia, Australias Largest Logistics and Transport Provider

[vignaesh1783]

Hi James,

I have a query here, is there any possibility of the same error occuring if there is 2 event (ORDER - CREATED, ORDER - MODIFIED) in a single agent?

Regards,
Vignaesh

[james_foran]

Perhaps.

I would advise you do the following.
1. Ensure AGENT logging is switched on in the System Log.
2. Run the Integration.
3. Search for Starting in the System Log.

This will give you a list of all agents that have been triggered. Find the ones that are effecting the Order.

Generally speaking though, we do our best to no use any MODIFIED events. If you are, there should only be 1 per Domain/Business Object. If you need to trigger additional agents, use Custom Events, and call these from the MODIFIED agent. This will give you much greater control over the order in which agents are executed also.

Sorry, this is a bit of a brain dump, but I hope you can find something in here that helps.

Regards,

[vignaesh1783]

Thanks James