[jira] [Commented] (QPID-5282) Sender timeouts may allow the peer to suffer an AMQFrameDecodingException
[
https://issues.apache.org/jira/browse/QPID-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831304#comment-13831304
]
ASF subversion and git services commented on QPID-5282:
---
Commit 1545184 from [~k-wall] in branch 'qpid/branches/0.26'
[ https://svn.apache.org/r1545184 ]
QPID-5282: Change IoSender to cause the socket to be closed after a sender
timeout.
Merged from trunk with the following command:
svn merge -c1543721 https://svn.apache.org/repos/asf/qpid/trunk/qpid
Sender timeouts may allow the peer to suffer an AMQFrameDecodingException
-
Key: QPID-5282
URL: https://issues.apache.org/jira/browse/QPID-5282
Project: Qpid
Issue Type: Bug
Components: Java Broker, Java Client, Java Common
Affects Versions: 0.25
Reporter: Keith Wall
Assignee: Alex Rudyy
Fix For: 0.27
If an IoSender#send suffers a timeout (IoSender.java#159) whilst awaiting
space in the sender's buffer, the socket which was being written to is left
open and a SenderException is thrown to the caller. The bytes that were to
be sent are lost. If the socket is subsequent written to again, the peer may
suffer an AMQFrameDecodingException as is tries to decode an incomplete
stream of data.
We saw this scenario in a support call. The working theory is that the
application'sJVM (using a JMS consumer) was under pressue, and this caused
TCP/IP back pressure to be felt by the broker. The Broker IoSender#send
method timed-out, but as the socket remained open, when a later message was
sent to the same JMS consumer application, the consuming application failed
with an AMQFrameDecodingException: the lost bytes meant it tried to process
message payload as if it were an AMQFrame.
The two exceptions of interest are (reproduced on trunk):
Broker side:
{code}
2013-10-31 14:41:18,471 ERROR [IoReceiver - /127.0.0.1:63867]
(v0_8.AMQProtocolEngine) - Error informing channel that receiving is
complete. Channel:
[/127.0.0.1:63867(guest):1]org.apache.qpid.transport.SenderException: write
timed out: -2147471360, -2147475456
at org.apache.qpid.transport.network.io.IoSender.send(IoSender.java:159)
at org.apache.qpid.transport.network.io.IoSender.send(IoSender.java:40)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.writeFrame(AMQProtocolEngine.java:689)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeFrame(ProtocolOutputConverterImpl.java:337)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:127)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:97)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeDeliver(ProtocolOutputConverterImpl.java:72)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$WriteDeliverMethod.deliverToClient(AMQProtocolEngine.java:1679)
at
org.apache.qpid.server.protocol.v0_8.SubscriptionImpl.sendToClient(SubscriptionImpl.java:693)
at
org.apache.qpid.server.protocol.v0_8.SubscriptionImpl$AckSubscription.send(SubscriptionImpl.java:303)
at
org.apache.qpid.server.queue.SimpleAMQQueue.deliverMessage(SimpleAMQQueue.java:826)
at
org.apache.qpid.server.queue.SimpleAMQQueue.deliverToSubscription(SimpleAMQQueue.java:745)
at
org.apache.qpid.server.queue.SimpleAMQQueue.enqueue(SimpleAMQQueue.java:693)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel$MessageDeliveryAction.postCommit(AMQChannel.java:1245)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel$AsyncCommand.complete(AMQChannel.java:1623)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel.sync(AMQChannel.java:1593)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel.receivedComplete(AMQChannel.java:218)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.receivedComplete(AMQProtocolEngine.java:324)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:304)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:104)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:131)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:47)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
at java.lang.Thread.run(Thread.java:662)
{code}
Then later client side:
{code}
2013-10-31 14:47:49,099 DEBUG [Dispatcher-1-Conn-1] [Dispatcher]
Dispatcher-1-Conn-1 thread terminating for channel
[jira] [Resolved] (QPID-5325) [Java Broker] Add ability to save web management console open tabs in user preferences
[ https://issues.apache.org/jira/browse/QPID-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-5325. -- Resolution: Fixed [Java Broker] Add ability to save web management console open tabs in user preferences -- Key: QPID-5325 URL: https://issues.apache.org/jira/browse/QPID-5325 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Alex Rudyy Assignee: Keith Wall Fix For: 0.25 Add ability to save web management console open tabs in user preferences -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5372) [Java Broker] An excessive amount of debug logging is generated for PreferencesProviderFactory when a Broker tab is opened in web management console
[
https://issues.apache.org/jira/browse/QPID-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall resolved QPID-5372.
--
Resolution: Fixed
Alex, those changes look reasonable to me. I think we should request for 0.26.
[Java Broker] An excessive amount of debug logging is generated for
PreferencesProviderFactory when a Broker tab is opened in web management
console
Key: QPID-5372
URL: https://issues.apache.org/jira/browse/QPID-5372
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.26, 0.27
Reporter: Alex Rudyy
Assignee: Keith Wall
Fix For: 0.27
An excessive amount of debug logging is generated for
PreferencesProviderFactory when a Broker tab is opened in web management
console:
{noformat}
2013-11-24 18:38:08,881 DEBUG [qtp943108539-62] (plugin.QpidServiceLoader) -
Found 1 implementations of interface
org.apache.qpid.server.plugin.PreferencesProviderFactory
2013-11-24 18:38:11,404 DEBUG [qtp943108539-53] (plugin.QpidServiceLoader) -
Found 1 implementations of interface
org.apache.qpid.server.plugin.PreferencesProviderFactory
2013-11-24 18:38:13,885 DEBUG [qtp943108539-53] (plugin.QpidServiceLoader) -
Found 1 implementations of interface
org.apache.qpid.server.plugin.PreferencesProviderFactory
2013-11-24 18:38:16,400 DEBUG [qtp943108539-53] (plugin.QpidServiceLoader) -
Found 1 implementations of interface
org.apache.qpid.server.plugin.PreferencesProviderFactory
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5282) Sender timeouts may allow the peer to suffer an AMQFrameDecodingException
[
https://issues.apache.org/jira/browse/QPID-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy closed QPID-5282.
Sender timeouts may allow the peer to suffer an AMQFrameDecodingException
-
Key: QPID-5282
URL: https://issues.apache.org/jira/browse/QPID-5282
Project: Qpid
Issue Type: Bug
Components: Java Broker, Java Client, Java Common
Affects Versions: 0.25
Reporter: Keith Wall
Assignee: Alex Rudyy
Fix For: 0.26, 0.27
If an IoSender#send suffers a timeout (IoSender.java#159) whilst awaiting
space in the sender's buffer, the socket which was being written to is left
open and a SenderException is thrown to the caller. The bytes that were to
be sent are lost. If the socket is subsequent written to again, the peer may
suffer an AMQFrameDecodingException as is tries to decode an incomplete
stream of data.
We saw this scenario in a support call. The working theory is that the
application'sJVM (using a JMS consumer) was under pressue, and this caused
TCP/IP back pressure to be felt by the broker. The Broker IoSender#send
method timed-out, but as the socket remained open, when a later message was
sent to the same JMS consumer application, the consuming application failed
with an AMQFrameDecodingException: the lost bytes meant it tried to process
message payload as if it were an AMQFrame.
The two exceptions of interest are (reproduced on trunk):
Broker side:
{code}
2013-10-31 14:41:18,471 ERROR [IoReceiver - /127.0.0.1:63867]
(v0_8.AMQProtocolEngine) - Error informing channel that receiving is
complete. Channel:
[/127.0.0.1:63867(guest):1]org.apache.qpid.transport.SenderException: write
timed out: -2147471360, -2147475456
at org.apache.qpid.transport.network.io.IoSender.send(IoSender.java:159)
at org.apache.qpid.transport.network.io.IoSender.send(IoSender.java:40)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.writeFrame(AMQProtocolEngine.java:689)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeFrame(ProtocolOutputConverterImpl.java:337)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:127)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:97)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeDeliver(ProtocolOutputConverterImpl.java:72)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$WriteDeliverMethod.deliverToClient(AMQProtocolEngine.java:1679)
at
org.apache.qpid.server.protocol.v0_8.SubscriptionImpl.sendToClient(SubscriptionImpl.java:693)
at
org.apache.qpid.server.protocol.v0_8.SubscriptionImpl$AckSubscription.send(SubscriptionImpl.java:303)
at
org.apache.qpid.server.queue.SimpleAMQQueue.deliverMessage(SimpleAMQQueue.java:826)
at
org.apache.qpid.server.queue.SimpleAMQQueue.deliverToSubscription(SimpleAMQQueue.java:745)
at
org.apache.qpid.server.queue.SimpleAMQQueue.enqueue(SimpleAMQQueue.java:693)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel$MessageDeliveryAction.postCommit(AMQChannel.java:1245)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel$AsyncCommand.complete(AMQChannel.java:1623)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel.sync(AMQChannel.java:1593)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel.receivedComplete(AMQChannel.java:218)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.receivedComplete(AMQProtocolEngine.java:324)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:304)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:104)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:131)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:47)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
at java.lang.Thread.run(Thread.java:662)
{code}
Then later client side:
{code}
2013-10-31 14:47:49,099 DEBUG [Dispatcher-1-Conn-1] [Dispatcher]
Dispatcher-1-Conn-1 thread terminating for channel
1:org.apache.qpid.client.AMQSession_0_8@560932fe
javax.jms.JMSException: Message consumer forcibly closed due to error:
org.apache.qpid.framing.AMQFrameDecodingException: End of frame marker not
found. Read 53 length=65527 type=3
at
org.apache.qpid.client.BasicMessageConsumer.returnMessageOrThrow(BasicMessageConsumer.java:531)
at
[jira] [Updated] (QPID-5282) Sender timeouts may allow the peer to suffer an AMQFrameDecodingException
[
https://issues.apache.org/jira/browse/QPID-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-5282:
-
Fix Version/s: 0.26
Sender timeouts may allow the peer to suffer an AMQFrameDecodingException
-
Key: QPID-5282
URL: https://issues.apache.org/jira/browse/QPID-5282
Project: Qpid
Issue Type: Bug
Components: Java Broker, Java Client, Java Common
Affects Versions: 0.25
Reporter: Keith Wall
Assignee: Alex Rudyy
Fix For: 0.26, 0.27
If an IoSender#send suffers a timeout (IoSender.java#159) whilst awaiting
space in the sender's buffer, the socket which was being written to is left
open and a SenderException is thrown to the caller. The bytes that were to
be sent are lost. If the socket is subsequent written to again, the peer may
suffer an AMQFrameDecodingException as is tries to decode an incomplete
stream of data.
We saw this scenario in a support call. The working theory is that the
application'sJVM (using a JMS consumer) was under pressue, and this caused
TCP/IP back pressure to be felt by the broker. The Broker IoSender#send
method timed-out, but as the socket remained open, when a later message was
sent to the same JMS consumer application, the consuming application failed
with an AMQFrameDecodingException: the lost bytes meant it tried to process
message payload as if it were an AMQFrame.
The two exceptions of interest are (reproduced on trunk):
Broker side:
{code}
2013-10-31 14:41:18,471 ERROR [IoReceiver - /127.0.0.1:63867]
(v0_8.AMQProtocolEngine) - Error informing channel that receiving is
complete. Channel:
[/127.0.0.1:63867(guest):1]org.apache.qpid.transport.SenderException: write
timed out: -2147471360, -2147475456
at org.apache.qpid.transport.network.io.IoSender.send(IoSender.java:159)
at org.apache.qpid.transport.network.io.IoSender.send(IoSender.java:40)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.writeFrame(AMQProtocolEngine.java:689)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeFrame(ProtocolOutputConverterImpl.java:337)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:127)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:97)
at
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeDeliver(ProtocolOutputConverterImpl.java:72)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$WriteDeliverMethod.deliverToClient(AMQProtocolEngine.java:1679)
at
org.apache.qpid.server.protocol.v0_8.SubscriptionImpl.sendToClient(SubscriptionImpl.java:693)
at
org.apache.qpid.server.protocol.v0_8.SubscriptionImpl$AckSubscription.send(SubscriptionImpl.java:303)
at
org.apache.qpid.server.queue.SimpleAMQQueue.deliverMessage(SimpleAMQQueue.java:826)
at
org.apache.qpid.server.queue.SimpleAMQQueue.deliverToSubscription(SimpleAMQQueue.java:745)
at
org.apache.qpid.server.queue.SimpleAMQQueue.enqueue(SimpleAMQQueue.java:693)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel$MessageDeliveryAction.postCommit(AMQChannel.java:1245)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel$AsyncCommand.complete(AMQChannel.java:1623)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel.sync(AMQChannel.java:1593)
at
org.apache.qpid.server.protocol.v0_8.AMQChannel.receivedComplete(AMQChannel.java:218)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.receivedComplete(AMQProtocolEngine.java:324)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:304)
at
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:104)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:131)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:47)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
at java.lang.Thread.run(Thread.java:662)
{code}
Then later client side:
{code}
2013-10-31 14:47:49,099 DEBUG [Dispatcher-1-Conn-1] [Dispatcher]
Dispatcher-1-Conn-1 thread terminating for channel
1:org.apache.qpid.client.AMQSession_0_8@560932fe
javax.jms.JMSException: Message consumer forcibly closed due to error:
org.apache.qpid.framing.AMQFrameDecodingException: End of frame marker not
found. Read 53 length=65527 type=3
at
org.apache.qpid.client.BasicMessageConsumer.returnMessageOrThrow(BasicMessageConsumer.java:531)
at
[jira] [Created] (QPID-5373) [Java Broker] SSL negotiation is being performed in the wrong thread
Robbie Gemmell created QPID-5373: Summary: [Java Broker] SSL negotiation is being performed in the wrong thread Key: QPID-5373 URL: https://issues.apache.org/jira/browse/QPID-5373 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.24 Environment: SSL negotiation is being performed in the accepting thread, which should ideally be used only for the minimal work of accepting the connecting and handing it off to another thread to process. This has been the case since support for SSL Client Certificate Authentication was added, as the code added to retrieve the remote peer is performed within the accepting thread, which forces the handshake to take place there. The handshake should be moved into another thread. Reporter: Robbie Gemmell -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5373) [Java Broker] SSL negotiation is being performed in the wrong thread
[ https://issues.apache.org/jira/browse/QPID-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-5373: - Environment: (was: SSL negotiation is being performed in the accepting thread, which should ideally be used only for the minimal work of accepting the connecting and handing it off to another thread to process. This has been the case since support for SSL Client Certificate Authentication was added, as the code added to retrieve the remote peer is performed within the accepting thread, which forces the handshake to take place there. The handshake should be moved into another thread.) [Java Broker] SSL negotiation is being performed in the wrong thread Key: QPID-5373 URL: https://issues.apache.org/jira/browse/QPID-5373 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.24 Reporter: Robbie Gemmell -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5373) [Java Broker] SSL negotiation is being performed in the accepting thread
[ https://issues.apache.org/jira/browse/QPID-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-5373: - Summary: [Java Broker] SSL negotiation is being performed in the accepting thread (was: [Java Broker] SSL negotiation is being performed in the wrong thread) [Java Broker] SSL negotiation is being performed in the accepting thread Key: QPID-5373 URL: https://issues.apache.org/jira/browse/QPID-5373 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.24 Reporter: Robbie Gemmell SSL negotiation is being performed in the accepting thread, which should ideally be used only for the minimal work of accepting the connecting and handing it off to another thread to process. This has been the case since support for SSL Client Certificate Authentication was added, as the code added to retrieve the remote peer is performed within the accepting thread, which forces the handshake to take place there. The handshake should be moved into another thread. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5373) [Java Broker] SSL negotiation is being performed in the wrong thread
[ https://issues.apache.org/jira/browse/QPID-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-5373: - Description: SSL negotiation is being performed in the accepting thread, which should ideally be used only for the minimal work of accepting the connecting and handing it off to another thread to process. This has been the case since support for SSL Client Certificate Authentication was added, as the code added to retrieve the remote peer is performed within the accepting thread, which forces the handshake to take place there. The handshake should be moved into another thread. [Java Broker] SSL negotiation is being performed in the wrong thread Key: QPID-5373 URL: https://issues.apache.org/jira/browse/QPID-5373 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.24 Reporter: Robbie Gemmell SSL negotiation is being performed in the accepting thread, which should ideally be used only for the minimal work of accepting the connecting and handing it off to another thread to process. This has been the case since support for SSL Client Certificate Authentication was added, as the code added to retrieve the remote peer is performed within the accepting thread, which forces the handshake to take place there. The handshake should be moved into another thread. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5037) [Java Broker- Web Management Console] Move log viewer into a separate tab and add abilities to download logs and filter log entries in the logs table
[ https://issues.apache.org/jira/browse/QPID-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831337#comment-13831337 ] Alex Rudyy commented on QPID-5037: -- Robbie, The clear filter confirmation dialog is only displayed when the are more then 4 non-empty filter conditions. If a user enters empty filter conditions in a filter dialog, those conditions are ignored and not accounted. I did a slight modification in a revision 1531965 to remove empty filter conditions when filter box is displayed again. [Java Broker- Web Management Console] Move log viewer into a separate tab and add abilities to download logs and filter log entries in the logs table - Key: QPID-5037 URL: https://issues.apache.org/jira/browse/QPID-5037 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Alex Rudyy Assignee: Alex Rudyy Fix For: 0.25 Move the log viewer functionality from the Broker tab to its own separate tab launched from the broker tab. Add the following functionality into log viewer: # Ability to download the log files # Ability for sorting, filtering # Use of colors to make more visual those rows which meet predefined conditions (e.g. WARN, ERROR messages) # Allow dynamic changing of displayed columns -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5037) [Java Broker- Web Management Console] Move log viewer into a separate tab and add abilities to download logs and filter log entries in the logs table
[ https://issues.apache.org/jira/browse/QPID-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-5037. -- Resolution: Fixed [Java Broker- Web Management Console] Move log viewer into a separate tab and add abilities to download logs and filter log entries in the logs table - Key: QPID-5037 URL: https://issues.apache.org/jira/browse/QPID-5037 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Alex Rudyy Assignee: Alex Rudyy Fix For: 0.25 Move the log viewer functionality from the Broker tab to its own separate tab launched from the broker tab. Add the following functionality into log viewer: # Ability to download the log files # Ability for sorting, filtering # Use of colors to make more visual those rows which meet predefined conditions (e.g. WARN, ERROR messages) # Allow dynamic changing of displayed columns -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Review Request 15788: [QMF] Issue compiler error on use of deprecated API
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15788/#review29372 --- Ship it! Ship It! - Chug Rolke On Nov. 22, 2013, 9:01 p.m., Kenneth Giusti wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15788/ --- (Updated Nov. 22, 2013, 9:01 p.m.) Review request for qpid, Andrew Stitcher, Gordon Sim, and Ted Ross. Bugs: qpid-5369 https://issues.apache.org/jira/browse/qpid-5369 Repository: qpid Description --- Causes any application that includes the QMF Agent or Console C++ headers to issue a compile-time error unless QMF_USE_DEPRECATED_API is defined by the application. The compiler error reads: In file included from /home/kgiusti/work/qpid/qpid/qpid/cpp/bindings/qmf2/examples/cpp/agent.cpp:22:0: /home/kgiusti/work/qpid/qpid/qpid/cpp/include/qmf/AgentSession.h:25:4: error: #error The API defined in this file has been DEPRECATED and will be removed in the future. /home/kgiusti/work/qpid/qpid/qpid/cpp/include/qmf/AgentSession.h:26:4: error: #error Define 'QMF_USE_DEPRECATED_API' to disable this error. Note: I'd like to propose this gets in for 0.26 - if you agree please comment as such on the JIRA, thanks. Diffs - /trunk/qpid/cpp/bindings/qmf2/examples/cpp/agent.cpp 1543123 /trunk/qpid/cpp/bindings/qmf2/examples/cpp/event_driven_list_agents.cpp 1543123 /trunk/qpid/cpp/bindings/qmf2/examples/cpp/list_agents.cpp 1543123 /trunk/qpid/cpp/bindings/qmf2/examples/cpp/print_events.cpp 1543123 /trunk/qpid/cpp/include/qmf/Agent.h 1543123 /trunk/qpid/cpp/include/qmf/AgentEvent.h 1543123 /trunk/qpid/cpp/include/qmf/AgentSession.h 1543123 /trunk/qpid/cpp/include/qmf/ConsoleEvent.h 1543123 /trunk/qpid/cpp/include/qmf/ConsoleSession.h 1543123 /trunk/qpid/cpp/include/qmf/Data.h 1543123 /trunk/qpid/cpp/include/qmf/DataAddr.h 1543123 /trunk/qpid/cpp/include/qmf/Handle.h 1543123 /trunk/qpid/cpp/include/qmf/Query.h 1543123 /trunk/qpid/cpp/include/qmf/Schema.h 1543123 /trunk/qpid/cpp/include/qmf/SchemaId.h 1543123 /trunk/qpid/cpp/include/qmf/SchemaMethod.h 1543123 /trunk/qpid/cpp/include/qmf/SchemaProperty.h 1543123 /trunk/qpid/cpp/include/qmf/SchemaTypes.h 1543123 /trunk/qpid/cpp/include/qmf/Subscription.h 1543123 /trunk/qpid/cpp/include/qmf/exceptions.h 1543123 /trunk/qpid/cpp/include/qmf/posix/EventNotifier.h 1543123 /trunk/qpid/cpp/include/qmf/qmf2.i 1543123 Diff: https://reviews.apache.org/r/15788/diff/ Testing --- Tested on windows (VS 2010) and linux (Fedora 18), both with and without QMF_USE_DEPRECATED_API defined. Thanks, Kenneth Giusti
[jira] [Commented] (QPID-5369) [qmf] Add deprecation warnings to the C++ Agent/Console API headers
[ https://issues.apache.org/jira/browse/QPID-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831494#comment-13831494 ] Chuck Rolke commented on QPID-5369: --- I approve this for 0.26. Without changing any functionality it makes any users well aware of the deprecation plan. [qmf] Add deprecation warnings to the C++ Agent/Console API headers --- Key: QPID-5369 URL: https://issues.apache.org/jira/browse/QPID-5369 Project: Qpid Issue Type: Wish Components: Qpid Managment Framework Affects Versions: 0.24 Reporter: Ken Giusti Assignee: Ken Giusti Fix For: 0.26 From the us...@qpid.apache.org mail thread: Hi All, I sent this email about a month ago with no replies to date. So I'd thought I'd re-ping the list. Is anyone using these libraries? If not, then I'd like to propose that we mark them as Deprecated in our upcoming 0.26 release. I volunteer adding the appropriate code warning directives to the build, so any code that attempts to include these APIs will issue deprecation warnings at compile time. We'll leave them available in the code for 0.26 (and I think at least one more release - Justin?), and if the warnings reveal a large user base, we can un-deprecate them. But in order to really stand behind this code, we'll have to invest some time in building unit tests for them. AFAIK, this stuff is not getting any test coverage right now. Opinions sought! thanks, -K - Original Message - From: Ken Giusti kgiu...@redhat.com To: us...@qpid.apache.org Sent: Thursday, October 17, 2013 1:51:32 PM Subject: Is anyone using the QMF C++ Agent and Console development libraries (libqmf2)? Hi All, Before I start investing time working on https://issues.apache.org/jira/browse/QPID-5226 and https://issues.apache.org/jira/browse/QPID-4981, I was wondering if anyone actually uses these C++ libraries. As far as I can tell, the code hasn't seen any serious development in over two years. That, and given that there are no unit tests run on that code (QPID-4981), I'm wondering if this code is actually being used. Please let me know, -K - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org -- -K -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-9) implement the JMS Message types and support for mapping them to/from AMQP messages
[ https://issues.apache.org/jira/browse/QPIDJMS-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831545#comment-13831545 ] ASF subversion and git services commented on QPIDJMS-9: --- Commit 1545320 from [~gemmellr] in branch 'jms/trunk' [ https://svn.apache.org/r1545320 ] QPIDJMS-9: add support for the durable header field in messages, ensure the producer sets/overrides this as necessary implement the JMS Message types and support for mapping them to/from AMQP messages -- Key: QPIDJMS-9 URL: https://issues.apache.org/jira/browse/QPIDJMS-9 Project: Qpid JMS Issue Type: Task Reporter: Robbie Gemmell Assignee: Robbie Gemmell implement the JMS message types and support for mapping them to/from AMQP messages -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5369) [qmf] Add deprecation warnings to the C++ Agent/Console API headers
[ https://issues.apache.org/jira/browse/QPID-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831559#comment-13831559 ] Justin Ross commented on QPID-5369: --- Reviewed by Chuck. Approved for 0.26. [qmf] Add deprecation warnings to the C++ Agent/Console API headers --- Key: QPID-5369 URL: https://issues.apache.org/jira/browse/QPID-5369 Project: Qpid Issue Type: Wish Components: Qpid Managment Framework Affects Versions: 0.24 Reporter: Ken Giusti Assignee: Ken Giusti Fix For: 0.26 From the us...@qpid.apache.org mail thread: Hi All, I sent this email about a month ago with no replies to date. So I'd thought I'd re-ping the list. Is anyone using these libraries? If not, then I'd like to propose that we mark them as Deprecated in our upcoming 0.26 release. I volunteer adding the appropriate code warning directives to the build, so any code that attempts to include these APIs will issue deprecation warnings at compile time. We'll leave them available in the code for 0.26 (and I think at least one more release - Justin?), and if the warnings reveal a large user base, we can un-deprecate them. But in order to really stand behind this code, we'll have to invest some time in building unit tests for them. AFAIK, this stuff is not getting any test coverage right now. Opinions sought! thanks, -K - Original Message - From: Ken Giusti kgiu...@redhat.com To: us...@qpid.apache.org Sent: Thursday, October 17, 2013 1:51:32 PM Subject: Is anyone using the QMF C++ Agent and Console development libraries (libqmf2)? Hi All, Before I start investing time working on https://issues.apache.org/jira/browse/QPID-5226 and https://issues.apache.org/jira/browse/QPID-4981, I was wondering if anyone actually uses these C++ libraries. As far as I can tell, the code hasn't seen any serious development in over two years. That, and given that there are no unit tests run on that code (QPID-4981), I'm wondering if this code is actually being used. Please let me know, -K - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org -- -K -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Review Request 15788: [QMF] Issue compiler error on use of deprecated API
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15788/#review29373 --- /trunk/qpid/cpp/include/qmf/Agent.h https://reviews.apache.org/r/15788/#comment56570 For the sake of DRY could you put these lines in qmf/ImportExport.h? It's not a blocking issue, my eye is just offended by so much repetition. /trunk/qpid/cpp/include/qmf/SchemaTypes.h https://reviews.apache.org/r/15788/#comment56571 Looks like this is the only block that doesn't precede an include of qmf/ImportExport.h, so perhaps move the error in there and replace this with #include qmf/ImportExport.h - Andrew Stitcher On Nov. 22, 2013, 9:01 p.m., Kenneth Giusti wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15788/ --- (Updated Nov. 22, 2013, 9:01 p.m.) Review request for qpid, Andrew Stitcher, Gordon Sim, and Ted Ross. Bugs: qpid-5369 https://issues.apache.org/jira/browse/qpid-5369 Repository: qpid Description --- Causes any application that includes the QMF Agent or Console C++ headers to issue a compile-time error unless QMF_USE_DEPRECATED_API is defined by the application. The compiler error reads: In file included from /home/kgiusti/work/qpid/qpid/qpid/cpp/bindings/qmf2/examples/cpp/agent.cpp:22:0: /home/kgiusti/work/qpid/qpid/qpid/cpp/include/qmf/AgentSession.h:25:4: error: #error The API defined in this file has been DEPRECATED and will be removed in the future. /home/kgiusti/work/qpid/qpid/qpid/cpp/include/qmf/AgentSession.h:26:4: error: #error Define 'QMF_USE_DEPRECATED_API' to disable this error. Note: I'd like to propose this gets in for 0.26 - if you agree please comment as such on the JIRA, thanks. Diffs - /trunk/qpid/cpp/bindings/qmf2/examples/cpp/agent.cpp 1543123 /trunk/qpid/cpp/bindings/qmf2/examples/cpp/event_driven_list_agents.cpp 1543123 /trunk/qpid/cpp/bindings/qmf2/examples/cpp/list_agents.cpp 1543123 /trunk/qpid/cpp/bindings/qmf2/examples/cpp/print_events.cpp 1543123 /trunk/qpid/cpp/include/qmf/Agent.h 1543123 /trunk/qpid/cpp/include/qmf/AgentEvent.h 1543123 /trunk/qpid/cpp/include/qmf/AgentSession.h 1543123 /trunk/qpid/cpp/include/qmf/ConsoleEvent.h 1543123 /trunk/qpid/cpp/include/qmf/ConsoleSession.h 1543123 /trunk/qpid/cpp/include/qmf/Data.h 1543123 /trunk/qpid/cpp/include/qmf/DataAddr.h 1543123 /trunk/qpid/cpp/include/qmf/Handle.h 1543123 /trunk/qpid/cpp/include/qmf/Query.h 1543123 /trunk/qpid/cpp/include/qmf/Schema.h 1543123 /trunk/qpid/cpp/include/qmf/SchemaId.h 1543123 /trunk/qpid/cpp/include/qmf/SchemaMethod.h 1543123 /trunk/qpid/cpp/include/qmf/SchemaProperty.h 1543123 /trunk/qpid/cpp/include/qmf/SchemaTypes.h 1543123 /trunk/qpid/cpp/include/qmf/Subscription.h 1543123 /trunk/qpid/cpp/include/qmf/exceptions.h 1543123 /trunk/qpid/cpp/include/qmf/posix/EventNotifier.h 1543123 /trunk/qpid/cpp/include/qmf/qmf2.i 1543123 Diff: https://reviews.apache.org/r/15788/diff/ Testing --- Tested on windows (VS 2010) and linux (Fedora 18), both with and without QMF_USE_DEPRECATED_API defined. Thanks, Kenneth Giusti
[jira] [Commented] (QPID-5330) Queue flow limit tests try to invoke a missing qpid-python-test
[ https://issues.apache.org/jira/browse/QPID-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831629#comment-13831629 ] Justin Ross commented on QPID-5330: --- Typo fix reviewed by me. Approved for 0.26. Queue flow limit tests try to invoke a missing qpid-python-test --- Key: QPID-5330 URL: https://issues.apache.org/jira/browse/QPID-5330 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.25 Reporter: Justin Ross Assignee: Andrew Stitcher Fix For: 0.25 This is from testing a release tarball. I believe this test should avoid running if it can't find qpid-python-test. 25/54 Testing: queue_flow_limit_tests 25/54 Test: queue_flow_limit_tests Command: /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/src/tests/run_test --build-dir=/tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/build --start-broker --broker-options=--default-flow-stop-threshold=80 --default-flow-resume-thre\ shold=70 -t --log-to-stderr=no --log-to-stdout=no /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/src/tests/run_queue_flow_limit_tests Directory: /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/build/src/tests queue_flow_limit_tests start time: Nov 09 19:51 EST Output: -- /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/src/tests/run_queue_flow_limit_tests: line 24: /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/build/src/tests/python/commands/qpid-python-test: No such file or directory end of output Test time = 3.96 sec -- Test Failed. queue_flow_limit_tests end time: Nov 09 19:51 EST queue_flow_limit_tests time elapsed: 00:00:03 -- -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5330) Queue flow limit tests try to invoke a missing qpid-python-test
[ https://issues.apache.org/jira/browse/QPID-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831634#comment-13831634 ] ASF subversion and git services commented on QPID-5330: --- Commit 1545346 from [~astitcher] in branch 'qpid/branches/0.26' [ https://svn.apache.org/r1545346 ] QPID-5330: Typo in original checkin [Original SVN change: https://svn.apache.org/repos/asf/qpid/trunk@1541765] Queue flow limit tests try to invoke a missing qpid-python-test --- Key: QPID-5330 URL: https://issues.apache.org/jira/browse/QPID-5330 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.25 Reporter: Justin Ross Assignee: Andrew Stitcher Fix For: 0.25 This is from testing a release tarball. I believe this test should avoid running if it can't find qpid-python-test. 25/54 Testing: queue_flow_limit_tests 25/54 Test: queue_flow_limit_tests Command: /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/src/tests/run_test --build-dir=/tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/build --start-broker --broker-options=--default-flow-stop-threshold=80 --default-flow-resume-thre\ shold=70 -t --log-to-stderr=no --log-to-stdout=no /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/src/tests/run_queue_flow_limit_tests Directory: /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/build/src/tests queue_flow_limit_tests start time: Nov 09 19:51 EST Output: -- /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/src/tests/run_queue_flow_limit_tests: line 24: /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/build/src/tests/python/commands/qpid-python-test: No such file or directory end of output Test time = 3.96 sec -- Test Failed. queue_flow_limit_tests end time: Nov 09 19:51 EST queue_flow_limit_tests time elapsed: 00:00:03 -- -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5369) [qmf] Add deprecation warnings to the C++ Agent/Console API headers
[ https://issues.apache.org/jira/browse/QPID-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831756#comment-13831756 ] ASF subversion and git services commented on QPID-5369: --- Commit 1545368 from [~kgiusti] in branch 'qpid/trunk' [ https://svn.apache.org/r1545368 ] QPID-5369: Issue compile-time error if deprecated QMF Agent or Console API used by applications [qmf] Add deprecation warnings to the C++ Agent/Console API headers --- Key: QPID-5369 URL: https://issues.apache.org/jira/browse/QPID-5369 Project: Qpid Issue Type: Wish Components: Qpid Managment Framework Affects Versions: 0.24 Reporter: Ken Giusti Assignee: Ken Giusti Fix For: 0.26 From the us...@qpid.apache.org mail thread: Hi All, I sent this email about a month ago with no replies to date. So I'd thought I'd re-ping the list. Is anyone using these libraries? If not, then I'd like to propose that we mark them as Deprecated in our upcoming 0.26 release. I volunteer adding the appropriate code warning directives to the build, so any code that attempts to include these APIs will issue deprecation warnings at compile time. We'll leave them available in the code for 0.26 (and I think at least one more release - Justin?), and if the warnings reveal a large user base, we can un-deprecate them. But in order to really stand behind this code, we'll have to invest some time in building unit tests for them. AFAIK, this stuff is not getting any test coverage right now. Opinions sought! thanks, -K - Original Message - From: Ken Giusti kgiu...@redhat.com To: us...@qpid.apache.org Sent: Thursday, October 17, 2013 1:51:32 PM Subject: Is anyone using the QMF C++ Agent and Console development libraries (libqmf2)? Hi All, Before I start investing time working on https://issues.apache.org/jira/browse/QPID-5226 and https://issues.apache.org/jira/browse/QPID-4981, I was wondering if anyone actually uses these C++ libraries. As far as I can tell, the code hasn't seen any serious development in over two years. That, and given that there are no unit tests run on that code (QPID-4981), I'm wondering if this code is actually being used. Please let me know, -K - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org -- -K -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5346) qpid-0.24 static libraries
[ https://issues.apache.org/jira/browse/QPID-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831850#comment-13831850 ] sprasad commented on QPID-5346: --- Any suggestions ? qpid-0.24 static libraries -- Key: QPID-5346 URL: https://issues.apache.org/jira/browse/QPID-5346 Project: Qpid Issue Type: Bug Components: Build Tools Affects Versions: 0.24 Reporter: sprasad Hi, It looks like qpid-0.24 build (linux) using cmake only generate shared libraries ( *.so). Let me know if static libraries build is supported on linux using cmake? Thanks -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4853) Connectors are not closed when connections are closed cleanly
[ https://issues.apache.org/jira/browse/QPID-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-4853. Resolution: Duplicate Connectors are not closed when connections are closed cleanly - Key: QPID-4853 URL: https://issues.apache.org/jira/browse/QPID-4853 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Priority: Blocker When a connection is closed cleanly by a client, the pn_connector_closed condition never occurs and the connector is not closed. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4611) Dispatch - Pause/Resume broken when invoked from non-server thread
[ https://issues.apache.org/jira/browse/QPID-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated QPID-4611: --- Priority: Trivial (was: Major) Dispatch - Pause/Resume broken when invoked from non-server thread -- Key: QPID-4611 URL: https://issues.apache.org/jira/browse/QPID-4611 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Priority: Trivial If an application starts Dispatch Server using dx_server_start (i.e. the non-blocking start method), the main thread cannot be used to invoke dx_server_pause/dx_server_resume. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5346) qpid-0.24 static libraries
[ https://issues.apache.org/jira/browse/QPID-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831975#comment-13831975 ] Darryl L. Pierce commented on QPID-5346: Hi, no currently the build system only producings shared libraries and not static libraries. qpid-0.24 static libraries -- Key: QPID-5346 URL: https://issues.apache.org/jira/browse/QPID-5346 Project: Qpid Issue Type: Bug Components: Build Tools Affects Versions: 0.24 Reporter: sprasad Hi, It looks like qpid-0.24 build (linux) using cmake only generate shared libraries ( *.so). Let me know if static libraries build is supported on linux using cmake? Thanks -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5346) qpid-0.24 static libraries
[ https://issues.apache.org/jira/browse/QPID-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832004#comment-13832004 ] Chuck Rolke commented on QPID-5346: --- Static link libraries have come up before but never had enough demand to make them happen, https://issues.apache.org/jira/browse/QPID-2259 qpid-0.24 static libraries -- Key: QPID-5346 URL: https://issues.apache.org/jira/browse/QPID-5346 Project: Qpid Issue Type: Bug Components: Build Tools Affects Versions: 0.24 Reporter: sprasad Hi, It looks like qpid-0.24 build (linux) using cmake only generate shared libraries ( *.so). Let me know if static libraries build is supported on linux using cmake? Thanks -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5374) Contribute java client docbook for 0-8..-0-9-1
Keith Wall created QPID-5374: Summary: Contribute java client docbook for 0-8..-0-9-1 Key: QPID-5374 URL: https://issues.apache.org/jira/browse/QPID-5374 Project: Qpid Issue Type: Improvement Components: Documentation Reporter: Keith Wall Assignee: Keith Wall We have a significant number of users utilising the Java client with the 0-8..0-9-1 protocols but unfortunately have no good documentation. It is felt the many behavioural differences between the java client when used with 0-10 and java client when used with 0-8..0-9-1 make a single consolidated docbook impractical. There would just be too many sentences beginning 'when using 0-10...', 'if using 0-8..0-9-1' etc and this would make the document unwieldy for both user groups. As a tactical step, this Jira will produce a separate docbook targeted for java client 0-8..0-9-1 only. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5374) Contribute java client docbook for 0-8..-0-9-1
[ https://issues.apache.org/jira/browse/QPID-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832043#comment-13832043 ] Keith Wall commented on QPID-5374: -- Uploaded WIP patches from Alex and me. Contribute java client docbook for 0-8..-0-9-1 -- Key: QPID-5374 URL: https://issues.apache.org/jira/browse/QPID-5374 Project: Qpid Issue Type: Improvement Components: Documentation Reporter: Keith Wall Assignee: Keith Wall Attachments: 0001-QPID-5374-i-Add-documentation-for-Qpid-AMQP-0-9-0-9-.patch, 0002-QPID-5374-Understandig-client-chapter-added-sections.patch We have a significant number of users utilising the Java client with the 0-8..0-9-1 protocols but unfortunately have no good documentation. It is felt the many behavioural differences between the java client when used with 0-10 and java client when used with 0-8..0-9-1 make a single consolidated docbook impractical. There would just be too many sentences beginning 'when using 0-10...', 'if using 0-8..0-9-1' etc and this would make the document unwieldy for both user groups. As a tactical step, this Jira will produce a separate docbook targeted for java client 0-8..0-9-1 only. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5374) Contribute java client docbook for 0-8..-0-9-1
[ https://issues.apache.org/jira/browse/QPID-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-5374: - Attachment: 0002-QPID-5374-Understandig-client-chapter-added-sections.patch 0001-QPID-5374-i-Add-documentation-for-Qpid-AMQP-0-9-0-9-.patch Contribute java client docbook for 0-8..-0-9-1 -- Key: QPID-5374 URL: https://issues.apache.org/jira/browse/QPID-5374 Project: Qpid Issue Type: Improvement Components: Documentation Reporter: Keith Wall Assignee: Keith Wall Attachments: 0001-QPID-5374-i-Add-documentation-for-Qpid-AMQP-0-9-0-9-.patch, 0002-QPID-5374-Understandig-client-chapter-added-sections.patch We have a significant number of users utilising the Java client with the 0-8..0-9-1 protocols but unfortunately have no good documentation. It is felt the many behavioural differences between the java client when used with 0-10 and java client when used with 0-8..0-9-1 make a single consolidated docbook impractical. There would just be too many sentences beginning 'when using 0-10...', 'if using 0-8..0-9-1' etc and this would make the document unwieldy for both user groups. As a tactical step, this Jira will produce a separate docbook targeted for java client 0-8..0-9-1 only. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
