Can you provide some more details on your environment? Are you using JIRA Standalone, or an external app server? If external, which app server?

thanks

com.atlassian.jira.web.util.component.PicoJavaActionFactory.getActionImpl(PicoJavaActionFactory.java:64) at webwork.action.factory.ScriptActionFactoryProxy.getActionImpl(ScriptActionFactoryProxy.java:54) at webwork.action.factory.XMLActionFactoryProxy.getActionImpl(XMLActionFactoryProxy.java:54) at webwork.action.factory.PrefixActionFactoryProxy.getActionImpl(PrefixActionFactoryProxy.java:102) at webwork.action.factory.JspActionFactoryProxy.getActionImpl(JspActionFactoryProxy.java:53) at webwork.action.factory.CommandActionFactoryProxy.getActionImpl(CommandActionFactoryProxy.java:62) at webwork.action.factory.AliasingActionFactoryProxy.getActionImpl(AliasingActionFactoryProxy.java:96) at webwork.action.factory.CommandActionFactoryProxy.getActionImpl(CommandActionFactoryProxy.java:53) at webwork.action.factory.ContextActionFactoryProxy.getActionImpl(ContextActionFactoryProxy.java:36) at webwork.action.factory.PrepareActionFactoryProxy.getActionImpl(PrepareActionFactoryProxy.java:37) at webwork.action.factory.ParametersActionFactoryProxy.getActionImpl(ParametersActionFactoryProxy.java:46) at webwork.action.factory.ChainingActionFactoryProxy.getActionImpl(ChainingActionFactoryProxy.java:52) at com.atlassian.jira.web.util.component.DefaultPicoActionFactory.getActionImpl(DefaultPicoActionFactory.java:49) at webwork.action.factory.ActionFactory.getAction(ActionFactory.java:63) at

Could you please try deleting Tomcat's work/ directory, and restarting. Occasionally Tomcat confuses itself about the state of compiled JSPs.

If this doesn't help, please attach the logs here (or mail them to jira-support@atlassian.com). If you don't mind sending us an XML backup that would also help.

Re. web.xml, you shouldn't be modifying anything in there - some things changed in web.xml between 2.6.1 and 3.0, so the unmodified 3.0 web.xml should be used.

As for Tomcat's server.xml and JSP compilation caching, I've cleared everything and am using 3.0.1 defaults now. That did not help.

Thanks for the reports.

I've just tried Tomcat 4.1.30 and an unable to replicate this problem there. Could you try deleting Tomcat's work/ directory, and see if that helps?

i tried today the life upgrade of our jira database, but it failed. Could you give me a hint, what my error could have been? Within the logs, it seems that jira doesnt recognize, that an interal upgrade of the database is necessary...
Starting service Tomcat-Standalone
Apache Tomcat/4.1.27
09.11.2004 09:34:05 org.objectweb.jotm.Jotm <init>
INFO: JOTM started with a local transaction factory which is not bound.
09.11.2004 09:34:05 org.objectweb.jotm.Jotm <init>
INFO: CAROL initialization
2004-11-09 09:34:07,087 WARN [core.entity.jdbc.DatabaseUtil] Entity "CustomField" has 9 fields but table "customfield" has 7 columns.
2004-11-09 09:34:07,089 WARN [core.entity.jdbc.DatabaseUtil] Field "customfieldsearcherkey" of entity "CustomField" is missing its corresponding column "CUSTOMFIELDSEARCHERKEY"
2004-11-09 09:34:07,113 WARN [core.entity.jdbc.DatabaseUtil] Field "customfieldtypekey" of entity "CustomField" is missing its corresponding column "CUSTOMFIELDTYPEKEY"
2004-11-09 09:34:07,120 WARN [core.entity.jdbc.DatabaseUtil] Entity "CustomFieldOption" has 6 fields but table "customfieldoption" has 4 columns.
2004-11-09 09:34:07,120 WARN [core.entity.jdbc.DatabaseUtil] Field "type" of entity "CustomFieldOption" is missing its corresponding column "optiontype"
2004-11-09 09:34:07,125 WARN [core.entity.jdbc.DatabaseUtil] Field "parentoptionid" of entity "CustomFieldOption" is missing its corresponding column "PARENTOPTIONID"
2004-11-09 09:34:07,131 WARN [core.entity.jdbc.DatabaseUtil] Entity "CustomFieldValue" has 9 fields but table "customfieldvalue" has 7 columns.
2004-11-09 09:34:07,131 WARN [core.entity.jdbc.DatabaseUtil] Field "parentkey" of entity "CustomFieldValue" is missing its corresponding column "PARENTKEY"
2004-11-09 09:34:07,187 WARN [core.entity.jdbc.DatabaseUtil] Field "valuetype" of entity "CustomFieldValue" is missing its corresponding column "VALUETYPE"
2004-11-09 09:34:07,244 WARN [core.entity.jdbc.DatabaseUtil] Entity "FieldLayoutSchemeAssociation" has no table in the database
2004-11-09 09:34:07,248 WARN [core.entity.jdbc.DatabaseUtil] Entity "IssueLink" has 5 fields but table "issuelink" has 4 columns.
2004-11-09 09:34:07,249 WARN [core.entity.jdbc.DatabaseUtil] Field "sequence" of entity "IssueLink" is missing its corresponding column "SEQUENCE"
2004-11-09 09:34:07,264 WARN [core.entity.jdbc.DatabaseUtil] Entity "IssueLinkType" has 5 fields but table "issuelinktype" has 4 columns.
2004-11-09 09:34:07,265 WARN [core.entity.jdbc.DatabaseUtil] Field "style" of entity "IssueLinkType" is missing its corresponding column "pstyle"
2004-11-09 09:34:07,270 WARN [core.entity.jdbc.DatabaseUtil] Entity "IssueType" has 6 fields but table "issuetype" has 5 columns.
2004-11-09 09:34:07,271 WARN [core.entity.jdbc.DatabaseUtil] Field "style" of entity "IssueType" is missing its corresponding column "pstyle"
2004-11-09 09:34:07,281 WARN [core.entity.jdbc.DatabaseUtil] Entity "PortalPage" has 5 fields but table "portalpage" has 3 columns.
2004-11-09 09:34:07,281 WARN [core.entity.jdbc.DatabaseUtil] Field "sequence" of entity "PortalPage" is missing its corresponding column "SEQUENCE"
2004-11-09 09:34:07,287 WARN [core.entity.jdbc.DatabaseUtil] Field "description" of entity "PortalPage" is missing its corresponding column "DESCRIPTION"
2004-11-09 09:34:07,317 WARN [core.entity.jdbc.DatabaseUtil] Entity "Version" has 9 fields but table "version" has 8 columns.
2004-11-09 09:34:07,317 WARN [core.entity.jdbc.DatabaseUtil] Field "releasedate" of entity "Version" is missing its corresponding column "RELEASEDATE"
2004-11-09 09:34:07,326 WARN [core.entity.jdbc.DatabaseUtil] Entity "Workflow" has no table in the database
2004-11-09 09:34:07,329 WARN [core.entity.jdbc.DatabaseUtil] Entity "WorkflowScheme" has no table in the database
2004-11-09 09:34:07,331 WARN [core.entity.jdbc.DatabaseUtil] Entity "WorkflowSchemeEntity" has no table in the database
09.11.2004 09:34:08 org.quartz.impl.StdSchedulerFactory instantiate
INFO: Quartz scheduler 'JiraQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
09.11.2004 09:34:08 org.quartz.impl.StdSchedulerFactory instantiate
INFO: Quartz scheduler version: 1.0.7
2004-11-09 09:42:38,220 WARN [ofbiz.core.entity.SequenceUtil] [SequenceUtil.SequenceBank.fillBank] first select failed: trying to add row, result set was empty for sequence: FieldLayoutSchemeAssociation
09.11.2004 09:42:38 org.quartz.core.QuartzScheduler start
INFO: Scheduler JiraQuartzScheduler_$_NON_CLUSTERED started.
[Filter: profiling] Using parameter [jira_profile]
[Filter: profiling] defaulting to off [autostart=false]
[Filter: profiling] Turning filter off [jira_profile=off]
09.11.2004 09:42:40 com.atlassian.jira.web.dispatcher.JiraServletDispatcher init
WARNUNG: Unable to find 'webwork.multipart.saveDir' property setting. Defaulting to javax.servlet.context.tempdir
09.11.2004 09:42:40 com.atlassian.jira.web.dispatcher.JiraServletDispatcher init
INFO: Action dispatcher initialized
log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester).
log4j:WARN Please initialize the log4j system properly.

Thx

Titus

Titus Leskien
Abteilung IT

SSI Schäfer Noell GmbH
i_Park Klingholz 18/19
D-97232 Giebelstadt

phone +49 / (0) 9334 / 979 - 409
fax +49 / (0) 9334 / 979 - 100
fax2 +49 / (0) 1212 / 5 126 03 146
eMail leskien@ssi-schaefer-noell.com
Internet www.ssi-schaefer-noell.com

----Ursprüngliche Nachricht----
Von: Jeff Turner (JIRA) jira@atlassian.com
Gesendet: Mittwoch, 3. November 2004 03:10
An: Leskien Titus
Betreff: [JIRA] Commented: (JRA-4977) Cannot add new portlet to
dashboard with older Tomcat versions

[ http://jira.atlassian.com/browse/JRA-4977?page=comments#action_27085 ]

Jeff Turner commented on JRA-4977:
----------------------------------

Scott,

I've just tried Tomcat 4.1.30 and an unable to replicate this problem there. Could you try deleting Tomcat's work/ directory, and see if that helps?

–
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.atlassian.com/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira

You need to export / re-import with HSQL as it does not support the SQL 'ALTER' statement.

If this is the case, can you export from your old system, and then re-import into your new system?

Actually - neither do I.

Titus - can you please create a support issue regarding your problems?

http://support.atlassian.com/

Cheers,
Scott

If you are able to replicate this, please raise a new issue and attach any relevant logs/server config files (perhaps on support.atlassian.com if these contain sensitive info). We are still unable to replicate this on Tomcat versions beyond 4.1.24, so any extra info you could provide would be helpful.

<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8083" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />

The new (correct) connector is:

<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8083" minProcessors="5"
maxProcessors="75" enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0"
connectionTimeout="20000" useURIValidationHack="false"
disableUploadTimeout="true"/>

Many thanks to Grant McKenzie for tracking this down.

Configuration:

Jira Prf.: 3.1 #80
Aache: 2.0.50
mod_jk2: 2.0.4

1. 1. 1. 1. 1. Request with Tomcat-HTTP #######
               POST /jira-enterprise/secure/AddPortlet.jspa HTTP/1.1
               Host: localhost:9080
               User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
               Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,/;q=0.5
               Accept-Language: en-us,en;q=0.5
               Accept-Encoding: gzip,deflate
               Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
               Keep-Alive: 300
               Connection: keep-alive
               Referer: http://localhost:9080/jira-enterprise/secure/AddPortlet!default.jspa?destination=dashboard
               Cookie: JSESSIONID=AF6E25FFC37E6010EFDCA34DD4AC01AF
               Content-Type: application/x-www-form-urlencoded
               Content-Length: 114
               portletId=com.atlassian.jira.plugin.system.portlets%3Abugzilla&destination=dashboard&Hinzuf%FCgen=Hinzuf%FCgen

HTTP/1.x 302 Moved Temporarily
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Location: http://localhost:9080/jira-enterprise/secure/SavePortlet!default.jspa?portletIdStr=com.atlassian.jira.plugin.system.portlets:bugzilla&destination=dashboard
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 0
Date: Thu, 31 Mar 2005 10:13:15 GMT
Server: Apache-Coyote/1.1
----------------------------------------------------------
http://localhost:9080/jira-enterprise/secure/SavePortlet!default.jspa?portletIdStr=com.atlassian.jira.plugin.system.portlets:bugzilla&destination=dashboard

GET /jira-enterprise/secure/SavePortlet!default.jspa?portletIdStr=com.atlassian.jira.plugin.system.portlets:bugzilla&destination=dashboard HTTP/1.1
Host: localhost:9080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,/;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://localhost:9080/jira-enterprise/secure/AddPortlet!default.jspa?destination=dashboard
Cookie: JSESSIONID=AF6E25FFC37E6010EFDCA34DD4AC01AF

HTTP/1.x 200 OK
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Type: text/html;charset=ISO-8859-1
Transfer-Encoding: chunked
Date: Thu, 31 Mar 2005 10:13:15 GMT
Server: Apache-Coyote/1.1

1. 1. 1. 1. / Request with Tomcat-HTTP #####

1. 1. 1. 1. 1. Request with Apache #####
               POST /jira-enterprise/secure/AddPortlet.jspa HTTP/1.1
               Host: jira
               User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
               Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,/;q=0.5
               Accept-Language: en-us,en;q=0.5
               Accept-Encoding: gzip,deflate
               Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
               Keep-Alive: 300
               Connection: keep-alive
               Referer: http://jira/jira-enterprise/secure/AddPortlet!default.jspa?destination=dashboard
               Cookie: JSESSIONID=6A515BB739CD944C853C1921999C641B
               Content-Type: application/x-www-form-urlencoded
               Content-Length: 114
               portletId=com.atlassian.jira.plugin.system.portlets%3Abugzilla&destination=dashboard&Hinzuf%FCgen=Hinzuf%FCgen

HTTP/1.x 302 Moved Temporarily
Date: Thu, 31 Mar 2005 10:15:29 GMT
Server: Apache/2.0.52 (Fedora)
Content-Type: text/html; charset=ISO-8859-1
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store, must-revalidate
Location: saveportlet!default.jspa?portletidstr=com.atlassian.jira.plugin.system.portlets:?portletIdStr=com.atlassian.jira.plugin.system.portlets:bugzilla&destination=dashboard
Content-Length: 0
Keep-Alive: timeout=15, max=97
Connection: Keep-Alive
----------------------------------------------------------
http://jira/jira-enterprise/secure/saveportlet!default.jspa?portletidstr=com.atlassian.jira.plugin.system.portlets:?portletIdStr=com.atlassian.jira.plugin.system.portlets:bugzilla&destination=dashboard

GET /jira-enterprise/secure/saveportlet!default.jspa?portletidstr=com.atlassian.jira.plugin.system.portlets:?portletIdStr=com.atlassian.jira.plugin.system.portlets:bugzilla&destination=dashboard HTTP/1.1
Host: jira
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,/;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://jira/jira-enterprise/secure/AddPortlet!default.jspa?destination=dashboard
Cookie: JSESSIONID=6A515BB739CD944C853C1921999C641B

HTTP/1.x 404 Not Found
Date: Thu, 31 Mar 2005 10:15:29 GMT
Server: Apache/2.0.52 (Fedora)
Content-Type: text/html;charset=ISO-8859-1
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Language: en-US
Pragma: no-cache
Cache-Control: no-cache, no-store, must-revalidate
Keep-Alive: timeout=15, max=97
Connection: Keep-Alive
Transfer-Encoding: chunked

1. 1. 1. 1. 1. /Request with Apache #####

The Difference is in the Location Header:

Tomcat-HTTP ok:
http://localhost:9080/jira-enterprise/secure/SavePortlet!default.jspa?portletIdStr=com.atlassian.jira.plugin.system.portlets:bugzilla&destination=dashboard

Apache/mod_jk2 wrong:
saveportlet!default.jspa?portletidstr=com.atlassian.jira.plugin.system.portlets:?portletIdStr=com.atlassian.jira.plugin.system.portlets:bugzilla&destination=dashboard

Because the Apache get the "saveportlet" Loaction it gets the 404 Error.

----------

I don't know if the Redirect in Jira or the mod_jk creates the wrong location. Maybe someone know how to workaround this.

Best Regards
Stephan Helas

Which connector are you using to hook Tomcat up with Apache? You should have:

<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="0"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>

i used the old AJP 1.3 Connector. With Coyote Connector the Redirect
works now.
Tanks a lot.

Best Regards
Stephan Helas