Jazz

Forum

Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Only first test runs in test suite

Igor M

(21●6●6) Jan 17 '11, 4:28 a.m.

Hello.

During Test Suite execution in sequential mode just first test is running,
and another tests are not.

In RQM log i see that message:

com.ibm.team.repository.common.TeamRepositoryException&#58; invalid project alias &#58; %25D0%2593%25D0%2590%25D0%259C%25D0%259C%25D0%2590



            at com.ibm.rqm.process.deployment.internal.ProjectAliasService.getProjectAreaByAlias&#40;ProjectAliasService.java&#58;179&#41;



            at sun.reflect.GeneratedMethodAccessor836.invoke&#40;Unknown Source&#41;



            at sun.reflect.DelegatingMethodAccessorImpl.invoke&#40;DelegatingMethodAccessorImpl.java&#58;43&#41;



            at java.lang.reflect.Method.invoke&#40;Method.java&#58;618&#41;



            at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke&#40;ExportProxyServiceRecord.java&#58;370&#41;



            at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0&#40;ExportProxyServiceRecord.java&#58;356&#41;



            at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke&#40;ExportProxyServiceRecord.java&#58;56&#41;



            at $Proxy417.getProjectAreaByAlias&#40;Unknown Source&#41;



            at com.ibm.rqm.planning.service.internal.rest.AttachmentRestService.perform_POST&#40;AttachmentRestService.java&#58;100&#41;



            at com.ibm.team.repository.service.TeamRawService.service&#40;TeamRawService.java&#58;90&#41;



            at sun.reflect.GeneratedMethodAccessor473.invoke&#40;Unknown Source&#41;



            at sun.reflect.DelegatingMethodAccessorImpl.invoke&#40;DelegatingMethodAccessorImpl.java&#58;43&#41;



            at java.lang.reflect.Method.invoke&#40;Method.java&#58;618&#41;



            at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke&#40;ExportProxyServiceRecord.java&#58;370&#41;



            at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0&#40;ExportProxyServiceRecord.java&#58;356&#41;



            at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke&#40;ExportProxyServiceRecord.java&#58;56&#41;



            at $Proxy425.service&#40;Unknown Source&#41;



            at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doRestService&#40;AbstractTeamServerServlet.java&#58;879&#41;



            at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2&#40;AbstractTeamServerServlet.java&#58;1768&#41;



            at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest&#40;AbstractTeamServerServlet.java&#58;1642&#41;



            at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service&#40;AbstractTeamServerServlet.java&#58;1555&#41;



            at javax.servlet.http.HttpServlet.service&#40;HttpServlet.java&#58;729&#41;



            at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service&#40;ServletManager.java&#58;180&#41;



            at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest&#40;ServletRegistration.java&#58;90&#41;



            at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias&#40;ProxyServlet.java&#58;111&#41;



            at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service&#40;ProxyServlet.java&#58;75&#41;



            at javax.servlet.http.HttpServlet.service&#40;HttpServlet.java&#58;729&#41;



            at org.eclipse.equinox.servletbridge.BridgeServlet.service&#40;BridgeServlet.java&#58;121&#41;



            at com.ibm.team.repository.server.servletbridge.JazzServlet.service&#40;JazzServlet.java&#58;54&#41;



            at javax.servlet.http.HttpServlet.service&#40;HttpServlet.java&#58;729&#41;



            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter&#40;ApplicationFilterChain.java&#58;269&#41;



            at org.apache.catalina.core.ApplicationFilterChain.doFilter&#40;ApplicationFilterChain.java&#58;188&#41;



            at org.apache.catalina.core.StandardWrapperValve.invoke&#40;StandardWrapperValve.java&#58;213&#41;



            at org.apache.catalina.core.StandardContextValve.invoke&#40;StandardContextValve.java&#58;172&#41;



            at org.apache.catalina.authenticator.AuthenticatorBase.invoke&#40;AuthenticatorBase.java&#58;525&#41;



            at org.apache.catalina.core.StandardHostValve.invoke&#40;StandardHostValve.java&#58;127&#41;



            at org.apache.catalina.valves.ErrorReportValve.invoke&#40;ErrorReportValve.java&#58;117&#41;



            at org.apache.catalina.core.StandardEngineValve.invoke&#40;StandardEngineValve.java&#58;108&#41;



            at org.apache.catalina.connector.CoyoteAdapter.service&#40;CoyoteAdapter.java&#58;174&#41;



            at org.apache.coyote.http11.Http11Processor.process&#40;Http11Processor.java&#58;873&#41;



            at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection&#40;Http11BaseProtocol.java&#58;665&#41;



            at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket&#40;PoolTcpEndpoint.java&#58;528&#41;



            at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt&#40;LeaderFollowerWorkerThread.java&#58;81&#41;



            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run&#40;ThreadPool.java&#58;689&#41;



            at java.lang.Thread.run&#40;Thread.java&#58;811&#41;

0 votes

1 answer

4,730 views

0 votes

One answer

Kurtis Martin

JAZZ DEVELOPER (1.4k●1●1) Jan 17 '11, 10:07 a.m.

That stack trace looks like an issue when trying to post an attachment. Not sure if it's related to the behavior you are seeing with test suites. But it could be. Try to run the first script in your suite by itself outside of the context of the test suite. Make sure it completes without any errors in your log.

I have heard folks mention issues like this, but I haven't seen a definitive cause. I saw this reported a while back on 2.0.1 iFix 2, so make sure you are on the latest fixpack/ifix release. It may have already been fixed.

I've also seen a situation where a customer corrupted the process configuration source file for their project area and it cause similar behavior. They accidentally did this after connecting the standalone RTC client to their RQM server and making changes to their project area configuration.

Also, I'm not sure if you've modified your role definitions any. But that could contribute to this issue. As the user running the suite would need to be in a role that has permissions to several execution related artifacts (e.g. Test Suite, Test Execution Records, Adapter Task).

0 votes

Your answer

Register or log in 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.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers

Answers and Comments

Question details

rational-quality-manager

× 10,978

Question asked: Jan 17 '11, 4:28 a.m.

Question was seen: 4,730 times

Last updated: Jan 17 '11, 4:28 a.m.

Related questions

.comment.not_top_scorer { display: block; } .comment-form-container { display: block; } .div.comment-tools { display: none; }