•  
      request #7248 Mylyn Connector: Internal error validating repository
    Infos
    #7248
    Peter Struck (p3t3rstruck)
    2014-07-30 17:52
    2014-07-21 13:59
    7258
    Details
    Mylyn Connector: Internal error validating repository
    Got the following error when try to login from Ecplise Kepler:

    Message:
    Internal error validating repository

    Exception Stack Trace:
    java.lang.reflect.InvocationTargetException
    at org.eclipse.mylyn.tasks.ui.wizards.AbstractRepositorySettingsPage$29.run(AbstractRepositorySettingsPage.java:2019)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
    Caused by: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)
    at com.google.gson.Gson.fromJson(Gson.java:803)
    at com.google.gson.Gson.fromJson(Gson.java:768)
    at com.google.gson.Gson.fromJson(Gson.java:717)
    at com.google.gson.Gson.fromJson(Gson.java:689)
    at org.tuleap.mylyn.task.core.internal.client.rest.RestOperation.checkServerError(RestOperation.java:343)
    at org.tuleap.mylyn.task.core.internal.client.rest.RestOperation.checkedRun(RestOperation.java:319)
    at org.tuleap.mylyn.task.core.internal.client.rest.TuleapRestClient.login(TuleapRestClient.java:206)
    at org.tuleap.mylyn.task.core.internal.client.rest.TuleapRestClient.validateConnection(TuleapRestClient.java:133)
    at org.tuleap.mylyn.task.ui.internal.repository.TuleapValidator.validate(TuleapValidator.java:84)
    at org.tuleap.mylyn.task.ui.internal.repository.TuleapRepositorySettingsPage$TuleapRepositoryValidator.run(TuleapRepositorySettingsPage.java:194)
    at org.eclipse.mylyn.tasks.ui.wizards.AbstractRepositorySettingsPage$29.run(AbstractRepositorySettingsPage.java:2009)
    ... 1 more
    Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1
    at com.google.gson.stream.JsonReader.beginObject(JsonReader.java:374)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:165)
    ... 12 more
    Root exception:
    com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)
    at com.google.gson.Gson.fromJson(Gson.java:803)
    at com.google.gson.Gson.fromJson(Gson.java:768)
    at com.google.gson.Gson.fromJson(Gson.java:717)
    at com.google.gson.Gson.fromJson(Gson.java:689)
    at org.tuleap.mylyn.task.core.internal.client.rest.RestOperation.checkServerError(RestOperation.java:343)
    at org.tuleap.mylyn.task.core.internal.client.rest.RestOperation.checkedRun(RestOperation.java:319)
    at org.tuleap.mylyn.task.core.internal.client.rest.TuleapRestClient.login(TuleapRestClient.java:206)
    at org.tuleap.mylyn.task.core.internal.client.rest.TuleapRestClient.validateConnection(TuleapRestClient.java:133)
    at org.tuleap.mylyn.task.ui.internal.repository.TuleapValidator.validate(TuleapValidator.java:84)
    at org.tuleap.mylyn.task.ui.internal.repository.TuleapRepositorySettingsPage$TuleapRepositoryValidator.run(TuleapRepositorySettingsPage.java:194)
    at org.eclipse.mylyn.tasks.ui.wizards.AbstractRepositorySettingsPage$29.run(AbstractRepositorySettingsPage.java:2009)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
    Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1
    at com.google.gson.stream.JsonReader.beginObject(JsonReader.java:374)
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:165)
    ... 12 more


    Session Data:
    eclipse.buildId=4.3.2.M20140221-1700
    java.version=1.7.0_55
    java.vendor=Oracle Corporation
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
    Framework arguments: -product org.eclipse.epp.package.standard.product
    Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.standard.product
    Mylyn
    7.2
    CentOS 5 + php53
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Declined
    2014-07-30
    Attachments
    References
    References list is empty

    Follow-ups

    User avatar
    Marked the ticket as declined since it does not require more work after discussion.

    • Status changed from New to Declined
    • Close date set to 2014-07-30
    User avatar
    last edited by: Peter Struck (p3t3rstruck) 2014-07-22 14:08
    Tuleap™ 7.2.99.20

    yes a proxy, but when browse that url i get the same result.

    I think you gave me the hint, i noticed a seperate package to install the core-rest. I tought its included at least in package tuleap-all-dependecies...

    i try to install and test again

    thx so much
    User avatar
    Which version of Tuleap do you use?
    Getting an error 404 on this indicates that the URL "https://your.server/api/v1/tokens" does not exist on your server, which is very strange, since it has been introduced in Tuleap 6.x (I don't remeber exactly, but it's not new)

    Do you have any network peculiarities? (proxy, firewall, this kind of thing)
    User avatar
    Well, that's on the Tuleap server side, so I don't know!
    Ask on the tuleap-devel mailing list, they'll answer you I'm sure. (And I'll how it's done at the same time.)
    User avatar
    Hello,

    I cannot reproduce this problem on tuleap.net.

    One thing is sure, it's that the user/password pair you provided to the connetor is not correct.
    Did you make sure to check the square "save password" to the right of the password field in the repository creation wizard?

    Nevertheless, even though the login/password is not right, you should not have such an error, you should get a clean error message.

    As far as I know, this behaviour can happen if you use your own Tuleap server and have activated the "debug mode".
    This is a known bug (#6727 I believe)