3 Replies Latest reply on Sep 9, 2010 5:37 AM by ollo_h

    Configuration

      Hi

       

      I'd like to realize a service with FTP-Gateway e.t.c. I'm using the JBoss ESB 4.7 (JBoss 5.1). Here is my jboss-esb.xml:

       

       

      <?xml version="1.0"?>
      <jbossesb parameterReloadSecs="5"
          xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.2.0.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.2.0.xsd http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.2.0.xsd">
          <providers>
              <ftp-provider hostname="localhost" name="FTP Provider">
                  <ftp-bus busid="ftpChannel">
                      <ftp-message-filter directory="C:\Development\ftp\ftpChannelGatewy"
                          error-delete="false" error-directory="C:\Development\ftp\ftpChannel\error"
                          error-suffix=".HAS_ERROR" input-suffix=".txt" passive="false"
                          password="my_password" post-delete="false"
                          post-directory="C:\Development\ftp\ftpChannel\finished"
                          post-rename="true" post-suffix=".COMPLETE" username="my_username"
                          work-suffix=".PROCESSING" />
                  </ftp-bus>
              </ftp-provider>
              <jms-provider connection-factory="ConnectionFactory"
                  name="JBossMQ">
                  <jms-bus busid="jmsChannel">
                      <jms-message-filter dest-name="queue/ftpChanelEsb"
                          dest-type="QUEUE" />
                  </jms-bus>
              </jms-provider>
          </providers>
          <services>
              <service category="poller"
                  description=" abc ... "
                  name="FTP Service">
                  <listeners>
                      <ftp-listener busidref="ftpChannel" is-gateway="true"
                          name="FTPGateway" maxThreads="3" schedule-frequency="30" />
                      <jms-listener busidref="jmsChannel" name="JBoss MQ Listener">
                          <jms-message-filter dest-name="queue/ftpChanelEsb"
                              dest-type="QUEUE" />
                      </jms-listener>
                  </listeners>
                  <actions mep="OneWay">
                      <action class="ch.suj.esb.ESBMessageHandler" name="MyFTPAction">
                          <property name="MyFTPAction is starting ... "></property>
                      </action>
                  </actions>
              </service>
          </services>
      </jbossesb>

       

      Ich I try to deploy this project, I have the following error:

       

      11:02:15,053 INFO  [EsbDeployment] Destroying 'FtpShedulerESB.esb'
      11:02:15,059 WARN  [HDScanner] Failed to process changes
      org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

       

      DEPLOYMENTS IN ERROR:
        Deployment "jboss.esb.vfsfile:/C:/Users/admin/jee_workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server1263392451376/deploy/FtpShedulerESB.esb/" is in error due to the following reason(s): org.jboss.soa.esb.ConfigurationException: Local FTP directory 'C:\tmp' doesn't exist.  Check your JBossESB config 'transports:org.jboss.soa.esb.ftp.localdir'

       

          at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
          at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
          at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
          at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
          at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369)
          at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
          at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
          at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
          at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
          at java.lang.Thread.run(Unknown Source)

       

      What ist here wrong? If I create the C:\temp directory, it doesn't change anything.

       

      Thanks.

        • 1. Re: Configuration
          nl

          Try creating the directory c:\tmp as it is said in the exception. Not c:\temp.

           

          Regards,

           

          Niels

          • 2. Re: Configuration
            garuda

            Hello,

             

            this configuration can be found in ../deploy/jbossesb.sar/jbossesb-properties.xml

             

            <properties name="transports" depends="core">

                  ...

                    <property value="/tmp"/>
                   ...
                 </properties>

             

            If you don't want to create this temp directory everytime you Install JBoss is installed, just change jboss-esb.sar in your JBOSS Installation package.

             

            <properties name="transports" depends="core">

                  ...

                    <property name="org.jboss.soa.esb.ftp.localdir" value="${jboss.server.home.dir}/tmp"/>
                  ...
                </properties>

             

            Br,

             

            Dennis

            • 3. Re: Configuration
              ollo_h

              Works for my installation.

               

              Thanks,

              Oliver