hi again,
John, I'm really desperate - I've given up the RMI and started
experimenting with openwfe's REST interface. everything goes well - I
can log in as admin, launch the workflow and this is it. next thing I
want to do is to connect to the status service (http://localhost:7078)
to check if a workflow item has arrived in the store of my interest
(in this particular case, "Store.alpha"). at this point (having REST
session opened from my client app), either pointing my browser to this
URL or:
URL url = new URL("http://localhost:7078";);
URLConnection c = url.openConnection(); // connect to status
hangs the worklist component completely, cpu usage raises to 100% and
the only way to get the stability back is to kill it with taskmgr.
this DID NOT occur in my previous version of code, which I posted
yesterday using RMI as standalone application. there, having a RMI
session open, the I had no problems with obtaining the engine's status
while a workflow instance was running and the workitem was waiting to
retrieve it from the store.
how this issue can be fixed?
regards,
bart
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OpenWFE users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/openwfe-users?hl=en
-~----------~----~----~----~------~----~------~--~---
