[#JRA-3148] Assignment breaks issue viewing

JIRA

Assignment breaks issue viewing

Created: 16/Feb/04 01:16 AM Updated: 30/Jul/06 07:36 PM

Component/s:

None

Affects Version/s:

2.5.2 Professional

Fix Version/s:

3.0 Pro Preview

Time Tracking:

Not Specified

File Attachments:

JIRA problem.txt (52 kB)

Image Attachments:

1. AssignmentError.jpg
(25 kB)

Environment:

« Hide

Win2000server, Bea Weblogic 8.1 Express, Oracle.
Ancient converted/imported data

Issue Links:

Reference

This issue relates to:

~~JRA-3121~~ SQL error when editing an issue

Participants:	Michael van Leeuwen and Owen Fellows
Since last comment:	4 years, 9 weeks, 5 days ago
Resolution Date:	22/Jun/04 02:44 AM
Labels:

Description

« Hide

When assigning an issue to the person issued the issue, the issue can no longer be viewed, due to a page error.

The data was transferred/imported from Jira 2.5 on RedHat/Tomcat/Oracle environment, where the assigment worked fine.

Attached is an image of the result when trying to view the issue and the consolelog from BEA.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Michael van Leeuwen added a comment - 16/Feb/04 01:19 AM

The page when an assignment to the original issuer is made and the issue is opened.

[ Permlink | « Hide ]

Michael van Leeuwen added a comment - 16/Feb/04 04:06 AM

Problem is caused by the mangling of data. Username is something like 'strangechar''strangechar'sername.

[ Permlink | « Hide ]

Michael van Leeuwen added a comment - 17/Feb/04 06:54 AM

Problem seems to be BEA Weblogic related.
Exporting the data; fixing the invalid assignees; and importing this in a standalone using an external datasource seems to prevent this problem.

[ Permlink | « Hide ]

Owen Fellows added a comment - 20/Jun/04 11:18 AM

Did the fix you explained in the comment solve the problem completly? Can this bug be closed?

[ Permlink | « Hide ]

Michael van Leeuwen added a comment - 21/Jun/04 01:31 AM

We probably used the oracle client libs as delivered with BEA in combination with Oracle9. This combination could be the source of our problems. Eventually we switched to standalone+Oracle9 which run correctly.

A note in the documentation to be carefull about which client (JDBC) library to use would suffice to close this issue, I think.

[ Permlink | « Hide ]

Owen Fellows added a comment - 22/Jun/04 02:44 AM

Add note to docs for next release about using BEA drivers.