January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-518) ReteViewer save as

by Mark Proctor (JIRA)

ReteViewer save as ------------------ Key: JBRULES-518 URL: http://jira.jboss.com/jira/browse/JBRULES-518 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.0.5 It would be nice to do a "save as" for a rete imagine, and specify t he resolution and output type - png, svg etc. -- 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

18 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1216) Problem with defining user listener service

by Mykola Hryhoryan (JIRA)

Problem with defining user listener service ------------------------------------------- Key: JBPORTAL-1216 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1216 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1 Environment: JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Reporter: Mykola Hryhoryan Assigned To: Julien Viet User listener service, defined in <app>/META-INF/jboss-service.xml doesn't start. jboss-service.xml code: <server> <mbean code="org.jboss.portal.core.event.PortalEventListenerServiceImpl" name="portal:service=ListenerService,type=window_listener" xmbean-dd="" xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> <xmbean /> <depends optional-attribute-name="Registry" proxy-type="attribute"> portal:service=ListenerRegistry </depends> <attribute name="RegistryId">window_listener</attribute> <attribute name="ListenerClassName"> biz.spacepeople.listeners.WindowConstraintEventListener </attribute> </mbean> </server> libarry with class WindowConstraintEventListener is in <JBOSS_HOME>\server\default\deploy\jboss-portal.sar\lib\ Sservice starts only if put mbean code into <JBOSS_HOME>\server\default\deploy\jboss-portal.sar\META-INF\jboss-service.xml -- 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

18 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1166) JACC Security integration documentation missing from Portal 2.4.X documentation

by Bradley Smith (JIRA)

JACC Security integration documentation missing from Portal 2.4.X documentation ------------------------------------------------------------------------------- Key: JBPORTAL-1166 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1166 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.4 Final Reporter: Bradley Smith Assigned To: Julien Viet Priority: Critical The documentation for JACC Security integration is missing in Portal 2.4 documentation it was available in the 2.2 release of portal. See also: http://jira.jboss.com/jira/browse/JBPORTAL-459 -- 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

18 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1154) Test metrics integration with JBoss ON

by Thomas Heute (JIRA)

Test metrics integration with JBoss ON -------------------------------------- Key: JBPORTAL-1154 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1154 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.6.CR1 JBoss Portal is exposing metrics, now, JBoss ON needs to use those metrics and we need to test the integration between JBoss ON and JBoss Portal. -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1137) Programatic control of portlet caching behavior

by Jerry Lacy (JIRA)

Programatic control of portlet caching behavior ------------------------------------------------- Key: JBPORTAL-1137 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1137 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.4 Final Environment: Portal 2.4, JDK 1.5, WindowsXP Reporter: Jerry Lacy Assigned To: Julien Viet Attempts to programatically alter the EXPIRATION_CACHE setting of a portlet from within the doView() method has not effect. e.g. response.setProperty( RenderResponse.EXPIRATION_CACHE, "0" ); Unless I am missing something, it doesn't appear that this was implemented anywhere (as of the 2.4 final release). I believe the problem is on line 65 of org.jboss.portal.portlet.aspects.portlet.ProducerCacheInterceptor.invoke(). The cache expiration value is being updated on each request using the configured EXPIRATION_CACHE value regardless of whether an EXPIRATION_CACHE property was set on the response. I added the following test which seems to work based on what little testing I have done so far: // Update the fragment cache info only if the value has not been overridden during render processing if ( fragmentResult.getProperties().getProperty(RenderResponse.EXPIRATION_CACHE) == null ) { fragmentResult.setExpirationSecs(cacheInfo.getExpirationSecs()); } -- 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

18 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1125) CMS needs to allow admins to delete page versions

by Alex Pinkin (JIRA)

CMS needs to allow admins to delete page versions ------------------------------------------------- Key: JBPORTAL-1125 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1125 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Reporter: Alex Pinkin Assigned To: Roy Russo Currently, old versions of pages can't be deleted. Users should be able to delete uneeded versions. -- 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

18 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1211) portal load test: optimize DB query

by Prabhat Jha (JIRA)

portal load test: optimize DB query ----------------------------------- Key: JBPORTAL-1211 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1211 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4.1 SP1 Reporter: Prabhat Jha Assigned To: Julien Viet During portal load test, we found some bottlenecks related to call to DB. At 500 simultaneous user thread, we start seeing org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout with min pool size of 20 and max pool size of 40. I am not sure but the following query which does join of 6 tables probably also needs to be optimized select portalobje0_.PK as PK20_0_, portalobje0_.LISTENER as LISTENER20_0_, portalobje0_4_.INSTANCE_REF as INSTANCE2_27_0_, case when portalobje0_1_.PK is not null then 1 when portalobje0_2_.PK is not null then 2 when portalobje0_3_.PK is not null then 3 when portalobje0_4_.PK is not null then 4 when portalobje0_.PK is not null then 0 end as clazz_0_, declaredpr1_.OBJECT_KEY as OBJECT1_2_, declaredpr1_.jbp_VALUE as jbp2_2_, declaredpr1_.NAME as NAME2_, modes2_.PK as PK3_, modes2_.name as name3_, windowstat3_.PK as PK4_, windowstat3_.name as name4_ from JBP_PORTAL_OBJECT portalobje0_ left outer join JBP_CONTEXT portalobje0_1_ on portalobje0_.PK=portalobje0_1_.PK left outer join JBP_PORTAL portalobje0_2_ on portalobje0_.PK=portalobje0_2_.PK left outer join JBP_PAGE portalobje0_3_ on portalobje0_.PK=portalobje0_3_.PK left outer join JBP_WINDOW portalobje0_4_ on portalobje0_.PK=portalobje0_4_.PK left outer join JBP_PORTAL_OBJECT_PROPS declaredpr1_ on portalobje0_.PK=declaredpr1_.OBJECT_KEY left outer join JBP_PORTAL_MODE modes2_ on portalobje0_.PK=modes2_.PK left outer join JBP_PORTAL_WINDOW_STATE windowstat3_ on portalobje0_.PK=windowstat3_.PK where portalobje0_.PK=? -- 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

18 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1110) Portlet Deployment Directory only allows deploy

by symmetrysolutions (JIRA)

Portlet Deployment Directory only allows deploy ----------------------------------------------- Key: JBPORTAL-1110 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1110 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Server Affects Versions: 2.4 Final Environment: Windows XP SP1, JBoss v4.0.5.GA, Java 1.5 Reporter: symmetrysolutions Assigned To: Julien Viet When the portlet is not deployed from the JBoss Home/server/default/deploy directory the portlet will not deploy. The following error is produced: 2006-11-10 08:59:55,937 ERROR [org.apache.catalina.core.StandardContext] Error starting static Resources java.lang.IllegalArgumentException: Document base C:\jboss-4.0.5.GA\server\default\.\deploy_40\helloworldjsf.war does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:140) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3848) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4019) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) The portlet is not being deployed from C:\jboss-4.0.5.GA\server\default\.\deploy_40 it is actually in C:\deploy_40 but the portal seems to assume the deployment is from the jboss server deploy directory. I always modify my deploy URL in my JBoss service to allow deployments from another directory. The portal itself is actually in this directory and is deploying correctly allong with all of its default portals but my portlet will not deploy unless I put it in the C:\jboss-4.0.5.GA\server\default\deploy directory. The portlet I am using is the default JSF Hello World portlet. I have not tried with other portlets. -- 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

18 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1077) Combination of JEMS 1.2.0beta2 with Portal profile and JBoss ON generates log errors for JBoss AS

by Pete Bennett (JIRA)

Combination of JEMS 1.2.0beta2 with Portal profile and JBoss ON generates log errors for JBoss AS ------------------------------------------------------------------------------------------------- Key: JBPORTAL-1077 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1077 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Environment: Fedora Core 5, Sun JDK 1.5.0_09-b01, JBoss ON 1.4, JEMS Installer 1.2.0beta2 with Portal profile Reporter: Pete Bennett 1. install the JEMS installer 1.2.0beta with the Portal profile 2. install a JON Agent on the same machine 3. follow the steps in the JON Server to enable Tomcat container performance logging 4. start the JEMS JBoss AS Server that has the Portal profile Each time the agent tries to harvest performance data from the JBoss Application server (whatever interval you specify, the following two errors are thrown). This issue is also documented at http://lists.jboss.org/pipermail/jboss-user/2006-August/009902.html . Everything still runs OK but it makes it hard to indentify and alert for REAL errors via JON. 14:53:00,043 ERROR [RoleModuleImpl] Cannot count roles org.hibernate.HibernateException: Unable to locate current JTA transaction at org.hibernate.context.JTASessionContext.currentSession(JTASessionContext.java:61) at org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:541) at org.jboss.portal.identity.db.RoleModuleImpl.getCurrentSession(RoleModuleImpl.java:416) at org.jboss.portal.identity.db.RoleModuleImpl.getRolesCount(RoleModuleImpl.java:286) at sun.reflect.GeneratedMethodAccessor334.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:99) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:197) at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.getAttribute(AbstractMBeanInvoker.java:362) at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:556) at net.hyperic.hq.product.servlet.webapp.JMXServlet.dmpCmd(JMXServlet.java:330) at net.hyperic.hq.product.servlet.webapp.JMXServlet.doGet(JMXServlet.java:468) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at net.hyperic.hq.product.servlet.filter.JMXFilter.doFilter(JMXFilter.java:277) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) 14:53:00,078 ERROR [UserModuleImpl] Cannot count users org.hibernate.HibernateException: Unable to locate current JTA transaction at org.hibernate.context.JTASessionContext.currentSession(JTASessionContext.java:61) at org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:541) at org.jboss.portal.identity.db.UserModuleImpl.getCurrentSession(UserModuleImpl.java:327) at org.jboss.portal.identity.db.UserModuleImpl.getUserCount(UserModuleImpl.java:304) at sun.reflect.GeneratedMethodAccessor419.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:99) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:197) at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.getAttribute(AbstractMBeanInvoker.java:362) at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:556) at net.hyperic.hq.product.servlet.webapp.JMXServlet.dmpCmd(JMXServlet.java:330) at net.hyperic.hq.product.servlet.webapp.JMXServlet.doGet(JMXServlet.java:468) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at net.hyperic.hq.product.servlet.filter.JMXFilter.doFilter(JMXFilter.java:277) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) -- 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

18 years, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1071) Clusterting problems in jboss-portal-2.4.1.CR1

by Rajesh Rajasekaran (JIRA)

Clusterting problems in jboss-portal-2.4.1.CR1 ---------------------------------------------- Key: JBPORTAL-1071 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1071 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran "Portal Session Replication" and "CMS Clustering" scenarios explained in the wiki do not work with jboss-portal-2.4.1.CR1 http://wiki.jboss.org/wiki/Wiki.jsp?page=PortalClusteringTests This was tested using postgresql -- 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

18 years, 10 months

2
1
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 January 2007