You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "tadpale (JIRA)" <se...@james.apache.org> on 2010/06/02 17:15:44 UTC
[jira] Created: (JAMES-1013) DO NOT Upgrade camel 2.2.0 to 2.3.0 -
IMPORTENT!!!
DO NOT Upgrade camel 2.2.0 to 2.3.0 - IMPORTENT!!!
--------------------------------------------------
Key: JAMES-1013
URL: https://issues.apache.org/jira/browse/JAMES-1013
Project: JAMES Server
Issue Type: Bug
Components: SpoolManager & Processors
Affects Versions: Trunk
Reporter: tadpale
god save me.
i have been in this trouble for 4 days.
this is a really big problem in camel 2.3.0 through 2.2.0 in James 3 now.
--------------------------------------------------------------------------------------------------
Channel[
Splitter[
on: BeanExpression[
bean:org.apache.james.transport.camel.MatcherSplitter@70fa2904 method: null
] to: Pipeline[
Channel[
choice{when org.apache.james.transport.camel.MatcherMatch@379aff8e: Channel[
org.apache.james.transport.camel.MailetProcessor@20ffe027
]}
], Channel[
choice{when org.apache.james.transport.camel.MailStateEquals@7ed5315d: Pipeline[
Channel[
org.apache.james.transport.camel.DisposeProcessor@4eb8a7ce
], Channel[
Stop
]
], when org.apache.james.transport.camel.MailStateNotEquals@5e9c11b8: Pipeline[
Channel[
BeanProcessor[
bean: mailClaimCheck
]
], Channel[
RecipientList[
BeanExpression[
bean:org.apache.james.transport.camel.JMSRecipientList@584f778e method: null
]
]
], Channel[
Stop
], Channel[
removeProperty(matcher)
], Channel[
removeProperty(onMatchException)
], Channel[
removeProperty(logger)
]
]}
]
] aggregate: UseOriginalAggregationStrategy
]
]
---------------------------------------------------------------------------
see Stop Chanel in MailStateEquals part generated by camel(test with RecipientIsLocal mailet in transport processor in spoolmanager.xml)
it will not kill the current processor complete.
HostIsLocal mailet will always be continue.
i think it is caused by camel 2.3.0's thread lock or some other sync mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-1013) DO NOT Upgrade camel 2.2.0 to 2.3.0 -
IMPORTENT!!!
Posted by "tadpale (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
tadpale updated JAMES-1013:
---------------------------
Description:
god save me.
i have been in this trouble for 4 days.
this is a really big problem in camel 2.3.0 though 2.2.0 in James 3 now.
--------------------------------------------------------------------------------------------------
Channel[
Splitter[
on: BeanExpression[
bean:org.apache.james.transport.camel.MatcherSplitter@70fa2904 method: null
] to: Pipeline[
Channel[
choice{when org.apache.james.transport.camel.MatcherMatch@379aff8e: Channel[
org.apache.james.transport.camel.MailetProcessor@20ffe027
]}
], Channel[
choice{when org.apache.james.transport.camel.MailStateEquals@7ed5315d: Pipeline[
Channel[
org.apache.james.transport.camel.DisposeProcessor@4eb8a7ce
], Channel[
Stop
]
], when org.apache.james.transport.camel.MailStateNotEquals@5e9c11b8: Pipeline[
Channel[
BeanProcessor[
bean: mailClaimCheck
]
], Channel[
RecipientList[
BeanExpression[
bean:org.apache.james.transport.camel.JMSRecipientList@584f778e method: null
]
]
], Channel[
Stop
], Channel[
removeProperty(matcher)
], Channel[
removeProperty(onMatchException)
], Channel[
removeProperty(logger)
]
]}
]
] aggregate: UseOriginalAggregationStrategy
]
]
---------------------------------------------------------------------------
see Stop Chanel in MailStateEquals part generated by camel(test with RecipientIsLocal mailet in transport processor in spoolmanager.xml)
it will not kill the current processor complete.
HostIsLocal mailet will always be continue.
i think it is caused by camel 2.3.0's thread lock or some other sync mechanism.
was:
god save me.
i have been in this trouble for 4 days.
this is a really big problem in camel 2.3.0 through 2.2.0 in James 3 now.
--------------------------------------------------------------------------------------------------
Channel[
Splitter[
on: BeanExpression[
bean:org.apache.james.transport.camel.MatcherSplitter@70fa2904 method: null
] to: Pipeline[
Channel[
choice{when org.apache.james.transport.camel.MatcherMatch@379aff8e: Channel[
org.apache.james.transport.camel.MailetProcessor@20ffe027
]}
], Channel[
choice{when org.apache.james.transport.camel.MailStateEquals@7ed5315d: Pipeline[
Channel[
org.apache.james.transport.camel.DisposeProcessor@4eb8a7ce
], Channel[
Stop
]
], when org.apache.james.transport.camel.MailStateNotEquals@5e9c11b8: Pipeline[
Channel[
BeanProcessor[
bean: mailClaimCheck
]
], Channel[
RecipientList[
BeanExpression[
bean:org.apache.james.transport.camel.JMSRecipientList@584f778e method: null
]
]
], Channel[
Stop
], Channel[
removeProperty(matcher)
], Channel[
removeProperty(onMatchException)
], Channel[
removeProperty(logger)
]
]}
]
] aggregate: UseOriginalAggregationStrategy
]
]
---------------------------------------------------------------------------
see Stop Chanel in MailStateEquals part generated by camel(test with RecipientIsLocal mailet in transport processor in spoolmanager.xml)
it will not kill the current processor complete.
HostIsLocal mailet will always be continue.
i think it is caused by camel 2.3.0's thread lock or some other sync mechanism.
> DO NOT Upgrade camel 2.2.0 to 2.3.0 - IMPORTENT!!!
> --------------------------------------------------
>
> Key: JAMES-1013
> URL: https://issues.apache.org/jira/browse/JAMES-1013
> Project: JAMES Server
> Issue Type: Bug
> Components: SpoolManager & Processors
> Affects Versions: Trunk
> Reporter: tadpale
>
> god save me.
> i have been in this trouble for 4 days.
> this is a really big problem in camel 2.3.0 though 2.2.0 in James 3 now.
> --------------------------------------------------------------------------------------------------
> Channel[
> Splitter[
> on: BeanExpression[
> bean:org.apache.james.transport.camel.MatcherSplitter@70fa2904 method: null
> ] to: Pipeline[
> Channel[
> choice{when org.apache.james.transport.camel.MatcherMatch@379aff8e: Channel[
> org.apache.james.transport.camel.MailetProcessor@20ffe027
> ]}
> ], Channel[
> choice{when org.apache.james.transport.camel.MailStateEquals@7ed5315d: Pipeline[
> Channel[
> org.apache.james.transport.camel.DisposeProcessor@4eb8a7ce
> ], Channel[
> Stop
> ]
> ], when org.apache.james.transport.camel.MailStateNotEquals@5e9c11b8: Pipeline[
> Channel[
> BeanProcessor[
> bean: mailClaimCheck
> ]
> ], Channel[
> RecipientList[
> BeanExpression[
> bean:org.apache.james.transport.camel.JMSRecipientList@584f778e method: null
> ]
> ]
> ], Channel[
> Stop
> ], Channel[
> removeProperty(matcher)
> ], Channel[
> removeProperty(onMatchException)
> ], Channel[
> removeProperty(logger)
> ]
> ]}
> ]
> ] aggregate: UseOriginalAggregationStrategy
> ]
> ]
> ---------------------------------------------------------------------------
> see Stop Chanel in MailStateEquals part generated by camel(test with RecipientIsLocal mailet in transport processor in spoolmanager.xml)
> it will not kill the current processor complete.
> HostIsLocal mailet will always be continue.
> i think it is caused by camel 2.3.0's thread lock or some other sync mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Assigned: (JAMES-1013) DO NOT Upgrade camel 2.2.0 to 2.3.0 -
IMPORTENT!!!
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer reassigned JAMES-1013:
------------------------------------
Assignee: Norman Maurer
> DO NOT Upgrade camel 2.2.0 to 2.3.0 - IMPORTENT!!!
> --------------------------------------------------
>
> Key: JAMES-1013
> URL: https://issues.apache.org/jira/browse/JAMES-1013
> Project: JAMES Server
> Issue Type: Bug
> Components: SpoolManager & Processors
> Affects Versions: Trunk
> Reporter: tadpale
> Assignee: Norman Maurer
>
> god save me.
> i have been in this trouble for 4 days.
> this is a really big problem in camel 2.3.0 though 2.2.0 in James 3 now.
> --------------------------------------------------------------------------------------------------
> Channel[
> Splitter[
> on: BeanExpression[
> bean:org.apache.james.transport.camel.MatcherSplitter@70fa2904 method: null
> ] to: Pipeline[
> Channel[
> choice{when org.apache.james.transport.camel.MatcherMatch@379aff8e: Channel[
> org.apache.james.transport.camel.MailetProcessor@20ffe027
> ]}
> ], Channel[
> choice{when org.apache.james.transport.camel.MailStateEquals@7ed5315d: Pipeline[
> Channel[
> org.apache.james.transport.camel.DisposeProcessor@4eb8a7ce
> ], Channel[
> Stop
> ]
> ], when org.apache.james.transport.camel.MailStateNotEquals@5e9c11b8: Pipeline[
> Channel[
> BeanProcessor[
> bean: mailClaimCheck
> ]
> ], Channel[
> RecipientList[
> BeanExpression[
> bean:org.apache.james.transport.camel.JMSRecipientList@584f778e method: null
> ]
> ]
> ], Channel[
> Stop
> ], Channel[
> removeProperty(matcher)
> ], Channel[
> removeProperty(onMatchException)
> ], Channel[
> removeProperty(logger)
> ]
> ]}
> ]
> ] aggregate: UseOriginalAggregationStrategy
> ]
> ]
> ---------------------------------------------------------------------------
> see Stop Chanel in MailStateEquals part generated by camel(test with RecipientIsLocal mailet in transport processor in spoolmanager.xml)
> it will not kill the current processor complete.
> HostIsLocal mailet will always be continue.
> i think it is caused by camel 2.3.0's thread lock or some other sync mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (JAMES-1013) DO NOT Upgrade camel 2.2.0 to 2.3.0 -
IMPORTENT!!!
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved JAMES-1013.
----------------------------------
Fix Version/s: 3.0-M1
Resolution: Fixed
Upgraded to camel 2.4.0 and specify the aggregationStrategy explicit, because the default has changed. This caused the trouble you noticed before.
See: http://camel.apache.org/camel-230-release.html (Important changes to consider when upgrading)
> DO NOT Upgrade camel 2.2.0 to 2.3.0 - IMPORTENT!!!
> --------------------------------------------------
>
> Key: JAMES-1013
> URL: https://issues.apache.org/jira/browse/JAMES-1013
> Project: JAMES Server
> Issue Type: Bug
> Components: SpoolManager & Processors
> Affects Versions: Trunk
> Reporter: tadpale
> Assignee: Norman Maurer
> Fix For: 3.0-M1
>
>
> god save me.
> i have been in this trouble for 4 days.
> this is a really big problem in camel 2.3.0 though 2.2.0 in James 3 now.
> --------------------------------------------------------------------------------------------------
> Channel[
> Splitter[
> on: BeanExpression[
> bean:org.apache.james.transport.camel.MatcherSplitter@70fa2904 method: null
> ] to: Pipeline[
> Channel[
> choice{when org.apache.james.transport.camel.MatcherMatch@379aff8e: Channel[
> org.apache.james.transport.camel.MailetProcessor@20ffe027
> ]}
> ], Channel[
> choice{when org.apache.james.transport.camel.MailStateEquals@7ed5315d: Pipeline[
> Channel[
> org.apache.james.transport.camel.DisposeProcessor@4eb8a7ce
> ], Channel[
> Stop
> ]
> ], when org.apache.james.transport.camel.MailStateNotEquals@5e9c11b8: Pipeline[
> Channel[
> BeanProcessor[
> bean: mailClaimCheck
> ]
> ], Channel[
> RecipientList[
> BeanExpression[
> bean:org.apache.james.transport.camel.JMSRecipientList@584f778e method: null
> ]
> ]
> ], Channel[
> Stop
> ], Channel[
> removeProperty(matcher)
> ], Channel[
> removeProperty(onMatchException)
> ], Channel[
> removeProperty(logger)
> ]
> ]}
> ]
> ] aggregate: UseOriginalAggregationStrategy
> ]
> ]
> ---------------------------------------------------------------------------
> see Stop Chanel in MailStateEquals part generated by camel(test with RecipientIsLocal mailet in transport processor in spoolmanager.xml)
> it will not kill the current processor complete.
> HostIsLocal mailet will always be continue.
> i think it is caused by camel 2.3.0's thread lock or some other sync mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (JAMES-1013) DO NOT Upgrade camel 2.2.0 to 2.3.0
- IMPORTENT!!!
Posted by "tadpale (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874964#action_12874964 ]
tadpale commented on JAMES-1013:
--------------------------------
i think so
> DO NOT Upgrade camel 2.2.0 to 2.3.0 - IMPORTENT!!!
> --------------------------------------------------
>
> Key: JAMES-1013
> URL: https://issues.apache.org/jira/browse/JAMES-1013
> Project: JAMES Server
> Issue Type: Bug
> Components: SpoolManager & Processors
> Affects Versions: Trunk
> Reporter: tadpale
>
> god save me.
> i have been in this trouble for 4 days.
> this is a really big problem in camel 2.3.0 though 2.2.0 in James 3 now.
> --------------------------------------------------------------------------------------------------
> Channel[
> Splitter[
> on: BeanExpression[
> bean:org.apache.james.transport.camel.MatcherSplitter@70fa2904 method: null
> ] to: Pipeline[
> Channel[
> choice{when org.apache.james.transport.camel.MatcherMatch@379aff8e: Channel[
> org.apache.james.transport.camel.MailetProcessor@20ffe027
> ]}
> ], Channel[
> choice{when org.apache.james.transport.camel.MailStateEquals@7ed5315d: Pipeline[
> Channel[
> org.apache.james.transport.camel.DisposeProcessor@4eb8a7ce
> ], Channel[
> Stop
> ]
> ], when org.apache.james.transport.camel.MailStateNotEquals@5e9c11b8: Pipeline[
> Channel[
> BeanProcessor[
> bean: mailClaimCheck
> ]
> ], Channel[
> RecipientList[
> BeanExpression[
> bean:org.apache.james.transport.camel.JMSRecipientList@584f778e method: null
> ]
> ]
> ], Channel[
> Stop
> ], Channel[
> removeProperty(matcher)
> ], Channel[
> removeProperty(onMatchException)
> ], Channel[
> removeProperty(logger)
> ]
> ]}
> ]
> ] aggregate: UseOriginalAggregationStrategy
> ]
> ]
> ---------------------------------------------------------------------------
> see Stop Chanel in MailStateEquals part generated by camel(test with RecipientIsLocal mailet in transport processor in spoolmanager.xml)
> it will not kill the current processor complete.
> HostIsLocal mailet will always be continue.
> i think it is caused by camel 2.3.0's thread lock or some other sync mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (JAMES-1013) DO NOT Upgrade camel 2.2.0 to 2.3.0
- IMPORTENT!!!
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874676#action_12874676 ]
Norman Maurer commented on JAMES-1013:
--------------------------------------
So you say it only happens with camel 2.3.0 with 2.2.0 everything works ?
> DO NOT Upgrade camel 2.2.0 to 2.3.0 - IMPORTENT!!!
> --------------------------------------------------
>
> Key: JAMES-1013
> URL: https://issues.apache.org/jira/browse/JAMES-1013
> Project: JAMES Server
> Issue Type: Bug
> Components: SpoolManager & Processors
> Affects Versions: Trunk
> Reporter: tadpale
>
> god save me.
> i have been in this trouble for 4 days.
> this is a really big problem in camel 2.3.0 though 2.2.0 in James 3 now.
> --------------------------------------------------------------------------------------------------
> Channel[
> Splitter[
> on: BeanExpression[
> bean:org.apache.james.transport.camel.MatcherSplitter@70fa2904 method: null
> ] to: Pipeline[
> Channel[
> choice{when org.apache.james.transport.camel.MatcherMatch@379aff8e: Channel[
> org.apache.james.transport.camel.MailetProcessor@20ffe027
> ]}
> ], Channel[
> choice{when org.apache.james.transport.camel.MailStateEquals@7ed5315d: Pipeline[
> Channel[
> org.apache.james.transport.camel.DisposeProcessor@4eb8a7ce
> ], Channel[
> Stop
> ]
> ], when org.apache.james.transport.camel.MailStateNotEquals@5e9c11b8: Pipeline[
> Channel[
> BeanProcessor[
> bean: mailClaimCheck
> ]
> ], Channel[
> RecipientList[
> BeanExpression[
> bean:org.apache.james.transport.camel.JMSRecipientList@584f778e method: null
> ]
> ]
> ], Channel[
> Stop
> ], Channel[
> removeProperty(matcher)
> ], Channel[
> removeProperty(onMatchException)
> ], Channel[
> removeProperty(logger)
> ]
> ]}
> ]
> ] aggregate: UseOriginalAggregationStrategy
> ]
> ]
> ---------------------------------------------------------------------------
> see Stop Chanel in MailStateEquals part generated by camel(test with RecipientIsLocal mailet in transport processor in spoolmanager.xml)
> it will not kill the current processor complete.
> HostIsLocal mailet will always be continue.
> i think it is caused by camel 2.3.0's thread lock or some other sync mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (JAMES-1013) DO NOT Upgrade camel 2.2.0 to 2.3.0
- IMPORTENT!!!
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882658#action_12882658 ]
Norman Maurer commented on JAMES-1013:
--------------------------------------
Sorry for the delay.. The issue got lost in my inbox :( Can you give us a bit more info about the "HostIsLocal mailet will always be continue. " ? I mean is the mail just not processed, stuck or what ? Thx
> DO NOT Upgrade camel 2.2.0 to 2.3.0 - IMPORTENT!!!
> --------------------------------------------------
>
> Key: JAMES-1013
> URL: https://issues.apache.org/jira/browse/JAMES-1013
> Project: JAMES Server
> Issue Type: Bug
> Components: SpoolManager & Processors
> Affects Versions: Trunk
> Reporter: tadpale
>
> god save me.
> i have been in this trouble for 4 days.
> this is a really big problem in camel 2.3.0 though 2.2.0 in James 3 now.
> --------------------------------------------------------------------------------------------------
> Channel[
> Splitter[
> on: BeanExpression[
> bean:org.apache.james.transport.camel.MatcherSplitter@70fa2904 method: null
> ] to: Pipeline[
> Channel[
> choice{when org.apache.james.transport.camel.MatcherMatch@379aff8e: Channel[
> org.apache.james.transport.camel.MailetProcessor@20ffe027
> ]}
> ], Channel[
> choice{when org.apache.james.transport.camel.MailStateEquals@7ed5315d: Pipeline[
> Channel[
> org.apache.james.transport.camel.DisposeProcessor@4eb8a7ce
> ], Channel[
> Stop
> ]
> ], when org.apache.james.transport.camel.MailStateNotEquals@5e9c11b8: Pipeline[
> Channel[
> BeanProcessor[
> bean: mailClaimCheck
> ]
> ], Channel[
> RecipientList[
> BeanExpression[
> bean:org.apache.james.transport.camel.JMSRecipientList@584f778e method: null
> ]
> ]
> ], Channel[
> Stop
> ], Channel[
> removeProperty(matcher)
> ], Channel[
> removeProperty(onMatchException)
> ], Channel[
> removeProperty(logger)
> ]
> ]}
> ]
> ] aggregate: UseOriginalAggregationStrategy
> ]
> ]
> ---------------------------------------------------------------------------
> see Stop Chanel in MailStateEquals part generated by camel(test with RecipientIsLocal mailet in transport processor in spoolmanager.xml)
> it will not kill the current processor complete.
> HostIsLocal mailet will always be continue.
> i think it is caused by camel 2.3.0's thread lock or some other sync mechanism.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org