It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×10,908

question asked: Mar 04 '12, 8:13 a.m.
question was seen: 3,211 times
last updated: Mar 04 '12, 8:13 a.m.

Related questions

FAQ - How this Forum works

Will my initial warehouse run ever finish ?

0
Kevin Ramer (4.5k●8●183●200) | asked Mar 04 '12, 8:13 a.m.
Just upgraded 4 QM repositories o 3.0.1.2 initiated the DW jobs as described in the upgrade. However the appserver machine is pegged at >90% CPU since the DW jobs started. The job is the Quality Manager job and there are several active services that have this stack trace: 


java.util.regex.Pattern$Slice.match(Pattern.java:3834)

   java.util.regex.Pattern$Start.match(Pattern.java:3055)

   java.util.regex.Matcher.search(Matcher.java:1108)

   java.util.regex.Matcher.find(Matcher.java:544)

   java.util.regex.Matcher.replaceAll(Matcher.java:818)

   java.lang.String.replaceAll(String.java:1566)

   com.ibm.rqm.integration.service.Util.unEscapeURL(Util.java:183)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.copyERElementtoJaxbERElement(ExecutionResultGetHandler.java:1056)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.access$3(ExecutionResultGetHandler.java:1003)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler$1.processItems(ExecutionResultGetHandler.java:320)

   com.ibm.rqm.common.service.util.ItemsVisitor.processItemsInternal(ItemsVisitor.java:24)

   com.ibm.rqm.common.service.util.ItemVisitor.fetchAndProcess(ItemVisitor.java:45)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.internalMarshal(ExecutionResultGetHandler.java:342)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.marshal(ExecutionResultGetHandler.java:223)

   com.ibm.rqm.integration.handler.AbstractGetHandler.generateFeed(AbstractGetHandler.java:1160)

   com.ibm.rqm.integration.handler.AbstractGetHandler.handleQueryRequest(AbstractGetHandler.java:962)

   com.ibm.rqm.integration.handler.AbstractGetHandler.handle(AbstractGetHandler.java:260)

   sun.reflect.GeneratedMethodAccessor304.invoke(Unknown Source)

   sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

   java.lang.reflect.Method.invoke(Method.java:618)

   org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)

   org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)

   org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)


with elapsed times ranging from a few minutes to over 2 hours. Meanwhile our database server is barely active.

So far overall time of "postUpdateSnapshotData" is 8-12h.

Repository database sizes 4-8 Gb.

:x

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Kevin Ramer (4.5k●8●183●200) | answered Mar 07 '12, 8:07 a.m.
Just upgraded 4 QM repositories o 3.0.1.2 initiated the DW jobs as described in the upgrade. However the appserver machine is pegged at >90% CPU since the DW jobs started. The job is the Quality Manager job and there are several active services that have this stack trace: 



java.util.regex.Pattern$Slice.match(Pattern.java:3834)

   java.util.regex.Pattern$Start.match(Pattern.java:3055)

   java.util.regex.Matcher.search(Matcher.java:1108)

   java.util.regex.Matcher.find(Matcher.java:544)

   java.util.regex.Matcher.replaceAll(Matcher.java:818)

   java.lang.String.replaceAll(String.java:1566)

   com.ibm.rqm.integration.service.Util.unEscapeURL(Util.java:183)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.copyERElementtoJaxbERElement(ExecutionResultGetHandler.java:1056)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.access$3(ExecutionResultGetHandler.java:1003)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler$1.processItems(ExecutionResultGetHandler.java:320)

   com.ibm.rqm.common.service.util.ItemsVisitor.processItemsInternal(ItemsVisitor.java:24)

   com.ibm.rqm.common.service.util.ItemVisitor.fetchAndProcess(ItemVisitor.java:45)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.internalMarshal(ExecutionResultGetHandler.java:342)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.marshal(ExecutionResultGetHandler.java:223)

   com.ibm.rqm.integration.handler.AbstractGetHandler.generateFeed(AbstractGetHandler.java:1160)

   com.ibm.rqm.integration.handler.AbstractGetHandler.handleQueryRequest(AbstractGetHandler.java:962)

   com.ibm.rqm.integration.handler.AbstractGetHandler.handle(AbstractGetHandler.java:260)

   sun.reflect.GeneratedMethodAccessor304.invoke(Unknown Source)

   sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

   java.lang.reflect.Method.invoke(Method.java:618)

   org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)

   org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)

   org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)


with elapsed times ranging from a few minutes to over 2 hours. Meanwhile our database server is barely active.

So far overall time of "postUpdateSnapshotData" is 8-12h.

Repository database sizes 4-8 Gb.

:x


Now what?

Failed Quality Management Jobs for RQM Mar 6, 2012 12:13 AM Mar 6, 2012 10:08 PM 21 hours, 55 minutes 



2012-03-06 22:08:56,350 [jazz: AsynchronousTaskRunner-2] ERROR com.ibm.team.datawarehouse.service.rqm              - class com.ibm.team.datawarehous

e.service.rqm.internal.etlbuild.RQMExecStepResRequestLookupETL:execute AQXRE5002E Executing Java ETL Exception: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: java.net.Sock

etTimeoutException: Read timed out

java.sql.SQLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.data

services.client.auth.AuthenticationException: java.net.SocketTimeoutException: Read timed out

        at com.ibm.rational.drivers.jdbc.xml.BaseRDSResultSet.fetchMoreData(BaseRDSResultSet.java:2098)

        at com.ibm.rational.drivers.jdbc.xml.BaseRDSResultSet.next(BaseRDSResultSet.java:1469)

        at com.ibm.team.datawarehouse.service.rqm.internal.etlbuild.RQMExecStepResRequestLookupETL.execute(RQMExecStepResRequestLookupETL.java:88)

        at com.ibm.team.datawarehouse.service.rqm.internal.RemoteRQMSnapshotService.updateSnapshot(RemoteRQMSnapshotService.java:394)

        at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService$1.run(AbstractRemoteSnapshotService.java:193)

        at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$4.run(RemoteDatabaseService.java:206)

        at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:379)

        at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:196)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:618)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:

56)

        at $Proxy25.write(Unknown Source)

        at com.ibm.team.datawarehouse.service.internal.RemoteDataWarehouseProvider.write(RemoteDataWarehouseProvider.java:28)

        at sun.reflect.GeneratedMethodAccessor655.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:618)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:

56)

        at $Proxy725.write(Unknown Source)

        at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService.updateData(AbstractRemoteSnapshotService.java:188)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:618)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
0
permanent link
Kevin Ramer (4.5k●8●183●200) | answered Mar 13 '12, 12:00 p.m.
Obviously, no one else has encountered this....

Just upgraded 4 QM repositories o 3.0.1.2 initiated the DW jobs as described in the upgrade. However the appserver machine is pegged at >90% CPU since the DW jobs started. The job is the Quality Manager job and there are several active services that have this stack trace: 



java.util.regex.Pattern$Slice.match(Pattern.java:3834)

   java.util.regex.Pattern$Start.match(Pattern.java:3055)

   java.util.regex.Matcher.search(Matcher.java:1108)

   java.util.regex.Matcher.find(Matcher.java:544)

   java.util.regex.Matcher.replaceAll(Matcher.java:818)

   java.lang.String.replaceAll(String.java:1566)

   com.ibm.rqm.integration.service.Util.unEscapeURL(Util.java:183)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.copyERElementtoJaxbERElement(ExecutionResultGetHandler.java:1056)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.access$3(ExecutionResultGetHandler.java:1003)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler$1.processItems(ExecutionResultGetHandler.java:320)

   com.ibm.rqm.common.service.util.ItemsVisitor.processItemsInternal(ItemsVisitor.java:24)

   com.ibm.rqm.common.service.util.ItemVisitor.fetchAndProcess(ItemVisitor.java:45)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.internalMarshal(ExecutionResultGetHandler.java:342)

   com.ibm.rqm.execution.service.integration.jaxb.ExecutionResultGetHandler.marshal(ExecutionResultGetHandler.java:223)

   com.ibm.rqm.integration.handler.AbstractGetHandler.generateFeed(AbstractGetHandler.java:1160)

   com.ibm.rqm.integration.handler.AbstractGetHandler.handleQueryRequest(AbstractGetHandler.java:962)

   com.ibm.rqm.integration.handler.AbstractGetHandler.handle(AbstractGetHandler.java:260)

   sun.reflect.GeneratedMethodAccessor304.invoke(Unknown Source)

   sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

   java.lang.reflect.Method.invoke(Method.java:618)

   org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)

   org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)

   org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)


with elapsed times ranging from a few minutes to over 2 hours. Meanwhile our database server is barely active.

So far overall time of "postUpdateSnapshotData" is 8-12h.

Repository database sizes 4-8 Gb.

:x


Now what?

Failed Quality Management Jobs for RQM Mar 6, 2012 12:13 AM Mar 6, 2012 10:08 PM 21 hours, 55 minutes 



2012-03-06 22:08:56,350 [jazz: AsynchronousTaskRunner-2] ERROR com.ibm.team.datawarehouse.service.rqm              - class com.ibm.team.datawarehous

e.service.rqm.internal.etlbuild.RQMExecStepResRequestLookupETL:execute AQXRE5002E Executing Java ETL Exception: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: java.net.Sock

etTimeoutException: Read timed out

java.sql.SQLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.data

services.client.auth.AuthenticationException: java.net.SocketTimeoutException: Read timed out

        at com.ibm.rational.drivers.jdbc.xml.BaseRDSResultSet.fetchMoreData(BaseRDSResultSet.java:2098)

        at com.ibm.rational.drivers.jdbc.xml.BaseRDSResultSet.next(BaseRDSResultSet.java:1469)

        at com.ibm.team.datawarehouse.service.rqm.internal.etlbuild.RQMExecStepResRequestLookupETL.execute(RQMExecStepResRequestLookupETL.java:88)

        at com.ibm.team.datawarehouse.service.rqm.internal.RemoteRQMSnapshotService.updateSnapshot(RemoteRQMSnapshotService.java:394)

        at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService$1.run(AbstractRemoteSnapshotService.java:193)

        at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$4.run(RemoteDatabaseService.java:206)

        at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:379)

        at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:196)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:618)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:

56)

        at $Proxy25.write(Unknown Source)

        at com.ibm.team.datawarehouse.service.internal.RemoteDataWarehouseProvider.write(RemoteDataWarehouseProvider.java:28)

        at sun.reflect.GeneratedMethodAccessor655.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:618)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:

56)

        at $Proxy725.write(Unknown Source)

        at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService.updateData(AbstractRemoteSnapshotService.java:188)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:618)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.