SCM CLI error code 13 - reserved (OSGi exception)

Christian Giesa (13●1●3●7) | asked Jun 09 '16, 8:54 a.m.
edited Jun 17 '16, 12:51 p.m. by David Lafreniere (4.8k●7)

When using the scm cli version 6.0.1 in combination out of another third party software we are sometimes getting an error message routed through like "Requesting components of workspace failed: Error from subprocess (13)".

We have executed the command 'fec.exe show status'.

The documentation of your error codes is telling something about the osgi (13 - reserved OSGi exception). Can you please give me some more information or hints why this error occurs? https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.team.scm.doc%2Ftopics%2Fr_scm_cli_retcodes.html

Further information:
RTC server 6.0.1 (ifix003)

Thanks

One answer

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Shashikant Padur (4.3k●2●7) | answered Jun 10 '16, 12:35 a.m.
JAZZ DEVELOPER

Couple of questions:

Which OS?

Do you have -vm option in your scm.ini and is it pointing to the IBM JRE 1.6?

Are you able to reproduce from the command prompt?

Comments

Christian Giesa commented Jun 10 '16, 3:04 a.m. | edited Jun 10 '16, 3:05 a.m.

Q:Which OS?
A: OS Windows Server 2008 R2 Enterprise

Q:Do you have -vm option in your scm.ini and is it pointing to the IBM JRE 1.6?
A: java version "1.7.0_79"
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)

Q:Are you able to reproduce from the command prompt?
A: We were not able to reproduce in command prompt, but it occurs round about 1 or 2 times a week on an Jenkins server where 1 job is executed about 10 times a day and 4 jobs are executed every night and about 6 times a week. So we have round about 70 executions a week.

Shashikant Padur commented Jun 14 '16, 3:55 a.m. | edited Jun 14 '16, 4:03 a.m.

JAZZ DEVELOPER

You should raise a support issue since this is an intermittent problem.

By the way, the recommended JRE is IBM JRE 1.6. I am not sure if that would solve the issue.

Christian Giesa commented Jun 23 '16, 6:42 a.m. | edited Jun 23 '16, 6:43 a.m.

I did some further investigations: Comparison between a successful build and a failed build: (excerpt of the scm cli logs)

-Last entry of a failed build
<record>...
<message>SunMSCAPI 1.7: Sun's Microsoft Crypto API provider</message>
</record>
no further entries in the log

In comparison to a successful build:
<record>...
<message>SunMSCAPI 1.7: Sun's Microsoft Crypto API provider</message> <--- same entry in comparison to error build

the following records are new

<record> ..
<message>Set parameter http.method.retry-handler = com.ibm.team.filesystem.client.restproxy.RestInvocationHandler$1@379f6d6</message>
</record>

more entries.....*

Another thing I recognized is: It always takes 5s until the fec command fails

Can you give me some hints regarding the com.ibm.team.filesystem.client.restproxy.RestInvocationHandle? Seems to be that the build is failing because of that restproxy?

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.

It's all about the answers!

Related questions

SCM CLI error code 13 - reserved (OSGi exception)

One answer

Your answer