History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: UP-1158
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Nick Bolton
Reporter: Elliot Metsger
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
uPortal

o.j.p.layout.dlm.RDBMDistributedLayoutStore broken for MS-SQL Server (resultset issue)

Created: 12/Jul/05 12:05 AM   Updated: 08/Jun/07 07:21 PM
Component/s: Distributed Layout Management (DLM)
Affects Version/s: 2.6.0 M1, 2.5.1 RC1, 2.5.1 RC2, 2.5.2 RC1, 2.5.1 RC3, 2.5.1 GA, 2.5.3 RC1, 2.5.2 GA, 2.5.3 RC2, 2.5.3 RC3, 2.5.3 GA, 2.6.0 RC1
Fix Version/s: 2.5.4, 2.6.0 RC2

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File up-1158.txt (3 kb)

Environment: CVS snapshot of rel-2-5-patches. Microsoft SQL (MS-SQL) Database Server. Tomcat 5.5.4. Sun Java 1.5.0-b64. MS Windows 2003 Standard Edition SP1.
Issue Links:
Generic Relation
This issue relates to:
UP-1039 2.5: RDBMPortletPreferencesStore does... Major Closed
UP-849 RDBMPortletPreferencesStore doesn't s... Major Closed
 


 Description  « Hide
After patching/hacking UP-1155, we ran across these result set exceptions which have been seen before in other UPortal classes (UP-1039, UP-849). These result set reading exceptions occur when attempting to view your institutions uPortal home page:

DEBUG [DLM Fragment Activator] dlm.RDBMDistributedLayoutStore.[] Jul/11 22:29:30 - RDBMUserLayoutStore::getStructureStylesheetUserPreferences(): SELECT PARAM_NAME, PARAM_VAL, PARAM_TYPE, ULS.STRUCT_ID, CHAN_ID, ULP.STRUCT_PARM_NM, ULP.STRUCT_PARM_VAL FROM UP_SS_USER_ATTS UUSA, UP_LAYOUT_STRUCT ULS, UP_LAYOUT_PARAM ULP WHERE UUSA.USER_ID=4 AND PROFILE_ID=1 AND SS_ID=4 AND SS_TYPE=1 AND UUSA.STRUCT_ID = ULS.STRUCT_ID AND UUSA.USER_ID = ULS.USER_ID AND UUSA.STRUCT_ID *= ULP.STRUCT_ID AND UUSA.USER_ID *= ULP.USER_ID
ERROR [DLM Fragment Activator] dlm.FragmentActivator.[] Jul/11 22:29:30 -

------ Problem occurred activating Entertainment------
Anomaly occurred while loading structure or theme stylesheet user preferences for fragment 'Entertainment'. The fragment will not be available for inclusion into user layouts.

java.lang.RuntimeException: Anomaly occurred while loading structure or theme stylesheet user preferences for fragment 'Entertainment'. The fragment will not be available for inclusion into user layouts.
at org.jasig.portal.layout.dlm.FragmentActivator.loadPreferences(FragmentActivator.java:350)
at org.jasig.portal.layout.dlm.FragmentActivator.activateFragments(FragmentActivator.java:118)
at org.jasig.portal.layout.dlm.RDBMDistributedLayoutStore$1.run(RDBMDistributedLayoutStore.java:175)
Caused by: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can not re-read row data for column 5.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseResultSet.validateColumnIndex(Unknown Source)
at com.microsoft.jdbc.base.BaseResultSet.getInt(Unknown Source)
at org.apache.commons.dbcp.DelegatingResultSet.getInt(DelegatingResultSet.java:186)
at org.jasig.portal.layout.dlm.RDBMDistributedLayoutStore._getStructureStylesheetUserPreferences(RDBMDistributedLayoutStore.java:1044)
at org.jasig.portal.layout.dlm.RDBMDistributedLayoutStore.getDistributedSSUP(RDBMDistributedLayoutStore.java:841)
at org.jasig.portal.layout.dlm.FragmentActivator.loadPreferences(FragmentActivator.java:343)
... 2 more

DEBUG [DLM Fragment Activator] dlm.FragmentActivator.[] Jul/11 22:29:30 -


 All   Comments   Work Log   Change History      Sort Order:
Elliot Metsger [12/Jul/05 12:06 AM]
Same exception seen in other RDBM-related classes for UPortal 2.4 and 2.5.

Elliot Metsger [12/Jul/05 12:08 AM]
This attached patch fixed this issue for us!

Elliot Metsger [15/Feb/06 04:46 PM]
An additional comment on this: we started out reporting and patching these types of issues. But they kept cropping up, so we ended up taking the easy way out and using the JTDS driver, which doesn't throw this exception.

Nick Bolton [08/Jun/07 05:44 PM]
Actually, I think this is a non-issue now. Column re-reads don't seem to be a factor now relating to this issue. There is a larger issue here where you have column re-reads in other modules. If we really want to support drivers that don't support column re-reads, then we need to address this everywhere. Alternatively, we can just stop supporting these drivers.

Nick Bolton [08/Jun/07 07:21 PM]
No change. See comments.