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:17:41 UTC
[jira] Updated: (JAMES-1013) DO NOT Upgrade camel 2.2.0 to 2.3.0 -
IMPORTENT!!!
[ 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