Results 1 to 5 of 5

Thread: Strange issue; decodedURLComponent

  1. #1
    Ext GWT Premium Member
    Join Date
    Jun 2008
    Location
    Poland
    Posts
    306

    Exclamation Strange issue; decodedURLComponent

    Hi,

    I'm using GXT 2.3.1a and GWT 2.7. Recently we notice the attached issue (decodedURLComponent cannot be null) but it is very random and occurs only with Tomcat, on Weblogic, Websphere or JBoss running on the same server it is working fine. Plus it is very random, it fails on 2/50 installations and I have no idea why, it is exactly the same web application, the same Tomcat version, on some server it works fine, on two it doesn't.
    Do you have any idea what can cause such an issue?

    Thanks,
    Mariusz

  2. #2
    Ext GWT Premium Member
    Join Date
    Jun 2008
    Location
    Poland
    Posts
    306

    Default

    It looks like I get this issue only when using Tomcat 8, I downgraded Tomcat to v7 and it works now fine.
    Any idea why GXT doesn't work with Tomcat 8?

    Thanks,
    Mariusz

  3. #3
    Sencha Sr Product Manager
    Join Date
    Jan 2012
    Location
    Arlington, WA
    Posts
    1,178

    Default

    It sounds like a timing issue in the execution of the code more than it does of the specific function failing because of tomcat 8. Hard to say without seeing how it's wired up. Would you have a test case of that so I could see if I could reproduce it?

  4. #4
    Ext GWT Premium Member
    Join Date
    Jun 2008
    Location
    Poland
    Posts
    306

    Default

    It's a very complex application and it's very hard to reproduce it... With so many communication I have no idea how to even test it.. It happened twice so far, in both situations on Tomcat as I remember, we changed the Tomcat version and it's working now. But I cannot reproduce it anymore, it's very strange.. Any idea where should I look for an issue?

    Thanks,
    Mariusz

  5. #5
    Sencha Sr Product Manager
    Join Date
    Jan 2012
    Location
    Arlington, WA
    Posts
    1,178

    Default

    I think narrowing down if it's a client or server side issue would be the first drilling routine. If it's related to the initialization, I'd be interested in the transit of resources and comparing that from working to not working machine. Outside of that, I don't have enough context to see how that exception is occuring. I might suggesting asking the same question on Stack Exchange, there are others that use tomcat too that might have seen that.

Similar Threads

  1. Strange issue in converting to Ext 4
    By frew in forum Sencha Ext JS Q&A
    Replies: 4
    Last Post: 22 Nov 2011, 7:09 PM
  2. Strange issue in Firefox 3
    By Lloyd K in forum Sencha Ext JS Q&A
    Replies: 6
    Last Post: 25 Feb 2009, 4:51 AM
  3. Strange Issue
    By gurusingh in forum Ext 1.x: Help & Discussion
    Replies: 3
    Last Post: 27 Feb 2008, 2:58 AM
  4. Very strange Ajax issue
    By luv2hike in forum Ext 2.x: Help & Discussion
    Replies: 2
    Last Post: 16 Feb 2008, 7:25 PM
  5. strange issue
    By gurusingh in forum Sencha Ext JS Q&A
    Replies: 1
    Last Post: 12 Nov 2007, 6:22 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •