Bug 1188635

Summary:	Failure to send mail to Roles in 4.13.1
Product:	[Other] RHQ Project	Reporter:	Nyiri Márk <nyiri.mark>
Component:	Alerts	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	bkramer, hrupp, nyiri.mark
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1224325

Description Nyiri Márk 2015-02-03 13:07:46 UTC

Description of problem:

Server can not send e-mail Alert for System Rules.

13:17:13,153 ERROR [org.rhq.enterprise.server.alert.AlertManagerBean] (Thread-40 (HornetQ-client-global-threads-1882874393)) Notification processing terminated abruptlyfailed to lazily initialize a collection of role: org.rhq.core.domain.authz.Role.subjects, could not in
itialize proxy - no Session





How reproducible:

I created a System Roles like name "IT-MIDDLEWARE" and some users member of this rule.

In Alert Definition Template RHQ, created Alert, with any condition Like "Goes Up" and notification  is System Roles:"IT-MIDDLEWARE"


Actual results:

When alert is fired, this see in server.log and not sending e-mail.

13:12:27,330 INFO [org.rhq.enterprise.server.core.AgentManagerBean] (EJB default - 8) Agent with name [aikjapp4.uat.cib.hu] just went down

13:12:34,434 ERROR [org.rhq.enterprise.server.alert.AlertManagerBean] 
(Thread-25 (HornetQ-client-global-threads-1882874393)) Notification processing terminated abruptlyfailed to lazily initialize a collectio
n of role: org.rhq.core.domain.authz.Role.subjects, could not initialize proxy - no Session




Expected results:


Additional info:
If i create System User notification for this alert then it is working, user get the email.

Comment 1 Nyiri Márk 2015-02-04 11:23:36 UTC

Hello!

maybe any workaround?

Comment 2 Nyiri Márk 2015-02-05 12:38:17 UTC

I set rhq to debug. but not too much info..
I try-d simple Rule name "TEST" not success :)


13:32:39,792 DEBUG [org.rhq.enterprise.server.alert.AlertManagerBean] (Thread-0 (HornetQ-client-global-threads-1005764547)) Sending alert notifications for Alert[id=10136]...
13:32:39,795 DEBUG [org.rhq.enterprise.server.plugin.pc.alert.AlertSenderPluginManager] (Thread-0 (HornetQ-client-global-threads-1005764547)) Loading server plugin class [org.rhq.enterprise.server.plugins.alertRoles.RolesSender]...
13:32:39,798 DEBUG [org.rhq.enterprise.server.plugin.pc.alert.AlertSenderPluginManager] (Thread-0 (HornetQ-client-global-threads-1005764547)) Loaded server plugin class [class org.rhq.enterprise.server.plugins.alertRoles.RolesSender]. initialized=[true]
13:32:39,798 DEBUG [org.rhq.enterprise.server.plugin.pc.alert.AlertSenderPluginManager] (Thread-0 (HornetQ-client-global-threads-1005764547)) Instantiating server plugin class [class org.rhq.enterprise.server.plugins.alertRoles.RolesSender]
13:32:39,798 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-0 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,799 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-0 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,800 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-8 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=1, xactions=3, loads=0, connects=1, time=14 ] for SLSB:ServerPluginManagerBean.getServerPlugin
13:32:39,808 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-0 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=2, xactions=0, loads=0, connects=1, time=9 ] for SLSB:ServerPluginManagerBean.getServerPlugin
13:32:39,810 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-8 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,819 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-0 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,821 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-8 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=1, xactions=2, loads=0, connects=1, time=11 ] for SLSB:ServerPluginManagerBean.getServerPluginRelationships
13:32:39,828 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-0 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=2, xactions=0, loads=0, connects=1, time=8 ] for SLSB:ServerPluginManagerBean.getServerPluginRelationships
13:32:39,830 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-8 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,832 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-8 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,838 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-0 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,839 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-0 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,843 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-0 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=0, xactions=0, loads=1, connects=1, time=3 ] for SLSB:RoleManagerBean.getRoleById
13:32:39,844 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-8 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=0, xactions=2, loads=2, connects=2, time=12 ] for SLSB:RoleManagerBean.getRoleById
13:32:39,852 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-0 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,852 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-0 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,853 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-8 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,854 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-8 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,860 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-0 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=0, xactions=2, loads=1, connects=2, time=8 ] for SLSB:RoleManagerBean.getRoleById
13:32:39,863 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-8 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=0, xactions=0, loads=2, connects=2, time=9 ] for SLSB:RoleManagerBean.getRoleById
13:32:39,868 ERROR [org.rhq.enterprise.server.alert.AlertManagerBean] (Thread-0 (HornetQ-client-global-threads-1005764547)) Notification processing terminated abruptlyfailed to lazily initialize a collection of role: org.rhq.core.domain.authz.Role.subjects, could not ini
tialize proxy - no Session
13:32:39,869 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-0 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,872 ERROR [org.rhq.enterprise.server.alert.AlertManagerBean] (Thread-8 (HornetQ-client-global-threads-1005764547)) Notification processing terminated abruptlyfailed to lazily initialize a collection of role: org.rhq.core.domain.authz.Role.subjects, could not ini
tialize proxy - no Session
13:32:39,873 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (Thread-8 (HornetQ-client-global-threads-1005764547)) No java.naming.factory.initial set. Using the default factory.
13:32:39,954 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-0 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=0, xactions=2, loads=254, connects=7, time=85 ] for SLSB:AlertManagerBean.addNotificationLog
13:32:39,961 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-8 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=0, xactions=0, loads=264, connects=9, time=88 ] for SLSB:AlertManagerBean.addNotificationLog
13:32:39,978 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-0 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=4, xactions=18, loads=268, connects=17, time=186 ](perf: too many xactions?) for SLSB:AlertManagerBean.sendAlertN
otificationsNSTx
13:32:39,979 DEBUG [org.rhq.enterprise.server.util.concurrent.AlertSerializer] (Thread-0 (HornetQ-client-global-threads-1005764547)) tid= 146: alertDefinitionId=11198: releasing write lock after being locked for millis=578
13:32:39,979 DEBUG [org.rhq.enterprise.server.util.concurrent.AlertSerializer] (Thread-0 (HornetQ-client-global-threads-1005764547)) tid= 146: alertDefinitionId=11198: released write lock
13:32:39,979 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-0 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=29, xactions=76, loads=546, connects=77, time=625 ](perf: too many xactions?) for SLSB:AlertConditionConsumerBean
.onMessage
13:32:39,980 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-8 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=4, xactions=23, loads=268, connects=18, time=200 ](perf: xaction nesting?)  for SLSB:AlertManagerBean.sendAlertNo
tificationsNSTx
13:32:39,980 DEBUG [org.rhq.enterprise.server.util.concurrent.AlertSerializer] (Thread-8 (HornetQ-client-global-threads-1005764547)) tid= 310: alertDefinitionId=10292: releasing write lock after being locked for millis=609
13:32:39,980 DEBUG [org.rhq.enterprise.server.util.concurrent.AlertSerializer] (Thread-8 (HornetQ-client-global-threads-1005764547)) tid= 310: alertDefinitionId=10292: released write lock
13:32:39,981 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (Thread-8 (HornetQ-client-global-threads-1005764547)) HibernateStats[ queries=30, xactions=81, loads=546, connects=78, time=639 ](perf: too many xactions?) for SLSB:AlertConditionConsumerBean
.onMessage
13:32:40,488 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (EJB default - 6) No java.naming.factory.initial set. Using the default factory.

Comment 3 Nyiri Márk 2015-02-09 07:50:46 UTC

Hello!

I installed a new centos 7 , rhq 13.1 with jre 1.7, and postgresql.
After rhq install first make a "TEST" rule, a user and alert template RHQ down alert with System Rule notification.
The problem is same before, so that problem is still exists in 13.1 and not my environment, db (oracle) problem.