Action Plug-in Not Working...
I developed an action plug-in which was working when simply deployed as a JAR. I then decided to use the plug-in "Development" tab for continued development of this plug-in. My first issue with the "Development" tab is that clicking the "Delete" button deletes ALL previously developed code (in contrast to, say, allowing you to keep the plug-in contents but removing the plug-in entry from the "Development" tab). The code was restored so this wasn't as painful as it could have been.
The real issue though is that the plug-in was recreated, tested and then deployed under the "Development" tab with no problems. Unfortunately, the server log now shows the following:
WARNING Scheduler Required extensions for Taskcom.my.class.name.action have not arrived in time. Execution discarded.
This message continues to repeat in the server log, apparently indicating a retry on the incident and plug-in execution.
Has anyone ever seen this error message or know what it means? I have searched online but don't seem to be able to find an answer. Thanks...
Dear PTC Support,
please create a support ticket with support archive and (if possible) the plugin in question or at least a detailed description how the different plugin types interact in terms of dependency and we'll look into it.
thanks,
Michael
I can't explain how frustrating this error is.. We have developed numerous plugins for our implementation and we see this issue quite often. We have plugins that depend on other plugins. This may be part of whats causing the problem. If this is a bug can it please get fixed..
Hi Thomas,
The warning message you've encountered may be a minor small bug but is most likely also harmless if the plugin is working as expected.
The reason is that the server periodically evaluates if there are pending incidents to process for each action plugin - this is the "Execution" mentioned in the message - this does not necessarily correspond with an actual call to "execute()" of the plugin itself.
The referenced extension might be missing due to a small bug which caused it to be cleared properly after a testing/deploy cycle.
regards, Michael
