-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
1.3.1
-
None
It seems that there is a problem with Crowd's redirect that may causing problems with Websphere.
- relates to
-
CWD-950 Officially support Websphere
- Closed
[CWD-949] Cannot deploy Crowd on Websphere 6.1.x Receive error WARNING: Cannot set header. Response already committed.
Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1509310 ] | New: JAC Bug Workflow v3 [ 3364498 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1391088 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1509310 ] |
Workflow | Original: Crowd Development Workflow v2 [ 272327 ] | New: Simplified Crowd Development Workflow v2 [ 1391088 ] |
Workflow | Original: JIRA Bug Workflow v2 [ 173800 ] | New: Crowd Development Workflow v2 [ 272327 ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: jira [ 124439 ] | New: JIRA Bug Workflow v2 [ 173800 ] |
Component/s | New: Deployment [ 12724 ] |
Summary | Original: Cannot deploy Crowd 1.3.x on Websphere 6.1.x Receive error WARNING: Cannot set header. Response already committed. | New: Cannot deploy Crowd on Websphere 6.1.x Receive error WARNING: Cannot set header. Response already committed. |
Support reference count | New: 4 |
We have no realistic plans to add Crowd support for Websphere, so I'm going to close this issue.
We recommend using Tomcat.