[JBoss JIRA] Created: (JBPORTAL-1338) content editors behave in not predictable manner
by Boleslaw Dawidowicz (JIRA)
content editors behave in not predictable manner
------------------------------------------------
Key: JBPORTAL-1338
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1338
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.6.Beta1
Reporter: Boleslaw Dawidowicz
Assigned To: Boleslaw Dawidowicz
Fix For: 2.6.CR1
Trying to use content editors in dashboard or in AdminPortlet when adding new portlets to page ends up with not predictable behaviour. You end up with either blank page or 'Connection Reset by Peer' message in your browser.
To reproduce just log in as user and go to dashboard or login as admin and try to add some portlets in AdminPortlet
- navigate thru CMS resources
- try to select Google widget
- try to add several portlet windows
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Closed: (JBAS-2629) Double index creation for alterTable
by Alexey Loubyansky (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2629?page=all ]
Alexey Loubyansky closed JBAS-2629.
-----------------------------------
Resolution: Done
Please, don't re-open issues resolved for already released versions. It's better to open a new one.
> Double index creation for alterTable
> ------------------------------------
>
> Key: JBAS-2629
> URL: http://jira.jboss.com/jira/browse/JBAS-2629
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CMP service
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: SuSE 10.0 with JDK-1.5.0_06
> Reporter: Jesper Pedersen
> Assigned To: Alexey Loubyansky
> Fix For: JBossAS-4.0.4.CR2, JBossAS-3.2.8 Final
>
> Attachments: jdbcstartcommand.patch, jdbcstartcommand.patch
>
>
> In JDBCStartCommand::hasIndex() the variable idxAscDesc may be null, since null is a valid result value for ASC_OR_DESC in DatabaseMetaData.
> This leads to returning false for hasIndex() and therefore creating an index on the column - which already may have one (after first deployment).
> Also the implementation currently looks at ascending columns.
> If someone shares their ideas on this matter I can cook up a patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Commented: (JBAS-2629) Double index creation for alterTable
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2629?page=comments#action_12359540 ]
Dimitris Andreadis commented on JBAS-2629:
------------------------------------------
Please don't re-open, rather create a new linked task, or subtask to work on this.
> Double index creation for alterTable
> ------------------------------------
>
> Key: JBAS-2629
> URL: http://jira.jboss.com/jira/browse/JBAS-2629
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CMP service
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: SuSE 10.0 with JDK-1.5.0_06
> Reporter: Jesper Pedersen
> Assigned To: Alexey Loubyansky
> Fix For: JBossAS-3.2.8 Final, JBossAS-4.0.4.CR2
>
> Attachments: jdbcstartcommand.patch, jdbcstartcommand.patch
>
>
> In JDBCStartCommand::hasIndex() the variable idxAscDesc may be null, since null is a valid result value for ASC_OR_DESC in DatabaseMetaData.
> This leads to returning false for hasIndex() and therefore creating an index on the column - which already may have one (after first deployment).
> Also the implementation currently looks at ascending columns.
> If someone shares their ideas on this matter I can cook up a patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Updated: (JBAS-2629) Double index creation for alterTable
by Jesper Pedersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2629?page=all ]
Jesper Pedersen updated JBAS-2629:
----------------------------------
Attachment: jdbcstartcommand.patch
Patch against current Branch_4_2 (pre 4.2.0GA / post 4.2.0CR2) that strips all " characters from the column name for comparison.
> Double index creation for alterTable
> ------------------------------------
>
> Key: JBAS-2629
> URL: http://jira.jboss.com/jira/browse/JBAS-2629
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CMP service
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: SuSE 10.0 with JDK-1.5.0_06
> Reporter: Jesper Pedersen
> Assigned To: Alexey Loubyansky
> Fix For: JBossAS-3.2.8 Final, JBossAS-4.0.4.CR2
>
> Attachments: jdbcstartcommand.patch, jdbcstartcommand.patch
>
>
> In JDBCStartCommand::hasIndex() the variable idxAscDesc may be null, since null is a valid result value for ASC_OR_DESC in DatabaseMetaData.
> This leads to returning false for hasIndex() and therefore creating an index on the column - which already may have one (after first deployment).
> Also the implementation currently looks at ascending columns.
> If someone shares their ideas on this matter I can cook up a patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Reopened: (JBAS-2629) Double index creation for alterTable
by Jesper Pedersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2629?page=all ]
Jesper Pedersen reopened JBAS-2629:
-----------------------------------
Reopened to provide a more fail-safe patch
> Double index creation for alterTable
> ------------------------------------
>
> Key: JBAS-2629
> URL: http://jira.jboss.com/jira/browse/JBAS-2629
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CMP service
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: SuSE 10.0 with JDK-1.5.0_06
> Reporter: Jesper Pedersen
> Assigned To: Alexey Loubyansky
> Fix For: JBossAS-3.2.8 Final, JBossAS-4.0.4.CR2
>
> Attachments: jdbcstartcommand.patch
>
>
> In JDBCStartCommand::hasIndex() the variable idxAscDesc may be null, since null is a valid result value for ASC_OR_DESC in DatabaseMetaData.
> This leads to returning false for hasIndex() and therefore creating an index on the column - which already may have one (after first deployment).
> Also the implementation currently looks at ascending columns.
> If someone shares their ideas on this matter I can cook up a patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months