Bug 564495

Summary:	NPE in Tomcat plugin when setting HTTP Connector's Keep-Alive timeout
Product:	[Other] RHQ Project	Reporter:	Ondřej Žižka <ozizka>
Component:	Plugins	Assignee:	Stefan Negrea <snegrea>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.3	CC:	cwelton, jshaughn, snegrea
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-02 07:26:25 UTC	Type:	---
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:	683054, 565628

Description Ondřej Žižka 2010-02-12 21:32:24 UTC

StR:
====

1) Go to the Tomcat 5 HTTP Connector / Configure / CURRENT
2) Set the Keep Alive Timeout value to something
3) Save
4) Go to HISTORY, see that operation. Scroll to the Keep-Alive property. You'll see the following stack trace:


java.lang.NullPointerException at org.rhq.plugins.jmx.MBeanResourceComponent.updateResourceConfiguration(MBeanResourceComponent.java:465) at org.rhq.plugins.jmx.MBeanResourceComponent.updateResourceConfiguration(MBeanResourceComponent.java:445) at org.jboss.on.plugins.tomcat.TomcatConnectorComponent.updateResourceConfiguration(TomcatConnectorComponent.java:224) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:595)


Note:  I did this with secured JMX if that matters; and set few other properties in the same operation.

Comment 1 wes hayutin 2010-02-16 16:58:47 UTC

Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug

Comment 2 wes hayutin 2010-02-16 17:03:31 UTC

making sure we're not missing any bugs in rhq_triage

Comment 6 Heiko W. Rupp 2011-01-12 17:08:14 UTC

Do you recall if that was for standalone tomcat or wihin AS? I guess the latter

Comment 7 Ondřej Žižka 2011-01-13 02:40:01 UTC

Standalone Tomcat / EWS.
See https://issues.jboss.org/browse/JBPAPP-3755 .

Comment 9 Charles Crouch 2011-03-08 13:27:09 UTC

Needs to be reproduced to see if it is still a problem

Comment 10 Ondřej Žižka 2011-03-16 00:18:35 UTC

Still happens. Re-assigning to cahrles.

JON 2.4.1
EWS 1.0.2
Tomcat 5.5




2011-03-15 20:15:43,467 INFO  [ResourceContainer.invoker.nonDaemon-15] (org.rhq.plugins.jmx.MBeanResourceComponent)- Failure setting MBean Resource configuration value
java.lang.NullPointerException
        at org.rhq.plugins.jmx.MBeanResourceComponent.updateResourceConfiguration(MBeanResourceComponent.java:472)
        at org.rhq.plugins.jmx.MBeanResourceComponent.updateResourceConfiguration(MBeanResourceComponent.java:452)
        at org.jboss.on.plugins.tomcat.TomcatConnectorComponent.updateResourceConfiguration(TomcatConnectorComponent.java:232)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)

Comment 11 Stefan Negrea 2011-10-14 21:32:04 UTC

This issues has been resolved around 2009. Also, I could not replicate it with the latest code.

Here is the git commit with the fix:
http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=ab2e3642e4a3790828d053461280d9384ee58668


Please retest.

Comment 12 Heiko W. Rupp 2013-09-02 07:26:25 UTC

Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.