February 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2258) Create file in CMS not working for several databases

by Viliam Rockai (JIRA)

Create file in CMS not working for several databases ---------------------------------------------------- Key: JBPORTAL-2258 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2258 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.7.0 Final Reporter: Viliam Rockai Assignee: Sohil Shah Fix For: 2.7.1 Final there are problems with CMS when using oracle9i, oracle10g and postgresql databases. when trying to create file, an error page (HTTP Status 500 - ) appears. please proceed these steps on clean database. create file with: 1. login as admin 2. click admin->cms 3. select create file and create file with these parameters FileName:"testfile" Description:"testdesc" Title:"testtitle" Language: English and type "test content" into the content textarea. 4. click create after clicking create you see and error page dependent on used database. for oracle 9i: exception javax.servlet.ServletException: java.sql.BatchUpdateException: ORA-00001: unique constraint (PORTAL.SYS_C0019847085) violated org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:278) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause java.sql.BatchUpdateException: ORA-00001: unique constraint (PORTAL.SYS_C0019847085) violated oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343) oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10698) org.jboss.resource.adapter.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:620) ----- for oracle 10g: exception javax.servlet.ServletException: java.sql.BatchUpdateException: ORA-00001: unique constraint (PORTAL.SYS_C0017247442) violated org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:278) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause java.sql.BatchUpdateException: ORA-00001: unique constraint (PORTAL.SYS_C0017247442) violated oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343) oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10698) org.jboss.resource.adapter.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:620) ----------- for postgres: exception javax.servlet.ServletException: java.sql.BatchUpdateException: Batch entry 0 insert into jbp_cms_wsp_prop (PROP_ID, PROP_DATA, PK) values (6bfbb6eb-47b9-472f-aadb-234861b8ddeb/{http://jboss.org/jcr/portalcms}lang..., <stream of 28 bytes>, 33) was aborted. Call getNextException to see the cause. org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:278) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause java.sql.BatchUpdateException: Batch entry 0 insert into jbp_cms_wsp_prop (PROP_ID, PROP_DATA, PK) values (6bfbb6eb-47b9-472f-aadb-234861b8ddeb/{http://jboss.org/jcr/portalcms}lang..., <stream of 28 bytes>, 33) was aborted. Call getNextException to see the cause. org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError(AbstractJdbc2Statement.java:2530) org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1317) org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:350) ------------ when the browsers back button is pressed, trying to click the create button again lead into new error (same for each db): ERROR Cause: javax.portlet.PortletException: org.jboss.portal.cms.CMSException: javax.transaction.xa.XAException Message: org.jboss.portal.cms.CMSException: javax.transaction.xa.XAException StackTrace: javax.portlet.PortletException: org.jboss.portal.cms.CMSException: javax.transaction.xa.XAException at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.processAction(CMSAdminPortlet.java:879) at org.jboss.portlet.JBossPortlet.processAction(JBossPortlet.java:392) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl$Invoker.doFilter(PortletContainerImpl.java:557) at org.jboss.portal.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:109) ------------------------------ the interesting part is that i.e. creation of a directory in cms is working fine at the start, but once you try to create file, you have this exception and you cannot create even the folder anymore. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

4
17
0 / 0

[JBoss JIRA] Created: (JBID-39) SAML2 Web Browser SSO

by Anil Saldhana (JIRA)

SAML2 Web Browser SSO --------------------- Key: JBID-39 URL: https://jira.jboss.org/jira/browse/JBID-39 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 1.0.0.alpha1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBID-35) XML Signature Support

by Anil Saldhana (JIRA)

[ https://jira.jboss.org/jira/browse/JBID-35?page=com.atlassian.jira.plugin... ] Anil Saldhana closed JBID-35. ----------------------------- Resolution: Done > XML Signature Support > --------------------- > > Key: JBID-35 > URL: https://jira.jboss.org/jira/browse/JBID-35 > Project: JBoss Identity > Issue Type: Task > Components: FederatedIdentity > Reporter: Anil Saldhana > Assignee: Anil Saldhana > Fix For: 1.0.0.alpha1 > > > We need to provide xml signature support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1468) Eliminate message.copy on DLQ and Expire. Instead just creating a new reference to the same message.

by Clebert Suconic (JIRA)

Eliminate message.copy on DLQ and Expire. Instead just creating a new reference to the same message. ---------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1468 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1468 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assignee: Tim Fox DLQ and Expire are copying Messages between queues, by assigning a new ID. This will be a problem with LargeMessages. (Say if a message has 2G. The move will need to copy a file around on the server file, and this could lead to timeouts since Expire could be generated from the user side). This would be a problem with replication also. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1459) Equivalent of servlet transport for JBM/Netty

by Tim Fox (JIRA)

Equivalent of servlet transport for JBM/Netty --------------------------------------------- Key: JBMESSAGING-1459 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1459 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0 Beta We need some kind of equivalent of the remoting servlet transport for Netty/JBM to allow JBM 2.0 to be used over standard web server port (8080) in AS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-544) Use NBIO for connection model

by Tim Fox (JIRA)

Use NBIO for connection model ----------------------------- Key: JBMESSAGING-544 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 For throughput and scalability we need to use a non blocking IO model to provide connections between jms clients and server. Unfortunately the JBoss remoting model does not currently allows this. We can either drive JBoss Remoting to support this model (may take some time) Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA. This would also solve the problem of providing a functional and performant multiplex transport. Essentially we need a bidirectional channel between jms client and server. On either end bytes can be read or witten in a non blocking fashion. On top of that we can introduce simple framing in order to provide multiplex functionality. -- 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

17 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-604) Duplicate message detection

by Tim Fox (JIRA)

Duplicate message detection --------------------------- Key: JBMESSAGING-604 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-604 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Whereas JMS requires once and only once *delivery* of messages, there are no such guarantees when sending messages to a queue/durable sub. This can result in duplicate messages existing in a queue or durable sub. For some clients this is unacceptable, so we should implement a feature which alerts to the presence of duplicates. This can be done by keeping a persistent cache of message (or transaction) id on the server. Entries should time out after a period of time. This will not remove duplicates 100% of the time since we cannot cache the previous values of id for ever, but only for a window. See forum thread for more details -- 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

17 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1341) Client side failover

by Tim Fox (JIRA)

Client side failover -------------------- Key: JBMESSAGING-1341 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1341 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta Need to re-enable client side failover. We will implement automatic failover onto backup node. This will involve resending messages that backup node says it has not received. This means we will need to keep track on the client side of messages sent but for which no confirmation has arrived. -- 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

17 years, 3 months

1
2
0 / 0

[JBoss JIRA] Commented: (JGRP-134) Emission of JMX notifications on membership changes

by Vladimir Blagojevic (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-134?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic commented on JGRP-134: ------------------------------------------ Actually it does not have to be at the top of the stack, can be anywhere in the stack. > Emission of JMX notifications on membership changes > --------------------------------------------------- > > Key: JGRP-134 > URL: https://jira.jboss.org/jira/browse/JGRP-134 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.9 > Reporter: Bela Ban > Assignee: Vladimir Blagojevic > Fix For: 2.8 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JGRP-134) Emission of JMX notifications on membership changes

by Vladimir Blagojevic (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-134?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic commented on JGRP-134: ------------------------------------------ It is very easy and clean to signal connect/disconnect/reconnect events since these are captured by ChannelListener and can be easily translated to JMX notifications - already have a working prototype. However, I am not sure how to do send notifications for view changes. > Emission of JMX notifications on membership changes > --------------------------------------------------- > > Key: JGRP-134 > URL: https://jira.jboss.org/jira/browse/JGRP-134 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.9 > Reporter: Bela Ban > Assignee: Vladimir Blagojevic > Fix For: 2.8 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2009