Metric notifications not showing

wlcommunityusers · Sep 19, 2018, 7:46 AM

Hi Team,

We are using WLSDM version 3.4.1 and we cannot viewing any notification.

	at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
	at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
	at com.wlsdm.O.I.doFilter(RRFilter.java:280)
	at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
	at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
	at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
	at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3748)
	at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3714)
	at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
	at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
	at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2283)
	at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2182)
	at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1491)
	at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
	at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: ERROR 25505: A read-only user or a user in a read-only database is not permitted to disable read-only mode on a connection.
	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
	at org.apache.derby.impl.sql.conn.GenericAuthorizer.setReadOnlyConnection(Unknown Source)
	at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.setReadOnly(Unknown Source)
	... 28 more
>
####<Sep 18, 2018 1:03:56 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><null

java.lang.NullPointerException
>
####<Sep 18, 2018 1:03:56 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><null

java.lang.NullPointerException
>
####<Sep 18, 2018 1:03:56 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><GenericLog.Monitoring:: CollectAppDefinedLogs return NULL!>
####<Sep 18, 2018 1:03:56 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><A read-only user or a user in a read-only database is not permitted to disable read-only mode on a connection.

java.sql.SQLException: A read-only user or a user in a read-only database is not permitted to disable read-only mode on a connection.
	at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
	at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
	at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
	at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
	at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
	at org.apache.derby.impl.jdbc.EmbedConnection.setReadOnly(Unknown Source)
	at com.wlsdm.database.PB.getConnection(DerbyConnectionUtils.java:48)
	at com.wlsdm.E.A.E.A.E.C(BaseManagerImpl.java:35)
	at com.wlsdm.E.A.E.A.E.<init>(BaseManagerImpl.java:23)
	at com.wlsdm.I.A.A.B.B.E.<init>(LogDefinitionConfig.java:17)
	at com.wlsdm.frontend.provider.EA.getAllLogDefinitions(GenericLogData.java:218)
	at com.wlsdm.O.O.Ä«(Data.java:2680)
	at com.wlsdm.O.O.A(Data.java:676)
	at com.wlsdm.O.O.doGet(Data.java:151)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
	at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
	at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
	at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
	at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
	at com.wlsdm.O.I.doFilter(RRFilter.java:280)
	at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
	at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
	at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
	at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3748)
	at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3714)
	at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
	at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
	at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2283)
	at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2182)
	at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1491)
	at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
	at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: ERROR 25505: A read-only user or a user in a read-only database is not permitted to disable read-only mode on a connection.
	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
	at org.apache.derby.impl.sql.conn.GenericAuthorizer.setReadOnlyConnection(Unknown Source)
	at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.setReadOnly(Unknown Source)
	... 29 more
>
####<Sep 18, 2018 1:03:56 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><null

java.lang.NullPointerException
>
####<Sep 18, 2018 1:03:56 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><GenericLog.Monitoring:: CollectAppDefinedLogs return NULL!>
####<Sep 18, 2018 1:03:56 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><null

java.lang.NullPointerException
>
####<Sep 18, 2018 1:03:56 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><GenericLog.Monitoring:: doRemoteTail.logFile return NULL!>
####<Sep 18, 2018 1:03:57 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><null

java.lang.NullPointerException
>
####<Sep 18, 2018 1:03:57 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><GenericLog.Monitoring:: CollectAppDefinedLogs return NULL!>
####<Sep 18, 2018 1:03:57 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><null

java.lang.NullPointerException
>
####<Sep 18, 2018 1:03:57 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><GenericLog.Monitoring:: CollectAppDefinedLogs return NULL!>
####<Sep 18, 2018 1:03:57 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><null

java.lang.NullPointerException
>
####<Sep 18, 2018 1:03:57 PM GMT+00:00><SEVERE><WLSDM><BEA-000000><GenericLog.Monitoring:: doRemoteTail.logFile return NULL!>

WLSDM Support · Sep 19, 2018, 7:33 AM

Hi,

It looks like a WLSDM DB issue.

This is might be happening because you do not have enough disk space on the machine.

Please check your disk for enough space.

After that please restart the (only) AdminServer.

Kind regards.

Metric notifications not showing

WLSDM: Native WebLogic Monitoring & Diagnostics