7 Replies Latest reply on Mar 3, 2009 5:21 AM by Kevin Conner

    Creating an FTP Provider and Listener for JBPM Callback Serv

    Steve Way Newbie

      Hi There,

      Not sure i am in the correct place, but if not please let me know and I will post elsewhere.
      I am extremely new to JBoss and ESB in particular, however here is my scenario and problem.

      I currently have a JBpm (jPDL) process deployed on the server. I can goto the JBPM-CONSOLE, start a process and signal through the states.

      What I am trying to achieve, is to create an FTP Listener, which when an XML file is placed on the FTP server, will notify the Process to start. I see we can acheieve this using JBpmCallback. With this I will use the BpmProcessor to execute the StartProcessInstanceCommand. All communication is one-way, that is, once and XML file is placed on the FTP server, all that needs to happen is that the FTP Listener will notify the OSOD Process to execute and everything is handled by the process from there. There is no repsonse message (in keeping with loose coupling also as no dependancy exists).

      However, whne i configure the provider and listener in the jbpm.esc\META-INF/jboss-esb.xml, then and exception is thrown by JBoss:


      12:25:10,437 INFO [NamingHelper] JNDI InitialContext properties:{}
      12:25:10,656 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.esb:deployment=jbpm.esb
      State: FAILED
      Reason: java.lang.RuntimeException: org.jboss.soa.esb.listeners.lifecycle.Mana
      gedLifecycleException: Unexpected exception while instantiating managed instance

      I Depend On:
      jboss.jca:service=DataSourceBinding,name=JbpmDS
      jboss.esb:service=JBPMDatabaseInitializer
      jboss.esb:deployment=jbossesb.esb

      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.esb:deployment=jbpm.esb
      State: FAILED
      Reason: java.lang.RuntimeException: org.jboss.soa.esb.listeners.lifecycle.Mana
      gedLifecycleException: Unexpected exception while instantiating managed instance

      I Depend On:
      jboss.jca:service=DataSourceBinding,name=JbpmDS
      jboss.esb:service=JBPMDatabaseInitializer
      jboss.esb:deployment=jbossesb.esb



      I have The following Configuration in the jboss-esb.xml, if this is right or wrong i would really appreciate any inputs from anyone. If what i am trying is not possible then your inputs on that would also be appreciated.:

      <?xml version="1.0"?>
      <jbossesb parameterReloadSecs="5"
       xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd">
       <providers>
       <ftp-provider hostname="XXXXX" name="InfotechFTP">
       <property name="username" value="XXXXX"/>
       <property name="password" value="XXXXX"/>
       <property name="directory" value="/OSOD/LicenceData/In"/>
       <property name="input-suffix" value=".xml"/>
       <ftp-bus busid="007">
       <ftp-message-filter directory="/OSOD/LicenceData/In" error-delete="false" input-suffix=".xml" passive="false" password="bpm" post-delete="false" protocol="ftp" read-only="true"username="bpm"/>
       </ftp-bus>
       </ftp-provider>
       </providers>
       <services>
       <service category="JBPM"
       description="Service which Calls jBPM Process using FTP Trigger" invmScope="GLOBAL" invmTransacted="false" name="FTPTriggerJBPM">
       <listeners>
       <ftp-listener busidref="007" is-gateway="true" maxThreads="2"
       name="InfotechFTP" poll-frequency-seconds="10"/>
       </listeners>
       <actions mep="OneWay">
       <action class="org.jboss.soa.esb.services.jbpm.actions.JBpmCallback" name="callback"/>
       <action class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor" name="createnewlicenseaction">
       <property name="command" value="StartProcessInstanceCommand"/>
       <property name="process-definition-name" value="OSODLicenseProcess"/>
       </action>
       </actions>
       </service>
       </services>
      </jbossesb>


      Many Thanks,

      Steve


        • 1. Re: Creating an FTP Provider and Listener for JBPM Callback
          Kevin Conner Master

          I moved this to the user forum.

          Can you check your logs to see if there was a failure reported earlier? This looks like a summary from the deployer.

          • 2. Re: Creating an FTP Provider and Listener for JBPM Callback
            Steve Way Newbie

            Thanks for the quick response.

            I looked through the trace, and found this is the only excpetion which is thrown:


            14:02:39,514 WARN [ScheduleMapper] Attrubute 'poll-frequency-seconds' is DEPREC
            ATED. Please change your configuration to use 'schedule-frequency'.
            14:02:39,530 INFO [Environment] Hibernate 3.2.4.sp1
            14:02:39,545 INFO [Environment] hibernate.properties not found
            14:02:39,561 INFO [Environment] Bytecode provider name : cglib
            14:02:39,577 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling
            14:02:39,577 INFO [AbstractFileGateway] No value specified for: max-millis-for-
            response - This will be an 'inbound-only' gateway
            14:02:39,592 WARN [ServiceController] Problem starting service jboss.esb:deploy
            ment=jbpm.esb
            java.lang.RuntimeException: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecyc
            leException: Unexpected exception while instantiating managed instance
             at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration
            .java:138)
             at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(J
            Boss4ESBDeployment.java:113)
             at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
            upport.java:289)
             at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
            eanSupport.java:245)
             at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
            sorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:155)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:264)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
             at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
            ler.java:978)
             at $Proxy0.start(Unknown Source)
             at org.jboss.system.ServiceController.start(ServiceController.java:417)
             at org.jboss.system.ServiceController.start(ServiceController.java:435)
             at org.jboss.system.ServiceController.start(ServiceController.java:435)
             at org.jboss.system.ServiceController.start(ServiceController.java:435)
             at org.jboss.system.ServiceController.start(ServiceController.java:435)
             at org.jboss.system.ServiceController.start(ServiceController.java:435)
             at org.jboss.system.ServiceController.start(ServiceController.java:435)
             at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
            sorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:155)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:264)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
             at $Proxy4.start(Unknown Source)
             at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
             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:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:155)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
             at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
            or.java:133)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
             at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
            BeanOperationInterceptor.java:142)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:264)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
             at $Proxy30.start(Unknown Source)
             at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197)
             at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
             at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
             at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
            sorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:155)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
             at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
            or.java:133)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
             at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
            BeanOperationInterceptor.java:142)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:264)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
             at $Proxy9.deploy(Unknown Source)
             at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
            tScanner.java:421)
             at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
            canner.java:634)
             at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
            doScan(AbstractDeploymentScanner.java:263)
             at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
            bstractDeploymentScanner.java:336)
             at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
            upport.java:289)
             at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
            eanSupport.java:245)
             at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
            sorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:155)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:264)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
             at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
            ler.java:978)
             at $Proxy0.start(Unknown Source)
             at org.jboss.system.ServiceController.start(ServiceController.java:417)
             at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
            sorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:155)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:264)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
             at $Proxy4.start(Unknown Source)
             at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
             at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
             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:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:155)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
             at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
            or.java:133)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
             at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
            BeanOperationInterceptor.java:142)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:264)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
             at $Proxy5.deploy(Unknown Source)
             at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
             at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
             at org.jboss.Main.boot(Main.java:200)
             at org.jboss.Main$1.run(Main.java:508)
             at java.lang.Thread.run(Thread.java:595)
            Caused by: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unex
            pected exception while instantiating managed instance
             at org.jboss.soa.esb.listeners.LifecycleUtil.getManagedInstances(Lifecyc
            leUtil.java:158)
             at org.jboss.soa.esb.listeners.LifecycleUtil.getGateways(LifecycleUtil.j
            ava:103)
             at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration
            .java:109)
             ... 114 more
            Caused by: java.lang.reflect.InvocationTargetException
             at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            
             at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
            orAccessorImpl.java:39)
             at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
            onstructorAccessorImpl.java:27)
             at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
             at org.jboss.soa.esb.listeners.LifecycleUtil.getManagedInstances(Lifecyc
            leUtil.java:154)
             ... 116 more
            Caused by: org.jboss.soa.esb.ConfigurationException: org.jboss.soa.esb.util.Remo
            teFileSystemException: org.jboss.soa.esb.ConfigurationException: Local FTP direc
            tory 'C:\tmp' doesn't exist. Check your JBossESB config 'transports:org.jboss.s
            oa.esb.ftp.localdir'
             at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.checkMyParm
            s(RemoteGatewayListener.java:94)
             at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.<init>(Remo
            teGatewayListener.java:64)
             at org.jboss.soa.esb.listeners.gateway.ReadOnlyRemoteGatewayListener.<in
            it>(ReadOnlyRemoteGatewayListener.java:82)
             ... 121 more
            Caused by: org.jboss.soa.esb.util.RemoteFileSystemException: org.jboss.soa.esb.C
            onfigurationException: Local FTP directory 'C:\tmp' doesn't exist. Check your J
            BossESB config 'transports:org.jboss.soa.esb.ftp.localdir'
             at org.jboss.soa.esb.util.RemoteFileSystemFactory.getRemoteFileSystem(Re
            moteFileSystemFactory.java:70)
             at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.checkMyParm
            s(RemoteGatewayListener.java:82)
             ... 123 more
            Caused by: org.jboss.soa.esb.ConfigurationException: Local FTP directory 'C:\tmp
            ' doesn't exist. Check your JBossESB config 'transports:org.jboss.soa.esb.ftp.l
            ocaldir'
             at org.jboss.internal.soa.esb.util.FtpImpl.<init>(FtpImpl.java:166)
             at org.jboss.internal.soa.esb.util.FtpImpl.<init>(FtpImpl.java:112)
             at org.jboss.soa.esb.util.RemoteFileSystemFactory.getRemoteFileSystem(Re
            moteFileSystemFactory.java:62)
             ... 124 more


            I changed the
            poll-frequency-seconds'
            to use
            'schedule-frequency'


            But still no joy.

            Many Thanks,

            Steve

            • 3. Re: Creating an FTP Provider and Listener for JBPM Callback
              Scott Dawson Apprentice

              I think the significant thing in the stacktrace is this:

              Caused by: org.jboss.soa.esb.ConfigurationException: org.jboss.soa.esb.util.Remo
              teFileSystemException: org.jboss.soa.esb.ConfigurationException: Local FTP direc
              tory 'C:\tmp' doesn't exist. Check your JBossESB config 'transports:org.jboss.s
              oa.esb.ftp.localdir'
              



              • 4. Re: Creating an FTP Provider and Listener for JBPM Callback
                Steve Way Newbie

                Can't believe missed that one.

                Many thanks for spotting that. One last question - how can i edit my original post? i have placed host, username and password information on there which needs to be private.

                Many Thanks,

                Steve

                • 5. Re: Creating an FTP Provider and Listener for JBPM Callback
                  Steve Way Newbie

                  I like the principles of ESB but they are starting to slowley drive me crazy! Thanks to your observations above, the jbpm.esb is no longer throwing an exception, however, I can see it connecting to the FTP server, start to process the file (the filename changes to .esbWorking) and then the filename has the extension .ERROR and the process doesn't execute. There is nothing in the logs which seems obvious to me. I even changed the log4j settings to ERROR then nothing is printed to the log. Here is my jboss0-esb.xml file and the log entry with log4j in DEBUG mode below that:


                  <?xml version="1.0"?>
                  <jbossesb parameterReloadSecs="600"
                   xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd"
                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd">
                  
                   <providers>
                  
                  
                   <jms-jca-provider name="CallbackQueue-JMS-Provider" connection-factory="ConnectionFactory">
                   <jms-bus busid="JBPMCallbackBus">
                   <jms-message-filter
                   dest-type="QUEUE"
                   dest-name="queue/JBPMCallbackQueue"
                   />
                   </jms-bus>
                   </jms-jca-provider>
                  
                   <ftp-provider name="FTPprovider" hostname="****" >
                   <ftp-bus busid="FTPChannel" >
                   <ftp-message-filter
                   username="***"
                   password="*****"
                   directory="DataOut/"
                   input-suffix=".xml"
                   passive="false"
                   work-suffix=".esbWorking"
                   post-delete="false"
                   post-suffix=".xml"
                   error-delete="false"
                   error-suffix=".ERROR"
                   />
                   </ftp-bus>
                   </ftp-provider>
                  
                   </providers>
                  
                  
                  
                   <services>
                  
                   <service category="JBossESB-Internal" name="JBpmCallbackService" description="Service which makes Callbacks into jBPM" >
                   <listeners>
                   <jms-listener name="JMS-DCQListener" busidref="JBPMCallbackBus" maxThreads="1"/>
                   </listeners>
                   <actions mep="OneWay">
                   <action name="action" class="org.jboss.soa.esb.services.jbpm.actions.JBpmCallback"/>
                   </actions>
                   </service>
                  
                  
                   <service category="JBossESB-jBPM" name="FTPService" description="Service which makes Callbacks into jBPM" >
                   <listeners>
                   <ftp-listener name="FtpGateway" busidref="FTPChannel" is-gateway="false"/>
                   </listeners>
                   <actions mep="OneWay">
                   <action name="create_new_process_instance" class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor">
                   <property name="command" value="StartProcessInstanceCommand" />
                   <property name="process-definition-name" value="LicenseProcessName"/>
                   </action>
                   </actions>
                   </service>
                   </services>
                  
                  
                  </jbossesb>



                  This entry in the log is repeated about 20 times.


                  2009-03-02 12:39:38,334 DEBUG [org.jbpm.job.executor.JobExecutorThread] obtained lock on jobs: []
                  2009-03-02 12:39:38,334 DEBUG [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[message, tx, scheduler, authentication, persistence, logging]'
                  2009-03-02 12:39:38,334 DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@f0cd6d
                  2009-03-02 12:39:38,334 DEBUG [org.jbpm.persistence.jta.JtaDbPersistenceService] begin user transaction
                  2009-03-02 12:39:38,334 DEBUG [org.jbpm.persistence.db.DbPersistenceService] using current hibernate session
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.jdbc.JDBCContext] successfully registered Synchronization
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.impl.SessionImpl] opened session at timestamp: 5062646080856065
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.jdbc.ConnectionManager] opening JDBC connection
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.SQL]
                  /* named HQL query JobSession.getFirstDueJob */ select
                  top ? job0_.ID_ as ID1_26_,
                  job0_.VERSION_ as VERSION3_26_,
                  job0_.DUEDATE_ as DUEDATE4_26_,
                  job0_.PROCESSINSTANCE_ as PROCESSI5_26_,
                  job0_.TOKEN_ as TOKEN6_26_,
                  job0_.TASKINSTANCE_ as TASKINST7_26_,
                  job0_.ISSUSPENDED_ as ISSUSPEN8_26_,
                  job0_.ISEXCLUSIVE_ as ISEXCLUS9_26_,
                  job0_.LOCKOWNER_ as LOCKOWNER10_26_,
                  job0_.LOCKTIME_ as LOCKTIME11_26_,
                  job0_.EXCEPTION_ as EXCEPTION12_26_,
                  job0_.RETRIES_ as RETRIES13_26_,
                  job0_.NAME_ as NAME14_26_,
                  job0_.REPEAT_ as REPEAT15_26_,
                  job0_.TRANSITIONNAME_ as TRANSIT16_26_,
                  job0_.ACTION_ as ACTION17_26_,
                  job0_.GRAPHELEMENTTYPE_ as GRAPHEL18_26_,
                  job0_.GRAPHELEMENT_ as GRAPHEL19_26_,
                  job0_.NODE_ as NODE20_26_,
                  job0_.CLASS_ as CLASS2_26_
                  from
                  JBPM_JOB job0_
                  where
                  (
                  job0_.LOCKOWNER_ is null
                  or job0_.LOCKOWNER_=?
                  )
                  and job0_.RETRIES_>0
                  and job0_.ISSUSPENDED_<>1
                  order by
                  job0_.DUEDATE_ asc
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open ResultSet (open ResultSets: 0, globally: 0)
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close ResultSet (open ResultSets: 1, globally: 1)
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.jdbc.ConnectionManager] aggressively releasing JDBC connection
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.jdbc.ConnectionManager] releasing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)]
                  2009-03-02 12:39:38,334 DEBUG [org.hibernate.engine.StatefulPersistenceContext] initializing non-lazy collections
                  2009-03-02 12:39:38,334 DEBUG [org.jbpm.JbpmContext] closing jbpmContext org.jbpm.JbpmContext@f0cd6d
                  2009-03-02 12:39:38,334 DEBUG [org.jbpm.svc.Services] closing service 'persistence': org.jbpm.persistence.jta.JtaDbPersistenceService@64f6
                  2009-03-02 12:39:38,334 DEBUG [org.jbpm.persistence.jta.JtaDbPersistenceService] committing user transaction
                  2009-03-02 12:39:38,334 DEBUG [org.jbpm.svc.Services] closing service 'tx': org.jbpm.tx.TxService@1e47f9d



                  Your assistance is much appreciated.

                  Kind regards,

                  Steve

                  • 6. Re: Creating an FTP Provider and Listener for JBPM Callback
                    Kevin Conner Master

                     

                    "mallers" wrote:
                    i have placed host, username and password information on there which needs to be private.

                    Done, let me know if there is anything else that needs to be removed.

                    • 7. Re: Creating an FTP Provider and Listener for JBPM Callback
                      Kevin Conner Master

                      The logs you include above appear to be the job executor scanning for tasks.

                      If your file has been moved to ERROR state then something has gone wrong with the pipeline. From what I can see the FTPService only creates and starts a process, completely within the realm of jBPM, so the obvious questions are
                      - Have you deployed your process definition to jBPM?
                      - Have you tried starting the process through the jBPM console?