Skip navigation
Currently Being Moderated

Error in EmailReceiver  and question on timeouts

Aug 9, 2006 3:26 PM

Hello All,

I am trying to implement a workflow that starts off with an EmailReceiver (like what Howard has posted about) to kick off the workflow. So, I use the Email Receiver QPAC as step 1 and I start the workflow by invoking it through the web services (http://hostname:8080/services).

I'm suddenly getting this error and cannot tell from the message where the exact issue is:
----------------------------------------------------------------
java.lang.RuntimeException: Start cannot be greater than end
at com.adobe.workflow.tools.qde.utils.XpathExpressionParser.getSubExpres sion(XpathExpressionParser.java:102)
at com.adobe.workflow.tools.qde.utils.VariableExpressionParser.getSubExp ression(VariableExpressionParser.java:68)
at com.adobe.workflow.tools.qde.utils.ExpressionWrapper.hasSubExpression (ExpressionWrapper.java:163)
at com.adobe.workflow.tools.qde.utils.ExpressionWrapper.setProcessDataBi naryValue(ExpressionWrapper.java:213)
at com.adobe.workflow.qpac.emailreceiver.EmailReceiverService.processEma il(EmailReceiverService.java:271)
at com.adobe.workflow.qpac.emailreceiver.EmailReceiverService.runTask(Em ailReceiverService.java:100)
at com.adobe.workflow.tools.qde.pat.service.PATAbstractPollingServiceEx. execute(PATAbstractPollingServiceEx.java:87)
at com.adobe.workflow.engine.PEUtil.executeAction(PEUtil.java:184)
at com.adobe.workflow.engine.ProcessEngineBMTBean.executeAction(ProcessE ngineBMTBean.java:1457)
at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncExecuteActionComm and(ProcessEngineBMTBean.java:1412)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(S tatelessSessionContainer.java:683)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invo ke(CachedConnectionInterceptor.java:185)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInte rceptor.java:84)
at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxI nterceptorBMT.java:144)
at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:6 2)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(Stat elessSessionInstanceInterceptor.java:72)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor. java:120)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFacto ryFinderInterceptor.java:122)
at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessi onContainer.java:331)
at org.jboss.ejb.Container.invoke(Container.java:723)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalPro xyFactory.java:359)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSes sionProxy.java:83)
at $Proxy276.asyncExecuteActionCommand(Unknown Source)
at com.adobe.workflow.engine.ProcessCommandControllerBean.onMessage(Proc essCommandControllerBean.java:109)
at sun.reflect.GeneratedMethodAccessor301.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(Mess ageDrivenContainer.java:458)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invo ke(CachedConnectionInterceptor.java:185)
at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(Message DrivenInstanceInterceptor.java:62)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInte rceptor.java:84)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxIntercep torCMT.java:315)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(
 
Replies
  • Currently Being Moderated
    Aug 9, 2006 3:37 PM   in reply to (Jennifer_B.)
    Hi
    That looks like a fairly old bug. Are you using the latest version of the EmailReceiver? From SDK 703?
    Howard
    http://www.avoka.com
     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2006 4:53 PM   in reply to (Jennifer_B.)
    Actually, a quick correction to Howard's post. You should use the Email Receiver QPAC from SDK 7.0.4. It was updated in that release.

    Chris
    Adobe Enterprise Developer Support
     
    |
    Mark as:
  • Currently Being Moderated
    Dec 26, 2006 11:37 PM   in reply to (Jennifer_B.)
    I use the same structure too. How can I start the workflow, which starts off with the emailreceiver, through webservice ?
     
    |
    Mark as:
  • Currently Being Moderated
    Jan 1, 2007 3:28 PM   in reply to (Jennifer_B.)
    Hi
    Check these out...
    http://www.adobeforums.com/cgi-bin/webx?128@@.3bbd9fd9
    http://www.adobeforums.com/cgi-bin/webx/.3bbd3104/5

    The example illustrated here uses a slightly different mechanism, but may also be useful...
    http://www.avoka.com/betaqpacs/The%20Folder%20Watch%20Pattern.pdf

    Howard
    http://www.avoka.com
     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)