[jira] [Resolved] (DISPATCH-1104) qdstat --log log levels are wrong
[
https://issues.apache.org/jira/browse/DISPATCH-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke resolved DISPATCH-1104.
---
Resolution: Fixed
Fix Version/s: 1.4.0
Fixed at Commit 385bbe9
> qdstat --log log levels are wrong
> -
>
> Key: DISPATCH-1104
> URL: https://issues.apache.org/jira/browse/DISPATCH-1104
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tools
>Affects Versions: 1.3.0
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 1.4.0
>
>
> From a log file:
> {{2018-08-16 09:52:25.964494 -0400 SERVER (info) Container Name: log-log}}
> {{2018-08-16 09:52:25.978344 -0400 SERVER (notice) Operational, 4 Threads
> Running (process ID 27166)}}
> {{2018-08-16 09:52:25.978371 -0400 SERVER (info) Running in DEBUG Mode}}
> {{2018-08-16 09:52:25.978506 -0400 SERVER (notice) Listening on 0.0.0.0:amqp}}
> {{2018-08-16 09:52:40.180461 -0400 SERVER (trace) Accepting connection on
> 0.0.0.0:amqp}}
> {{From qdstat --log:}}
> {{Thu Aug 16 09:52:25 2018 SERVER (info) Container Name: log-log}}
> {{Thu Aug 16 09:52:25 2018 SERVER (critical) Operational, 4 Threads Running
> (process ID 27166)}}
> {{Thu Aug 16 09:52:25 2018 SERVER (info) Running in DEBUG Mode}}
> {{Thu Aug 16 09:52:25 2018 SERVER (critical) Listening on 0.0.0.0:amqp}}
> {{Thu Aug 16 09:52:40 2018 SERVER (none) Accepting connection on
> 0.0.0.0:amqp}}
--
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] (DISPATCH-1104) qdstat --log log levels are wrong
[
https://issues.apache.org/jira/browse/DISPATCH-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582891#comment-16582891
]
ASF subversion and git services commented on DISPATCH-1104:
---
Commit 385bbe9ebe69cf567b4e88d016d5eaca38ce73d2 in qpid-dispatch's branch
refs/heads/master from [~chug]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=385bbe9 ]
DISPATCH-1104: use correct log level names for qdstat GET-LOG
Convert mask bit to index for referencing name table.
Qdstat level names in tests now match what is in system log file.
> qdstat --log log levels are wrong
> -
>
> Key: DISPATCH-1104
> URL: https://issues.apache.org/jira/browse/DISPATCH-1104
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tools
>Affects Versions: 1.3.0
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
>
> From a log file:
> {{2018-08-16 09:52:25.964494 -0400 SERVER (info) Container Name: log-log}}
> {{2018-08-16 09:52:25.978344 -0400 SERVER (notice) Operational, 4 Threads
> Running (process ID 27166)}}
> {{2018-08-16 09:52:25.978371 -0400 SERVER (info) Running in DEBUG Mode}}
> {{2018-08-16 09:52:25.978506 -0400 SERVER (notice) Listening on 0.0.0.0:amqp}}
> {{2018-08-16 09:52:40.180461 -0400 SERVER (trace) Accepting connection on
> 0.0.0.0:amqp}}
> {{From qdstat --log:}}
> {{Thu Aug 16 09:52:25 2018 SERVER (info) Container Name: log-log}}
> {{Thu Aug 16 09:52:25 2018 SERVER (critical) Operational, 4 Threads Running
> (process ID 27166)}}
> {{Thu Aug 16 09:52:25 2018 SERVER (info) Running in DEBUG Mode}}
> {{Thu Aug 16 09:52:25 2018 SERVER (critical) Listening on 0.0.0.0:amqp}}
> {{Thu Aug 16 09:52:40 2018 SERVER (none) Accepting connection on
> 0.0.0.0:amqp}}
--
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] (QPIDJMS-411) Improve out of the the frame tracing loggers to include the binary payload
[ https://issues.apache.org/jira/browse/QPIDJMS-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-411. -- Resolution: Fixed > Improve out of the the frame tracing loggers to include the binary payload > -- > > Key: QPIDJMS-411 > URL: https://issues.apache.org/jira/browse/QPIDJMS-411 > Project: Qpid JMS > Issue Type: Improvement > Components: qpid-jms-client >Affects Versions: 0.36.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 0.37.0 > > > When the 'amqp.traceFrames' option is enabled the tracing only includes the > TransportFrame content and not the optional payload data. Improve this > logging to include a string formatted representation of the payload data. -- 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] (QPIDJMS-411) Improve out of the the frame tracing loggers to include the binary payload
[ https://issues.apache.org/jira/browse/QPIDJMS-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582799#comment-16582799 ] ASF subversion and git services commented on QPIDJMS-411: - Commit b1b417ed8b4dfac096872cf2706e33282f1a064e in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=b1b417e ] QPIDJMS-411 Improve output of amqp.traceFrames with payload Output payload as formatted string with truncation (configuration of length added). > Improve out of the the frame tracing loggers to include the binary payload > -- > > Key: QPIDJMS-411 > URL: https://issues.apache.org/jira/browse/QPIDJMS-411 > Project: Qpid JMS > Issue Type: Improvement > Components: qpid-jms-client >Affects Versions: 0.36.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 0.37.0 > > > When the 'amqp.traceFrames' option is enabled the tracing only includes the > TransportFrame content and not the optional payload data. Improve this > logging to include a string formatted representation of the payload data. -- 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
[GitHub] qpid-proton pull request #153: support libressl
Github user archerabi closed the pull request at: https://github.com/apache/qpid-proton/pull/153 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #153: support libressl
GitHub user archerabi opened a pull request: https://github.com/apache/qpid-proton/pull/153 support libressl You can merge this pull request into a Git repository by running: $ git pull https://github.com/better/qpid-proton libressl Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/153.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #153 commit ceb0523f00caf77b71027abf8d0cabe7133fdcca Author: Abhijith Reddy Date: 2018-08-16T15:02:10Z support libressl --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDJMS-411) Improve out of the the frame tracing loggers to include the binary payload
Timothy Bish created QPIDJMS-411: Summary: Improve out of the the frame tracing loggers to include the binary payload Key: QPIDJMS-411 URL: https://issues.apache.org/jira/browse/QPIDJMS-411 Project: Qpid JMS Issue Type: Improvement Components: qpid-jms-client Affects Versions: 0.36.0 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 0.37.0 When the 'amqp.traceFrames' option is enabled the tracing only includes the TransportFrame content and not the optional payload data. Improve this logging to include a string formatted representation of the payload data. -- 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] (DISPATCH-1104) qdstat --log log levels are wrong
Chuck Rolke created DISPATCH-1104:
-
Summary: qdstat --log log levels are wrong
Key: DISPATCH-1104
URL: https://issues.apache.org/jira/browse/DISPATCH-1104
Project: Qpid Dispatch
Issue Type: Bug
Components: Tools
Affects Versions: 1.3.0
Reporter: Chuck Rolke
Assignee: Chuck Rolke
>From a log file:
{{2018-08-16 09:52:25.964494 -0400 SERVER (info) Container Name: log-log}}
{{2018-08-16 09:52:25.978344 -0400 SERVER (notice) Operational, 4 Threads
Running (process ID 27166)}}
{{2018-08-16 09:52:25.978371 -0400 SERVER (info) Running in DEBUG Mode}}
{{2018-08-16 09:52:25.978506 -0400 SERVER (notice) Listening on 0.0.0.0:amqp}}
{{2018-08-16 09:52:40.180461 -0400 SERVER (trace) Accepting connection on
0.0.0.0:amqp}}
{{From qdstat --log:}}
{{Thu Aug 16 09:52:25 2018 SERVER (info) Container Name: log-log}}
{{Thu Aug 16 09:52:25 2018 SERVER (critical) Operational, 4 Threads Running
(process ID 27166)}}
{{Thu Aug 16 09:52:25 2018 SERVER (info) Running in DEBUG Mode}}
{{Thu Aug 16 09:52:25 2018 SERVER (critical) Listening on 0.0.0.0:amqp}}
{{Thu Aug 16 09:52:40 2018 SERVER (none) Accepting connection on 0.0.0.0:amqp}}
--
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] (QPIDJMS-409) JMS Scheduled Delivery delivers messages before time under load
[
https://issues.apache.org/jira/browse/QPIDJMS-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582539#comment-16582539
]
Timothy Bish commented on QPIDJMS-409:
--
There isn't quite enough to go on in the logs provided, could you ensure that
the ENV var PN_TRACE_FRM is set to "true". Also a reproducer will go a lot
further in finding out what is going on as otherwise we are just guessing.
> JMS Scheduled Delivery delivers messages before time under load
> ---
>
> Key: QPIDJMS-409
> URL: https://issues.apache.org/jira/browse/QPIDJMS-409
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.35.0
> Environment: Application is a Spring Boot application - version
> 2.0.4.RELEASE
> Qpid JMS Client version is 0.35.0
> Operating system where problem occurs is Windows 10
> I have found this problem using the following different message brokers:
> * Apache Artemis 2.4.0
> * Apache Artemis 2.6.2
> * Apache Qpid Broker 7.0.6
>Reporter: Ian Rowlands
>Priority: Major
> Attachments: successful_delayed_delivery.txt
>
>
> When under system load, the Qpid JMS client doesn't handle scheduled message
> delivery correct - it delivers the message prior to the required time.
> When running one request, the scheduling works correctly. The load to
> reproduce this isn't very high (i.e running about 5 of my job processes
> simultaneously seems to trip it up pretty quickly).
> I have used different JMS Brokers with the same client code and the same
> problem occurs with both Brokers (see environment).
> I am using Spring JMS Template to send the JMS message. The key piece of code
> is something like:
> {{delayedDeliveryjmsTemplate.setDeliveryDelay(timeoutPeriod);}}
> {{delayedDeliveryjmsTemplate.convertAndSend(queueName, timeoutMsg, (Message
> jmsMessage) -> {}}
> {{ jmsMessage.setStringProperty(OBJECT_TYPE_FIELD,
> timeoutMsg.getClass().getSimpleName());}}
> {{jmsMessage.setStringProperty(OBJECT_TYPE_FIELD,
> timeoutMsg.getClass().getSimpleName());}}
> {{ return jmsMessage;}}
> {{});}}
> I realise you want more logging details but I'm unsure what would be best to
> log. Please let me know and I'll do so.
>
>
--
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
