Hi Akhil,
Thanks for raising JIRA and attaching the screenshots from MAT.
As per screnshot [1] it seems that heap memory was consumed by java.io.File
objects. Judging by the file names, the file objects were created by log
appender whilst compression broker logs.
What type of file appender are you using with Qpid Broker? Is it
"org.apache.log4j.QpidCompositeRollingAppender"? You can check
${QPID_HOME}/etc/log4j.xml for logging configuration?
We are not aware about any defect in QpidCompositeRollingAppender which
would manifest in heap memory consumption by java.io.File objects.
The broker logging functionality in version 0.32 is based on log4j . It was
replaced with slf4j and logback in following 6.x versions.
You can consider migration to newer version of broker (6.1.3 at the moment
of writing this email). If migration of broker is not an option, you can
try replacing the log appender with another one.
Kind Regards,
Alex
[1] https://issues.apache.org/jira/browse/QPID-7828
[2] https://issues.apache.org/jira/secure/attachment/12873368/image1.PNG
On 19 June 2017 at 11:46, Akhil Samnotra <[email protected]> wrote:
> HI ,
> I have even raised the jira but didnt got any resolution.
>
> Thanks
> Akhil
>
> On Mon, Jun 19, 2017 at 1:47 PM, Oleksandr Rudyy <[email protected]> wrote:
>
> > Hi Akhil,
> >
> > The screenshots did not get through with your latest email. Could you
> > please try raising JIRA and attaching the screnshots to it?
> >
> > Kind Regards,
> > Alex
> >
> > On 17 June 2017 at 06:04, Akhil Samnotra <[email protected]>
> wrote:
> >
> > > hi ,
> > >
> > > please find the screenshots attached.
> > > thanks
> > >
> > > Akhil
> > >
> > > On Sat, Jun 17, 2017 at 1:52 AM, Oleksandr Rudyy <[email protected]>
> > wrote:
> > >
> > >> Hi Akhil,
> > >> It seems attachments have been stripped off. Could you please resend
> > them
> > >> or raise a JIRA [1] and attach your screenshots to the JIRA?
> > >>
> > >> Kind Regards,
> > >> Alex
> > >>
> > >> [1] https://issues.apache.org/jira/projects/QPID
> > >>
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> >
>
