Application logs stopped coming in DevTest 10.7.2 version

[Naga Raji Lakkakula]

For all versions, we have created separate log path in vmoptions file. For DevTest 10.7.2, logs are not coming in mentioned path neither on home path. 

They had come while on the installation starting, suddenly they stopped coming.  No logs for ED and Registry and any other component except IAM logs. Please help. Thank you.

------------------------------
Raji
------------------------------

[Sankar Natarajan]

Hi Naga Rani
Is this observed in a recently upgraded 10.7.2 environment? Would
you mind share your logging.properties file. You may also open a support
ticket to have this tracked.

--
regards
Sankar Natarajan

--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.

[Vaibhav Jain]

Hi Raji,

Please share the properties files for further analysis.

Thanks

------------------------------
Regards,
Vaibhav Jain
Capgemini
------------------------------

[Roy Gandham]

# See https://logging.apache.org/log4j/2.x/index.html and https://logging.apache.org/log4j/2.x/manual/index.html

# This file is polled regularly by LISA applications at runtime so you can add new DEBUG loggers
# or change system-wide logging without restarting LISA apps.
name = DevTest_Logging
status = error
monitorInterval = 10

#Add the below packages attribute to detect the custom appender package for centralized remote registry logs
#packages = com.itko.lisa.net
rootLogger.level = INFO

rootLogger.appenderRefs = A1
rootLogger.appenderRef.A1.ref = A1

##Add the registry appender Ref to rootLogger appenderRefs list like rootLogger.appenderRefs = A1,registry
##and uncomment the below line for registry appenderRef
#rootLogger.appenderRef.registry.ref = registry

##Add the below property to add TEST_STEP appenderRef to rootLogger and set the rootLogger level to DEBUG for logging events.
#rootLogger.appenderRef.TEST_STEP.ref = TEST_STEP

#----------------
#FILTERS
#----------------
filters = threshold
filter.threshold.type = ThresholdFilter
filter.threshold.level = DEBUG

#----------------
#APPENDERS
#----------------
appenders = A1, ACL_LOG, VSEAPP, ADVICE_APP, THREAD_DUMPS, STDOUT, SPLUNKAPP, EXCEPTIONAPP

appender.A1.type = RollingFile
appender.A1.name = A1
appender.A1.fileName = ${sys:lisa.tmpdir}/${sys:LISA_LOG}
appender.A1.filePattern = ${sys:lisa.tmpdir}/${sys:LISA_LOG}.%i
appender.A1.layout.type = PatternLayout
appender.A1.layout.pattern = %d{ISO8601}{UTC}Z (%d{HH:mm}) [%t] %-5p %-30c - %m%n
appender.A1.policies.type = Policies
appender.A1.policies.size.type = SizeBasedTriggeringPolicy
appender.A1.policies.size.size = 10MB
appender.A1.strategy.type = DefaultRolloverStrategy
appender.A1.strategy.max = 5
appender.A1.strategy.fileIndex = min

appender.ACL_LOG.type = RollingFile
appender.ACL_LOG.name = ACL_LOG
appender.ACL_LOG.fileName = ${sys:lisa.tmpdir}/acl.log
appender.ACL_LOG.filePattern = ${sys:lisa.tmpdir}/acl.log.%i
appender.ACL_LOG.layout.type = PatternLayout
appender.ACL_LOG.layout.pattern = %d{ISO8601}{UTC}Z (%d{HH:mm}) [%t] %-5p %-30c - %m%n
appender.ACL_LOG.policies.type = Policies
appender.ACL_LOG.policies.size.type = SizeBasedTriggeringPolicy
appender.ACL_LOG.policies.size.size = 10MB
appender.ACL_LOG.strategy.type = DefaultRolloverStrategy
appender.ACL_LOG.strategy.max = 5
appender.ACL_LOG.strategy.fileIndex = min

appender.VSEAPP.type = RollingFile
appender.VSEAPP.name = VSEAPP
appender.VSEAPP.fileName = ${sys:lisa.tmpdir}/vse_matches.log
appender.VSEAPP.filePattern = ${sys:lisa.tmpdir}/vse_matches.log.%i
appender.VSEAPP.layout.type = PatternLayout
appender.VSEAPP.layout.pattern = %d{ISO8601}{UTC}Z (%d{HH:mm})[%t] %-5p - %m%n
appender.VSEAPP.policies.type = Policies
appender.VSEAPP.policies.size.type = SizeBasedTriggeringPolicy
appender.VSEAPP.policies.size.size = 10MB
appender.VSEAPP.strategy.type = DefaultRolloverStrategy
appender.VSEAPP.strategy.max = 20
appender.VSEAPP.strategy.fileIndex = min

appender.ADVICE_APP.type = RollingFile
appender.ADVICE_APP.name = ADVICE_APP
appender.ADVICE_APP.fileName = ${sys:lisa.tmpdir}/advice.log
appender.ADVICE_APP.filePattern = ${sys:lisa.tmpdir}/advice.log.%i
appender.ADVICE_APP.layout.type = PatternLayout
appender.ADVICE_APP.layout.pattern = %d{ISO8601}{UTC}Z (%d{HH:mm}) %-5p - %m%n
appender.ADVICE_APP.policies.type = Policies
appender.ADVICE_APP.policies.size.type = SizeBasedTriggeringPolicy
appender.ADVICE_APP.policies.size.size = 10MB
appender.ADVICE_APP.strategy.type = DefaultRolloverStrategy
appender.ADVICE_APP.strategy.max = 20
appender.ADVICE_APP.strategy.fileIndex = min

appender.THREAD_DUMPS.type = RollingFile
appender.THREAD_DUMPS.name = THREAD_DUMPS
appender.THREAD_DUMPS.fileName = ${sys:lisa.tmpdir}/threadDumps/TD_${sys:LISA_LOG}
appender.THREAD_DUMPS.filePattern = ${sys:lisa.tmpdir}/threadDumps/TD_${sys:LISA_LOG}.%i
appender.THREAD_DUMPS.layout.type = PatternLayout
appender.THREAD_DUMPS.layout.pattern = %d{ISO8601}{UTC}Z (%d{HH:mm}) [%t] %-5p - %m%n
appender.THREAD_DUMPS.policies.type = Policies
appender.THREAD_DUMPS.policies.size.type = SizeBasedTriggeringPolicy
appender.THREAD_DUMPS.policies.size.size = 10MB
appender.THREAD_DUMPS.strategy.type = DefaultRolloverStrategy
appender.THREAD_DUMPS.strategy.max = 20
appender.THREAD_DUMPS.strategy.fileIndex = min

appender.STDOUT.type = Console
appender.STDOUT.name = STDOUT
appender.STDOUT.layout.type = PatternLayout
appender.STDOUT.layout.pattern = %d{ISO8601}{UTC}Z (%d{HH:mm}) [%t] %-5p %-30c - %m%n

##For cloud runs, you probably want centralized logging so add the below registry appender properties,
##And Mirror our logging to the (remote) registry.
##Also add this appender to the appenders list

#appender.registry.type = LoggingToRegistryAppender
#appender.registry.name = registry
#appender.registry.layout.type = PatternLayout
#appender.registry.layout.pattern = %d{ISO8601}{UTC}Z (%d{HH:mm}) [%t] %-5p %-30c - %m%n

############################################
##Each Test step includes a log message element.
##To send the log message to a specific file at runtime, add the following appender properties
#and add this appender to the appenders list

#appender.TEST_STEP.type = RollingFile
#appender.TEST_STEP.name = TEST_STEP
#appender.TEST_STEP.fileName = ${sys:lisa.tmpdir}/test_step.log
#appender.TEST_STEP.filePattern = ${sys:lisa.tmpdir}/test_step.%i.log
#appender.TEST_STEP.policies.type = Policies
#appender.TEST_STEP.policies.size.type = SizeBasedTriggeringPolicy
#appender.TEST_STEP.policies.size.size=10MB
#appender.TEST_STEP.strategy.type = DefaultRolloverStrategy
#appender.TEST_STEP.strategy.max = 5
#appender.TEST_STEP.layout.type = PatternLayout
#appender.TEST_STEP.layout.pattern =%d{ISO8601}{UTC}Z (%d{HH:mm}) [%t] %-5p %-30c - %m%n

#----------------
#LOGGERS
#----------------
# The following lines adjust the log levels of third-party libraries used by LISA so that
# they don't clutter the logs with messages unrelated to LISA.
loggers = teamdev, eventlogger, apache, smardec, apachehttp, mchange, hibernate, jfree, jniwrapper, rmi, threadDumper, eclipse, codehaus, grails, springframework, jndi, flywaydb, jayway, sf, quartz, jettyAnnotationParser, jettyWebContext, NIOSession, springsecuritycore, springsecurityldap, springldapcore, securityAuth, VSE, ADVICE, threadDumpLogger, hibernateorm, apachehttpheader, apachehttpwire, SPLUNK, EXCEPTION

##Add the following logging properties for Test Step.  And add testStep to the loggers list as well
#logger.testStep.name = com.itko.lisa.test.StepLogger
#logger.testStep.level = DEBUG
#logger.testStep.additivity = false
#logger.testStep.appenderRefs = TEST_STEP

logger.teamdev.name = com.teamdev
logger.teamdev.level = WARN
logger.teamdev.additivity = false
logger.teamdev.appenderRef.A1.ref = A1

logger.eventlogger.name = EventLogger
logger.eventlogger.level = WARN
logger.eventlogger.additivity = false
logger.eventlogger.appenderRef.A1.ref = A1

logger.apache.name = org.apache
logger.apache.level = ERROR
logger.apache.additivity = false
logger.apache.appenderRef.A1.ref = A1

logger.smardec.name = com.smardec
logger.smardec.level = ERROR
logger.smardec.additivity = false
logger.smardec.appenderRef.A1.ref = A1

logger.apachehttp.name = org.apache.http
logger.apachehttp.level = ERROR
logger.apachehttp.additivity = false
logger.apachehttp.appenderRef.A1.ref = A1

logger.mchange.name = com.mchange.v2
logger.mchange.level = ERROR
logger.mchange.additivity = false
logger.mchange.appenderRef.A1.ref = A1

logger.hibernate.name = org.hibernate
logger.hibernate.level = WARN
logger.hibernate.additivity = false
logger.hibernate.appenderRef.A1.ref = A1

logger.jfree.name = org.jfree
logger.jfree.level = ERROR
logger.jfree.additivity = false
logger.jfree.appenderRef.A1.ref = A1

logger.jniwrapper.name = com.jniwrapper
logger.jniwrapper.level = ERROR
logger.jniwrapper.additivity = false
logger.jniwrapper.appenderRef.A1.ref = A1

logger.rmi.name = sun.rmi
logger.rmi.level = INFO
logger.rmi.additivity = false
logger.rmi.appenderRef.A1.ref = A1

logger.threadDumper.name = com.itko.util.ThreadDumper
logger.threadDumper.level = INFO
logger.threadDumper.additivity = false
logger.threadDumper.appenderRef.A1.ref = A1

logger.eclipse.name = org.eclipse
logger.eclipse.level = WARN
logger.eclipse.additivity = false
logger.eclipse.appenderRef.A1.ref = A1

logger.codehaus.name = org.codehaus
logger.codehaus.level = WARN
logger.codehaus.additivity = false
logger.codehaus.appenderRef.A1.ref = A1

logger.grails.name = org.grails
logger.grails.level = WARN
logger.grails.additivity = false
logger.grails.appenderRef.A1.ref = A1

logger.springframework.name = org.springframework
logger.springframework.level = WARN
logger.springframework.additivity = false
logger.springframework.appenderRef.A1.ref = A1

logger.jndi.name = jndi
logger.jndi.level = WARN
logger.jndi.additivity = false
logger.jndi.appenderRef.A1.ref = A1

logger.flywaydb.name = org.flywaydb
logger.flywaydb.level = WARN
logger.flywaydb.additivity = false
logger.flywaydb.appenderRef.A1.ref = A1

logger.jayway.name = com.jayway
logger.jayway.level = WARN
logger.jayway.additivity = false
logger.jayway.appenderRef.A1.ref = A1

logger.sf.name = net.sf
logger.sf.level = WARN
logger.sf.additivity = false
logger.sf.appenderRef.A1.ref = A1

logger.quartz.name = org.quartz
logger.quartz.level = WARN
logger.quartz.additivity = false
logger.quartz.appenderRef.A1.ref = A1

logger.jettyAnnotationParser.name = org.eclipse.jetty.annotations.AnnotationParser
logger.jettyAnnotationParser.level = ERROR
logger.jettyAnnotationParser.additivity = false
logger.jettyAnnotationParser.appenderRef.A1.ref = A1

logger.jettyWebContext.name = org.eclipse.jetty.webapp.WebAppContext
logger.jettyWebContext.level = ERROR
logger.jettyWebContext.additivity = false
logger.jettyWebContext.appenderRef.A1.ref = A1

# Uncomment the following to enable the TRACE level debugging for NIO operations. This is used in conjunction with the
# local.properites property com.itko.lisa.vse.sio.loggerName=NIOSession
logger.NIOSession.name = NIOSession
logger.NIOSession.level = TRACE
logger.NIOSession.additivity = false
logger.NIOSession.appenderRef.A1.ref = A1

# Keep a separate log for ACL events. This logger contains all logging related to the authentication
# providers. It is deliberately kept separate from the application log to minimize noise.
logger.springsecuritycore.name = org.springframework.security.core
logger.springsecuritycore.level = DEBUG
logger.springsecuritycore.additivity = true
logger.springsecuritycore.appenderRefs = ACL_LOG
logger.springsecuritycore.appenderRef.ACL_LOG.ref = ACL_LOG

logger.springsecurityldap.name = org.springframework.security.ldap
logger.springsecurityldap.level = DEBUG
logger.springsecurityldap.additivity = true
logger.springsecurityldap.appenderRefs= ACL_LOG
logger.springsecurityldap.appenderRef.ACL_LOG.ref = ACL_LOG

logger.springldapcore.name = org.springframework.ldap.core
logger.springldapcore.level = DEBUG
logger.springldapcore.additivity = true
logger.springldapcore.appenderRefs = ACL_LOG
logger.springldapcore.appenderRef.ACL_LOG.ref = ACL_LOG

logger.securityAuth.name = com.ca.dts.security.authentication
logger.securityAuth.level = DEBUG
logger.securityAuth.additivity = false
logger.securityAuth.appenderRefs = ACL_LOG
logger.securityAuth.appenderRef.ACL_LOG.ref = ACL_LOG

# Keep a separate log for VSE transaction match/no-match events, this makes debugging much easier.
# Change INFO below to WARN for production systems, the logging is expensive and will slow down
# systems with high transaction rates. Do not simply comment out the following line; explicitly
# set the log level to OFF or WARN instead of INFO
logger.VSE.name = VSE
logger.VSE.level = INFO
# If you want to add VSE logging to other log destinations, comment out the next line
logger.VSE.additivity = false
logger.VSE.appenderRefs = VSEAPP
logger.VSE.appenderRef.VSEAPP.ref = VSEAPP

# Keep a separate log for advisory events. This logger warns of potential configuration issues, potential
# memory leaks, etc. It is deliberately kept separate to the application log to minimize noise.
logger.ADVICE.name = ADVICE
logger.ADVICE.level = INFO
logger.ADVICE.additivity = false
logger.ADVICE.appenderRefs = ADVICE_APP
logger.ADVICE.appenderRef.ADVICE_APP.ref = ADVICE_APP

# If periodic thread dumps are enabled, this is where they will be sent. Note that we log at INFO level by default so
# to actually get the thread dumps just change WARN in the threadDumpLogger level to INFO, even with LISA servers and/or
# workstation running and you should get a thread dump in the named file within 30 seconds.  Search for 'threadDump'
# in lisa.properties for more info. This makes it very simple to get thread dump to debug performance issues, simply
# change WARN in threadDumpLogger level to INFO, wait for a minute or two, then (maybe) change it back to WARN to prevent the
# thread dumps.
#
# You can also generate a point-in-time thread dump with the LISA_HOME/bin/ServiceManager application
# e.g. ServiceManager -threadDump tcp://hostname:2014/Simulator  or use standard java tools such as jstack
#
logger.threadDumpLogger.name = threadDumpLogger
logger.threadDumpLogger.level = WARN
logger.threadDumpLogger.additivity = false
logger.threadDumpLogger.appenderRefs = THREAD_DUMPS
logger.threadDumpLogger.appenderRef.THREAD_DUMPS.ref = THREAD_DUMPS

logger.hibernateorm.name = org.hibernate.orm.deprecation
logger.hibernateorm.level = ERROR
logger.hibernateorm.additivity = false
logger.hibernateorm.appenderRef.A1.ref = A1

logger.apachehttpheader.name = org.apache.http.headers
logger.apachehttpheader.level = ERROR

logger.apachehttpwire.name = org.apache.http.wire
logger.apachehttpwire.level = ERROR

###########################################
# Splunk Custom logging
############################################

appender.SPLUNKAPP.type = RollingFile
appender.SPLUNKAPP.name = SPLUNKAPP
appender.SPLUNKAPP.fileName = ${sys:lisa.tmpdir}/splunk_custom.log
appender.SPLUNKAPP.filePattern =${sys:lisa.tmpdir}/splunk_custom.log.%i
appender.SPLUNKAPP.layout.type = PatternLayout
appender.SPLUNKAPP.layout.pattern = %d{yyyy-MM-dd'T'HH:mm:ss,SSSZ} %c{1} [%p] %m%n
appender.SPLUNKAPP.policies.type = Policies
appender.SPLUNKAPP.policies.size.type = SizeBasedTriggeringPolicy
appender.SPLUNKAPP.policies.size.size = 10MB
appender.SPLUNKAPP.strategy.type = DefaultRolloverStrategy
appender.SPLUNKAPP.strategy.max = 20
appender.SPLUNKAPP.strategy.fileIndex = min

logger.SPLUNK.name = SPLUNKAPP
logger.SPLUNK.level = INFO
logger.SPLUNK.additivity = false
logger.SPLUNK.appenderRefs = SPLUNKAPP
logger.SPLUNK.appenderRef.SPLUNKAPP.ref = SPLUNKAPP

############################################
# Exception Custom logging
############################################

appender.EXCEPTIONAPP.type = RollingFile
appender.EXCEPTIONAPP.name = EXCEPTIONAPP
appender.EXCEPTIONAPP.fileName = ${sys:lisa.tmpdir}/exception_custom.log
appender.EXCEPTIONAPP.filePattern =${sys:lisa.tmpdir}/exception_custom.log.%i
appender.EXCEPTIONAPP.layout.type = PatternLayout
appender.EXCEPTIONAPP.layout.pattern = %d{yyyy-MM-dd'T'HH:mm:ss,SSSZ} %c{1} [%p] %m%n
appender.EXCEPTIONAPP.policies.type = Policies
appender.EXCEPTIONAPP.policies.size.type = SizeBasedTriggeringPolicy
appender.EXCEPTIONAPP.policies.size.size = 10MB
appender.EXCEPTIONAPP.strategy.type = DefaultRolloverStrategy
appender.EXCEPTIONAPP.strategy.max = 20
appender.EXCEPTIONAPP.strategy.fileIndex = min

logger.EXCEPTION.name = EXCEPTIONAPP
logger.EXCEPTION.level = INFO
logger.EXCEPTION.additivity = false
logger.EXCEPTION.appenderRefs = EXCEPTIONAPP
logger.EXCEPTION.appenderRef.EXCEPTIONAPP.ref = EXCEPTIONAPP

[Marcy Nunns]

Issued is resolved, this post was opened before the support case was logged, you can refer to this KB: Custom Application logs stopped coming in DevTest 10.7.2 version

[Roy Gandham]

Hellpo Marcy,

This was posted by my team before we log a support incident. As the issue is resolved., Pls mark this post as completed or ignored.

Thanks
Rg



> On Jun 12, 2023, at 9:00 AM, Marcy Nunns via Broadcom <[e-mail]> wrote:
>
> <https: community.broadcom.com/="">
> Service Virtualization <https: community.broadcom.com/enterprisesoftware/communities/community-home/digestviewer?communitykey="94bda077-625b-4914-8ac3-c88a06c2cc23">
> Post New Message <mailto:[e-mail]>
> Re: Application logs stopped coming in DevTest 10.7.2 version <https: community.broadcom.com/enterprisesoftware/discussion/application-logs-stopped-coming-in-devtest-1072-version#bmb5600bfc-7205-4f6f-a774-0188afe29afb="">
> Reply to Group <mailto:bro[e-mail]?subject=re:%20application%20logs%20stopped%20coming%20in%20devtest%2010.7.2%20version> Reply to Sender <https: community.broadcom.com/enterprisesoftware/communities/all-discussions/postreply?messagekey="b5600bfc-7205-4f6f-a774-0188afe29afb&ListKey=d4484a56-be7e-428f-99d1-26cc0f5a617e&SenderKey=5b791154-4038-497d-8d95-dd9a32bb1413">
> <https: community.broadcom.com/network/members/profile?userkey="5b791154-4038-497d-8d95-dd9a32bb1413">
> Jun 12, 2023 9:59 AM
> Marcy Nunns <https: community.broadcom.com/network/members/profile?userkey="5b791154-4038-497d-8d95-dd9a32bb1413">
> Please post your vmoptions files for Enterprise Dashboard, Registry and Portal. Provide your current logging.properties file as well.
>
> A customer has an issue where they were writing out Splunk logs and after upgrading to DevTest 10.7.2 they did not write out, and it was because 10.7.2 uses log4j2, you can refer to this KB: Custom Application logs stopped coming in DevTest 10.7.2 version <https: knowledge.broadcom.com/external/article?articleid="267735">
>
> Reply to Group Online <https: community.broadcom.com/enterprisesoftware/communities/all-discussions/postreply?messagekey="b5600bfc-7205-4f6f-a774-0188afe29afb&ListKey=d4484a56-be7e-428f-99d1-26cc0f5a617e"> Reply to Group via Email <mailto:bro[e-mail]?subject=re:%20application%20logs%20stopped%20coming%20in%20devtest%2010.7.2%20version> View Thread <https: community.broadcom.com/enterprisesoftware/discussion/application-logs-stopped-coming-in-devtest-1072-version#bmb5600bfc-7205-4f6f-a774-0188afe29afb=""> Recommend <https: community.broadcom.com/enterprisesoftware/discussion/application-logs-stopped-coming-in-devtest-1072-version?messagekey="b5600bfc-7205-4f6f-a774-0188afe29afb&cmd=rate&cmdarg=add#bmb5600bfc-7205-4f6f-a774-0188afe29afb"> Forward <https: community.broadcom.com/enterprisesoftware/communities/all-discussions/forwardmessages?messagekey="b5600bfc-7205-4f6f-a774-0188afe29afb&ListKey=d4484a56-be7e-428f-99d1-26cc0f5a617e"> Flag as Inappropriate <https: community.broadcom.com/enterprisesoftware/discussion/application-logs-stopped-coming-in-devtest-1072-version?markappropriate="b5600bfc-7205-4f6f-a774-0188afe29afb#bmb5600bfc-7205-4f6f-a774-0188afe29afb">
> -------------------------------------------
> Original Message:
> Sent: Apr 21, 2023 07:20 AM
> From: Naga Raji Lakkakula
> Subject: Application logs stopped coming in DevTest 10.7.2 version
>
> For all versions, we have created separate log path in vmoptions file. For DevTest 10.7.2, logs are not coming in mentioned path neither on home path.
>
> They had come while on the installation starting, suddenly they stopped coming. No logs for ED and Registry and any other component except IAM logs. Please help. Thank you.
>
>
>
> ------------------------------
> Raji
> ------------------------------
>
>
>
>
> You are receiving this notification because you followed the 'Application logs stopped coming in DevTest 10.7.2 version' message thread. If you do not wish to follow this, please click here <https: community.broadcom.com/higherlogic/common/unfollow.aspx?userkey="054774dd-701f-4be6-9d21-745c81303a53&sKey=KeyRemoved&ItemKey=6e518d51-fe76-4d57-96ef-0187a389709a">.
> Update your email preferences <https: community.broadcom.com/go.aspx?c="Preferences§ion=email"> to choose the types of email you receive
>
> Unsubscribe from all participation emails <https: community.broadcom.com/higherlogic/egroups/unsubscribe.aspx?userkey="054774dd-701f-4be6-9d21-745c81303a53&sKey=KeyRemoved&mClass=Social">