[jira] [Updated] (PROTON-1920) Adjust transport deprecations in preparation for future changes
[ https://issues.apache.org/jira/browse/PROTON-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1920: Issue Type: Task (was: Improvement) > Adjust transport deprecations in preparation for future changes > --- > > Key: PROTON-1920 > URL: https://issues.apache.org/jira/browse/PROTON-1920 > Project: Qpid Proton > Issue Type: Task > Components: proton-c >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Fix For: proton-c-0.25.0 > > > * De-deprecate get and set context functions > * Add notes about deprecations conditioned on upcoming changes > * Deprecate functions no longer used after the introduction of the connection > driver -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1920) Adjust transport deprecations in preparation for future changes
[ https://issues.apache.org/jira/browse/PROTON-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved PROTON-1920. - Resolution: Done > Adjust transport deprecations in preparation for future changes > --- > > Key: PROTON-1920 > URL: https://issues.apache.org/jira/browse/PROTON-1920 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Fix For: proton-c-0.25.0 > > > * De-deprecate get and set context functions > * Add notes about deprecations conditioned on upcoming changes > * Deprecate functions no longer used after the introduction of the connection > driver -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1920) Adjust transport deprecations in preparation for future changes
[ https://issues.apache.org/jira/browse/PROTON-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594327#comment-16594327 ] ASF subversion and git services commented on PROTON-1920: - Commit 70bbdd1366edea001e6f371d52cc9c6f17d9fd72 in qpid-proton's branch refs/heads/master from [~jr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=70bbdd1 ] PROTON-1920: Update transport and endpoint context deprecations > Adjust transport deprecations in preparation for future changes > --- > > Key: PROTON-1920 > URL: https://issues.apache.org/jira/browse/PROTON-1920 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Fix For: proton-c-0.25.0 > > > * De-deprecate get and set context functions > * Add notes about deprecations conditioned on upcoming changes > * Deprecate functions no longer used after the introduction of the connection > driver -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-1920) Adjust transport deprecations in preparation for future changes
[ https://issues.apache.org/jira/browse/PROTON-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-1920: --- Assignee: Justin Ross > Adjust transport deprecations in preparation for future changes > --- > > Key: PROTON-1920 > URL: https://issues.apache.org/jira/browse/PROTON-1920 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Fix For: proton-c-0.25.0 > > > * De-deprecate get and set context functions > * Add notes about upcoming deprecations conditioned on upcoming changes > * Deprecate functions no longer used after the introduction of the connection > driver -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1920) Adjust transport deprecations in preparation for future changes
Justin Ross created PROTON-1920: --- Summary: Adjust transport deprecations in preparation for future changes Key: PROTON-1920 URL: https://issues.apache.org/jira/browse/PROTON-1920 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Justin Ross Fix For: proton-c-0.25.0 * De-deprecate get and set context functions * Add notes about upcoming deprecations conditioned on upcoming changes * Deprecate functions no longer used after the introduction of the connection driver -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1920) Adjust transport deprecations in preparation for future changes
[ https://issues.apache.org/jira/browse/PROTON-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1920: Description: * De-deprecate get and set context functions * Add notes about deprecations conditioned on upcoming changes * Deprecate functions no longer used after the introduction of the connection driver was: * De-deprecate get and set context functions * Add notes about upcoming deprecations conditioned on upcoming changes * Deprecate functions no longer used after the introduction of the connection driver > Adjust transport deprecations in preparation for future changes > --- > > Key: PROTON-1920 > URL: https://issues.apache.org/jira/browse/PROTON-1920 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Fix For: proton-c-0.25.0 > > > * De-deprecate get and set context functions > * Add notes about deprecations conditioned on upcoming changes > * Deprecate functions no longer used after the introduction of the connection > driver -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8219) [Broker-J] Authentication results are cached in SimpleLdap and OAUTH2 authentication providers per connection basis
[ https://issues.apache.org/jira/browse/QPID-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8219. -- Resolution: Fixed > [Broker-J] Authentication results are cached in SimpleLdap and OAUTH2 > authentication providers per connection basis > --- > > Key: QPID-8219 > URL: https://issues.apache.org/jira/browse/QPID-8219 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, > qpid-java-broker-7.0.2, qpid-java-6.1, qpid-java-6.1.1, qpid-java-6.1.2, > qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-broker-7.0.0, qpid-java-6.1.5, > qpid-java-broker-7.0.1, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, > qpid-java-broker-7.0.6 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0, > qpid-java-broker-7.0.7 > > > SimpleLdap and OAUTH2 authentication providers were supposed to cache > authentication results per remote host basis. Thus, when connections are made > from the same host using the same credentials, the cached authentication > result should be reused. The current caching approach takes into > consideration an ephemeral port of the connection. As result, a new > connection from the same host with the same credentials cannot reuse previous > authentication result due to a different ephemeral port. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7710) [Java Broker] Json configuration store can only save one binding with the same binding key per queue
[ https://issues.apache.org/jira/browse/QPID-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7710: - Affects Version/s: qpid-java-6.1.7 qpid-java-6.1.6 qpid-java-6.1.3 qpid-java-6.1.4 qpid-java-6.1.5 > [Java Broker] Json configuration store can only save one binding with the > same binding key per queue > > > Key: QPID-7710 > URL: https://issues.apache.org/jira/browse/QPID-7710 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-6.1, qpid-java-6.1.1, > qpid-java-6.1.2, qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-6.1.5, > qpid-java-6.1.7 >Reporter: Alex Rudyy >Priority: Major > > Creating two queue bindings with the same routing key to different exchanges > results in saving only one of them in json configuration store. This problem > only affects 6.1.x. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-7710) [Java Broker] Json configuration store can only save one binding with the same binding key per queue
[ https://issues.apache.org/jira/browse/QPID-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy closed QPID-7710. Resolution: Won't Fix The issue is fixed in 7.0 and above. The routing key is stored as a name of Binding configured object in 6.1. Fixing this issue in 6.1 requires changes to the category which has been removed in 7.0. Please, upgrade to 7.0 or above if your require this functionality. > [Java Broker] Json configuration store can only save one binding with the > same binding key per queue > > > Key: QPID-7710 > URL: https://issues.apache.org/jira/browse/QPID-7710 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.1, qpid-java-6.1.1, qpid-java-6.1.2 >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-6.1.7 > > > Creating two queue bindings with the same routing key to different exchanges > results in saving only one of them in json configuration store. This problem > only affects 6.1.x. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7710) [Java Broker] Json configuration store can only save one binding with the same binding key per queue
[ https://issues.apache.org/jira/browse/QPID-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7710: - Fix Version/s: (was: qpid-java-6.1.7) > [Java Broker] Json configuration store can only save one binding with the > same binding key per queue > > > Key: QPID-7710 > URL: https://issues.apache.org/jira/browse/QPID-7710 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.1, qpid-java-6.1.1, qpid-java-6.1.2 >Reporter: Alex Rudyy >Priority: Major > > Creating two queue bindings with the same routing key to different exchanges > results in saving only one of them in json configuration store. This problem > only affects 6.1.x. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8215) The link-store fails to create its tables with Sybase
[ https://issues.apache.org/jira/browse/QPID-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy closed QPID-8215. Resolution: Fixed Fix Version/s: qpid-java-broker-7.1.0 > The link-store fails to create its tables with Sybase > - > > Key: QPID-8215 > URL: https://issues.apache.org/jira/browse/QPID-8215 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.4 >Reporter: Olivier VERMEULEN >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > Unknown type 'TIMESTAMP' when using a Sybase DB -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8236) [Broker-J] Changing of group name, address or node name in BDB HA virtual host node should be disallowed
[
https://issues.apache.org/jira/browse/QPID-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-8236:
Assignee: Alex Rudyy
> [Broker-J] Changing of group name, address or node name in BDB HA virtual
> host node should be disallowed
> -
>
> Key: QPID-8236
> URL: https://issues.apache.org/jira/browse/QPID-8236
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, 0.32, qpid-java-6.0.8,
> qpid-java-broker-7.0.6
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0,
> qpid-java-broker-7.0.7
>
>
> The BDB HA Virtual Host Node group name, address or node name can be changed
> using management interfaces, for example REST API. However, the change of
> this attributes is not reflected in the underlying BDB JE infrastructure. In
> fact, the change of group name, address or node name is unsupported by BDB
> JE. The only way any of them can be changed is by resetting the group
> information using BDB JE utility {{DbResetRepGroup}} which resets the group
> to a single node.
> The Qpid Broker should not allow to change group name, address or node name
> attributes in BDB HA Virtual Host node via management API.
> If group is changed, on next broker restart the impacted {{VHN}} fails to
> start with the following error logged into broker logs:
> {noformat}
> ERROR [qtp699327636-161] (o.a.q.s.m.p.f.ExceptionHandlingFilter) - Unexpected
> exception in servlet '/api/latest/virtualhostnode/node1':
> java.lang.RuntimeException: Unexpected exception on environment creation
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironmentInSeparateThread(ReplicatedEnvironmentFacade.java:1578)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironment(ReplicatedEnvironmentFacade.java:1526)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.(ReplicatedEnvironmentFacade.java:288)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacadeFactory.createEnvironmentFacade(ReplicatedEnvironmentFacadeFactory.java:130)
> at
> org.apache.qpid.server.store.berkeleydb.BDBConfigurationStore.init(BDBConfigurationStore.java:120)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.activate(BDBHAVirtualHostNodeImpl.java:338)
> at
> org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.doActivate(AbstractVirtualHostNode.java:169)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1526)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1505)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainStateIfOpenedOrReopenFailed(AbstractConfiguredObject.java:1489)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.access$1700(AbstractConfiguredObject.java:97)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1716)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1678)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:639)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
> at
> com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
> at
> com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:58)
> at
>
[jira] [Updated] (QPID-8236) [Broker-J] Changing of group name, address or node name in BDB HA virtual host node should be disallowed
[
https://issues.apache.org/jira/browse/QPID-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8236:
-
Status: Reviewable (was: In Progress)
> [Broker-J] Changing of group name, address or node name in BDB HA virtual
> host node should be disallowed
> -
>
> Key: QPID-8236
> URL: https://issues.apache.org/jira/browse/QPID-8236
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, 0.32, qpid-java-6.0.8,
> qpid-java-broker-7.0.6
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0,
> qpid-java-broker-7.0.7
>
>
> The BDB HA Virtual Host Node group name, address or node name can be changed
> using management interfaces, for example REST API. However, the change of
> this attributes is not reflected in the underlying BDB JE infrastructure. In
> fact, the change of group name, address or node name is unsupported by BDB
> JE. The only way any of them can be changed is by resetting the group
> information using BDB JE utility {{DbResetRepGroup}} which resets the group
> to a single node.
> The Qpid Broker should not allow to change group name, address or node name
> attributes in BDB HA Virtual Host node via management API.
> If group is changed, on next broker restart the impacted {{VHN}} fails to
> start with the following error logged into broker logs:
> {noformat}
> ERROR [qtp699327636-161] (o.a.q.s.m.p.f.ExceptionHandlingFilter) - Unexpected
> exception in servlet '/api/latest/virtualhostnode/node1':
> java.lang.RuntimeException: Unexpected exception on environment creation
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironmentInSeparateThread(ReplicatedEnvironmentFacade.java:1578)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironment(ReplicatedEnvironmentFacade.java:1526)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.(ReplicatedEnvironmentFacade.java:288)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacadeFactory.createEnvironmentFacade(ReplicatedEnvironmentFacadeFactory.java:130)
> at
> org.apache.qpid.server.store.berkeleydb.BDBConfigurationStore.init(BDBConfigurationStore.java:120)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.activate(BDBHAVirtualHostNodeImpl.java:338)
> at
> org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.doActivate(AbstractVirtualHostNode.java:169)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1526)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1505)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainStateIfOpenedOrReopenFailed(AbstractConfiguredObject.java:1489)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.access$1700(AbstractConfiguredObject.java:97)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1716)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1678)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:639)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
> at
> com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
> at
> com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:58)
>
[jira] [Commented] (QPID-8236) [Broker-J] Changing of group name, address or node name in BDB HA virtual host node should be disallowed
[
https://issues.apache.org/jira/browse/QPID-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593910#comment-16593910
]
ASF subversion and git services commented on QPID-8236:
---
Commit 3bf704d534399f0e06a8386b216b64a6fd74ba02 in qpid-broker-j's branch
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=3bf704d ]
QPID-8236: [Broker-J] Make BDB HA group name, address and node name immutable
(cherry picked from commit d6ca0de4d4f193fd84ade278ad024e4f44ae22c7)
> [Broker-J] Changing of group name, address or node name in BDB HA virtual
> host node should be disallowed
> -
>
> Key: QPID-8236
> URL: https://issues.apache.org/jira/browse/QPID-8236
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, 0.32, qpid-java-6.0.8,
> qpid-java-broker-7.0.6
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0,
> qpid-java-broker-7.0.7
>
>
> The BDB HA Virtual Host Node group name, address or node name can be changed
> using management interfaces, for example REST API. However, the change of
> this attributes is not reflected in the underlying BDB JE infrastructure. In
> fact, the change of group name, address or node name is unsupported by BDB
> JE. The only way any of them can be changed is by resetting the group
> information using BDB JE utility {{DbResetRepGroup}} which resets the group
> to a single node.
> The Qpid Broker should not allow to change group name, address or node name
> attributes in BDB HA Virtual Host node via management API.
> If group is changed, on next broker restart the impacted {{VHN}} fails to
> start with the following error logged into broker logs:
> {noformat}
> ERROR [qtp699327636-161] (o.a.q.s.m.p.f.ExceptionHandlingFilter) - Unexpected
> exception in servlet '/api/latest/virtualhostnode/node1':
> java.lang.RuntimeException: Unexpected exception on environment creation
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironmentInSeparateThread(ReplicatedEnvironmentFacade.java:1578)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironment(ReplicatedEnvironmentFacade.java:1526)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.(ReplicatedEnvironmentFacade.java:288)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacadeFactory.createEnvironmentFacade(ReplicatedEnvironmentFacadeFactory.java:130)
> at
> org.apache.qpid.server.store.berkeleydb.BDBConfigurationStore.init(BDBConfigurationStore.java:120)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.activate(BDBHAVirtualHostNodeImpl.java:338)
> at
> org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.doActivate(AbstractVirtualHostNode.java:169)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1526)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1505)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainStateIfOpenedOrReopenFailed(AbstractConfiguredObject.java:1489)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.access$1700(AbstractConfiguredObject.java:97)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1716)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1678)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:639)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
>
[jira] [Commented] (QPID-8236) [Broker-J] Changing of group name, address or node name in BDB HA virtual host node should be disallowed
[
https://issues.apache.org/jira/browse/QPID-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593909#comment-16593909
]
ASF subversion and git services commented on QPID-8236:
---
Commit 579fd32e411cdb8811cd6912715cd2a051ea6cea in qpid-broker-j's branch
refs/heads/6.1.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=579fd32 ]
QPID-8236: [Broker-J] Make BDB HA group name, address and node name immutable
(cherry picked from commit d6ca0de4d4f193fd84ade278ad024e4f44ae22c7)
> [Broker-J] Changing of group name, address or node name in BDB HA virtual
> host node should be disallowed
> -
>
> Key: QPID-8236
> URL: https://issues.apache.org/jira/browse/QPID-8236
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, 0.32, qpid-java-6.0.8,
> qpid-java-broker-7.0.6
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0,
> qpid-java-broker-7.0.7
>
>
> The BDB HA Virtual Host Node group name, address or node name can be changed
> using management interfaces, for example REST API. However, the change of
> this attributes is not reflected in the underlying BDB JE infrastructure. In
> fact, the change of group name, address or node name is unsupported by BDB
> JE. The only way any of them can be changed is by resetting the group
> information using BDB JE utility {{DbResetRepGroup}} which resets the group
> to a single node.
> The Qpid Broker should not allow to change group name, address or node name
> attributes in BDB HA Virtual Host node via management API.
> If group is changed, on next broker restart the impacted {{VHN}} fails to
> start with the following error logged into broker logs:
> {noformat}
> ERROR [qtp699327636-161] (o.a.q.s.m.p.f.ExceptionHandlingFilter) - Unexpected
> exception in servlet '/api/latest/virtualhostnode/node1':
> java.lang.RuntimeException: Unexpected exception on environment creation
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironmentInSeparateThread(ReplicatedEnvironmentFacade.java:1578)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironment(ReplicatedEnvironmentFacade.java:1526)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.(ReplicatedEnvironmentFacade.java:288)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacadeFactory.createEnvironmentFacade(ReplicatedEnvironmentFacadeFactory.java:130)
> at
> org.apache.qpid.server.store.berkeleydb.BDBConfigurationStore.init(BDBConfigurationStore.java:120)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.activate(BDBHAVirtualHostNodeImpl.java:338)
> at
> org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.doActivate(AbstractVirtualHostNode.java:169)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1526)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1505)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainStateIfOpenedOrReopenFailed(AbstractConfiguredObject.java:1489)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.access$1700(AbstractConfiguredObject.java:97)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1716)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1678)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:639)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
>
[jira] [Commented] (QPID-8236) [Broker-J] Changing of group name, address or node name in BDB HA virtual host node should be disallowed
[
https://issues.apache.org/jira/browse/QPID-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593878#comment-16593878
]
ASF subversion and git services commented on QPID-8236:
---
Commit d6ca0de4d4f193fd84ade278ad024e4f44ae22c7 in qpid-broker-j's branch
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=d6ca0de ]
QPID-8236: [Broker-J] Make BDB HA group name, address and node name immutable
> [Broker-J] Changing of group name, address or node name in BDB HA virtual
> host node should be disallowed
> -
>
> Key: QPID-8236
> URL: https://issues.apache.org/jira/browse/QPID-8236
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, 0.32, qpid-java-6.0.8,
> qpid-java-broker-7.0.6
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0,
> qpid-java-broker-7.0.7
>
>
> The BDB HA Virtual Host Node group name, address or node name can be changed
> using management interfaces, for example REST API. However, the change of
> this attributes is not reflected in the underlying BDB JE infrastructure. In
> fact, the change of group name, address or node name is unsupported by BDB
> JE. The only way any of them can be changed is by resetting the group
> information using BDB JE utility {{DbResetRepGroup}} which resets the group
> to a single node.
> The Qpid Broker should not allow to change group name, address or node name
> attributes in BDB HA Virtual Host node via management API.
> If group is changed, on next broker restart the impacted {{VHN}} fails to
> start with the following error logged into broker logs:
> {noformat}
> ERROR [qtp699327636-161] (o.a.q.s.m.p.f.ExceptionHandlingFilter) - Unexpected
> exception in servlet '/api/latest/virtualhostnode/node1':
> java.lang.RuntimeException: Unexpected exception on environment creation
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironmentInSeparateThread(ReplicatedEnvironmentFacade.java:1578)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironment(ReplicatedEnvironmentFacade.java:1526)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.(ReplicatedEnvironmentFacade.java:288)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacadeFactory.createEnvironmentFacade(ReplicatedEnvironmentFacadeFactory.java:130)
> at
> org.apache.qpid.server.store.berkeleydb.BDBConfigurationStore.init(BDBConfigurationStore.java:120)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.activate(BDBHAVirtualHostNodeImpl.java:338)
> at
> org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.doActivate(AbstractVirtualHostNode.java:169)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1526)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1505)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainStateIfOpenedOrReopenFailed(AbstractConfiguredObject.java:1489)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.access$1700(AbstractConfiguredObject.java:97)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1716)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1678)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:639)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
>
[jira] [Updated] (QPID-8236) [Broker-J] Changing of group name, address or node name in BDB HA virtual host node should be disallowed
[
https://issues.apache.org/jira/browse/QPID-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8236:
-
Description:
The BDB HA Virtual Host Node group name, address or node name can be changed
using management interfaces, for example REST API. However, the change of this
attributes is not reflected in the underlying BDB JE infrastructure. In fact,
the change of group name, address or node name is unsupported by BDB JE. The
only way any of them can be changed is by resetting the group information
using BDB JE utility {{DbResetRepGroup}} which resets the group to a single
node.
The Qpid Broker should not allow to change group name, address or node name
attributes in BDB HA Virtual Host node via management API.
If group is changed, on next broker restart the impacted {{VHN}} fails to start
with the following error logged into broker logs:
{noformat}
ERROR [qtp699327636-161] (o.a.q.s.m.p.f.ExceptionHandlingFilter) - Unexpected
exception in servlet '/api/latest/virtualhostnode/node1':
java.lang.RuntimeException: Unexpected exception on environment creation
at
org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironmentInSeparateThread(ReplicatedEnvironmentFacade.java:1578)
at
org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironment(ReplicatedEnvironmentFacade.java:1526)
at
org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.(ReplicatedEnvironmentFacade.java:288)
at
org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacadeFactory.createEnvironmentFacade(ReplicatedEnvironmentFacadeFactory.java:130)
at
org.apache.qpid.server.store.berkeleydb.BDBConfigurationStore.init(BDBConfigurationStore.java:120)
at
org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.activate(BDBHAVirtualHostNodeImpl.java:338)
at
org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.doActivate(AbstractVirtualHostNode.java:169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1526)
at
org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1505)
at
org.apache.qpid.server.model.AbstractConfiguredObject.attainStateIfOpenedOrReopenFailed(AbstractConfiguredObject.java:1489)
at
org.apache.qpid.server.model.AbstractConfiguredObject.access$1700(AbstractConfiguredObject.java:97)
at
org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1716)
at
org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1678)
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:639)
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
at
com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
at
com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:58)
at
com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:75)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sleepycat.je.EnvironmentFailureException: (JE 7.4.5) The
argument: ha2 does not match the expected group name: ha UNEXPECTED_STATE:
Unexpected internal state, may have side effects.
at
com.sleepycat.je.EnvironmentFailureException.unexpectedState(EnvironmentFailureException.java:428)
at
[jira] [Updated] (QPID-8236) [Broker-J] Changing of group name, address or node name in BDB HA virtual host node should be disallowed
[
https://issues.apache.org/jira/browse/QPID-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8236:
-
Summary: [Broker-J] Changing of group name, address or node name in BDB HA
virtual host node should be disallowed (was: [Broker-J] Changing of group
name in BDB HA virtual host node should be disallowed )
> [Broker-J] Changing of group name, address or node name in BDB HA virtual
> host node should be disallowed
> -
>
> Key: QPID-8236
> URL: https://issues.apache.org/jira/browse/QPID-8236
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, 0.32, qpid-java-6.0.8,
> qpid-java-broker-7.0.6
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0,
> qpid-java-broker-7.0.7
>
>
> The group name of BDB HA Virtual Host Node can be changed using management
> interfaces, for example REST API. However, the change of group name is not
> reflected in the underlying BDB JE infrastructure. In fact, the change of
> group name is unsupported by BDB JE. The only way the group can be changed is
> by resetting the group information using BDB JE utility {{DbResetRepGroup}}
> which resets the group to a single node.
> The Qpid Broker should not allow to change group name attribute in BDB HA
> Virtual Host node via management API.
> If group is changed, on next broker restart the impacted {{VHN}} fails to
> start with the following error logged into broker logs:
> {noformat}
> ERROR [qtp699327636-161] (o.a.q.s.m.p.f.ExceptionHandlingFilter) - Unexpected
> exception in servlet '/api/latest/virtualhostnode/node1':
> java.lang.RuntimeException: Unexpected exception on environment creation
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironmentInSeparateThread(ReplicatedEnvironmentFacade.java:1578)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironment(ReplicatedEnvironmentFacade.java:1526)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.(ReplicatedEnvironmentFacade.java:288)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacadeFactory.createEnvironmentFacade(ReplicatedEnvironmentFacadeFactory.java:130)
> at
> org.apache.qpid.server.store.berkeleydb.BDBConfigurationStore.init(BDBConfigurationStore.java:120)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.activate(BDBHAVirtualHostNodeImpl.java:338)
> at
> org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.doActivate(AbstractVirtualHostNode.java:169)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1526)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1505)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainStateIfOpenedOrReopenFailed(AbstractConfiguredObject.java:1489)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.access$1700(AbstractConfiguredObject.java:97)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1716)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1678)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:639)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
> at
> com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
> at
>
[jira] [Created] (QPID-8236) [Broker-J] Changing of group name in BDB HA virtual host node should be disallowed
Alex Rudyy created QPID-8236:
Summary: [Broker-J] Changing of group name in BDB HA virtual host
node should be disallowed
Key: QPID-8236
URL: https://issues.apache.org/jira/browse/QPID-8236
Project: Qpid
Issue Type: Bug
Components: Broker-J
Affects Versions: qpid-java-broker-7.0.6, qpid-java-6.0.8, 0.32,
qpid-java-6.1.6
Reporter: Alex Rudyy
Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0,
qpid-java-broker-7.0.7
The group name of BDB HA Virtual Host Node can be changed using management
interfaces, for example REST API. However, the change of group name is not
reflected in the underlying BDB JE infrastructure. In fact, the change of group
name is unsupported by BDB JE. The only way the group can be changed is by
resetting the group information using BDB JE utility {{DbResetRepGroup}} which
resets the group to a single node.
The Qpid Broker should not allow to change group name attribute in BDB HA
Virtual Host node via management API.
If group is changed, on next broker restart the impacted {{VHN}} fails to start
with the following error logged into broker logs:
{noformat}
ERROR [qtp699327636-161] (o.a.q.s.m.p.f.ExceptionHandlingFilter) - Unexpected
exception in servlet '/api/latest/virtualhostnode/node1':
java.lang.RuntimeException: Unexpected exception on environment creation
at
org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironmentInSeparateThread(ReplicatedEnvironmentFacade.java:1578)
at
org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.createEnvironment(ReplicatedEnvironmentFacade.java:1526)
at
org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.(ReplicatedEnvironmentFacade.java:288)
at
org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacadeFactory.createEnvironmentFacade(ReplicatedEnvironmentFacadeFactory.java:130)
at
org.apache.qpid.server.store.berkeleydb.BDBConfigurationStore.init(BDBConfigurationStore.java:120)
at
org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.activate(BDBHAVirtualHostNodeImpl.java:338)
at
org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.doActivate(AbstractVirtualHostNode.java:169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1526)
at
org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1505)
at
org.apache.qpid.server.model.AbstractConfiguredObject.attainStateIfOpenedOrReopenFailed(AbstractConfiguredObject.java:1489)
at
org.apache.qpid.server.model.AbstractConfiguredObject.access$1700(AbstractConfiguredObject.java:97)
at
org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1716)
at
org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1678)
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:639)
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
at
com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:111)
at
com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:58)
at
com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:75)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sleepycat.je.EnvironmentFailureException: (JE 7.4.5) The
argument: ha2 does not
[jira] [Commented] (DISPATCH-1103) auto-links should retry after detach
[ https://issues.apache.org/jira/browse/DISPATCH-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593797#comment-16593797 ] ASF subversion and git services commented on DISPATCH-1103: --- Commit d59ce4172683414ee7925c20b3da78e1e2227eb0 in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=d59ce41 ] DISPATCH-1103 - Additional fix. Cancel scheduled timer if trying to reschedule same timer > auto-links should retry after detach > > > Key: DISPATCH-1103 > URL: https://issues.apache.org/jira/browse/DISPATCH-1103 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Affects Versions: 1.3.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.4.0 > > > When an auto-link is activated, it attempts to attach to a node on the remote > container. If this attach fails, or succeeds and subsequently gets detached, > the auto-link will remain in the failed state until it is later re-activated. > Active auto-links that fail to attach or become detached should periodically > attempt to reattach to the remote node. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active
[
https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593598#comment-16593598
]
Jeremy commented on PROTON-1917:
Hello [~rgodfrey]
With the updated zip, the problem is solved. Thanks for your reactiveness.
This solves both this issue and the broker-j issue.
cheers
> [proton-c] the c++ proton consumer with retry should continue to retry if
> virtual host not active
> -
>
> Key: PROTON-1917
> URL: https://issues.apache.org/jira/browse/PROTON-1917
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Affects Versions: proton-c-0.22.0
>Reporter: Jeremy
>Priority: Major
>
> I have a running broker, and a configured queue containing messages.
> I also have a consumer, where I configured the max number of attempts to 0
> (infinite retry).
> I kill the broker (ctrl-c) and start it on the same port.
> Upon reconnection, I get the following error message randomly:
> {code:java}
> receive_with_retry on_connection_open
> receive_with_retry: on_error: amqp:not-found: Virtual host 'localhost' is not
> active
> main: end{code}
> In the case where the consumer is able to connect, the consumer continues to
> consume the messages normally.
> However, in the broker web interface, I see upon each re-connection, an extra
> connection (same ip and port) to the queue. As if, the old connection is not
> killed. I wasn't expecting this behavior. This might be a separate issue.
> I was able to reproduce with the following code, on windows 7 (msvc 12 2013)
> {code:java}
> class receive_with_retry : public proton::messaging_handler {
> private:
>std::string url;
>std::string queueName;
> public:
>receive_with_retry(const std::string , const std::string& q) : url(u),
> queueName(q) {}
>void on_container_start(proton::container ) override {
> std::cout << "receive_with_retry on_container_start" << std::endl;
> c.connect(
> url,
> proton::connection_options()
> .idle_timeout(proton::duration(2000))
> .reconnect(proton::reconnect_options()
> .max_attempts(0)
> .delay(proton::duration(3000))
> .delay_multiplier(1)
> .max_delay(proton::duration(3001;
>}
>void on_connection_open(proton::connection& c) override {
> std::cout << "receive_with_retry on_connection_open " << std::endl;
> c.open_receiver(queueName,
> proton::receiver_options().auto_accept(false));
>}
>void on_session_open(proton::session& session) override {
> std::cout << "receive_with_retry on_session_open " << std::endl;
>}
>void on_receiver_open(proton::receiver& receiver) override {
> std::cout << "receive_with_retry on_receiver_open " << std::endl;
> receiver.open();
>}
>void on_message(proton::delivery& delivery, proton::message )
> override {
> std::cout << "receive_with_retry on_message " << message.body() <<
> std::endl;
> // Can be used for throttling
> // std::this_thread::sleep_for(std::chrono::milliseconds(100));
> // commented out in order not to exit immediately, but continue on
> consuming the messages.
> // delivery.receiver().close();
> // delivery.receiver().connection().close();
>}
>void on_transport_error(proton::transport& error) override {
> std::cout << "receive_with_retry: on_transport_error: " <<
> error.error().what() << std::endl;
> error.connection().close();
>}
>void on_error(const proton::error_condition& error) override {
> std::cout << "receive_with_retry: on_error: " << error.what() <<
> std::endl;
>}
> };
> void receiveWithRetry(const std::string& url, const std::string& queueName){
>try {
> std::cout << "main: start" << std::endl;
> receive_with_retry receiveWithRetry(url, queueName);
> proton::container(receiveWithRetry).run();
> std::cout << "main: end" << std::endl;
>}
>catch (const std::exception& cause) {
> std::cout << "main: caught exception: " << cause.what() << std::endl;
>}
> }
> int main() {
>try {
> receiveWithRetry("amqp://localhost:5673", "test_queue");
> return 0;
>}
>catch (const std::exception& e) {
> std::cerr << e.what() << std::endl;
>}
>return 1;
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active
[
https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593394#comment-16593394
]
Rob Godfrey commented on PROTON-1917:
-
So - I cleaned and rebuilt the broker at the end of last week, just in case I
had given you a bad build somehow (before I noticed you had actually described
a different error). Can you re-download from the other JIRA and try again...
there should literally be no way that the (rebuilt) broker could generate the
amqp:not-found "Virtual host 'localhost' is not active" error.
> [proton-c] the c++ proton consumer with retry should continue to retry if
> virtual host not active
> -
>
> Key: PROTON-1917
> URL: https://issues.apache.org/jira/browse/PROTON-1917
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Affects Versions: proton-c-0.22.0
>Reporter: Jeremy
>Priority: Major
>
> I have a running broker, and a configured queue containing messages.
> I also have a consumer, where I configured the max number of attempts to 0
> (infinite retry).
> I kill the broker (ctrl-c) and start it on the same port.
> Upon reconnection, I get the following error message randomly:
> {code:java}
> receive_with_retry on_connection_open
> receive_with_retry: on_error: amqp:not-found: Virtual host 'localhost' is not
> active
> main: end{code}
> In the case where the consumer is able to connect, the consumer continues to
> consume the messages normally.
> However, in the broker web interface, I see upon each re-connection, an extra
> connection (same ip and port) to the queue. As if, the old connection is not
> killed. I wasn't expecting this behavior. This might be a separate issue.
> I was able to reproduce with the following code, on windows 7 (msvc 12 2013)
> {code:java}
> class receive_with_retry : public proton::messaging_handler {
> private:
>std::string url;
>std::string queueName;
> public:
>receive_with_retry(const std::string , const std::string& q) : url(u),
> queueName(q) {}
>void on_container_start(proton::container ) override {
> std::cout << "receive_with_retry on_container_start" << std::endl;
> c.connect(
> url,
> proton::connection_options()
> .idle_timeout(proton::duration(2000))
> .reconnect(proton::reconnect_options()
> .max_attempts(0)
> .delay(proton::duration(3000))
> .delay_multiplier(1)
> .max_delay(proton::duration(3001;
>}
>void on_connection_open(proton::connection& c) override {
> std::cout << "receive_with_retry on_connection_open " << std::endl;
> c.open_receiver(queueName,
> proton::receiver_options().auto_accept(false));
>}
>void on_session_open(proton::session& session) override {
> std::cout << "receive_with_retry on_session_open " << std::endl;
>}
>void on_receiver_open(proton::receiver& receiver) override {
> std::cout << "receive_with_retry on_receiver_open " << std::endl;
> receiver.open();
>}
>void on_message(proton::delivery& delivery, proton::message )
> override {
> std::cout << "receive_with_retry on_message " << message.body() <<
> std::endl;
> // Can be used for throttling
> // std::this_thread::sleep_for(std::chrono::milliseconds(100));
> // commented out in order not to exit immediately, but continue on
> consuming the messages.
> // delivery.receiver().close();
> // delivery.receiver().connection().close();
>}
>void on_transport_error(proton::transport& error) override {
> std::cout << "receive_with_retry: on_transport_error: " <<
> error.error().what() << std::endl;
> error.connection().close();
>}
>void on_error(const proton::error_condition& error) override {
> std::cout << "receive_with_retry: on_error: " << error.what() <<
> std::endl;
>}
> };
> void receiveWithRetry(const std::string& url, const std::string& queueName){
>try {
> std::cout << "main: start" << std::endl;
> receive_with_retry receiveWithRetry(url, queueName);
> proton::container(receiveWithRetry).run();
> std::cout << "main: end" << std::endl;
>}
>catch (const std::exception& cause) {
> std::cout << "main: caught exception: " << cause.what() << std::endl;
>}
> }
> int main() {
>try {
> receiveWithRetry("amqp://localhost:5673", "test_queue");
> return 0;
>}
>catch (const std::exception& e) {
> std::cerr << e.what() << std::endl;
>}
>return 1;
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (QPID-8229) [Broker-J][6.x] Queue bindings are not removed on queue deletion when BDB/DERBY/JDBC configuration stores are used
[
https://issues.apache.org/jira/browse/QPID-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8229:
-
Status: Reviewable (was: In Progress)
> [Broker-J][6.x] Queue bindings are not removed on queue deletion when
> BDB/DERBY/JDBC configuration stores are used
> --
>
> Key: QPID-8229
> URL: https://issues.apache.org/jira/browse/QPID-8229
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, qpid-java-6.1, qpid-java-6.1.2,
> qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-6.1.5
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Critical
> Fix For: qpid-java-6.1.7
>
>
> Queue bindings can be left behind in BDB/DERBY/JDBC configuration stores on
> queue deletion. When virtual host with a deleted queue and orphaned binding
> is restarted, the Virtual Host startup fails with error "422 - No parent of
> class Queue found.". The following warning is reported into the logs:
> {noformat}
> WARN [HttpManagement-HTTP-379] (o.a.q.s.m.p.s.r.RestServlet) -
> IllegalArgumentException processing request
> http://localhost:8080/api/latest/virtualhost/tmp2/tmp2 from user
> '[/0:0:0:0:0:0:0:1:61279, admin]': No parent of class Queue found.
> {noformat}
> The work-around for the issue would a deletion of all queue bindings prior
> queue deletion. There is no work around which would allow to delete orphaned
> bindings and recover Virtual Host configuration apart from changing store
> data directly which is not feasible in case of BDB.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8229) [Broker-J][6.x] Queue bindings are not removed on queue deletion when BDB/DERBY/JDBC configuration stores are used
[
https://issues.apache.org/jira/browse/QPID-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-8229:
Assignee: Alex Rudyy
> [Broker-J][6.x] Queue bindings are not removed on queue deletion when
> BDB/DERBY/JDBC configuration stores are used
> --
>
> Key: QPID-8229
> URL: https://issues.apache.org/jira/browse/QPID-8229
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, qpid-java-6.1, qpid-java-6.1.2,
> qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-6.1.5
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Critical
> Fix For: qpid-java-6.1.7
>
>
> Queue bindings can be left behind in BDB/DERBY/JDBC configuration stores on
> queue deletion. When virtual host with a deleted queue and orphaned binding
> is restarted, the Virtual Host startup fails with error "422 - No parent of
> class Queue found.". The following warning is reported into the logs:
> {noformat}
> WARN [HttpManagement-HTTP-379] (o.a.q.s.m.p.s.r.RestServlet) -
> IllegalArgumentException processing request
> http://localhost:8080/api/latest/virtualhost/tmp2/tmp2 from user
> '[/0:0:0:0:0:0:0:1:61279, admin]': No parent of class Queue found.
> {noformat}
> The work-around for the issue would a deletion of all queue bindings prior
> queue deletion. There is no work around which would allow to delete orphaned
> bindings and recover Virtual Host configuration apart from changing store
> data directly which is not feasible in case of BDB.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8229) [Broker-J][6.x] Queue bindings are not removed on queue deletion when BDB/DERBY/JDBC configuration stores are used
[
https://issues.apache.org/jira/browse/QPID-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593387#comment-16593387
]
ASF subversion and git services commented on QPID-8229:
---
Commit ca3dd59c30112e048636380db54196143028e22a in qpid-broker-j's branch
refs/heads/6.1.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=ca3dd59 ]
QPID-8229: [Java Broker] Ensure changes made to existing durable children of
virtualhost after virtualhost restart are persisted
(cherry picked from commit d27237d87672dff846603e5d04a849116ee47fac)
# Conflicts:
#
broker-core/src/main/java/org/apache/qpid/server/store/VirtualHostStoreUpgraderAndRecoverer.java
#
broker-core/src/main/java/org/apache/qpid/server/virtualhost/AbstractVirtualHost.java
> [Broker-J][6.x] Queue bindings are not removed on queue deletion when
> BDB/DERBY/JDBC configuration stores are used
> --
>
> Key: QPID-8229
> URL: https://issues.apache.org/jira/browse/QPID-8229
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, qpid-java-6.1, qpid-java-6.1.2,
> qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-6.1.5
>Reporter: Alex Rudyy
>Priority: Critical
> Fix For: qpid-java-6.1.7
>
>
> Queue bindings can be left behind in BDB/DERBY/JDBC configuration stores on
> queue deletion. When virtual host with a deleted queue and orphaned binding
> is restarted, the Virtual Host startup fails with error "422 - No parent of
> class Queue found.". The following warning is reported into the logs:
> {noformat}
> WARN [HttpManagement-HTTP-379] (o.a.q.s.m.p.s.r.RestServlet) -
> IllegalArgumentException processing request
> http://localhost:8080/api/latest/virtualhost/tmp2/tmp2 from user
> '[/0:0:0:0:0:0:0:1:61279, admin]': No parent of class Queue found.
> {noformat}
> The work-around for the issue would a deletion of all queue bindings prior
> queue deletion. There is no work around which would allow to delete orphaned
> bindings and recover Virtual Host configuration apart from changing store
> data directly which is not feasible in case of BDB.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active
[
https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593281#comment-16593281
]
Jeremy commented on PROTON-1917:
My bad. As I said, I was testing from a different host 'lahad01', to ensure a
fresh broker environment. That being said, I also tested from my own machine
(same as before), and I will be posting the logs.
As you can see from the logs above, the consumer consumed a couple of messages,
then, upon broker restart, I got an amqp not-found error unknown hostname...
The logs on my machine are the following:
{code:java}
main: start
receive_with_retry on_container_start
receive_with_retry on_connection_open
receive_with_retry on_session_open
receive_with_retry on_receiver_open
[002E5C70]:(PN_PROACTOR_TIMEOUT)
[002E5C70]:(PN_PROACTOR_TIMEOUT)
[002E5C70]:(PN_PROACTOR_TIMEOUT)
receive_with_retry on_connection_open
receive_with_retry on_session_open
receive_with_retry on_receiver_open
receive_with_retry on_receiver_open
[002E5C70]:(PN_PROACTOR_TIMEOUT)
[002E5C70]:(PN_PROACTOR_TIMEOUT)
receive_with_retry on_connection_open
receive_with_retry: on_error: amqp:not-found: Virtual host 'localhost' is not
active
[002E5C70]:(PN_PROACTOR_INACTIVE)
[002E5C70]:(PN_PROACTOR_INTERRUPT)
main: end
Press any key to continue . . .{code}
Same error on my machine. Not that I cleaned the qpid broker cache under
C:\Users\jeremy\appdata\... I generated a new work dir for the patched broker,
and copied the config from the old broker.
Not sure if the patched broker logs will help. I kill the broker with a ctrl-c
then start it on the same port. For my last scenario, the queue does not
contain any messages.
{code:java}
D:\qpid\qpid-broker\7.0.3-patched>bin\qpid-server.bat -prop
"BROKER_HTTP_PORT=10102" -prop "BROKER_AMQP_PORT=5673"
Warning: Qpid classpath not set. CLASSPATH set to
D:\qpid\qpid-broker\7.0.3-patched\lib\*;D:\qpid\qpid-broker\7.0.3-patched\lib\plugins\*;D:\qpid\qpid-broker\7.
0.3-patched\lib\opt\*
Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC -XX:+UseConcMarkSweepGC
-XX:+HeapDumpOnOutOfMemoryError
Info: QPID_JAVA_MEM not set. Defaulting to JAVA_MEM -Xmx512m
-XX:MaxDirectMemorySize=1536m
[Broker] BRK-1006 : Using configuration :
D:\qpid\qpid-broker\7.0.3-patched\jeremy\config.json
[Broker] BRK-1001 : Startup : Version: 7.0.3 Build:
62d7ae692b47746c42949c2e646f33a966e6a1a1
[Broker] BRK-1010 : Platform : JVM : Oracle Corporation version: 1.8.0_131-b11
OS : Windows 7 version: 6.1 arch: amd64 cores: 12
[Broker] BRK-1011 : Maximum Memory : Heap : 518,979,584 bytes Direct :
1,610,612,736 bytes
[Broker] BRK-1017 : Process : PID : 21400
[Broker] BRK-1002 : Starting : Listening on TCP port 5673
[Broker] MNG-1001 : Web Management Startup
[Broker] MNG-1002 : Starting : HTTP : Listening on TCP port 10102
[Broker] MNG-1004 : Web Management Ready
[Broker] BRK-1019 : WARNING - some services were unable to start. The following
components are in the ERRORed state [BrokerLogger[id=83452a76-8bc4-43ca-97fc-15c
4c417c546, name=logfile, type=File]]
[Broker] BRK-1004 : Qpid Broker Ready
Terminate batch job (Y/N)?
^CThe system cannot open the device or file specified.
D:\qpid\qpid-broker\7.0.3-patched>
D:\qpid\qpid-broker\7.0.3-patched>bin\qpid-server.bat -prop
"BROKER_HTTP_PORT=10102" -prop "BROKER_AMQP_PORT=5673"
Warning: Qpid classpath not set. CLASSPATH set to
D:\qpid\qpid-broker\7.0.3-patched\lib\*;D:\qpid\qpid-broker\7.0.3-patched\lib\plugins\*;D:\qpid\qpid-broker\7.
0.3-patched\lib\opt\*
Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC -XX:+UseConcMarkSweepGC
-XX:+HeapDumpOnOutOfMemoryError
Info: QPID_JAVA_MEM not set. Defaulting to JAVA_MEM -Xmx512m
-XX:MaxDirectMemorySize=1536m
[Broker] BRK-1006 : Using configuration :
D:\qpid\qpid-broker\7.0.3-patched\jeremy\config.json
[Broker] BRK-1001 : Startup : Version: 7.0.3 Build:
62d7ae692b47746c42949c2e646f33a966e6a1a1
[Broker] BRK-1010 : Platform : JVM : Oracle Corporation version: 1.8.0_131-b11
OS : Windows 7 version: 6.1 arch: amd64 cores: 12
[Broker] BRK-1011 : Maximum Memory : Heap : 518,979,584 bytes Direct :
1,610,612,736 bytes
[Broker] BRK-1017 : Process : PID : 15788
[Broker] BRK-1002 : Starting : Listening on TCP port 5673
[Broker] MNG-1001 : Web Management Startup
[Broker] MNG-1002 : Starting : HTTP : Listening on TCP port 10102
[Broker] MNG-1004 : Web Management Ready
[Broker] BRK-1019 : WARNING - some services were unable to start. The following
components are in the ERRORed state [BrokerLogger[id=11602439-fc97-4a3c-ae73-51d
18dde6ffb, name=logfile, type=File]]
[Broker] BRK-1004 : Qpid Broker Ready
Terminate batch job (Y/N)?
^C
D:\qpid\qpid-broker\7.0.3-patched>
D:\qpid\qpid-broker\7.0.3-patched>bin\qpid-server.bat -prop
"BROKER_HTTP_PORT=10102" -prop "BROKER_AMQP_PORT=5673"
Warning: Qpid classpath not set. CLASSPATH set to
