Jazz installed in Websphere redirects in endless loop.
Hi,
I had jazz 0.6 m2a working great in Websphere. I recently uninstalled it and installed the Beta 2 war file. Now when I try and access Jazz it seems to go into an endless loop redirecting from /jazz/web to /jazz/admin to /jazz/web to /jazz/admin on and on. . . I was able to confirm this using the wget command line which I've posted the output from below. Any ideas? It works find it I shut down Websphere and run it in Tomcat. Thanks, Mike Antosh wget http://someserver.ibm.com:9080/jazz --12:57:02-- http://someserver.ibm.com:9080/jazz => `jazz' Resolving someserver.ibm.com... 192.168.1.1 Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web --12:57:06-- http://someserver.ibm.com:9080/jazz/web => `web' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/admin --12:57:06-- http://someserver.ibm.com:9080/jazz/admin => `admin.1' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web --12:57:06-- http://someserver.ibm.com:9080/jazz/web => `web' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/admin --12:57:06-- http://someserver.ibm.com:9080/jazz/admin => `admin.1' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web --12:57:06-- http://someserver.ibm.com:9080/jazz/web => `web' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/admin --12:57:06-- http://someserver.ibm.com:9080/jazz/admin => `admin.1' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web --12:57:06-- http://someserver.ibm.com:9080/jazz/web => `web' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/admin --12:57:06-- http://someserver.ibm.com:9080/jazz/admin => `admin.1' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web --12:57:06-- http://someserver.ibm.com:9080/jazz/web => `web' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/admin --12:57:06-- http://someserver.ibm.com:9080/jazz/admin => `admin.1' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web --12:57:06-- http://someserver.ibm.com:9080/jazz/web => `web' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/admin --12:57:06-- http://someserver.ibm.com:9080/jazz/admin => `admin.1' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web --12:57:06-- http://someserver.ibm.com:9080/jazz/web => `web' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/admin --12:57:06-- http://someserver.ibm.com:9080/jazz/admin => `admin.1' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web --12:57:06-- http://someserver.ibm.com:9080/jazz/web => `web' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/admin --12:57:06-- http://someserver.ibm.com:9080/jazz/admin => `admin.1' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web --12:57:06-- http://someserver.ibm.com:9080/jazz/web => `web' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/admin --12:57:06-- http://someserver.ibm.com:9080/jazz/admin => `admin.1' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web --12:57:06-- http://someserver.ibm.com:9080/jazz/web => `web' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/admin --12:57:06-- http://someserver.ibm.com:9080/jazz/admin => `admin.1' Connecting to someserver.ibm.com:9080... connected. HTTP request sent, awaiting response... 302 Found Location: http://someserver.ibm.com:9080/jazz/web 20 redirections exceeded. |
4 answers
When you uninstalled the old WAR did you delete the temp directory for it ?
antosh wrote: Hi, |
I don't know what or where the temp directory is, so unless WAS would have deleted it for me, it's still there.
Where is it located? Thanks again, Mike |
You typically find it in directory something like this.
profiles\AppSrv01\temp\rblaptopNode01\server1 In this directory there will be a sub-dir called jazz_war (or something like that). Delete this whole subdirectory. WAS tries to delete it when the application is uninstalled but if a resource in any sub directory is locked the delete will fail. Richard antosh wrote: I don't know what or where the temp directory is, so unless WAS would |
Thank you very much! I uninstalled the war again and ran a find . -name \*azz\*ar\* and came up with quite a bit of left over stuff. Most of it empty directories but there were files in temp as you indicated. I removed this and reinstalled the application. It's working as far as I can tell so I'll let my users pound on it now.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.