Support

Expand all | Collapse all

InboundJaxrsResponse - 400 Bad Request

  • 1.  InboundJaxrsResponse - 400 Bad Request

    Posted 06-07-2019 12:30
    Edited by Marshall Richard 06-10-2019 09:59
    I have one user who is experiencing some weird behavior.  This User logs in to Jama, go to the Project Test Plans, selects a active test plan and then clicks on the Test Run tab.  Normally this would return the list of all the test runs for that cycle and Test plan but instead the browser returns the attached error message.

    Error Message Bad Request
    The user is located out of the country (on the other side of the globe) so i can't walk or drive out to the Users location and sit down to look over the browser setting.  The error doesn't show up in the log viewer so no help there.  Is there another log or can i up the logging level of one of the logs to capture this information?

    Does anyone have suggestion on how to pin point the users issue?

    Jama Connect 8.25.5 (Self Hosted) Production

    ------------------------------
    Marshall Richard
    Louisiana Office of Technology Services
    Baton Rouge LA
    ------------------------------


  • 2.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-10-2019 11:50
    Marshall:

    Two things initially pop to mind:

    Considering how this user is located remotely, I am wondering if they might be able to provide you a video screen capture (screencast or Zoom recording) of the process leading up to the behavior? Sounds like having some visibility here would be helpful for your troubleshooting process.

    Also, I am wondering if this user has all the permissions needed to view all the items associated with the Test Center?

    Marshall, your thoughts?

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 3.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-10-2019 14:18
    The User did provide a video to show the issue.  It shows the events in this order;
    1. The User logs into Jama
    2. The User clicks on the Project with the issue in the Recently Viewed list
    3. The User clicks Test Plans tabs
    3. The User clicks on one of the test plans in the list.
    4.  They User clicks on the Test Runs tab in the upper right corner and the error message pops up within 5 seconds.

    The error message only appears when the User tries to access the Test Runs for any Test Plan for that Project.  They have a Collaborator license and have read access to the project.
    The User is using Chrome for the Browser but is in Incognito mode.  I asked for try accessing the test runs when not in incognito mode but they have reported getting the same error message.

    ------------------------------
    Marshall Richard
    Louisiana Office of Technology Services
    Baton Rouge LA
    ------------------------------



  • 4.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-10-2019 16:04
    Marshall:

    Sounds like this issue is currently effecting this one user only? If so, I would try:

    1. Disable the current user experiencing this problem.
    2. Create a new user for this person with the exact same permissions (they would need to re-subscribe to any subscriptions)
    3. I would also advise a full reindex after creating the new user.

    Marshall, try this and let me know if it helps your user.

    Best,

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 5.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-17-2019 09:28
    When you say "disable the current user" do you mean disable the AD account or the Jama account that was added through LDAP?
    If you are referring to just the Jama account, we will not be able to create a new user since we use add user from LDAP.  Jama would say that an account with that name already exist.  Unless there is a safe way to permanently delete a Jama user from the Database, this is not a option.

    We are running Jama on RHEL our version of Jama is 8.25.5.  Is there a log that this type of error message would be logged in that would provide more information on the issue the user is experiencing.

    ------------------------------
    Marshall Richard
    Louisiana Office of Technology Services
    Baton Rouge LA
    ------------------------------



  • 6.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-17-2019 11:27
    Marshall:

    If your company is using a LDAP then you will most likely have to reconfigure this user in LDAP. You could go through a process of changing this current user's credentials to something else (preferably to something no one else has or will have in the future) and then recreating this user again. This would be a process your company IT professionals would most likely know how to maneuver for you: using the correct protocols of disabling and syncing when necessary - depending on how your particular network is configured.

    Hope this helps,

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 7.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-28-2019 12:23
    I had a chance to schedule a time with the users that where having the access issue so they could walk through the process that is giving them the error while i had the "advance" logging turned on.  I then created a support bundle, downloaded it and then looked over everything that was captured during the testing time.  What i found was when the user was experiencing the issue, in the jamaseach.log i saw a search error.

    13:10:02.462 [elasticsearch[Black Jack Tarr][transport_client_worker][T#7]{New I/O worker #7}] WARN org.elasticsearch.transport - [Black Jack Tarr] Transport response handler not found of id [2608595]
    13:10:02.466 [qtp371397455-19479] WARN c.j.s.s.p.resource.SearchResource - search by object: index: jama, ndexrestype: ContourItem, exception: A search error occurred.
    Caused by: java.lang.Exception: execution exception during phase "query": RemoteTransportException[[Conquest][10.4.6.12:9300][indices:data/read/search[phase/query]]]; nested: QueryPhaseExecutionException[Result window is too large, from + size must be less than or equal to: [1000000] but was [5000000]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level parameter.];
    at com.jamasoftware.service.search.provider.SearchException.<init>(SearchException.java:9) ~[classes!/:2.2.3]

    Could this be a possible cause for the 400 Bad Request my User (now two Users) are getting when trying to pull up Test Runs?



    ------------------------------
    Marshall Richard
    Louisiana Office of Technology Services
    Baton Rouge LA
    ------------------------------



  • 8.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-28-2019 13:02
    Marshall:

    From initially reading this Error message it looks like the data-set your users are attempting to retrieve is too large (by 5X) for the limits set. It would be interesting to read the whole Support bundle to get a better picture, could you make a ticket with our Support team, attach this bundle, so that we have the security to review this for you? I will look out for it and attach this thread to the ticket to complete the circle of communication for our Technical Support Engineers.

    Thank you,

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 9.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-28-2019 14:15
    I tried to enter a support ticket and attach the support bundle but since the bundle is 258 MB, it wouldn't let me attach it.  I was going to try to open a ticket through email but i again ran into a file size issue.  is there something other way to get the support bundle to you?

    I also noticed that in the drop down menu for Version, i could not find our version of Jama (8.25.5).

    ------------------------------
    Marshall Richard
    Louisiana Office of Technology Services
    Baton Rouge LA
    ------------------------------



  • 10.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-28-2019 15:37
    Not a problem, just mention that you have a Support bundle but its too big to attach. A support team member will send you an uplink. And mention the version in the body of the email and our BSS will triage it with that info.

    Thank you,

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 11.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-28-2019 15:45
    Thank you for all your help.  I have submitted a support ticket (#48322).

    ------------------------------
    Marshall Richard
    Louisiana Office of Technology Services
    Baton Rouge LA
    ------------------------------



  • 12.  RE: InboundJaxrsResponse - 400 Bad Request

    Posted 06-28-2019 15:49
    Great Marshall,

    I linked this thread to the ticket, I'll follow the progress and if we come up with a sharable solution will communicate it here in this thread for anyone else who might find it useful.

    Best,

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------