It's all about the answers!

Ask a question

RejectedExecutionException - SCM DELIVER


0
1
Bernd van Oostrum (21523955) | asked Aug 14 '15, 8:55 a.m.
edited Aug 14 '15, 8:56 a.m.
Every now and then, we're having a 'RejectedExecutionException' at the moment of 'SCM DELIVER'.
This command is executed as part of 'mvn scm:checkin'

We are working with RTC 5.0.1
Depending on where/when the error occurs, we can just rerun the build and cross our fingers.

Is there anything we can do to avoid having this error?

[INFO] --- maven-scm-plugin:1.9.2:checkin (default-cli) @ SatmarsServices ---

[INFO] Executing: cmd.exe /X /C "scm create changeset --username s_JTSBUILD --password ***** "set development parent 4.45-INT-SNAPSHOT""

[INFO] Working directory: D:\Jenkins\workspace\rtc.release.int.fleetservices.satmarsservices\SatmarsServices

[INFO] Executing: cmd.exe /X /C "scm status --username s_JTSBUILD --password ***** --wide"

[INFO] Working directory: D:\Jenkins\workspace\rtc.release.int.fleetservices.satmarsservices\SatmarsServices

[INFO] Executing: cmd.exe /X /C "scm checkin --username s_JTSBUILD --password ***** ."

[INFO] Working directory: D:\Jenkins\workspace\rtc.release.int.fleetservices.satmarsservices\SatmarsServices

[INFO] Executing: cmd.exe /X /C "scm deliver --repository-uri https://rtc.essers.com:9443/ccm --username s_JTSBUILD --password ***** --source "java.bld.int.fleetservices Workspace" --target java.integration --overwrite-uncommitted"

[INFO] Working directory: D:\Jenkins\workspace\rtc.release.int.fleetservices.satmarsservices\SatmarsServices

[ERROR] Error: java.util.concurrent.RejectedExecutionException: Task com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher$4@59f1464d rejected from java.util.concurrent.ThreadPoolExecutor@22e52a56[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 40]

      at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2114)

      at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:852)

      at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1415)

      at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher.queue(EventSource.java:787)

      at com.ibm.team.repository.client.util.EventSource.sendEvents(EventSource.java:639)

      at com.ibm.team.repository.client.util.EventSource.release(EventSource.java:404)

      at com.ibm.team.filesystem.rcp.core.internal.changes.util.ComponentSyncContext.setLoggedIn(ComponentSyncContext.java:1305)

      at com.ibm.team.filesystem.rcp.core.internal.changes.util.listeners.RepositoryListener.handleEvents(RepositoryListener.java:58)

      at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher$1.run(EventSource.java:720)

      at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

      at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher.process(EventSource.java:713)

      at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher$3.run(EventSource.java:771)

      at com.ibm.team.repository.client.util.ThreadCheck.runProhibitingLongOps(ThreadCheck.java:174)

      at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher.process(EventSource.java:756)

      at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher$4.run(EventSource.java:790)

      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1176)

      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)


Regards,
Bernd.


Comments
Arun K Sriramaiah commented Aug 14 '15, 10:52 a.m. | edited Aug 18 '15, 5:57 a.m.

   Hi Bernd,


Please have a check  below links.

     Here are the related links:

Regards,
Arun.


Bernd van Oostrum commented Aug 16 '15, 12:36 p.m.

Hi @arusrira,

How do these links help me resolving the interna java-error ('RejectedExecutionException') I'm facing?



Donald Nong commented Aug 16 '15, 7:52 p.m.

Have you checked the ccm.log file or other available log files for more detailed error messages? The function "runProhibitingLongOps" in the stack makes me think that the issue may be caused by some timeouts.


Arun K Sriramaiah commented Aug 17 '15, 8:32 a.m.

Hi Bernd,


If you have a RTC - Jenkins integration which could be used for doing all the build related things instead of using the scm or lscm commands. might help.

Please refer the similar forum post below.


Regards,
Arun.


Christian Giesa commented Dec 09 '15, 10:38 a.m. | edited Dec 09 '15, 10:39 a.m.

Hello,

is there any update on this issue? We are facing the same problem with the scm cli. We are working with RTC 5.0.2 and getting exactly the same error message (see below).

The only difference is that we are trying to run the following command: scm.exe show history -r https://***/ccm/ -nl en -C component --json -m 2147483646 -w workspace_uuid

java.util.concurrent.RejectedExecutionException: Task com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher$4@d974da rejected from java.util.concurrent.ThreadPoolExecutor@1e743f7[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 1865]

        at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor.reject(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor.execute(Unknown Source)

        at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher.queue(EventSource.java:787)

        at com.ibm.team.repository.client.util.EventSource.sendEvents(EventSource.java:639)

        at com.ibm.team.repository.client.util.EventSource.release(EventSource.java:404)

        at com.ibm.team.filesystem.rcp.core.internal.changes.util.ComponentSyncContext.setLoggedIn(ComponentSyncContext.java:1305)

        at com.ibm.team.filesystem.rcp.core.internal.changes.util.listeners.RepositoryListener.handleEvents(RepositoryListener.java:58)

        at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher$1.run(EventSource.java:720)

        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

        at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher.process(EventSource.java:713)

        at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher$3.run(EventSource.java:771)

        at com.ibm.team.repository.client.util.ThreadCheck.runProhibitingLongOps(ThreadCheck.java:174)

        at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher.process(EventSource.java:756)

        at com.ibm.team.repository.client.util.EventSource$BackgroundEventDispatcher$4.run(EventSource.java:790)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

        at java.lang.Thread.run(Unknown Source)

Regards,
Chris


Geoffrey Clemm commented Dec 09 '15, 11:56 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

It is very likely you will need to work with IBM support, if you don't get an answer on the forum.   The fact that you get this error outside of the Maven context is a good thing, since it should make it easier for support to reproduce.

showing 5 of 6 show 1 more comments

Be the first one to answer this question!


Register or to post your answer.