Jump to content


p4dtg changelist writeback problem

p4dtg

  • Please log in to reply
3 replies to this topic

#1 johnruck68

johnruck68

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 14 March 2017 - 07:05 PM

I am trying to re-activate a once working perforce<->Jira integration after having migrated server machines so this might just be a config issue hiding somewhere that I haven't found.  In p4dtg, I can get "Valid connection to server" on both the Defect Tracking Sources and Perforce Server Sources tabs and I am also successfully getting jobs created in Perforce from Jira issues that are moved into a development state so I know that the p4dtg is successfully talking to both applications.  The problem I am seeing is on the updating of the changelist information back into Jira.  I have the P4Fix -> Change Info showing (and I have even recreated it to make sure it was current) but nothing shows up in the Change Info field.  What has me perplexed is what I am finding in the Jira-rest log file generated by p4dtg -

Mar 14, 2017 1:21:27 PM com.perforce.p4dtg.plugin.jira.tcp.internal.request.RequestHandler queryDefects
SEVERE: RestClientException{statusCode=Optional.of(404), errorCollections=[ErrorCollection{status=404, errors={}, errorMessages=[The user named '' does not exist]}]}
RestClientException{statusCode=Optional.of(404), errorCollections=[ErrorCollection{status=404, errors={}, errorMessages=[The user named '' does not exist]}]}
at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.claim(DelegatingPromise.java:47)
at com.perforce.p4dtg.plugin.jira.tcp.internal.request.RequestHandler.queryDefects(RequestHandler.java:542)
at com.perforce.p4dtg.plugin.jira.tcp.internal.request.RequestHandler.listDefects(RequestHandler.java:438)
at com.perforce.p4dtg.plugin.jira.tcp.server.TcpSocketServer.getResponse(TcpSocketServer.java:288)
at com.perforce.p4dtg.plugin.jira.tcp.server.TcpSocketServer.handle(TcpSocketServer.java:351)
at com.perforce.p4dtg.plugin.jira.tcp.server.TcpSocketServer.start(TcpSocketServer.java:426)
at com.perforce.p4dtg.plugin.jira.tcp.server.TcpSocketServer.start(TcpSocketServer.java:333)
at com.perforce.p4dtg.plugin.jira.tcp.server.TcpSocketServer.main(TcpSocketServer.java:500)
Caused by: RestClientException{statusCode=Optional.of(404), errorCollections=[ErrorCollection{status=404, errors={}, errorMessages=[The user named '' does not exist]}]}
at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:166)
at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:160)
at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:48)
at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:12)
at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:285)
at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:162)
at com.google.common.util.concurrent.Futures$7.run(Futures.java:1072)
at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:161)
at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:146)
at com.google.common.util.concurrent.AbstractFuture.done(AbstractFuture.java:235)
at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:172)
at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53)
at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:285)
at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:162)
at com.google.common.util.concurrent.Futures$7.run(Futures.java:1072)
at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:161)
at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:146)
at com.google.common.util.concurrent.AbstractFuture.done(AbstractFuture.java:235)
at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:172)
at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53)
at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$1$1.run(SettableFuturePromiseHttpPromiseAsyncClient.java:46)
at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable$1.run(SettableFuturePromiseHttpPromiseAsyncClient.java:197)
at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.runInContext(SettableFuturePromiseHttpPromiseAsyncClient.java:90)
at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable.run(SettableFuturePromiseHttpPromiseAsyncClient.java:192)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Any idea why only this step would not be authenticating as a valid user?  I have verified that I can log into Jira with the user/password that I have specified for it in p4dtg so the account does work.  The account is just setup as a normal user account though (not an Admin level one), is this the problem?

the P4DTG is current one available from your website, Jira is version (v6.3.15#6346-sha1:dbc023d) if this helps.

[Edit - update] - making the account used by p4dtg into a Jira administrator account did not resolve this error message.

#2 johnruck68

johnruck68

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 15 March 2017 - 06:10 PM

Well, this error ended up being a non issue from the standpoint of getting the changelist info back into Jira - that was caused by the default permission scheme only allows Project Role (Developers) to be able to edit issues (which is what the changelist updating is doing).  So I now at least have the changelists updating properly, but I still have no idea what is throwing that user permission error that is in the original posting.

Fyi - to find this setting, go into any project in Jira, then Adminstration->Permissions to see the roles and who has what permissions.

#3 Tubah

Tubah

    Advanced Member

  • Staff
  • 44 posts

Posted 15 March 2017 - 11:42 PM

regarding the

In the KB  P4DTG JIRA Troubleshooting  set the flag for -Djavadts.DUMP_DEBUG=true for the jira source.
This logs to the jira-rest-XXXXX.log.0 file.

Set the mapping's attribute logging level to 3 if not already.

Restart replication.  

In a browser, login into JIRA with the p4dtg user ('perforce') used in jira source.

Update/create an issue in JIRA.   Examine the actual JQL queries in the jira-rest-*.log file.

Cut & paste that JQL into an jira advanced query (while still logged into JIRA as the p4dtg user).

Does that then work or not?

#4 johnruck68

johnruck68

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 17 March 2017 - 06:03 PM

Hmm, I guess we can close this ticket but the mystery will remain.  I made the adjustments you requested to get the extra logging to occur and since then (and even after returning them back to their original settings) I am not seeing the errors being generated at all.  So guess we can leave it as an unknown at this point since I cant cause it to occur anymore.  Thanks for your efforts.





Also tagged with one or more of these keywords: p4dtg

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users