Yes, where/when/how send is being called might be important, thats one
reason why I asked for an example showing the behaviour.
The java reactor does also has a wakeup method to prod the thread
blocked in process() to life, which notes itself to be the only method
you can call at the same time ano
It looks to already be configurable, e.g. you could call the same
method to update the value from the thread running the reactor,
perhaps in the onReactorInit() handler. That said, I'm not sure youd
would normally want to, except maybe to increase it, which is
presumably not what you were thinking
Iiuc, calling anything except wakeup from outside the reactor thread is
forbidden.
Reactor (whole proton-c and proton-j) has no locks to protect against
such use.
The general pattern is to trigger your application from a handler for
'on reactor init' and
add that handler to the reactor before sta
On 26. 02. 16 15.36, Bozo Dragojevic wrote:
> Iiuc, calling anything except wakeup from outside the reactor thread is
> forbidden.
>
> Reactor (whole proton-c and proton-j) has no locks to protect against
> such use.
>
> The general pattern is to trigger your application from a handler for
> 'on re
[
https://issues.apache.org/jira/browse/PROTON-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169197#comment-15169197
]
ASF subversion and git services commented on PROTON-1138:
-
Commit
[
https://issues.apache.org/jira/browse/PROTON-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169588#comment-15169588
]
Ollivier Robert commented on PROTON-1073:
-
I think it can be closed, I managed to
