Details
-
Suggestion
-
Resolution: Fixed
-
Fresh 2.5.2 install (prof. eval.) WinXP, standalone, behind a firewall
Description
After installing JIRA 2.5.2 I added an issue and got an ConnectionException + InternalWorkflowException.
[FATAL] XMLWorkflowFactory - -Error creating workflow descriptor
<java.net.ConnectException: Connection timed out: connect>
2003-11-26 17:24:58,331 ERROR [web.action.issue.CreateIssueDetails]
com.opensymphony.workflow.InternalWorkflowException
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
....
The reason is that our bugtrack server is behind a firewall and could not connect to zeus.atlassian.com to download
the /osworkflow/workflow_2_5.dtd file (which obviously is needed).
This is not documented, and i can't find an option to let JIRA go over our proxy. I had to open our firewall for zeus.atlassian.com.
This should be at least stated in the requirements for JIRA, the file should be shipped with the standard install, or an better errormessage should be generated, because it prevents adding new issues and leaves one pretty puzzled.
Attachments
Issue Links
- is duplicated by
-
JRASERVER-2789 Unable to create issue
- Closed
-
JRASERVER-2896 workflow error in fresh install standalone
- Closed
-
JRASERVER-2790 Opening issue is very slow and workflow-actions aren't available
- Closed
-
JRASERVER-2800 Cannot create issue - NOT AGAIN !
- Closed
-
JRASERVER-2864 Can't create new issue when opensymphony.com is down
- Closed
- relates to
-
JRASERVER-2736 File not found: http:/www.opensymphony.com/osworkflow/osworkflow.dtd
- Closed
-
JRASERVER-2865 Run JIRA Standalone in a JVM sandbox
- Closed