I have a service whis is processing some data from an ftp listener on jboss esb which works just fine on my local machine, but when i'm deploying it on my test-production server it doesn't run at all, the log says that deplyment went fine, no problems, but then nothing happends, i've increased loggin level for esb classes and i found something like this:
2009-12-04 18:49:57,005 DEBUG [DataCollector] gateway-name= does not match service=JBPMDatabaseInitializer
(yes, empty gateway-name) repeated for all existing services. Any ideas anyone?
configuration:
<providers>
<ftp-provider name="SranDocumentsFTPprovider"
hostname="somehost">
<ftp-bus busid="sranDocumentsFTPChannel">
<ftp-message-filter username="someuser" password="somepassword"
passive="false"
directory="/home/whatever/scanner/inbound"
input-suffix=""
work-suffix=".processing"
post-delete="false"
post-directory="/home/whatever/scanner/processed"
post-suffix=".processed"
error-delete="false"
error-directory="/home/whatever/scanner/error"
error-suffix=".error" />
</ftp-bus>
</ftp-provider>
<jms-provider name="JBossMQ" connection-factory="ConnectionFactory">
<jms-bus busid="sranDocumentJmsChannel">
<jms-message-filter dest-type="QUEUE" dest-name="queue/scan_documents_queue" selector="type='whatever'" />
</jms-bus>
</jms-provider>
</providers>
<services>
<service category="SranerServiceCategory" name="SranerService" description="whatever">
<listeners>
<ftp-listener
name="FtpGateway"
busidref="sranDocumentsFTPChannel"
is-gateway="true"
maxThreads="3"
schedule-frequency="30">
</ftp-listener>
<jms-listener name="SranDocumentsAction" busidref="sranDocumentJmsChannel" />
</listeners>
<actions mep="OneWay">
<action name="ProcessSranDocuments" class="somepackage.ProcessSranedDocument">
<property name="message" value="Starting sran action..." />
</action>
</actions>
</service>
</services>
