Description of problem:
After rebooting the Satellite or restarting the Satellite services, the error below can be seen in the logs during the startup of Tomcat:
Aug 25 09:28:02 alsouza-sat617b server[1099]: 25-Aug-2025 09:28:02.235 WARNING [main] com.google.inject.internal.ProxyFactory.<init> Method [public void org.candlepin.model.ConsumerCurator.delete(org.candlepin.model.Persisted)] is synthetic and is being intercepted by [com.google.inject.persist.jpa.JpaLocalTxnInterceptor@7aee3236]. This could indicate a bug. The method may be intercepted twice, or may not be intercepted at all. # grep "com.google.inject" /var/log/messages | cut -d'[' -f4 | cut -d']' -f1 | sort -u public org.candlepin.model.Persisted org.candlepin.model.ConsumerCurator.create(org.candlepin.model.Persisted,boolean) public org.candlepin.model.Persisted org.candlepin.model.OwnerCurator.create(org.candlepin.model.Persisted) public org.candlepin.model.Persisted org.candlepin.model.ProductCurator.create(org.candlepin.model.Persisted) public org.candlepin.model.Persisted org.candlepin.model.ProductCurator.merge(org.candlepin.model.Persisted) public org.candlepin.model.Persisted org.candlepin.model.RulesCurator.create(org.candlepin.model.Persisted) public void org.candlepin.model.ConsumerCurator.delete(org.candlepin.model.Persisted) public void org.candlepin.model.EntitlementCertificateCurator.delete(org.candlepin.model.Persisted) public void org.candlepin.model.EntitlementCurator.delete(org.candlepin.model.Persisted) public void org.candlepin.model.PoolCurator.delete(org.candlepin.model.Persisted) public void org.candlepin.model.ProductCurator.delete(org.candlepin.model.Persisted) public void org.candlepin.model.RulesCurator.delete(org.candlepin.model.Persisted)
How reproducible:
Every time
Is this issue a regression from an earlier version:
No
Steps to Reproduce:
1. Restart Satellite services or reboot Satellite server
2. Watch /var/log/messages during Tomcat start-up
3.
Actual behavior:
Several warnings about methods from Candlepin can be seen. No issue is associated with this. Just highlighting as a cause for concern.
Expected behavior:
WARNING messages tend to cause panic and raise concern. If these log lines are expected/necessary, then reducing the log line's severity level should be considered.
Business Impact / Additional info:
None