[jira] [Updated] (QPIDJMS-245) Factory connection string in JNDI properties file will be decoded twice resulting to unexpected value

2017-01-03 Thread Allan Li (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Allan Li updated QPIDJMS-245:
-
Description: 
In JmsConnectionFactory.java, line 390 - 391, method parseQuery(queryString)
390   Map map = 
PropertyUtil.parseQuery(this.remoteURI.getQuery());
391   applyURIOptions(map);
Code of line 390 will decode the remoteURI twice, the first time is in 
"this.remoteURI.getQuery();", then in method "PropertyUtil.parseQuery" 
(PropertyUtil.java, line 200), it will be decoded again.
This double-decode will generate wrong value. 
For example, the passed in query string is URL encoded 
"jms.password=lBMflBhWkvVy7zamjCN24tCa%2BHn%2FavVwyRltDI%2Fk8kE%3D". (the 
example is retrieved from a Azure Service Bus SAS key). After the first 
decoding, it gets the right expected value 
"lBMflBhWkvVy7zamjCN24tCa+Hn/avVwyRltDI/k8kE=", but if decoded again, it will 
become "lBMflBhWkvVy7zamjCN24tCa Hn/avVwyRltDI/k8kE=". Basically the '+' is 
decoded to ' '. And this wrong string will be set as connection's password and 
it will fail when connecting to target message server due to wrong password.

Using getRawQuery() instead of getQuery() should fix this issue.

  was:
In JmsConnectionFactory.java, line 390 - 391, method parseQuery(queryString)
390   Map map = 
PropertyUtil.parseQuery(this.remoteURI.getQuery());
391   applyURIOptions(map);
Code of line 390 will decode the remoteURI twice, the first time is via 
"this.remoteURI.getQuery());", then in method "PropertyUtil.parseQuery" 
(PropertyUtil.java, line 200), it will be decode again.
This will generate wrong value. 
For example, the passed in query string is URL encoded 
"jms.password=lBMflBhWkvVy7zamjCN24tCa%2BHn%2FavVwyRltDI%2Fk8kE%3D". (the 
example is retrieved from a Azure Service Bus SAS key). After the first time 
decoding, it gets the right expected value 
"lBMflBhWkvVy7zamjCN24tCa+Hn/avVwyRltDI/k8kE=", but if decoded again, it will 
become "lBMflBhWkvVy7zamjCN24tCa Hn/avVwyRltDI/k8kE=". Basically the '+' is 
decoded to ' '. And this wrong string will be set as password and it will fail 
when connecting to target message server due to wrong password.

Using getRawQuery() instead of getQuery() should fix this issue.


> Factory connection string in JNDI properties file will be decoded twice 
> resulting to unexpected value
> -
>
> Key: QPIDJMS-245
> URL: https://issues.apache.org/jira/browse/QPIDJMS-245
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.11.1
> Environment: Any
>Reporter: Allan Li
>
> In JmsConnectionFactory.java, line 390 - 391, method parseQuery(queryString)
> 390   Map map = 
> PropertyUtil.parseQuery(this.remoteURI.getQuery());
> 391   applyURIOptions(map);
> Code of line 390 will decode the remoteURI twice, the first time is in 
> "this.remoteURI.getQuery();", then in method "PropertyUtil.parseQuery" 
> (PropertyUtil.java, line 200), it will be decoded again.
> This double-decode will generate wrong value. 
> For example, the passed in query string is URL encoded 
> "jms.password=lBMflBhWkvVy7zamjCN24tCa%2BHn%2FavVwyRltDI%2Fk8kE%3D". (the 
> example is retrieved from a Azure Service Bus SAS key). After the first 
> decoding, it gets the right expected value 
> "lBMflBhWkvVy7zamjCN24tCa+Hn/avVwyRltDI/k8kE=", but if decoded again, it will 
> become "lBMflBhWkvVy7zamjCN24tCa Hn/avVwyRltDI/k8kE=". Basically the '+' is 
> decoded to ' '. And this wrong string will be set as connection's password 
> and it will fail when connecting to target message server due to wrong 
> password.
> Using getRawQuery() instead of getQuery() should fix this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDJMS-245) Factory connection string in JNDI properties file will be decoded twice resulting to unexpected value

2017-01-03 Thread Allan Li (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Allan Li updated QPIDJMS-245:
-
Description: 
In JmsConnectionFactory.java, line 390 - 391, method parseQuery(queryString)
390   Map map = 
PropertyUtil.parseQuery(this.remoteURI.getQuery());
391   applyURIOptions(map);
Code of line 390 will decode the remoteURI twice, the first time is via 
"this.remoteURI.getQuery());", then in method "PropertyUtil.parseQuery" 
(PropertyUtil.java, line 200), it will be decode again.
This will generate wrong value. 
For example, the passed in query string is URL encoded 
"jms.password=lBMflBhWkvVy7zamjCN24tCa%2BHn%2FavVwyRltDI%2Fk8kE%3D". (the 
example is retrieved from a Azure Service Bus SAS key). After the first time 
decoding, it gets the right expected value 
"lBMflBhWkvVy7zamjCN24tCa+Hn/avVwyRltDI/k8kE=", but if decoded again, it will 
become "lBMflBhWkvVy7zamjCN24tCa Hn/avVwyRltDI/k8kE=". Basically the '+' is 
decoded to ' '. And this wrong string will be set as password and it will fail 
when connecting to target message server due to wrong password.

Using getRawQuery() instead of getQuery() should fix this issue.

  was:
In JmsConnectionFactory.java, line 390 - 391, method parseQuery(queryString)
390   Map map = 
PropertyUtil.parseQuery(this.remoteURI.getQuery());
391   applyURIOptions(map);
Code of line 390 will decode the remoteURI twice, the first time is via 
"this.remoteURI.getQuery());", then in method "PropertyUtil.parseQuery" 
(PropertyUtil.java, line 200), it will be decode again.
This will generate wrong value. 
For example, the passed in query string is URL encoded 
"jms.password=lBMflBhWkvVy7zamjCN24tCa%2BHn%2FavVwyRltDI%2Fk8kE%3D". (the 
example is retrieved from a Azure Service Bus SAS key). After the first time 
decoding, it gets the right expected value 
"lBMflBhWkvVy7zamjCN24tCa+Hn/avVwyRltDI/k8kE=", but if decoded again, it will 
become "lBMflBhWkvVy7zamjCN24tCa Hn/avVwyRltDI/k8kE=". Basically the '+' is 
decoded to ' '. And this wrong string will be set as password and it will fail 
when connecting to target message server due to wrong password.


> Factory connection string in JNDI properties file will be decoded twice 
> resulting to unexpected value
> -
>
> Key: QPIDJMS-245
> URL: https://issues.apache.org/jira/browse/QPIDJMS-245
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.11.1
> Environment: Any
>Reporter: Allan Li
>
> In JmsConnectionFactory.java, line 390 - 391, method parseQuery(queryString)
> 390   Map map = 
> PropertyUtil.parseQuery(this.remoteURI.getQuery());
> 391   applyURIOptions(map);
> Code of line 390 will decode the remoteURI twice, the first time is via 
> "this.remoteURI.getQuery());", then in method "PropertyUtil.parseQuery" 
> (PropertyUtil.java, line 200), it will be decode again.
> This will generate wrong value. 
> For example, the passed in query string is URL encoded 
> "jms.password=lBMflBhWkvVy7zamjCN24tCa%2BHn%2FavVwyRltDI%2Fk8kE%3D". (the 
> example is retrieved from a Azure Service Bus SAS key). After the first time 
> decoding, it gets the right expected value 
> "lBMflBhWkvVy7zamjCN24tCa+Hn/avVwyRltDI/k8kE=", but if decoded again, it will 
> become "lBMflBhWkvVy7zamjCN24tCa Hn/avVwyRltDI/k8kE=". Basically the '+' is 
> decoded to ' '. And this wrong string will be set as password and it will 
> fail when connecting to target message server due to wrong password.
> Using getRawQuery() instead of getQuery() should fix this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPIDJMS-245) Factory connection string in JNDI properties file will be decoded twice resulting to unexpected value

2017-01-03 Thread Allan Li (JIRA) 
Allan Li created QPIDJMS-245:


 Summary: Factory connection string in JNDI properties file will be 
decoded twice resulting to unexpected value
 Key: QPIDJMS-245
 URL: https://issues.apache.org/jira/browse/QPIDJMS-245
 Project: Qpid JMS
  Issue Type: Bug
  Components: qpid-jms-client
Affects Versions: 0.11.1
 Environment: Any
Reporter: Allan Li


In JmsConnectionFactory.java, line 390 - 391, method parseQuery(queryString)
390   Map map = 
PropertyUtil.parseQuery(this.remoteURI.getQuery());
391   applyURIOptions(map);
Code of line 390 will decode the remoteURI twice, the first time is via 
"this.remoteURI.getQuery());", then in method "PropertyUtil.parseQuery" 
(PropertyUtil.java, line 200), it will be decode again.
This will generate wrong value. 
For example, the passed in query string is URL encoded 
"jms.password=lBMflBhWkvVy7zamjCN24tCa%2BHn%2FavVwyRltDI%2Fk8kE%3D". (the 
example is retrieved from a Azure Service Bus SAS key). After the first time 
decoding, it gets the right expected value 
"lBMflBhWkvVy7zamjCN24tCa+Hn/avVwyRltDI/k8kE=", but if decoded again, it will 
become "lBMflBhWkvVy7zamjCN24tCa Hn/avVwyRltDI/k8kE=". Basically the '+' is 
decoded to ' '. And this wrong string will be set as password and it will fail 
when connecting to target message server due to wrong password.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPIDJMS-243) NPE is reported when failover tries to connect to stopped/not available broker

2017-01-03 Thread Timothy Bish (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved QPIDJMS-243.
--
Resolution: Fixed

> NPE is reported when failover tries to connect to stopped/not available broker
> --
>
> Key: QPIDJMS-243
> URL: https://issues.apache.org/jira/browse/QPIDJMS-243
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.20.0
> Environment: Qpid Broker 7.0.0-SNAPSHOT
>Reporter: Alex Rudyy
>Assignee: Timothy Bish
>Priority: Minor
>
> I see the following log issued on failure attempt to establish connection to 
> a stopped(not available) broker listed in failover URL
> {noformat}
> 2016-12-30 16:42:24,738 [localhost:5672]] - WARN  AmqpProvider
>- Caught problem during update processing: null
> java.lang.NullPointerException
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpConnection.handleResourceClosure(AmqpConnection.java:124)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.closeResource(AmqpAbstractResource.java:151)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:257)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:850)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1800(AmqpProvider.java:93)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider$18.run(AmqpProvider.java:784)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> The exception does not impact client functionality as client seems continue 
> to work as normal. The exception is reported only on trunk. 0.11 client does 
> not have this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDJMS-243) NPE is reported when failover tries to connect to stopped/not available broker

2017-01-03 Thread Timothy Bish (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish updated QPIDJMS-243:
-
Fix Version/s: 0.20.0

> NPE is reported when failover tries to connect to stopped/not available broker
> --
>
> Key: QPIDJMS-243
> URL: https://issues.apache.org/jira/browse/QPIDJMS-243
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.20.0
> Environment: Qpid Broker 7.0.0-SNAPSHOT
>Reporter: Alex Rudyy
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 0.20.0
>
>
> I see the following log issued on failure attempt to establish connection to 
> a stopped(not available) broker listed in failover URL
> {noformat}
> 2016-12-30 16:42:24,738 [localhost:5672]] - WARN  AmqpProvider
>- Caught problem during update processing: null
> java.lang.NullPointerException
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpConnection.handleResourceClosure(AmqpConnection.java:124)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.closeResource(AmqpAbstractResource.java:151)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:257)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:850)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1800(AmqpProvider.java:93)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider$18.run(AmqpProvider.java:784)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> The exception does not impact client functionality as client seems continue 
> to work as normal. The exception is reported only on trunk. 0.11 client does 
> not have this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDJMS-243) NPE is reported when failover tries to connect to stopped/not available broker

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPIDJMS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796377#comment-15796377
 ] 

ASF subversion and git services commented on QPIDJMS-243:
-

Commit 91e1b02ad42fcd734c411cac311fe6da228e1a38 in qpid-jms's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=91e1b02 ]

QPIDJMS-243 Fix potential NPE on close of resource

On close of a not fully initialized connection resource it could
encounter an NPE because the connection session was not created.

> NPE is reported when failover tries to connect to stopped/not available broker
> --
>
> Key: QPIDJMS-243
> URL: https://issues.apache.org/jira/browse/QPIDJMS-243
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.20.0
> Environment: Qpid Broker 7.0.0-SNAPSHOT
>Reporter: Alex Rudyy
>Assignee: Timothy Bish
>Priority: Minor
>
> I see the following log issued on failure attempt to establish connection to 
> a stopped(not available) broker listed in failover URL
> {noformat}
> 2016-12-30 16:42:24,738 [localhost:5672]] - WARN  AmqpProvider
>- Caught problem during update processing: null
> java.lang.NullPointerException
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpConnection.handleResourceClosure(AmqpConnection.java:124)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.closeResource(AmqpAbstractResource.java:151)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:257)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:850)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1800(AmqpProvider.java:93)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider$18.run(AmqpProvider.java:784)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> The exception does not impact client functionality as client seems continue 
> to work as normal. The exception is reported only on trunk. 0.11 client does 
> not have this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPIDJMS-243) NPE is reported when failover tries to connect to stopped/not available broker

2017-01-03 Thread Timothy Bish (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish reassigned QPIDJMS-243:


Assignee: Timothy Bish

> NPE is reported when failover tries to connect to stopped/not available broker
> --
>
> Key: QPIDJMS-243
> URL: https://issues.apache.org/jira/browse/QPIDJMS-243
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.20.0
> Environment: Qpid Broker 7.0.0-SNAPSHOT
>Reporter: Alex Rudyy
>Assignee: Timothy Bish
>Priority: Minor
>
> I see the following log issued on failure attempt to establish connection to 
> a stopped(not available) broker listed in failover URL
> {noformat}
> 2016-12-30 16:42:24,738 [localhost:5672]] - WARN  AmqpProvider
>- Caught problem during update processing: null
> java.lang.NullPointerException
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpConnection.handleResourceClosure(AmqpConnection.java:124)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.closeResource(AmqpAbstractResource.java:151)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:257)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:850)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1800(AmqpProvider.java:93)
>   at 
> org.apache.qpid.jms.provider.amqp.AmqpProvider$18.run(AmqpProvider.java:784)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> The exception does not impact client functionality as client seems continue 
> to work as normal. The exception is reported only on trunk. 0.11 client does 
> not have this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1350) Rearrange source code to clarify library organisation

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796319#comment-15796319
 ] 

ASF subversion and git services commented on PROTON-1350:
-

Commit 16da86ebbe08d64e32408c97cc5016ca458351af in qpid-proton's branch 
refs/heads/go1 from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=16da86e ]

PROTON-1350: Install proton-c core library
- This was missed from the initial PROTON-1350 commit


> Rearrange source code to clarify library organisation
> -
>
> Key: PROTON-1350
> URL: https://issues.apache.org/jira/browse/PROTON-1350
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.16.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1374) 0.16.0 release tasks

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796318#comment-15796318
 ] 

ASF subversion and git services commented on PROTON-1374:
-

Commit 2389a2179e39fd53912a3e28369b1b409d94c996 in qpid-proton's branch 
refs/heads/go1 from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=2389a21 ]

PROTON-1374: update the .so version to 11 on master for 0.17.0


> 0.16.0 release tasks
> 
>
> Key: PROTON-1374
> URL: https://issues.apache.org/jira/browse/PROTON-1374
> Project: Qpid Proton
>  Issue Type: Task
>  Components: release
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.16.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1378) Two reactor final events generated

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796324#comment-15796324
 ] 

ASF subversion and git services commented on PROTON-1378:
-

Commit 673c75e71af00bf56e0e977c46be572144dbb578 in qpid-proton's branch 
refs/heads/go1 from Clifford Jansen
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=673c75e ]

PROTON-1378: only generate a single PN_REACTOR_FINAL in reactor.c


> Two reactor final events generated
> --
>
> Key: PROTON-1378
> URL: https://issues.apache.org/jira/browse/PROTON-1378
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.16.0
>Reporter: Cliff Jansen
>Assignee: Cliff Jansen
> Fix For: 0.17.0
>
>
> pn_reactor_process will insert a second PN_REACTOR_FINAL into the collector 
> in pn_reactor_run.  This is mostly harmless but leaves a reference to the 
> reactor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1375) Compile without warnings under clang 4.0

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796322#comment-15796322
 ] 

ASF subversion and git services commented on PROTON-1375:
-

Commit 79d06f0705a973a00fc66283462fa12ad729a708 in qpid-proton's branch 
refs/heads/go1 from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=79d06f0 ]

PROTON-1375: Don't use default promoted parameter to va_start


> Compile without warnings under clang 4.0
> 
>
> Key: PROTON-1375
> URL: https://issues.apache.org/jira/browse/PROTON-1375
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.16.0
> Environment: Debian Jessie. Install latest clang 4.0 snapshot from 
> http://apt.llvm.org/.
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: 0.17.0
>
>
> The following warnings prevent me from compiling proton-c with clang 4.0 
> snaphot
> # (/) /qpid-proton-fuzz/proton-c/src/tests/object.c:60:16: error: passing an 
> object that undergoes default argument promotion to 'va_start' has undefined 
> behavior
> # (x) 
> /test/qpid-proton/proton-c/bindings/cpp/include/proton/message.hpp:51:11: 
> error: instantiation of function
>   'proton::internal::cached_map proton::scalar>::cached_map' required here, but no definition is
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1376) [C, windows] Release 0.16 build fail - src/protocol.h clobbered

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796323#comment-15796323
 ] 

ASF subversion and git services commented on PROTON-1376:
-

Commit 9377d859b5096dfeb3e00c935610784ecbc3c04f in qpid-proton's branch 
refs/heads/go1 from [~chug]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=9377d85 ]

PROTON-1376: Serialize re-construction of generated files for Windows

Windows builds wrongly regenerate files for libraries qpid-proton and
qpid-proton-core. Regeneration creates file churn that sometimes
breaks builds. This patch introduces a phony dependency so that
the generated file reconstruction does not cause a problem.


> [C, windows] Release 0.16 build fail - src/protocol.h clobbered
> ---
>
> Key: PROTON-1376
> URL: https://issues.apache.org/jira/browse/PROTON-1376
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.16.0
> Environment: Visual Studio 2012, x64
>Reporter: Chuck Rolke
> Fix For: 0.17.0
>
>
> Target generated_c_files builds the src/protocol.h and src/encodings.h files.
> Then projects qpid-proton and qpid-proton-core depend on generated_c_files.
> It appears that generated_c_files as a dependency does not respect existing 
> src/protocol.h and src/encodings.h files and generates them three times in 
> total.
> On a four-core build system the files are created three times but well before 
> other build threads try to use them. On other systems the timing is such that 
> a compilation of codec.c needs protocol.h but it is erased by the third file 
> creation.
> {noformat}
> 2>-- Build started: Project: generated_c_files, Configuration: Debug x64 
> --
> 2>Build started 12/12/2016 4:49:28 PM.
> 2>CustomBuild:
> 2>  Building Custom Rule P:/qpid-proton/proton-c/CMakeLists.txt
> 2>  CMake does not need to re-run because 
> P:\qpid-proton\build\proton-c\CMakeFiles\generate.stamp is up-to-date.
> 2>  Generating src/protocol.h
> 2>  Generating src/encodings.h
> 2>
> 2>Build succeeded.
> 3>-- Build started: Project: qpid-proton, Configuration: Debug x64 --
> 4>-- Build started: Project: qpid-proton-core, Configuration: Debug x64 
> --
> 3>  Building Custom Rule P:/qpid-proton/proton-c/CMakeLists.txt
> 3>  CMake does not need to re-run because 
> P:\qpid-proton\build\proton-c\CMakeFiles\generate.stamp is up-to-date.
> 3>  Generating src/encodings.h
> 3>  Generating src/protocol.h
> 3>ClCompile:
> 3>  object.c
> 3>  list.c
> 3>  map.c
> 3>  string.c
> 3>  iterator.c
> 4>Build started 12/12/2016 4:49:29 PM.
> 3>  record.c
> 3>  log.c
> 3>  util.c
> 3>  error.c
> 3>  buffer.c
> 4>CustomBuild:
> 4>  Building Custom Rule P:/qpid-proton/proton-c/CMakeLists.txt
> 3>  types.c
> 4>  CMake does not need to re-run because 
> P:\qpid-proton\build\proton-c\CMakeFiles\generate.stamp is up-to-date.
> 4>  Generating src/encodings.h
> 3>  framing.c
> 3>  codec.c
> 4>  Generating src/protocol.h
> 3>..\..\proton-c\src\core\codec.c(33): fatal error C1083: Cannot open include 
> file: 'protocol.h': No such file or directory
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1379) Compile without warnings under g++ 7.0

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796325#comment-15796325
 ] 

ASF subversion and git services commented on PROTON-1379:
-

Commit cd6ecc5fd9cc29cd2fa594c59166dd9d432fd4b9 in qpid-proton's branch 
refs/heads/go1 from [~jdanek]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=cd6ecc5 ]

PROTON-1379: [C++ binding] Add #if'd #include 
[closes #92]


> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian testing. GCC nightly build from 
> https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
>  Labels: patch
> Fix For: 0.17.0
>
>
> The following error prevents from compiling the cpp binding with g++ 7.0 
> snaphot
> # (/) /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
> error: 'std::function' has not been declared
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1350) Rearrange source code to clarify library organisation

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796320#comment-15796320
 ] 

ASF subversion and git services commented on PROTON-1350:
-

Commit 16da86ebbe08d64e32408c97cc5016ca458351af in qpid-proton's branch 
refs/heads/go1 from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=16da86e ]

PROTON-1350: Install proton-c core library
- This was missed from the initial PROTON-1350 commit


> Rearrange source code to clarify library organisation
> -
>
> Key: PROTON-1350
> URL: https://issues.apache.org/jira/browse/PROTON-1350
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.16.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1374) 0.16.0 release tasks

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796317#comment-15796317
 ] 

ASF subversion and git services commented on PROTON-1374:
-

Commit a2465276f1e115d8a516b3b725ab57bcc2aed6b2 in qpid-proton's branch 
refs/heads/go1 from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=a246527 ]

PROTON-1374: update versions to 0.17.0-SNAPSHOT on master


> 0.16.0 release tasks
> 
>
> Key: PROTON-1374
> URL: https://issues.apache.org/jira/browse/PROTON-1374
> Project: Qpid Proton
>  Issue Type: Task
>  Components: release
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.16.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (DISPATCH-557) High connection rates cause problems in the Python management agent

2017-01-03 Thread Ganesh Murthy (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DISPATCH-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy resolved DISPATCH-557.

Resolution: Fixed

> High connection rates cause problems in the Python management agent
> ---
>
> Key: DISPATCH-557
> URL: https://issues.apache.org/jira/browse/DISPATCH-557
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.7.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
>Priority: Critical
> Fix For: 0.8.0
>
>
> Since connection entities are the only non-configuration (spontaneously 
> occurring) entities that are still managed by the Python agent, high rates of 
> opening and closing connections causes large CPU overhead in the agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPIDJMS-242) Creation of consumer hangs when connection is in a process of re-establishing by failover

2017-01-03 Thread Timothy Bish (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish reassigned QPIDJMS-242:


Assignee: Timothy Bish

> Creation of consumer hangs when connection is in a process of re-establishing 
> by failover
> -
>
> Key: QPIDJMS-242
> URL: https://issues.apache.org/jira/browse/QPIDJMS-242
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.11.1, 0.20.0
> Environment: Qpid Broker 7.0.0-SNAPSHOT
>Reporter: Alex Rudyy
>Assignee: Timothy Bish
> Attachments: ConsumerCreationHangsOnFailover.java, 
> broker-log.snippet.txt, thread-dump.txt
>
>
> The creation of consumer (Session#createConsumer) hangs if invoked when 
> underlying connection is being re-established by failover process. Even when 
> failover successfully restores the connectivity, the invoked method 
> createConsumer  does not return. I see the following in the stack trace:
> {noformat}
> "main" prio=10 tid=0x7f2524009800 nid=0x3d5d waiting on condition 
> [0x7f252b0e4000]
>java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0x0007ad360b30> (a 
> java.util.concurrent.CountDownLatch$Sync)
>   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>   at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
>   at 
> org.apache.qpid.jms.provider.ProviderFuture.sync(ProviderFuture.java:97)
>   at 
> org.apache.qpid.jms.JmsConnection.createResource(JmsConnection.java:601)
>   at 
> org.apache.qpid.jms.JmsConnection.createResource(JmsConnection.java:590)
>   at 
> org.apache.qpid.jms.JmsMessageConsumer.(JmsMessageConsumer.java:114)
>   at 
> org.apache.qpid.jms.JmsMessageConsumer.(JmsMessageConsumer.java:72)
>   at org.apache.qpid.jms.JmsSession.createConsumer(JmsSession.java:387)
>   at org.apache.qpid.jms.JmsSession.createConsumer(JmsSession.java:375)
>   at org.apache.qpid.jms.JmsSession.createConsumer(JmsSession.java:367)
>   at org.apache.qpid.jms.example.Test2.main(Test2.java:65)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> {noformat}
> The consumer is created successfully on broker side. Broker even sends the 
> messages through.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-602) Add a favicon to the stand-alone router site

2017-01-03 Thread Ernest Allen (JIRA) 
Ernest Allen created DISPATCH-602:
-

 Summary: Add a favicon to the stand-alone router site
 Key: DISPATCH-602
 URL: https://issues.apache.org/jira/browse/DISPATCH-602
 Project: Qpid Dispatch
  Issue Type: New Feature
  Components: Console
Affects Versions: 0.7.0
Reporter: Ernest Allen
Priority: Trivial


When a browser loads a web site it automatically requests the file favicon.ico 
from the site's home dir. If it exists it uses that icon in the browser's 
address bar and in any bookmarks for that site.

Add a 32x32 icon to the stand-alone router's home dir.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (DISPATCH-601) Valgrind errors in dispatch tests

2017-01-03 Thread Ted Ross (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DISPATCH-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross reassigned DISPATCH-601:
-

Assignee: Ted Ross

> Valgrind errors in dispatch tests
> -
>
> Key: DISPATCH-601
> URL: https://issues.apache.org/jira/browse/DISPATCH-601
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Reporter: Alan Conway
>Assignee: Ted Ross
> Fix For: 0.8.0
>
> Attachments: dispatch-valgrind-err.txt
>
>
> There are several valgrind erros appearing in the dispatch tests. Full test 
> output will be attached but the errors are all similar to this:
> {code}
> ==18019== Invalid read of size 1
> ==18019==at 0x4C30CAB: strcpy (vg_replace_strmem.c:506)
> ==18019==by 0x69DDFFD: strcpy (string3.h:110)
> ==18019==by 0x69DDFFD: _sasl_strdup (common.c:183)
> ==18019==by 0x69E55A4: sasl_server_new (server.c:1076)
> ==18019==by 0x50DD88F: pni_init_server (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DC1F8: pni_sasl_start_server_if_needed.part.2 (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DC7BE: pn_output_write_sasl (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DEBBA: process_output_ssl (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DA35C: pn_transport_pending (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x4E6EDA9: connector_process (driver.c:770)
> ==18019==by 0x4E6EC3A: qdpn_connector_process (driver.c:730)
> ==18019==by 0x4E907B3: process_connector (server.c:679)
> ==18019==by 0x4E91321: thread_run (server.c:957)
> ==18019==  Address 0x11be7331 is 1 bytes inside a block of size 17 free'd
> ==18019==at 0x4C2ED4A: free (vg_replace_malloc.c:530)
> ==18019==by 0x50DCA0E: pn_sasl_free (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D58BF: pn_transport_finalize (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50C7BF8: pn_class_decref (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D406F: pn_event_finalize_cast (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50C7BF8: pn_class_decref (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D437C: pn_collector_pop (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D43AE: pn_collector_next (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D440F: pn_collector_release (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D4438: pn_collector_free (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x4E8E6C2: free_qd_connection (server.c:100)
> ==18019==by 0x4E9152B: thread_run (server.c:984)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (DISPATCH-601) Valgrind errors in dispatch tests

2017-01-03 Thread Ted Ross (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DISPATCH-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross updated DISPATCH-601:
--
Fix Version/s: 0.8.0

> Valgrind errors in dispatch tests
> -
>
> Key: DISPATCH-601
> URL: https://issues.apache.org/jira/browse/DISPATCH-601
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Reporter: Alan Conway
> Fix For: 0.8.0
>
> Attachments: dispatch-valgrind-err.txt
>
>
> There are several valgrind erros appearing in the dispatch tests. Full test 
> output will be attached but the errors are all similar to this:
> {code}
> ==18019== Invalid read of size 1
> ==18019==at 0x4C30CAB: strcpy (vg_replace_strmem.c:506)
> ==18019==by 0x69DDFFD: strcpy (string3.h:110)
> ==18019==by 0x69DDFFD: _sasl_strdup (common.c:183)
> ==18019==by 0x69E55A4: sasl_server_new (server.c:1076)
> ==18019==by 0x50DD88F: pni_init_server (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DC1F8: pni_sasl_start_server_if_needed.part.2 (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DC7BE: pn_output_write_sasl (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DEBBA: process_output_ssl (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DA35C: pn_transport_pending (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x4E6EDA9: connector_process (driver.c:770)
> ==18019==by 0x4E6EC3A: qdpn_connector_process (driver.c:730)
> ==18019==by 0x4E907B3: process_connector (server.c:679)
> ==18019==by 0x4E91321: thread_run (server.c:957)
> ==18019==  Address 0x11be7331 is 1 bytes inside a block of size 17 free'd
> ==18019==at 0x4C2ED4A: free (vg_replace_malloc.c:530)
> ==18019==by 0x50DCA0E: pn_sasl_free (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D58BF: pn_transport_finalize (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50C7BF8: pn_class_decref (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D406F: pn_event_finalize_cast (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50C7BF8: pn_class_decref (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D437C: pn_collector_pop (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D43AE: pn_collector_next (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D440F: pn_collector_release (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D4438: pn_collector_free (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x4E8E6C2: free_qd_connection (server.c:100)
> ==18019==by 0x4E9152B: thread_run (server.c:984)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (DISPATCH-601) Valgrind errors in dispatch tests

2017-01-03 Thread Alan Conway (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DISPATCH-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway updated DISPATCH-601:
-
Attachment: dispatch-valgrind-err.txt

Full output of test run with valgrind

> Valgrind errors in dispatch tests
> -
>
> Key: DISPATCH-601
> URL: https://issues.apache.org/jira/browse/DISPATCH-601
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Reporter: Alan Conway
> Attachments: dispatch-valgrind-err.txt
>
>
> There are several valgrind erros appearing in the dispatch tests. Full test 
> output will be attached but the errors are all similar to this:
> {code}
> ==18019== Invalid read of size 1
> ==18019==at 0x4C30CAB: strcpy (vg_replace_strmem.c:506)
> ==18019==by 0x69DDFFD: strcpy (string3.h:110)
> ==18019==by 0x69DDFFD: _sasl_strdup (common.c:183)
> ==18019==by 0x69E55A4: sasl_server_new (server.c:1076)
> ==18019==by 0x50DD88F: pni_init_server (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DC1F8: pni_sasl_start_server_if_needed.part.2 (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DC7BE: pn_output_write_sasl (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DEBBA: process_output_ssl (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50DA35C: pn_transport_pending (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x4E6EDA9: connector_process (driver.c:770)
> ==18019==by 0x4E6EC3A: qdpn_connector_process (driver.c:730)
> ==18019==by 0x4E907B3: process_connector (server.c:679)
> ==18019==by 0x4E91321: thread_run (server.c:957)
> ==18019==  Address 0x11be7331 is 1 bytes inside a block of size 17 free'd
> ==18019==at 0x4C2ED4A: free (vg_replace_malloc.c:530)
> ==18019==by 0x50DCA0E: pn_sasl_free (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D58BF: pn_transport_finalize (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50C7BF8: pn_class_decref (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D406F: pn_event_finalize_cast (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50C7BF8: pn_class_decref (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D437C: pn_collector_pop (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D43AE: pn_collector_next (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D440F: pn_collector_release (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x50D4438: pn_collector_free (in 
> /usr/local/lib64/libqpid-proton.so.10.0.0)
> ==18019==by 0x4E8E6C2: free_qd_connection (server.c:100)
> ==18019==by 0x4E9152B: thread_run (server.c:984)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-601) Valgrind errors in dispatch tests

2017-01-03 Thread Alan Conway (JIRA) 
Alan Conway created DISPATCH-601:


 Summary: Valgrind errors in dispatch tests
 Key: DISPATCH-601
 URL: https://issues.apache.org/jira/browse/DISPATCH-601
 Project: Qpid Dispatch
  Issue Type: Bug
  Components: Routing Engine
Reporter: Alan Conway
 Attachments: dispatch-valgrind-err.txt

There are several valgrind erros appearing in the dispatch tests. Full test 
output will be attached but the errors are all similar to this:
{code}
==18019== Invalid read of size 1
==18019==at 0x4C30CAB: strcpy (vg_replace_strmem.c:506)
==18019==by 0x69DDFFD: strcpy (string3.h:110)
==18019==by 0x69DDFFD: _sasl_strdup (common.c:183)
==18019==by 0x69E55A4: sasl_server_new (server.c:1076)
==18019==by 0x50DD88F: pni_init_server (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50DC1F8: pni_sasl_start_server_if_needed.part.2 (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50DC7BE: pn_output_write_sasl (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50DEBBA: process_output_ssl (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50DA35C: pn_transport_pending (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x4E6EDA9: connector_process (driver.c:770)
==18019==by 0x4E6EC3A: qdpn_connector_process (driver.c:730)
==18019==by 0x4E907B3: process_connector (server.c:679)
==18019==by 0x4E91321: thread_run (server.c:957)
==18019==  Address 0x11be7331 is 1 bytes inside a block of size 17 free'd
==18019==at 0x4C2ED4A: free (vg_replace_malloc.c:530)
==18019==by 0x50DCA0E: pn_sasl_free (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50D58BF: pn_transport_finalize (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50C7BF8: pn_class_decref (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50D406F: pn_event_finalize_cast (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50C7BF8: pn_class_decref (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50D437C: pn_collector_pop (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50D43AE: pn_collector_next (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50D440F: pn_collector_release (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x50D4438: pn_collector_free (in 
/usr/local/lib64/libqpid-proton.so.10.0.0)
==18019==by 0x4E8E6C2: free_qd_connection (server.c:100)
==18019==by 0x4E9152B: thread_run (server.c:984)
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (DISPATCH-600) Support secure websockets

2017-01-03 Thread Ted Ross (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DISPATCH-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross updated DISPATCH-600:
--
Fix Version/s: 0.8.0

> Support secure websockets
> -
>
> Key: DISPATCH-600
> URL: https://issues.apache.org/jira/browse/DISPATCH-600
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 0.7.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
> Fix For: 0.8.0
>
>
> To support connecting to a secure websocket the console needs to:
> - load external resources using https: instead of http:
> - connect to the websocket using wss:// if the page was loaded from  a 
> https: address.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-557) High connection rates cause problems in the Python management agent

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795298#comment-15795298
 ] 

ASF subversion and git services commented on DISPATCH-557:
--

Commit 1a3775066d5a13f1a37da55148718bd0ae5070ef in qpid-dispatch's branch 
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=1a37750 ]

DISPATCH-557 - Addtional fix. Added type, ssl and opened fields to the 
management connection response. These fields were present in the connection 
that was managed by the Python agent


> High connection rates cause problems in the Python management agent
> ---
>
> Key: DISPATCH-557
> URL: https://issues.apache.org/jira/browse/DISPATCH-557
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.7.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
>Priority: Critical
> Fix For: 0.8.0
>
>
> Since connection entities are the only non-configuration (spontaneously 
> occurring) entities that are still managed by the Python agent, high rates of 
> opening and closing connections causes large CPU overhead in the agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-600) Support secure websockets

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795266#comment-15795266
 ] 

ASF subversion and git services commented on DISPATCH-600:
--

Commit 3a20b50554f5def325bcd27b2c834f8c3f7007dd in qpid-dispatch's branch 
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=3a20b50 ]

DISPATCH-600 Use correct protocol


> Support secure websockets
> -
>
> Key: DISPATCH-600
> URL: https://issues.apache.org/jira/browse/DISPATCH-600
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 0.7.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> To support connecting to a secure websocket the console needs to:
> - load external resources using https: instead of http:
> - connect to the websocket using wss:// if the page was loaded from  a 
> https: address.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-557) High connection rates cause problems in the Python management agent

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795186#comment-15795186
 ] 

ASF subversion and git services commented on DISPATCH-557:
--

Commit 427836291cf9f2faa77fd43fd39c49f6c0bfebd9 in qpid-dispatch's branch 
refs/heads/master from [~tr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=4278362 ]

DISPATCH-557 - Fixed broken tests


> High connection rates cause problems in the Python management agent
> ---
>
> Key: DISPATCH-557
> URL: https://issues.apache.org/jira/browse/DISPATCH-557
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.7.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
>Priority: Critical
> Fix For: 0.8.0
>
>
> Since connection entities are the only non-configuration (spontaneously 
> occurring) entities that are still managed by the Python agent, high rates of 
> opening and closing connections causes large CPU overhead in the agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-557) High connection rates cause problems in the Python management agent

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795184#comment-15795184
 ] 

ASF subversion and git services commented on DISPATCH-557:
--

Commit a38673a69f5d7dd2a206a71e9d1bef38711feb53 in qpid-dispatch's branch 
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=a38673a ]

DISPATCH-557 - Moved management of connections from python agent to router core


> High connection rates cause problems in the Python management agent
> ---
>
> Key: DISPATCH-557
> URL: https://issues.apache.org/jira/browse/DISPATCH-557
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.7.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
>Priority: Critical
> Fix For: 0.8.0
>
>
> Since connection entities are the only non-configuration (spontaneously 
> occurring) entities that are still managed by the Python agent, high rates of 
> opening and closing connections causes large CPU overhead in the agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-557) High connection rates cause problems in the Python management agent

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795185#comment-15795185
 ] 

ASF subversion and git services commented on DISPATCH-557:
--

Commit d1b0ea36a3b0a080e763313cb25b132ccc1b13e1 in qpid-dispatch's branch 
refs/heads/master from [~tr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=d1b0ea3 ]

DISPATCH-557 - Added name and tenant to the connection entity.


> High connection rates cause problems in the Python management agent
> ---
>
> Key: DISPATCH-557
> URL: https://issues.apache.org/jira/browse/DISPATCH-557
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.7.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
>Priority: Critical
> Fix For: 0.8.0
>
>
> Since connection entities are the only non-configuration (spontaneously 
> occurring) entities that are still managed by the Python agent, high rates of 
> opening and closing connections causes large CPU overhead in the agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-600) Support secure websockets

2017-01-03 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795150#comment-15795150
 ] 

ASF subversion and git services commented on DISPATCH-600:
--

Commit 75492de7a01cac6c4e0a0580ad151ddcc73b17a2 in qpid-dispatch's branch 
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=75492de ]

DISPATCH-600 Changes to console for Supporting secure websockets


> Support secure websockets
> -
>
> Key: DISPATCH-600
> URL: https://issues.apache.org/jira/browse/DISPATCH-600
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 0.7.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> To support connecting to a secure websocket the console needs to:
> - load external resources using https: instead of http:
> - connect to the websocket using wss:// if the page was loaded from  a 
> https: address.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-600) Support secure websockets

2017-01-03 Thread Ernest Allen (JIRA) 
Ernest Allen created DISPATCH-600:
-

 Summary: Support secure websockets
 Key: DISPATCH-600
 URL: https://issues.apache.org/jira/browse/DISPATCH-600
 Project: Qpid Dispatch
  Issue Type: Improvement
  Components: Console
Affects Versions: 0.7.0
Reporter: Ernest Allen
Assignee: Ernest Allen


To support connecting to a secure websocket the console needs to:

- load external resources using https: instead of http:
- connect to the websocket using wss:// if the page was loaded from  a 
https: address.
 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-557) High connection rates cause problems in the Python management agent

2017-01-03 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795122#comment-15795122
 ] 

ASF GitHub Bot commented on DISPATCH-557:
-

Github user ganeshmurthy closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/132


> High connection rates cause problems in the Python management agent
> ---
>
> Key: DISPATCH-557
> URL: https://issues.apache.org/jira/browse/DISPATCH-557
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.7.0
>Reporter: Ted Ross
>Assignee: Ganesh Murthy
>Priority: Critical
> Fix For: 0.8.0
>
>
> Since connection entities are the only non-configuration (spontaneously 
> occurring) entities that are still managed by the Python agent, high rates of 
> opening and closing connections causes large CPU overhead in the agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch pull request #132: DISPATCH-557 - Moved management of connecti...

2017-01-03 Thread ganeshmurthy 
Github user ganeshmurthy closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/132


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org