ds,
> Daniil Kirilyuk
>
> On Tue, 24 Oct 2023 at 14:47, Adrian Pasternak
> wrote:
> >
> > Hi,
> >
> > We are using qpid-broker-j version 9.1.0 as a dependency in our project.
> >
> > It seems that just adding qpid-broker as a dependency:
> >
org.apache.qpid
> qpid-broker
> 9.1.0
>
>
> Disables all logback logging in our application.
>
> I've debugged logback and found out that this behavior might be caused by a
> change:
> https://github.com/apache/qpid-broker-j/blame/9.1.0/broker-plugins/lo
Hi,
We are using qpid-broker-j version 9.1.0 as a dependency in our project.
It seems that just adding qpid-broker as a dependency:
org.apache.qpid
qpid-broker
9.1.0
Disables all logback logging in our application.
I've debugged logback and found out that this behavior mig
You can configure the logging levels depending on what logging
implementation you are using. Sounds like you have it at info. To be
honest though, the client generally does not print all the
headers/properties/body etc so even then you probably wont get what
you want.
Make sure the PN_TRACE_FRM
general-q-QueueLookup=
Currently, this is the only message that I see in the weblogic log:
Connection ID:6147a0e7-1870-4a1a-8dd5-bd7102fc1aa4:106 connected to server:
amqps://
I am looking for a way to get more detail, like debug or verbose level logging,
of a message send. Ideally, want to se
I can't find an example on how to access the intern logging of the proton
library from c++.
The API for proton c does have a chapter for logging.
How can I do this?
Thanks.
To be clear, this isnt simply some regular logging done at trace level
but rather a low-level protocol-frame log that's only enabled and
output at trace level upon express request, which you have.
It would have to parse the wire payload to obfuscate it, which the
bits doing this simply
Hi Team,
We are using qpid-jms-client-57.0 to receive message from ServiceBus. We
need to enable TRACE level logging for issue identification.
While enabling TRACE level logging, we realized that credentials are getting
logged at TRACE level which is a security breach.
Can I request you to
Thanks Alex!
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
Thanks Alex.
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
Hi Brian,
The supported file logger attributes can be found in the "API
Documentation". The link to API documentation is available from the top
horizontal menu in the Web Management Console.
The supported attributes are
maxFileSize number read/write
compressOldFiles boolean read/write
rollDaily b
Hi!
I want to configure things like max file size and add compression via the
Broker J JSON config. Looking at the source, I tried to guess what the
attribute names would be. Is this right?
"brokerloggers" : [ {
"name" : "logfile",
"type" : "File",
"maxFileSize" : 50,
"maxHistory
Hello!
I’m having an issue starting up qpid due to conflicting loggers. Specifically,
this explicit cast is throwing errors
https://github.com/apache/qpid-broker-j/blob/6.1.x/broker/src/main/java/org/apache/qpid/server/Broker.java#L147-L148.
Is there anyway to override this or bypass logging
sufficient to
identify a thread over a period of time). Other than that, it also helps us
align with the logging that we do at our product level, and the tooling
that we have to log mine (which works by thread Id).
I will try to use customConversionSpecifier.
Thanks
Ramayan
On Mon, Apr 3, 2017 at 4
Hi Ramayan,
Sorry, I might have been partially mistaken in my previous response.
No two threads should have the same name at the same time.
If that would be the case that would be a bug.
However, it is possible that a thread switches names and assumes a name
a different thread held previously.
Hi,
I have not tried this before but a quick web search suggests [1, 2] you
could achieve this by means of a custom converter.
Regarding Houskeeping threads sharing the same name, on trunk this
should no longer be the case.
If you encounter other thread pools with this behaviour please flag it
Hi All,
After looking logback's PatternLayout, I don't think its possible to log
thread id by simply supplying a pattern for it. Has anyone looked into ways
to achieve it?
I would like to have thread ids in the log lines as well, since it appears
to be me that same thread name gets assigned for m
Thanks for the answer Rob,
actually I expected to get the same logging as in JMS client 0.9 or 0.10
(done with sfl4j).
The protocol logging in JMS client 1.0 is better than nothing but the
previous logging contained more information.
Regards,
Erik
2014-07-20 17:21 GMT+02:00 Rob Godfrey
Thank you for the answer Rob,
actually I expected to get the same logging as in JMS client 0.9 or 0.10 (done
with sfl4j).
The protocol logging in JMS client 1.0 is better than nothing but the previous
logging contained much more information.
E.g. correlationId and userId of the received and send
The JMS 1.0 client does have some AMQP protocol logging, for which it uses
java.util.logging...
See
http://mail-archives.apache.org/mod_mbox/qpid-users/201402.mbox/%3CCACsaS94QyZbYrScWNtChgk=gn3ojdzgsl5sk5rrnvoj9izj...@mail.gmail.com%3E
for an example of how to turn that logging on.
Is this the
Hi there,
in Qpid JMS AMQP 0.9 and 0.10 there was slf4j which could be used to get
logging information from the JMS client.
In 1.0 there is no logging at all. Will it be included again?
Regards,
Erik
Hi Andreas,
In release 0.28 full client logging-control was included.
See https://reviews.apache.org/r/16316/
Examples of the controls available are in the "View Diff", file
src/tests/MessagingLogger.cpp
If you are running an older release try to apply this patch and use thi
Hi All,
Sometimes I find it very useful to switch the client api logging on.
The user interface is powerful but also not too comfortable.
So what about providing a little interface for easy usage as an example
in the next Qpid release?
Maybe something like this header file QpidApiLogger.h
https://issues.apache.org/jira/browse/DISPATCH-50 has a patch ready for
review.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
Some months ago we deprecated (and removed) all the qpid::client and
associated code from the header files exposed for application use.
One capability we removed was that of being able to control the internal
logging that qpid does. Since qpid is being embedded in some other
application
On 04/16/2012 01:29 PM, Todd Herman wrote:
I am using Windows and don't know what "export" is.
Oops, sorry! I missed the obvious there :-)
I did, however, already setup the log enable environment variable and that
didn't seem to do anything. Does anyone have any other suggestions?
Since y
On Mon, Apr 16, 2012 at 12:29:51PM +, Todd Herman wrote:
> I am using Windows and don't know what "export" is.
For windows it would be:
set QPID_LOG_ENABLE="info+"
See, as an example, the file qpid-server.bat in the distribution source.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat,
e. 510 | Herndon, VA 20171
m: 703-489-8761 | www.apx-labs.com | @APXLabs
-Original Message-
From: Gordon Sim [mailto:g...@redhat.com]
Sent: Monday, April 16, 2012 4:09 AM
To: users@qpid.apache.org
Subject: Re: turn on logging in qpid c++ client
On 04/16/2012 03:26 AM, Todd Herman wrote
On 04/16/2012 03:26 AM, Todd Herman wrote:
I have a service that I wrote in C#. It is using the dotnet binding for the
c++ qpid client. I have logging in my application that logs what is going on.
Ion the conneciton object, I have turned on AutoReconnect. When my code tries
to connect but
I have a service that I wrote in C#. It is using the dotnet binding for the
c++ qpid client. I have logging in my application that logs what is going on.
Ion the conneciton object, I have turned on AutoReconnect. When my code tries
to connect but can't, my code appears to hang. The
On 09/16/2011 09:41 AM, Alan Conway wrote:
>
> In general qpidd is not designed to re-set configuration on the fly.
> Resetting log levels would be straightforward. I'm not sure about ACL.
> Include it in the JIRA and we'll see what can be done.
ACL can be reset on the fly.
place a new ACL file
On 09/15/2011 11:54 AM, Alex Kulyavtsev wrote:
On Sep 15, 2011, at 8:24 AM, Alan Conway wrote:
Not presently, qpidd ignores SIGHUP. Open a JIRA for this, with details of
what you want qpidd to do on SIGUP.
Besides switching logs, can it be done qpidd will re-read qpidd.conf and acl
files to a
On Thu, Sep 15, 2011 at 10:54:16AM -0500, Alex Kulyavtsev wrote:
> On Sep 15, 2011, at 8:24 AM, Alan Conway wrote:
>
> >Not presently, qpidd ignores SIGHUP. Open a JIRA for this, with
> >details of what you want qpidd to do on SIGUP.
>
> Besides switching logs, can it be done qpidd will re-read q
On Sep 15, 2011, at 8:24 AM, Alan Conway wrote:
Not presently, qpidd ignores SIGHUP. Open a JIRA for this, with
details of what you want qpidd to do on SIGUP.
Besides switching logs, can it be done qpidd will re-read qpidd.conf
and acl files to avoid restart when configuration changed?
Thin
On 09/13/2011 09:58 AM, Bradley Scalio wrote:
Thanks for the great turnaround!
One final question then on logging. With logrotate usually a postrotate sighup
on the pidfile will cause the process to then write to the new logs, but this
isn't working either for qpid when running in daemon
Thanks for the great turnaround!
One final question then on logging. With logrotate usually a postrotate
sighup on the pidfile will cause the process to then write to the new
logs, but this isn't working either for qpid when running in daemon mode:
compress
/var/log/qpid
On 09/13/2011 08:28 AM, Bradley Scalio wrote:
Greetings,
Trying to turn off logging to /var/log/messages and send qpidd logging to
/var/log/qpidd.log
I tried the following in our qpidd.conf:
sed -i '$a log-to-file=/var/log/qpidd.log' qpidd.conf
sed -i '$a log-to-syslog=no
gards,
Pavel Moravec
GSS SEG
Red Hat
- Original Message -
> From: "Bradley Scalio"
> To: users@qpid.apache.org
> Sent: Tuesday, September 13, 2011 2:28:14 PM
> Subject: Logging
> Greetings,
>
> Trying to turn off logging to /var/log/messages and send qpidd lo
Greetings,
Trying to turn off logging to /var/log/messages and send qpidd logging
to /var/log/qpidd.log
I tried the following in our qpidd.conf:
sed -i '$a log-to-file=/var/log/qpidd.log' qpidd.conf
sed -i '$a log-to-syslog=no' qpidd.conf
I get logging to /var/log/qpid
Hi all,
Thanks for the response.
On Fri, Apr 8, 2011 at 8:29 PM, Carl Trieloff wrote:
>
> If the file got deleted, then Linux will let you continue to log to the
> FD, tossing the contents to dev null.
>
I do not think file got delete, its there and it stops logging, I will
doubl
Hi Lahiru,
> Hi Devs,
>
> We have a critical situation with out client deployment since
> we do not see any logging in a production system ?
What platform is this? What Qpid version?
> If someone can provide some input it would be great for us.
>
> Lahiru
>
> On T
If the file got deleted, then Linux will let you continue to log to the
FD, tossing the contents to dev null.
Do you have log rotation setup, alternately, you can configure the log
to syslog option.
Basically if you run a production broker with logging on, then you need
to select a log
Hi Devs,
We have a critical situation with out client deployment since we do not see
any logging in a production system ?
If someone can provide some input it would be great for us.
Lahiru
On Thu, Apr 7, 2011 at 12:54 PM, Lahiru Gunathilake wrote:
> Hi all,
>
> We have configur
Hi all,
We have configured Qpid C++ broker to write the logs to a file using qpidd
arguments. After running couple of hours it stops logging anything ?
What is the default logging level (We have not specified any logging level )
?
Can someone give any clue why this is happening ? Qpid works
to use my application's existing logging
functions.
If not, at least, I would like to suppress output to stderr, and instead
direct it to a specific file.
Could someone point me to how I could go about doing this?
To disable logging entirely:
#include
qpid::log::Logger::instance().clear(
o.
I understand the use of environment variables (on the client) like
QPID_LOG_TO_FILE, QPID_LOG_SOURCE etc
But I'd like to control this programmatically in my app, ideally by
overriding some class/member function and
instead redirect the log messages to use my application's existing logging
s (on the client) like
QPID_LOG_TO_FILE, QPID_LOG_SOURCE etc
But I'd like to control this programmatically in my app, ideally by
overriding some class/member function and
instead redirect the log messages to use my application's existing logging
functions.
If not, at least, I would l
Java Broker Users,
I have been working on designs for improving the logging from the Java
Broker. The current logging is more aimed at developers so providing
more operational focused log messages would be good.
The design is up on the wiki here:
http://cwiki.apache.org/confluence/display/qpid
48 matches
Mail list logo
