November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2206) NPE on shutdown with Sun RI portlet

by Chris Laprun (JIRA)

NPE on shutdown with Sun RI portlet ----------------------------------- Key: JBPORTAL-2206 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2206 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.7.0 CR1 Reporter: Chris Laprun Priority: Minor Fix For: 2.7.1 Final java.lang.NullPointerException at com.sun.faces.portlet.FacesPortlet.destroy(FacesPortlet.java:122) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.destroyPortlet(PortletContainerImpl.java:436) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.stop(PortletContainerImpl.java:356) at org.jboss.portal.portlet.impl.container.PortletContainerLifeCycle.invokeStop(PortletContainerLifeCycle.java:81) at org.jboss.portal.portlet.impl.container.LifeCycle.managedStop(LifeCycle.java:163) at org.jboss.portal.portlet.impl.container.PortletApplicationLifeCycle.stopDependents(PortletApplicationLifeCycle.java:363) at org.jboss.portal.portlet.impl.container.LifeCycle.managedStop(LifeCycle.java:156) at org.jboss.portal.portlet.impl.container.PortletApplicationLifeCycle.destroy(PortletApplicationLifeCycle.java:141) at org.jboss.portal.portlet.deployment.jboss.PortletAppDeployment.destroy(PortletAppDeployment.java:333) at org.jboss.portal.server.deployment.jboss.DeploymentContext.destroy(DeploymentContext.java:125) at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.destroy(PortalDeploymentInfoContext.java:252) at org.jboss.portal.server.deployment.jboss.ServerDeployer.destroy(ServerDeployer.java:235) at org.jboss.deployment.MainDeployer.destroy(MainDeployer.java:704) at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:639) at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:632) at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:615) -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2239) DeploymentException on Windows

by Prabhat Jha (JIRA)

DeploymentException on Windows ------------------------------ Key: JBPORTAL-2239 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2239 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.7.0 Final Reporter: Prabhat Jha Assignee: Thomas Heute Fix For: 2.7.1 Final Viliam noticed this first when trying to automate selnium test on windows. I am to reproduce on XP machine as well. When deploying portal using "build.bat deploy-all" and accessing portal page in browser gives: java.lang.IllegalStateException: Context does not exist org.jboss.portal.core.model.portal.DefaultPortalCommandFactory.doMapping(DefaultPortalCommandFactory.java:75) org.jboss.portal.core.controller.Controller.handle(Controller.java:252) org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) org.jboss.portal.core.cms.aspect.IdentityBindingInterceptor.invoke(IdentityBindingInterceptor.java:47) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:68) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) Root cause is: 2008-11-11 09:37:04,125 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: jar:file:/C:/portal/jboss-4.2.3.GA/server/default/tmp/deploy/tmp5407jboss-portal.sar!/conf/data/default-object.xml org.jboss.deployment.DeploymentException: Invalid byte 2 of 2-byte UTF-8 sequence.; - nested throwable: (org.xml.sax.SAXParseException: Invalid byte 2 of 2-byte UTF-8 sequence.) at org.jboss.portal.core.deployment.jboss.ObjectDeployment.start(ObjectDeployment.java:103) at org.jboss.portal.server.deployment.jboss.DeploymentContext.start(DeploymentContext.java:99) at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.start(PortalDeploymentInfoContext.java:220) at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerDeployer.java:217) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy212.deploy(Unknown Source) at org.jboss.portal.server.deployment.jboss.ServerDeployer.registerFactory(ServerDeployer.java:119) at org.jboss.portal.server.deployment.jboss.AbstractDeploymentFactory.registerFactory(AbstractDeploymentFactory.java:113) at org.jboss.portal.server.deployment.jboss.AbstractDeploymentFactory.st -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2195) Creating portal objects with a name or path exceeding 255 characters fails

by Martin Putz (JIRA)

Creating portal objects with a name or path exceeding 255 characters fails -------------------------------------------------------------------------- Key: JBPORTAL-2195 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2195 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.6 Final Reporter: Martin Putz Assignee: Thomas Heute Creating a single portal page with a name longer than 255 characters OR creating multiple nested portal pages resulting in a path longer than 255 characters fails with the following exception: java.sql.BatchUpdateException: Batch entry 0 insert into JBP_OBJECT_NODE ("PATH", NAME, PARENT_KEY, PK) values (test.abcdefghijklmnopqrstuvwxyz abcdefghijklmnopqrstuvwxyz abcdefghijklmnopqrstuvwxyz abcdefghijklmnopqrstuvwxyz abcdefghijklmnopqrstuvwxyz abcdefghijklmnopqrstuvwxyz abcdefghijklmnopqrstuvwxyz abcdefghijklmnopqrstuvwxyz abcdefghijklmnopqrstuvwxyz.asdfasdf sadfasdfasdf, asdfasdf sadfasdfasdf, NULL, 101) was aborted. Call getNextException to see the cause. ... at org.jboss.portal.core.impl.model.portal.PersistentPortalObjectContainer$1.createChild(PersistentPortalObjectContainer.java:103) at org.jboss.portal.core.impl.model.portal.ObjectNode.addChild(ObjectNode.java:151) at org.jboss.portal.core.impl.model.portal.PortalObjectImpl.addChild(PortalObjectImpl.java:680) at org.jboss.portal.core.impl.model.portal.PageImpl.createPage(PageImpl.java:74) The problem is that PersistentPortalObjectContainer.createChild only handles ConstraintViolationExceptions. This exception should be handled gracefully and a proper error message should be displayed instead of the stack trace. -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2237) Where to click to edit a preference value should be clearer

by Chris Laprun (JIRA)

Where to click to edit a preference value should be clearer ----------------------------------------------------------- Key: JBPORTAL-2237 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2237 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.7.0 Final, 2.6.7 Final Reporter: Chris Laprun Fix For: 2.7.1 Final, 2.6.8 Final -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2133) Update documentation umbrella task

by Chris Laprun (JIRA)

Update documentation umbrella task ---------------------------------- Key: JBPORTAL-2133 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2133 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Reference Guide Affects Versions: 2.7.0 Beta1 Reporter: Chris Laprun Fix For: 2.6.7 Final -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4722) Injection of ISecurityManagement via Annotation

by Anil Saldhana (JIRA)

Injection of ISecurityManagement via Annotation ----------------------------------------------- Key: JBAS-4722 URL: http://jira.jboss.com/jira/browse/JBAS-4722 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Anil Saldhana Assigned To: William DeCoste Fix For: JBossAS-5.0.0.Beta3 Currently an instance of JNDIBasedSecurityManagement (interface is ISecurityManagement) is being used in the EJB3AuthenticationInterceptorv2. We need to get this injected (rather than hard coded) via an annotation. -- 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, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-4904) Improve error message when binding fails

by Andrew Rubinger (JIRA)

Improve error message when binding fails ---------------------------------------- Key: JBAS-4904 URL: http://jira.jboss.com/jira/browse/JBAS-4904 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.2.2.GA Reporter: Andrew Rubinger Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA Upon attempt to bind an a subcontext to an address already bound by an object, the following exception occurs: java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context at org.jboss.util.naming.Util.createSubcontext(Util.java:69) at org.jboss.util.naming.Util.rebind(Util.java:125) at org.jboss.util.naming.Util.rebind(Util.java:113) Error message should be in form "Can't bind subContext/obj, because subContext is already bound" -- 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, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-6173) Change "file:/" protocol to "vfsfile:/" in System Properties used by Server

by Andrew Lee Rubinger (JIRA)

Change "file:/" protocol to "vfsfile:/" in System Properties used by Server --------------------------------------------------------------------------- Key: JBAS-6173 URL: https://jira.jboss.org/jira/browse/JBAS-6173 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: JBossAS-5.0.0.GA Replace the following System property values with "vfsfile:/" protocol URLs: jboss.home.url file:/home/alrubinger/business/jboss/wc/jbossas/trunk/build/output/jboss-5.0.0.GA/ jboss.lib.url file:/home/alrubinger/business/jboss/wc/jbossas/trunk/build/output/jboss-5.0.0.GA/lib/ jboss.server.base.url file:/home/alrubinger/business/jboss/wc/jbossas/trunk/build/output/jboss-5.0.0.GA/server/ jboss.server.config.url file:/home/alrubinger/business/jboss/wc/jbossas/trunk/build/output/jboss-5.0.0.GA/server/default/conf/ jboss.server.home.url file:/home/alrubinger/business/jboss/wc/jbossas/trunk/build/output/jboss-5.0.0.GA/server/default/ jboss.server.lib.url file:/home/alrubinger/business/jboss/wc/jbossas/trunk/build/output/jboss-5.0.0.GA/server/default/lib/ jboss.shared.lib.url file:/home/alrubinger/business/jboss/wc/jbossas/trunk/build/output/jboss-5.0.0.GA/server/lib/ As not every instance of AS will be launched from a filesystem. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-4569) ClusterPatrition.stopService( ) fails when server is shut down

by Jerry Gauthier (JIRA)

ClusterPatrition.stopService( ) fails when server is shut down -------------------------------------------------------------- Key: JBAS-4569 URL: http://jira.jboss.com/jira/browse/JBAS-4569 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Jerry Gauthier Assigned To: Jerry Gauthier Priority: Minor Fix For: JBossAS-5.0.0.Beta3 When the server is shut down, the stopService( ) method of ClusterPartition fails with a lengthy stack trace when attempting to unbind the partition from JNDI. The error occurs because InitialContext can't be instantiated due to the following exception. javax.naming.NoInitialContextException: Cannot instantiate class: org.jboss.iiop.naming.ORBInitialContextFactory[Root exception is java.lang.ClassNotFoundException: org.jboss.iiop.naming.ORBInitialContextFactory] This error only occurs when the server is being shut down; it doesn't occur if the HAPArtition service is stopped while the server is running. -- 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, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1217) QueueBrowser only enumerates messages in memory - not paged ones

by Peter Schuebl (JIRA)

QueueBrowser only enumerates messages in memory - not paged ones ---------------------------------------------------------------- Key: JBMESSAGING-1217 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1217 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.0.SP3 Environment: JBoss Messaging 1.4.0.SP3 (using MySQL for persistence) JBoss AS 4.2.1.GA Java 1.6.0_03-b05 Windows XP Reporter: Peter Schuebl Assigned To: Tim Fox The QueueBrowser only enumerates the messages in memory, it won't list the messages which are paged. For testing I setup a queue with the following settings: - FullSize: 20 - PageSize: 10 - DownCacheSize: 5 No consumer is set up for this queue. If I send now 42 messages to this queue browsing the queue (or using the listAllMessages MBean function) only lists 20 of this messages. The MessageCount attribute of the queue correctly displays 42. -- 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, 4 months

3
3
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 November 2008