Bug 562236

Summary: EAP 4.2/4.3 CPs cannot be applied with JON-2.3
Product: [Other] RHQ Project Reporter: Jaroslaw Kijanowski <jkijanow>
Component: PluginsAssignee: Charles Crouch <ccrouch>
Status: CLOSED WORKSFORME QA Contact: Sunil Kondkar <skondkar>
Severity: high Docs Contact:
Priority: high    
Version: 1.3CC: ccrouch, cwelton, fdrabek, hbrock, ian.springer, mharvey
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-27 18:04:48 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: 557793, 558582    
Attachments:
Description Flags
before applying CP
none
before applying CP (details)
none
after applying CP
none
after applying CP (details) none

Description Jaroslaw Kijanowski 2010-02-05 17:18:30 UTC 
Description of problem:
I was able to patch 4.2.GA, however I wasn't able to patch any other EAP 4.x version.

I've tried with 4.2, 4.2CP06, 4.3 and 4.3CP06. The JBoss Versions recognized by JON 2.3 are:

Version: 4.2.0.GA
Version: 4.2.0.GA_CP06
Version: 4.3.0.GA
Version: 4.3.0.GA_CP06

but in the old JON 1.4 they were:

JBoss Version: 4.2.0.GA
JBoss Version: 4.2.0.GA_CP06_EAP
JBoss Version: 4.3.0.GA_EAP
JBoss Version: 4.3.0.GA_CP06_EAP
and that's in line with the JMX values.

So as of today, it's not possible to apply any cumulative patches up on 4.2 and 4.3.
I could workaround this by changing the metadata of all CPs (removing that "EAP" part of their resource version), but then it won't work with JON 1.4. 


Version-Release number of selected component (if applicable):
JON-2.3.1-8436
jon-plugin-pack-eap-2.3.0.GA
EAP 4.2/4.3

How reproducible:
Always

Steps to Reproduce:
1. setup JON (with EAP plugins), EAP 4.x, Agent, discover EAP
2. setup Channel for EAP CPs

  
Actual results:
Besides EAP 4.2.GA no CPs show up as available to be applied.

Expected results:
All current EAP 4.2/4.3 releases have CPs available on the CSP and they should also be available for JON users.

Additional info:
Comment 1 Charles Crouch 2010-02-05 20:09:30 UTC 
*** Bug 561146 has been marked as a duplicate of this bug. ***
Comment 2 Filip Drabek 2010-02-06 12:03:11 UTC 
Update from EAP4.3 CP1 to JBoss EAP 4.3.0.GA_CP05 failed with message : 

Step Description:
java.lang.RuntimeException: Could not stream package bits for [PackageDetailsKey[Name=JBoss EAP 4.3.0.GA_CP05, Version=4.3.0.GA_CP05 Arch=noarch Type=cumulativePatch]]

Error Message:
[Warning] javax.ejb.EJBException: java.lang.RuntimeException: Could not stream package bits for [PackageDetailsKey[Name=JBoss EAP 4.3.0.GA_CP05, Version=4.3.0.GA_CP05 Arch=noarch Type=cumulativePatch]]
	at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
	at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:240)
	at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:210)
	at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:84)
	at $Proxy370.outputPackageVersionBitsGivenResource(Unknown Source)
	at org.rhq.enterprise.server.content.ContentServerServiceImpl.downloadPackageBitsGivenResource(ContentServerServiceImpl.java:89)
	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.enterprise.communications.command.impl.remotepojo.server.RemotePojoInvocationCommandService.execute(RemotePojoInvocationCommandService.java:184)
	at sun.reflect.GeneratedMethodAccessor244.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)
	at $Proxy441.execute(Unknown Source)
	at org.rhq.enterprise.communications.command.server.CommandProcessor.handleIncomingInvocationRequest(CommandProcessor.java:290)
	at org.rhq.enterprise.communications.command.server.CommandProcessor.invoke(CommandProcessor.java:184)
	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
	at org.jboss.remoting.transport.servlet.ServletServerInvoker.processRequest(ServletServerInvoker.java:232)
	at sun.reflect.GeneratedMethodAccessor241.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)
	at $Proxy384.processRequest(Unknown Source)
	at org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.processRequest(ServerInvokerServlet.java:128)
	at org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.doPost(ServerInvokerServlet.java:157)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.rhq.helpers.rtfilter.filter.RtFilter.doFilter(RtFilter.java:124)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
	at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.RuntimeException: Could not stream package bits for [PackageDetailsKey[Name=JBoss EAP 4.3.0.GA_CP05, Version=4.3.0.GA_CP05 Arch=noarch Type=cumulativePatch]]
	at org.rhq.enterprise.server.content.ContentSourceManagerBean.outputPackageVersionBitsRangeHelper(ContentSourceManagerBean.java:1466)
	at org.rhq.enterprise.server.content.ContentSourceManagerBean.outputPackageVersionBitsRangeGivenResource(ContentSourceManagerBean.java:1309)
	at org.rhq.enterprise.server.content.ContentSourceManagerBean.outputPackageVersionBitsGivenResource(ContentSourceManagerBean.java:1260)
	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.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
	at org.rhq.enterprise.server.common.TransactionInterruptInterceptor.addCheckedActionToTransactionManager(TransactionInterruptInterceptor.java:77)
	at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118)
	at org.rhq.enterprise.server.authz.RequiredPermissionsInterceptor.checkRequiredPermissions(RequiredPermissionsInterceptor.java:153)
	at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118)
	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
	... 72 more
Caused by: java.lang.RuntimeException: Stream data cannot be copied
	at org.rhq.core.util.stream.StreamUtil.copy(StreamUtil.java:118)
	at org.rhq.enterprise.server.content.ContentSourceManagerBean.outputPackageVersionBitsRangeHelper(ContentSourceManagerBean.java:1443)
	... 97 more
Caused by: org.rhq.enterprise.communications.command.client.RemoteIOException
	at org.rhq.enterprise.communications.command.client.RemoteOutputStream.sendRequest(RemoteOutputStream.java:218)
	at org.rhq.enterprise.communications.command.client.RemoteOutputStream.write(RemoteOutputStream.java:185)
	at org.rhq.core.util.stream.StreamUtil.copy(StreamUtil.java:112)
	... 98 more
Caused by: java.lang.IllegalArgumentException: A command asked to access an unknown output stream with ID of [3].  The command was: [Command: type=[remoteoutstream]; cmd-in-response=[false]; config=[{}]; params=[{streamId=3, invocation=NameBasedInvocation[write]}]]
	at org.rhq.enterprise.communications.command.impl.stream.server.RemoteOutputStreamCommandService.execute(RemoteOutputStreamCommandService.java:229)
	at sun.reflect.GeneratedMethodAccessor216.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
	at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
	at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
	at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
	at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)
	at $Proxy0.execute(Unknown Source)
	at org.rhq.enterprise.communications.command.server.CommandProcessor.handleIncomingInvocationRequest(CommandProcessor.java:290)
	at org.rhq.enterprise.communications.command.server.CommandProcessor.invoke(CommandProcessor.java:184)
	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608)
	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406)
	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
Comment 3 Filip Drabek 2010-02-10 21:56:27 UTC 
2010-02-10 19:26:57,296 DEBUG [WorkerThread#0[10.11.9.90:43494]] (jboss.remoting.transport.socket.ClientSocketWrapper)- reset timeout: 60000
2010-02-10 19:27:00,559 DEBUG [WorkerThread#0[10.11.9.90:43494]] (enterprise.communications.command.server.CommandProcessor)- {CommandProcessor.executing}Executing command [Command: type=[remoteoutstream]; cmd-in-response=[false]; config=[{}]; params=[{streamId=1, invocation=NameBasedInvocation[write]}]]
2010-02-10 19:27:00,624 WARN  [WorkerThread#0[10.11.9.90:43494]] (command.impl.stream.server.RemoteOutputStreamCommandService)- {RemoteOutputStreamCommandService.invoke-stream-failure}Output stream being accessed from a remote client encountered an exception - the method invoked was [write]. The command was: [Command: type=[remoteoutstream]; cmd-in-response=[false]; config=[{}]; params=[{streamId=1, invocation=NameBasedInvocation[write]}]]
java.lang.IllegalArgumentException: A command asked to access an unknown output stream with ID of [1].  The command was: [Command: type=[remoteoutstream]; cmd-in-response=[false]; config=[{}]; params=[{streamId=1, invocation=NameBasedInvocation[write]}]]
	at org.rhq.enterprise.communications.command.impl.stream.server.RemoteOutputStreamCommandService.execute(RemoteOutputStreamCommandService.java:229)
	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 com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
	at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
	at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
	at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
	at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)
	at $Proxy0.execute(Unknown Source)
	at org.rhq.enterprise.communications.command.server.CommandProcessor.handleIncomingInvocationRequest(CommandProcessor.java:290)
	at org.rhq.enterprise.communications.command.server.CommandProcessor.invoke(CommandProcessor.java:184)
	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608)
	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406)
	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
Comment 4 Ian Springer 2010-02-17 16:39:45 UTC 
Some more details based on investigation done by Joseph:

* for EAP 4.3.0.GA_CP01 through 4.3.0.GA_CP07, no patches show up
* for EAP 4.2.0.GA, the CP01 patch does not show up
* for EAP 4.2.0.GA_CP01, the CP01 shows up -- but it shouldn't
* for EAP 4.2.0.GA_CP02 through 4.2.0.GA_CP08, no patches show up
Comment 9 Filip Drabek 2010-03-09 21:24:45 UTC 
To test the fix :

1) To test updating of data which are already stored in DB :
  a) Use the older release and try to apply the cumulative patches. (The goal is
    to download the cumulative patch to database)
  b) upgrade the server to new version /run db-upgrade/ and install the  
    cumulative patch to some EAP instance
2) Use fresh install and test if applying cumulative patches works.
    a) test on Oracle
    b) test on Postgres
Comment 13 Jaroslaw Kijanowski 2010-03-24 17:14:53 UTC 
JON 2.3.1 GA + EAP plugin pack

When I install a CP I see one package (4.3.GA CP07) and the status is "In Progress" - see before.png and before-details.png

However once this is done (successfully BTW) I see two packages (4.3 GA_CP07), one has the status "Currently Installed" and one has "Installation in Progress" - see after.png

Besides that when I go to the detailed view to display the manual steps I need to perform, the "Step Number" is always "1" - see after-details1.png

Anyway, I was able to patch:

EAP 4.3 GA -> CP07
EAP 4.3 GA_CP06 -> CP07
EAP 4.2 GA -> CP08
EAP 4.2 GA_CP07 -> CP08

So I'm closing this bugzilla, if you think the two 'issues' mentioned above are real problems, let me know and I'll create a new bz for that.
Comment 14 Jaroslaw Kijanowski 2010-03-24 17:16:06 UTC 
Created attachment 402361 [details]
before applying CP
Comment 15 Jaroslaw Kijanowski 2010-03-24 17:16:45 UTC 
Created attachment 402362 [details]
before applying CP (details)
Comment 16 Jaroslaw Kijanowski 2010-03-24 17:17:36 UTC 
Created attachment 402364 [details]
after applying CP
Comment 17 Jaroslaw Kijanowski 2010-03-24 17:18:09 UTC 
Created attachment 402365 [details]
after applying CP (details)
Comment 18 Charles Crouch 2010-03-24 18:10:52 UTC 
>However once this is done (successfully BTW) I see two packages (4.3 GA_CP07),
>one has the status "Currently Installed" and one has "Installation in Progress"
>- see after.png

Those two items are listed in the audit trail, which I believe is by design. If you look in the completed requests table, there is only one row showing success.

>Besides that when I go to the detailed view to display the manual steps I need
>to perform, the "Step Number" is always "1" - see after-details1.png

This is a known minor issue for which I believe we already have a BZ for

I also see the version trait getting updated in your after screenshots so this all appears to be working correctly. I'm going to resolve this issue.
Thanks for testing effort Jarek
Comment 20 Corey Welton 2010-05-27 18:04:48 UTC 
QA Closing - this has been fixed and tested. (see bug #566235)