Created attachment 881772 [details] agent.log Description of problem: deploying war to domain mode (all manged servers) lead to infinite discovery queue operation run Version-Release number of selected component (if applicable): jon 3.2.1 CP (01.04) How reproducible: always Steps to Reproduce: 1. install jon 3.2.0 2. apply CP to 3.2.0 3. have EAP 6 in domain mode 4. deploy ear (see attachment in BZ #1034218) as domain deployment 5. assign it to all server groups 6. run discovery Actual results: discovery scan stays in InProgress state forever exceptions in agent.log Expected results: discovery run finishes, eap sub-directories/sub-resources discovered Additional info: screen-shot attached fragment from agent.log attached
Created attachment 881773 [details] discovery_infinite_loop
According to stactrace this seems to be caused by switchyard plugin (but may required a fix in AS7 plugin as well). Could you please re-test without having switchyard plugin installed?
Created attachment 881830 [details] apache_snmp_connection-agent.log.png2
removing switch-yard plugin fixed discovery job (it finishes) - the warnings are still visible in agent.log
Ok. So to me that means that we need to file another bz or reassign this bz to the fsw team? @Mike Foley, what do you think here? That means that the version of plugin pack that was deployed with this server will throw errors on agent and cause infinite discovery(defined above) when deployed after cumulative patch 1. This is bad and should be addressed by an updated plugin pack request I think that may need to be released at same time as the cumulative patch? @Armine can we get more details about the plugin pack contents that were deployed onto the server. If it's the same plugin pack that is available with the 3.2.0.GA release then the above applies. If it's the latest plugin pack that was released with FSW, then it's a slightly smaller impact but still bad. CC'ing GSS as well.
This doesn't appear to be a 3.2.1 regression and most likely existed in 3.2.0.GA and is being re-targeted to 3.2.2. This also appears to indicate that the latest FSW update-01 for 3.2 introduces a regression and may require a separate FSW BZ.
action item: QE/Armine retest with JON 3.2 GA. if the issue repros on JON 3.2 GA ... -we need a new BZ. and then escalate that BZ with FSW -we can close this -this does not block JON 3.2.1 if the issue does not repro on JON 3.2 GA -this issue is blocking on JON 3.2.1 -assign target to JON 3.2.1 -this issue blocks JON 3.2.1
retested with 3.2.0 GA and 3.2.0 CP1 (#2 build) - cannot reproduce anymore, closing as works for me.