headers
Dirk Olmes (JIRA | 2 Jan 2012 06:19

[mule-jira] Commented: (MULE-4193) HttpsPollingConnector is broken


    [
http://www.mulesoft.org/jira/browse/MULE-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45429#comment-45429
] 

Dirk Olmes commented on MULE-4193:
----------------------------------

3.2.x: http://fisheye.codehaus.org/changelog/mule/?cs=23571

> HttpsPollingConnector is broken
> -------------------------------
>
>                 Key: MULE-4193
>                 URL: http://www.mulesoft.org/jira/browse/MULE-4193
>             Project: Mule
>          Issue Type: Bug
>          Components: Transport: HTTP(S) / Jetty
>    Affects Versions: 2.1.2
>            Reporter: Andrew Perepelytsya
>            Assignee: Dirk Olmes
>            Priority: Major
>             Fix For: 3.2.2
>
>

--

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dirk Olmes (JIRA | 2 Jan 2012 06:19

[mule-jira] Closed: (MULE-4193) HttpsPollingConnector is broken


     [
http://www.mulesoft.org/jira/browse/MULE-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dirk Olmes closed MULE-4193.
----------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Bug Backlog)
                   3.2.2

> HttpsPollingConnector is broken
> -------------------------------
>
>                 Key: MULE-4193
>                 URL: http://www.mulesoft.org/jira/browse/MULE-4193
>             Project: Mule
>          Issue Type: Bug
>          Components: Transport: HTTP(S) / Jetty
>    Affects Versions: 2.1.2
>            Reporter: Andrew Perepelytsya
>            Assignee: Dirk Olmes
>            Priority: Major
>             Fix For: 3.2.2
>
>

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pablo La Greca (JIRA | 2 Jan 2012 17:06

[mule-jira] Created: (MULE-6004) Commit on exception strategy JMS, FILE and FTP are transport are not consuming the message

Commit on exception strategy JMS, FILE and FTP are transport are not consuming the message
------------------------------------------------------------------------------------------

                 Key: MULE-6004
                 URL: http://www.mulesoft.org/jira/browse/MULE-6004
             Project: Mule
          Issue Type: Bug
          Components: Transport: File, Transport: FTP / SFTP, Transport: JMS
    Affects Versions: 3.3 M1
            Reporter: Pablo La Greca
            Assignee: Pablo La Greca
             Fix For: 3.3 M2

When an exception is thrown, and exception strategy has commit configuration, then messages should be
consumed. Currently messages are being rollback.

--

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 4 comments |
headers
Pablo La Greca (JIRA | 2 Jan 2012 17:34

[mule-jira] Commented: (MULE-6004) Commit on exception strategy JMS, FILE and FTP are transport are not consuming the message


    [
http://www.mulesoft.org/jira/browse/MULE-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45441#comment-45441
] 

Pablo La Greca commented on MULE-6004:
--------------------------------------

Configuration like:

{code}
<flow>
  <inbound>
  ...
  <default-exception-strategy>
      <commit-transaction exception-pattern="*"/>
  </deault-exception-strategy>
</flow>
{code}
or 
{code}
<flow>
  <inbound>
  ...
  <catch-exception-strategy/>
</flow>
{code}

Will consume inbound message
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pablo La Greca (JIRA | 2 Jan 2012 17:36

[mule-jira] Commented: (MULE-6004) Commit on exception strategy JMS, FILE and FTP are transport are not consuming the message


    [
http://www.mulesoft.org/jira/browse/MULE-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45442#comment-45442
] 

Pablo La Greca commented on MULE-6004:
--------------------------------------

https://fisheye.codehaus.org/changelog/mule/?cs=23574

> Commit on exception strategy JMS, FILE and FTP are transport are not consuming the message
> ------------------------------------------------------------------------------------------
>
>                 Key: MULE-6004
>                 URL: http://www.mulesoft.org/jira/browse/MULE-6004
>             Project: Mule
>          Issue Type: Bug
>          Components: Transport: File, Transport: FTP / SFTP, Transport: JMS
>    Affects Versions: 3.3 M1
>            Reporter: Pablo La Greca
>            Assignee: Pablo La Greca
>             Fix For: 3.3 M2
>
>
> When an exception is thrown, and exception strategy has commit configuration, then messages should be
consumed. Currently messages are being rollback.

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pablo La Greca (JIRA | 2 Jan 2012 17:36

[mule-jira] Closed: (MULE-6004) Commit on exception strategy JMS, FILE and FTP are transport are not consuming the message


     [
http://www.mulesoft.org/jira/browse/MULE-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pablo La Greca closed MULE-6004.
--------------------------------

    Resolution: Fixed

> Commit on exception strategy JMS, FILE and FTP are transport are not consuming the message
> ------------------------------------------------------------------------------------------
>
>                 Key: MULE-6004
>                 URL: http://www.mulesoft.org/jira/browse/MULE-6004
>             Project: Mule
>          Issue Type: Bug
>          Components: Transport: File, Transport: FTP / SFTP, Transport: JMS
>    Affects Versions: 3.3 M1
>            Reporter: Pablo La Greca
>            Assignee: Pablo La Greca
>            Priority: Critical
>             Fix For: 3.3 M2
>
>
> When an exception is thrown, and exception strategy has commit configuration, then messages should be
consumed. Currently messages are being rollback.

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Feist (JIRA | 2 Jan 2012 17:41

[mule-jira] Commented: (MULE-6004) Commit on exception strategy JMS, FILE and FTP are transport are not consuming the message


    [
http://www.mulesoft.org/jira/browse/MULE-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45443#comment-45443
] 

Daniel Feist commented on MULE-6004:
------------------------------------

Did this affect 3.2?

> Commit on exception strategy JMS, FILE and FTP are transport are not consuming the message
> ------------------------------------------------------------------------------------------
>
>                 Key: MULE-6004
>                 URL: http://www.mulesoft.org/jira/browse/MULE-6004
>             Project: Mule
>          Issue Type: Bug
>          Components: Transport: File, Transport: FTP / SFTP, Transport: JMS
>    Affects Versions: 3.3 M1
>            Reporter: Pablo La Greca
>            Assignee: Pablo La Greca
>            Priority: Critical
>             Fix For: 3.3 M2
>
>
> When an exception is thrown, and exception strategy has commit configuration, then messages should be
consumed. Currently messages are being rollback.

--

-- 
This message is automatically generated by JIRA.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Feist (JIRA | 2 Jan 2012 19:54

[mule-jira] Commented: (MULE-5893) As a user I want to be able to continue processing a message when an error occurs returning the result of processing as a response


    [
http://www.mulesoft.org/jira/browse/MULE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45446#comment-45446
] 

Daniel Feist commented on MULE-5893:
------------------------------------

Can you add a link to the documentation for this please?

> As a user I want to be able to continue processing a message when an error occurs returning the result of
processing as a response
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MULE-5893
>                 URL: http://www.mulesoft.org/jira/browse/MULE-5893
>             Project: Mule
>          Issue Type: New Feature
>          Components: Core: Exception Handling
>            Reporter: Daniel Feist
>            Assignee: Pablo La Greca
>            Priority: Blocker
>             Fix For: 3.3 M1
>
>
> *Uses cases*
> - HTTP inbound endpoint receives a JSON message, process it through flow, if execution is successful
return a JSON response, if execution fails then log current message and return a JSON error response
> *Configuration*
> {code}
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Feist (JIRA | 2 Jan 2012 19:54

[mule-jira] Commented: (MULE-5977) Ensure there is complete documentation on session properties and their behaviour


    [
http://www.mulesoft.org/jira/browse/MULE-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45447#comment-45447
] 

Daniel Feist commented on MULE-5977:
------------------------------------

http://www.mulesoft.org/documentation/display/MULECDEV/Session+Property+Behavior

> Ensure there is complete documentation on session properties and their behaviour
> --------------------------------------------------------------------------------
>
>                 Key: MULE-5977
>                 URL: http://www.mulesoft.org/jira/browse/MULE-5977
>             Project: Mule
>          Issue Type: Sub-task
>          Components: Core: Sessions
>            Reporter: Daniel Feist
>            Assignee: Daniel Feist
>            Priority: Major
>             Fix For: 3.3 M1
>
>

--

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ramiro Rinaudo (JIRA | 3 Jan 2012 00:40

[mule-jira] Commented: (MULE-5986) As a user I want to the ability to rollback current transaction and send a notification about the message at the time of the exception


    [
http://www.mulesoft.org/jira/browse/MULE-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45450#comment-45450
] 

Ramiro Rinaudo commented on MULE-5986:
--------------------------------------

I would love to see a config on how this can be done today, and how it improves with this changes. 

> As a user I want to the ability to rollback current transaction and send a notification about the message at
the time of the exception
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MULE-5986
>                 URL: http://www.mulesoft.org/jira/browse/MULE-5986
>             Project: Mule
>          Issue Type: New Feature
>          Components: Core: Exception Handling, Core: Transactions
>            Reporter: Pablo La Greca
>            Assignee: Pablo La Greca
>            Priority: Critical
>             Fix For: 3.3 M2
>
>
> *Use case* 
> Start execution by reading a record from the database, make a web service call and update same record with
obtained information. If it fails I want to rollback transaction and send a notification to technical
operations team
> *Acceptance Criteria*
(Continue reading)

Permalink | Reply | 0 comments |

Gmane