[JBoss JIRA] Resolved: (JBPORTAL-740) Postgres constraint violation causes CMS create to blank portlet
by Roy Russo (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-740?page=all ]
Roy Russo resolved JBPORTAL-740.
--------------------------------
Fix Version/s: 2.4.1 Final
Resolution: Won't Fix
Assignee: Roy Russo
> Postgres constraint violation causes CMS create to blank portlet
> ----------------------------------------------------------------
>
> Key: JBPORTAL-740
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-740
> Project: JBoss Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Portal CMS
> Affects Versions: 2.4 Final
> Environment: Mac OS X 10.4.5, PostgreqQL 8.1
> Reporter: Leonard Sitongia
> Assigned To: Roy Russo
> Fix For: 2.4.1 Final
>
>
> I'm trying the portal code in CVS today.
> It looks like a constraint violation triggers a series of exceptions which result in the CMSAdmin portlet disappearing.
> I'm using the WCK editor to create a new web page under default. When I click to save it, the page is refreshed but the CMSAdmin portlet is gone, no longer in the page.
> I see these errors:
> 2006-03-10 13:25:05,126 DEBUG [org.hibernate.util.JDBCExceptionReporter] could not insert: [org.jboss.portal.cms.h
> ibernate.state.WSPProp] [insert into jbp_cms_wsp_prop (PROP_ID, PROP_DATA, PK) values (?, ?, ?)]
> org.postgresql.util.PSQLException: ERROR: duplicate key violates unique constraint "jbp_cms_wsp_prop_pkey"
> 2006-03-10 13:25:05,131 ERROR [org.hibernate.util.JDBCExceptionReporter] ERROR: duplicate key violates unique cons
> traint "jbp_cms_wsp_prop_pkey"
> 2006-03-10 13:25:05,131 ERROR [org.hibernate.event.def.AbstractFlushingEventListener] Could not synchronize databa
> se state with session
> org.hibernate.exception.ConstraintViolationException: could not insert: [org.jboss.portal.cms.hibernate.state.WSPP
> rop]
> 2006-03-10 13:25:05,179 ERROR [org.apache.jackrabbit.core.state.XAItemStateManager] org.apache.jackrabbit.core.sta
> te.ItemStateException: failed to write property state: 90af15f1-c5d7-47ba-9cee-c73f38861627/{http://www.jcp.org/jc
> r/1.0}primaryType: could not insert: [org.jboss.portal.cms.hibernate.state.WSPProp]
> 2006-03-10 13:25:05,181 DEBUG [org.hibernate.jdbc.JDBCContext] no active transaction, could not register Synchroni
> zation
> 2006-03-10 13:25:06,177 ERROR [org.jboss.portal.core.portlet.cms.admin.CMSAdminPortlet] The portlet threw an excep
> tion
> java.lang.NullPointerException
> at org.jboss.portal.core.portlet.cms.admin.CMSAdminPortlet.doView(CMSAdminPortlet.java:148)
--
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, 6 months
[JBoss JIRA] Resolved: (JBPORTAL-581) index.html (utf8)
by Roy Russo (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-581?page=all ]
Roy Russo resolved JBPORTAL-581.
--------------------------------
Fix Version/s: 2.6.Beta1
Resolution: Cannot Reproduce Bug
> index.html (utf8)
> -----------------
>
> Key: JBPORTAL-581
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-581
> Project: JBoss Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Portal CMS
> Affects Versions: 2.2.1 Final
> Environment: solaris9(sparc) 1G memory Mysql4.1
> Reporter: kevnlin kevnlin
> Assigned To: Roy Russo
> Fix For: 2.6.Beta1
>
>
> I change jboss-service.xml lang -->zh
> and create a file in CMS -default folder -index.html (lang ZH)
> the index.html context UTF8 word
> but cann't view chinese word in default page
> I try the portal 2.2.1 RC1 Jboss4.0.3SP1
> could U tell me the corrent step to show chinses page
>
> I find the error log
> 2006-01-21 23:15:48,588 ERROR [org.jboss.portal.core.command.InvokeWindowActionCommand] An portlet exception occured in portlet portal.CMSPortlet
> java.lang.NullPointerException
> at org.jboss.portal.cms.impl.ContentImpl.getSize(ContentImpl.java:174)
> at org.jboss.portal.core.portlet.cms.CMSPortlet.processAction(CMSPortlet.java:123)
> at org.jboss.portal.portlet.PortletContainer.invokeAction(PortletContainer.java:483)
> at org.jboss.portal.portlet.PortletContainer.dispatch(PortletContainer.java:424)
> at org.jboss.portal.server.app.ComponentInvocation.dispatch(ComponentInvocation.java:79)
> at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:140)
> at org.jboss.portal.core.aspects.component.TransactionInterceptor.invoke(TransactionInterceptor.java:72)
> at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
> at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
> at org.jboss.portal.core.aspects.component.HeaderInterceptor.invoke(HeaderInterceptor.java:50)
> at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
> at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
> at org.jboss.portal.server.aspects.component.NavigationInterceptor.invoke(NavigationInterceptor.java:76)
> at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
> at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
> at org.jboss.portal.server.aspects.component.CacheInterceptor.invoke(CacheInterceptor.java:167)
> at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
> at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
> at org.jboss.portal.server.aspects.component.ModesInterceptor.invoke(ModesInterceptor.java:88)
> at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
--
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, 6 months
[JBoss JIRA] Created: (JBREM-581) can not do connection validation with ssl transport (only impacts detection)
by Tom Elrod (JIRA)
can not do connection validation with ssl transport (only impacts detection)
----------------------------------------------------------------------------
Key: JBREM-581
URL: http://jira.jboss.com/jira/browse/JBREM-581
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: detection
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
When a detector gets the detection message from a server, the detection message does not include (nor should it), the ssl info needed to make the ping invocation on that server to verify it is indeed dead. Per JBREM-580, will currently just avoid making ping invocation if transport supports ssl. This means that never does the ping invocation to ensure that the server is really down (and not just lack of getting detection message update), but instead will just consider it dead if detection message is stale.
--
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, 6 months
[JBoss JIRA] Created: (JBPORTAL-1104) setting expiration cache has no effect.
by Brian McGovern (JIRA)
setting expiration cache has no effect.
---------------------------------------
Key: JBPORTAL-1104
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1104
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Server
Affects Versions: 2.4 Final
Environment: Happens on all my environments W2K
Reporter: Brian McGovern
Assigned To: Julien Viet
Fix For: 2.4.1 Final, 2.4 Final
Doing the following in the portlet code OR setting the expiration-cache to 0 in the portlet.xml has no effect on the portlet.
public void doView(RenderRequest request, RenderResponse response) throws PortletException, IOExcept
ion, UnavailableException
{
response.setProperty( RenderResponse.EXPIRATION_CACHE, "0" );
}
--
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, 6 months
[JBoss JIRA] Created: (JBRULES-504) Cannot use the object's property named as "attributes" in a rule
by Vineeth Varghese (JIRA)
Cannot use the object's property named as "attributes" in a rule
----------------------------------------------------------------
Key: JBRULES-504
URL: http://jira.jboss.com/jira/browse/JBRULES-504
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.0.4
Environment: Windows 2000 with Jdk1.5
Reporter: Vineeth Varghese
Assigned To: Mark Proctor
Attachments: src.zip
The word "attributes" seem to be a keyword in JBoss Rules. Basically if I have an Object that has a property named as "attributes", I cannot use it in the IDE or create a rulebase out of it. We end up getting the following error:-
org.drools.rule.InvalidRulePackage: unknown:9:19 Unexpected token 'attributes'
at org.drools.rule.Package.checkValidity(Unknown Source)
at org.drools.common.AbstractRuleBase.addPackage(Unknown Source)
at com.sample.DroolsTest.readRule(DroolsTest.java:72)
at com.sample.DroolsTest.main(DroolsTest.java:23)
Even the IDE highlights this as an error.
--
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, 6 months