[jira] [Commented] (DISPATCH-1407) Memory leak on link policy denial
[
https://issues.apache.org/jira/browse/DISPATCH-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925174#comment-16925174
]
Chuck Rolke commented on DISPATCH-1407:
---
Router policy also allows controlling clients with a maxSessions limit. This
limit is enforced differently and will not produce a memory leak.
For sessions the limit is negotiated at the AMQP level. The router has no
handlers for denying sessions because it is a protocol violation for the client
to exceed that limit. An AmqpDotnetLite client attempting to open 256 sessions
when the router limit is 2 will see:
```
Exception Amqp.AmqpException: remote channel 2 is above negotiated channel_max
1.
at Amqp.Connection.ThrowIfClosed(String operation)
at Amqp.Connection.AddSession(Session session)
at Amqp.Session..ctor(Connection connection, Begin begin, OnBegin onBegin)
at Amqp.Session..ctor(Connection connection)
at Examples.Interop.SessionHammer.Main(String[] args) in
/home/chug/Downloads/amq-dotnet-2.5.0-core-sdk/examples/Interop.SessionHammer/Interop.SessionHammer.cs:line
54.
```
> Memory leak on link policy denial
> -
>
> Key: DISPATCH-1407
> URL: https://issues.apache.org/jira/browse/DISPATCH-1407
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Policy Engine
>Affects Versions: 1.8.0
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Attachments: A.conf, default.json
>
>
> A router with a simple policy that denies most addresses starts and uses 10M
> bytes of memory. A test client loops 25k times opening a link to a denied
> address over a single connection and session. Now the router uses 276 Mbytes.
> An example policy is
> ```
> [
>["vhost", {
> "hostname": "$default",
> "allowUnknownUser": true,
> "groups" : {
>"$default": {
> "remoteHosts": "*",
> "allowDynamicSource": true,
> "allowAnonymousSender": true,
> "sources": "$management, examples, q1",
> "targets": "$management, examples, q1"
>}
> }
>}]
> ]
> ```
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2100) Switch from CMake to Bazel?
[ https://issues.apache.org/jira/browse/PROTON-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925136#comment-16925136 ] Omer Katz commented on PROTON-2100: --- I'm going to close this for now. I'll move the discussion to the mailing list. > Switch from CMake to Bazel? > --- > > Key: PROTON-2100 > URL: https://issues.apache.org/jira/browse/PROTON-2100 > Project: Qpid Proton > Issue Type: Wish > Components: proton-c >Reporter: Omer Katz >Priority: Major > > Bazel is a modern build system for polygot repositories like qpid-proton. > Using it should simplify how we build and package our bindings and c library. > This issue is an opportunity to discuss if we want to switch and if so, how. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2097) Linkage error when openssl version is too old or new (not sure)
[
https://issues.apache.org/jira/browse/PROTON-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925134#comment-16925134
]
Omer Katz commented on PROTON-2097:
---
I did use a virtualenv out of those pyenv installed pythons.
Same result.
> Linkage error when openssl version is too old or new (not sure)
> ---
>
> Key: PROTON-2097
> URL: https://issues.apache.org/jira/browse/PROTON-2097
> Project: Qpid Proton
> Issue Type: Improvement
> Components: python-binding
>Affects Versions: proton-c-0.29.0
>Reporter: Omer Katz
>Priority: Major
> Fix For: proton-c-0.30.0
>
>
> After successfully building I'm getting the following error when I try to
> import _cproton.
> {code:java}
> undefined symbol: CRYPTO_set_locking_callback{code}
> This is not the behavior I expected.
> The build should fail if this symbol is not present.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-2100) Switch from CMake to Bazel?
[ https://issues.apache.org/jira/browse/PROTON-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omer Katz closed PROTON-2100. - Resolution: Won't Fix > Switch from CMake to Bazel? > --- > > Key: PROTON-2100 > URL: https://issues.apache.org/jira/browse/PROTON-2100 > Project: Qpid Proton > Issue Type: Wish > Components: proton-c >Reporter: Omer Katz >Priority: Major > > Bazel is a modern build system for polygot repositories like qpid-proton. > Using it should simplify how we build and package our bindings and c library. > This issue is an opportunity to discuss if we want to switch and if so, how. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
