You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "jan cwik (JIRA)" <ji...@apache.org> on 2007/12/12 15:02:43 UTC
[jira] Created: (ODE-218) ExchangeListener.exchangeAccepted is not
called
ExchangeListener.exchangeAccepted is not called
-----------------------------------------------
Key: ODE-218
URL: https://issues.apache.org/jira/browse/ODE-218
Project: ODE
Issue Type: Bug
Components: JBI Integration
Affects Versions: 1.1
Environment: unix/windows
Reporter: jan cwik
ExchangeListener.exchangeAccepted is not called when response comes back comes back to the bpel's invoke.
The ExchangeListener.exchangeSent is called when bpel's invoke is performed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: BpelEvent.eventContext deprecated and is null for some events
Posted by "Nowakowski, Mateusz" <Ma...@sabre-holdings.com>.
> I noticed that EventContext class is not considered deprecated. It
means
> it would be removed in later version of ODE.
>
> I read in previous emails that the reason is that eventContext cannot
> provide variables which are persistent.
>
> But we are using only in-memory process and we need access to
variables
> to make somehow correlate BPEL events/logs with underlying JBI message
> exchange. Maybe is good decision to do not deprecate EventContext, but
> do not pass it when process is persistent, or change EventContext
class
> name.
>
>
>Which type of information are you looking for that would be in the
context
>and not on the variable? Now the new variable value is supposed to be
set >on
>the event itself if you need it.
My exact situation is that it is not possible to correlate
EventListeners logs with logs from ServiceMix where MessageExchange is
available. The only solution was to put some data into payload and then
put it into variable in ODE. Then use EventContext to get variable data.
But BpelEvent.eventContext is sometimes null and now is deprecated...
The ideal situation would be when EventContext contains underlying JBI
MessageExchange or its properties (especially
JbiConstants.CORRELATION_ID property)
> The second thing I noticed is that BpelEvent.eventContext is null for
> such bpel events:
> ProcessInstanceStartedEvent, ProcessInstanceStateChangeEvent,
> VariableReadEvent, ProcessMessageExchangeEvent, ProcessCompletionEvent
>
> I understand that for example ProcessInstanceStartedEvent there is no
> variables set, but for ProcessMessageExchangeEvent and
> ProcessCompletionEvent should be available.
>
>
>The initial goal of the event context was to give you visibility on
>variable
>modifications within a given scope. Those events aren't associated to
>variables so there's nothing much the context can provide you. What
would
>you use the event context for with these events?
I'm performing transaction flow tracking and I need to correlate
ServiceMix logs and BPEL logs. For ServiceMix I logged always
JbiConstants. CORRELATION_ID, but when I'm entering ODE I don't have
access to this information from BpelEvent.
I use ProcessInstanceStartedEvent as entry point and
ProcessCompletionEvent as end point of transaction in ODE. I can
correlate this two logs using ProcessId and ProcessInstanceId, but it is
impossible for me to correlate ODE logs with ServiceMix logs.
--
Regards
Mateusz Nowakowski
Re: BpelEvent.eventContext deprecated and is null for some events
Posted by Matthieu Riou <ma...@offthelip.org>.
On Dec 13, 2007 6:38 AM, Nowakowski, Mateusz <
Mateusz.Nowakowski@sabre-holdings.com> wrote:
> Hi all
>
> I noticed that EventContext class is not considered deprecated. It means
> it would be removed in later version of ODE.
>
> I read in previous emails that the reason is that eventContext cannot
> provide variables which are persistent.
>
> But we are using only in-memory process and we need access to variables
> to make somehow correlate BPEL events/logs with underlying JBI message
> exchange. Maybe is good decision to do not deprecate EventContext, but
> do not pass it when process is persistent, or change EventContext class
> name.
>
Which type of information are you looking for that would be in the context
and not on the variable? Now the new variable value is supposed to be set on
the event itself if you need it.
------------
>
> The second thing I noticed is that BpelEvent.eventContext is null for
> such bpel events:
> ProcessInstanceStartedEvent, ProcessInstanceStateChangeEvent,
> VariableReadEvent, ProcessMessageExchangeEvent, ProcessCompletionEvent
>
> I understand that for example ProcessInstanceStartedEvent there is no
> variables set, but for ProcessMessageExchangeEvent and
> ProcessCompletionEvent should be available.
>
The initial goal of the event context was to give you visibility on variable
modifications within a given scope. Those events aren't associated to
variables so there's nothing much the context can provide you. What would
you use the event context for with these events?
Thanks,
Matthieu
>
>
> --
> Regards
> Mateusz Nowakowski
>
BpelEvent.eventContext deprecated and is null for some events
Posted by "Nowakowski, Mateusz" <Ma...@sabre-holdings.com>.
Hi all
I noticed that EventContext class is not considered deprecated. It means
it would be removed in later version of ODE.
I read in previous emails that the reason is that eventContext cannot
provide variables which are persistent.
But we are using only in-memory process and we need access to variables
to make somehow correlate BPEL events/logs with underlying JBI message
exchange. Maybe is good decision to do not deprecate EventContext, but
do not pass it when process is persistent, or change EventContext class
name.
------------
The second thing I noticed is that BpelEvent.eventContext is null for
such bpel events:
ProcessInstanceStartedEvent, ProcessInstanceStateChangeEvent,
VariableReadEvent, ProcessMessageExchangeEvent, ProcessCompletionEvent
I understand that for example ProcessInstanceStartedEvent there is no
variables set, but for ProcessMessageExchangeEvent and
ProcessCompletionEvent should be available.
--
Regards
Mateusz Nowakowski
RE: [jira] Commented: (ODE-218) ExchangeListener.exchangeAccepted is not called
Posted by "Cwik, Jan" <Ja...@sabre-holdings.com>.
Hi,
You are right, I switched ODE to asynchronous mode and I got the
exchangeAccepted event. Since it works in asynchronous let's close the
issue.
thanks
jan
-----Original Message-----
From: Guillaume Nodet (JIRA) [mailto:jira@apache.org]
Sent: Tuesday, December 18, 2007 11:20 PM
To: dev@ode.apache.org
Subject: [jira] Commented: (ODE-218) ExchangeListener.exchangeAccepted
is not called
[
https://issues.apache.org/jira/browse/ODE-218?page=com.atlassian.jira.pl
ugin.system.issuetabpanels:comment-tabpanel#action_12552912 ]
Guillaume Nodet commented on ODE-218:
-------------------------------------
Jan, you're talking about a ServiceMix exchangeListener, right ?
These are configured on the JBI container and are not related to ODE
anyhow.
Generally speaking, the Ode JBI component is not tied to ServiceMix at
all, so this must be a ServiceMix specific issue.
I think this issue should be closed and reopened on ServiceMix, though
you should try to give a bit more details about it.
Actually, I think the problem may comes from the fact that in your case,
the exchange is sent synchronously (using sendSync on the
DeliveryChannel), in which case I think you'll never receive the
ExchangeAccepted event.
> ExchangeListener.exchangeAccepted is not called
> -----------------------------------------------
>
> Key: ODE-218
> URL: https://issues.apache.org/jira/browse/ODE-218
> Project: ODE
> Issue Type: Bug
> Components: JBI Integration
> Affects Versions: 1.1
> Environment: unix/windows
> Reporter: jan cwik
>
> ExchangeListener.exchangeAccepted is not called when response comes
back comes back to the bpel's invoke.
> The ExchangeListener.exchangeSent is called when bpel's invoke is
performed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-218) ExchangeListener.exchangeAccepted is
not called
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552912 ]
Guillaume Nodet commented on ODE-218:
-------------------------------------
Jan, you're talking about a ServiceMix exchangeListener, right ?
These are configured on the JBI container and are not related to ODE anyhow.
Generally speaking, the Ode JBI component is not tied to ServiceMix at all, so this must be a ServiceMix specific issue.
I think this issue should be closed and reopened on ServiceMix, though you should try to give a bit more details about it.
Actually, I think the problem may comes from the fact that in your case, the exchange is sent synchronously (using sendSync on the DeliveryChannel), in which case I think you'll never receive the ExchangeAccepted event.
> ExchangeListener.exchangeAccepted is not called
> -----------------------------------------------
>
> Key: ODE-218
> URL: https://issues.apache.org/jira/browse/ODE-218
> Project: ODE
> Issue Type: Bug
> Components: JBI Integration
> Affects Versions: 1.1
> Environment: unix/windows
> Reporter: jan cwik
>
> ExchangeListener.exchangeAccepted is not called when response comes back comes back to the bpel's invoke.
> The ExchangeListener.exchangeSent is called when bpel's invoke is performed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-218) ExchangeListener.exchangeAccepted is
not called
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552894 ]
Alex Boisvert commented on ODE-218:
-----------------------------------
Guillaume, any thoughts on this?
> ExchangeListener.exchangeAccepted is not called
> -----------------------------------------------
>
> Key: ODE-218
> URL: https://issues.apache.org/jira/browse/ODE-218
> Project: ODE
> Issue Type: Bug
> Components: JBI Integration
> Affects Versions: 1.1
> Environment: unix/windows
> Reporter: jan cwik
>
> ExchangeListener.exchangeAccepted is not called when response comes back comes back to the bpel's invoke.
> The ExchangeListener.exchangeSent is called when bpel's invoke is performed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-218) ExchangeListener.exchangeAccepted is not
called
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert resolved ODE-218.
-------------------------------
Resolution: Invalid
Jan Cwik, said on the mailing list,
Hi,
You are right, I switched ODE to asynchronous mode and I got the
exchangeAccepted event. Since it works in asynchronous let's close the
issue.
thanks
jan
> ExchangeListener.exchangeAccepted is not called
> -----------------------------------------------
>
> Key: ODE-218
> URL: https://issues.apache.org/jira/browse/ODE-218
> Project: ODE
> Issue Type: Bug
> Components: JBI Integration
> Affects Versions: 1.1
> Environment: unix/windows
> Reporter: jan cwik
>
> ExchangeListener.exchangeAccepted is not called when response comes back comes back to the bpel's invoke.
> The ExchangeListener.exchangeSent is called when bpel's invoke is performed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.