[
https://jira.codehaus.org/browse/SCM-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304631#comment-304631
]
Stefan Schlott commented on SCM-652:
------------------------------------
In a completely unrelated project, I stumbled over a very similar-sounding
problem: Connecting to the client via Java API without giving any credentials
resulted in the same UnsatisfiedLinkError. The solution in my case: After
creating the MKS integration point and session, call "si connect" -
autoconnecting doesn't seem to work.
> Exception UnsatisfiedLinkError when running under Linux
> -------------------------------------------------------
>
> Key: SCM-652
> URL: https://jira.codehaus.org/browse/SCM-652
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-integrity
> Affects Versions: 1.6
> Environment: Linux Red-Hat 4 Update 6 32bits
> JDK 1.6.0_11
> Maven 2.2.1
> MKS Source 2009
> Build: 8.10.0.5799
> Service Pack: 005-01
> Hotfixes: C041000005-019, C041000005-021
> Copyright 2001 - 2010 MKS Software Inc.; in Canada copyright owned by MKS
> Inc. All rights reserved.
> Reporter: Jeremie BOUSQUET
> Priority: Critical
>
> I have a very light test project stored in Integrity.
> SCM commands (like "scm:status") ran against this project under windows work
> well.
> If I check-out this same project under Linux environment (with an MKS client
> 2009 configured properly), I get the following error when running scm:status
> (or any other command) :
> [INFO] [scm:status {execution: default-cli}]
> [INFO] MKS Integrity API Version: 4.10
> [INFO] Attempting to connect with the MKS Integrity Server
> [INFO] Using a common session. Connection information is obtained from
> client preferences
> java.lang.UnsatisfiedLinkError: Cannot load apiclientrunner
> at
> com.mks.connect.ClientCmdRunnerImpl.<init>(ClientCmdRunnerImpl.java:53)
> at
> com.mks.connect.UserApplicationSessionImpl._createCmdRunner(UserApplicationSessionImpl.java:546)
> at
> com.mks.connect.CmdRunnerCreatorImpl.createCmdRunner(CmdRunnerCreatorImpl.java:90)
> at
> org.apache.maven.scm.provider.integrity.APISession.connect(APISession.java:115)
> at
> org.apache.maven.scm.provider.integrity.command.login.IntegrityLoginCommand.executeLoginCommand(IntegrityLoginCommand.java:66)
> at
> org.apache.maven.scm.command.login.AbstractLoginCommand.executeCommand(AbstractLoginCommand.java:45)
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
> at
> org.apache.maven.scm.provider.integrity.IntegrityScmProvider.login(IntegrityScmProvider.java:182)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.login(AbstractScmProvider.java:730)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.status(AbstractScmProvider.java:772)
> at
> org.apache.maven.scm.manager.AbstractScmManager.status(AbstractScmManager.java:487)
> at org.apache.maven.scm.plugin.StatusMojo.execute(StatusMojo.java:54)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [ERROR] MKS API Exception: Cannot load apiclientrunner
> [INFO] exited with return code -1
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Cannot run status command :
> Embedded error: Can't login.
> Exit Code: -1
> Here no credentials were provided in the SCM connection url, but providing
> credentials lead to the same error.
> A command "si connect" issued under same environment with same parameters
> (hostname, credentials...) connects successfully to MKS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
