[JBoss JIRA] Created: (JBESB-840) FTP Quickstart not deploying properly because it can't pick up the ftp config from quickstart.properties
by Tom Fennelly (JIRA)
FTP Quickstart not deploying properly because it can't pick up the ftp config from quickstart.properties
--------------------------------------------------------------------------------------------------------
Key: JBESB-840
URL: http://jira.jboss.com/jira/browse/JBESB-840
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.2
Tom Fennelly wrote:
> > Hi there.
> >
> > In order to get the FTP helloworld quickstart to deploy, I had to
> > locally modify the following in base-build.xml...
> >
> > <target name="assert-ftp-config">
> > <condition property="quickstart.ftp.config">
> > <and>
> > <isset property="jbossesb.ftp.hostname"/>
> > <isset property="jbossesb.ftp.username"/>
> > <isset property="jbossesb.ftp.password"/>
> > <isset property="jbossesb.ftp.directory"/>
> > </and>
> > </condition>
> > <fail unless="quickstart.ftp.config" message="Please configure
> > ftp properties in quickstart.properties"/>
> > </target>
> > .. to...
> > <target name="assert-ftp-config">
> > <condition property="quickstart.ftp.config">
> > <and>
> > <isset property="quickstart.jbossesb.ftp.hostname"/>
> > <isset property="quickstart.jbossesb.ftp.username"/>
> > <isset property="quickstart.jbossesb.ftp.password"/>
> > <isset property="quickstart.jbossesb.ftp.directory"/>
> > </and>
> > </condition>
> > <fail unless="quickstart.ftp.config" message="Please configure
> > ftp properties in quickstart.properties"/>
> > </target>
> >
> > Anyone any ideas? Kev?
Yes, it has been broken. Create a JIRA and assign it to me, I'll fix
it. It is related to embedding the QSes into the build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Created: (JBESB-831) Add an application ability to remove messages from the DLQ
by Mark Little (JIRA)
Add an application ability to remove messages from the DLQ
----------------------------------------------------------
Key: JBESB-831
URL: http://jira.jboss.com/jira/browse/JBESB-831
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Kurt Stam
Fix For: 5.0
It would be useful for certain applications to be able to remove messages from the DLQ even if they were automatically added by the ESB. For example, suppose that the ESB adds a message to the DLQ because the service was down. The application knows this and most of the time it's fine. However, in some situations (specifically in the async case) it may use the DLQ as a backup to it's own application level retries, e.g., trying to do something else to compensate for the failure to deliver. If this "something else" fails, then the DLQ redelivery is good. If it succeeds, it may not be necessary (or wise) to let the redelivery from the DLQ go ahead.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Created: (JBESB-830) DLQ is used in ServiceInvoker.deliverSync
by Mark Little (JIRA)
DLQ is used in ServiceInvoker.deliverSync
-----------------------------------------
Key: JBESB-830
URL: http://jira.jboss.com/jira/browse/JBESB-830
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Kurt Stam
Fix For: 4.2
I thought it would only kick-in automatically in the case of deliveryAsync. For synchronous we should leave it up to the sender to invoke the DLQ when/if a sync failure error occurs. If it's automatic then it may actually conflict with the application's attempt to do something else at that level. For example, sending a synchronous "debit my current account" message to BankA fails, so the application then decides to send a "debit my savings account" message to BankB, which succeeds. However, later on because we put the first "debit my current account" request into the DLQ and redelivery kicks in, it eventually gets delivered and both accounts are subsequently debited. That sort of inconsistency shouldn't happen in the synchronous case. It can't help but happen in the async case unless the application programmer does something at the application level, and in which case it's out of our domain anyway.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Created: (JBESB-824) Product build bug: leaves out the "scripts" folder when producing jbossesb-rosetta.jar
by Burr Sutter (JIRA)
Product build bug: leaves out the "scripts" folder when producing jbossesb-rosetta.jar
--------------------------------------------------------------------------------------
Key: JBESB-824
URL: http://jira.jboss.com/jira/browse/JBESB-824
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Reporter: Burr Sutter
Assigned To: Mark Little
Priority: Critical
Fix For: 4.2
The current jbossesb-rosetta.jar file "drops" the org\jboss\soa\esb\listeners\gateway\scripts folder from the final distro.
The Groovy gateway uses this script:
rosetta\src\org\jboss\soa\esb\listeners\gateway\scripts\MessageInjectionConsole.groovy
This script should be available to this jboss-esb.xml when using the Groovy "gateway"
<service category="MyGroovy"
name="ACustomService"
description="EPR Description" >
<listeners>
<groovy-listener name="groovy-client" script="MessageInjectionConsole.groovy" is-gateway="true" />
<jms-listener name="ESBListener"
busidref="quickstartEsbChannel"
maxThreads="1"/>
</listeners>
<actions>
<action name="first" class="org.jboss.soa.esb.samples.quickstart.groovygateway.MyBasicAction" process="displayMessage" >
<property name="exceptionMethod" value="exceptionHandler" />
</action>
</actions>
</service>
My workaround for now is to copy that .groovy file into my .esb archive since it is missing from the base product's jars.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months