November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-806) JBM is assuming it can look up system properties on the client side

by Tim Fox (JIRA)

JBM is assuming it can look up system properties on the client side ------------------------------------------------------------------- Key: JBMESSAGING-806 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-806 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP3, 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta2, 1.0.1.SP4 JBM (JMSRemotingConnection) does several System.getProperties() to get the override bind address and port. However in a security restricted environment e.g. jnlp or applet this may not work. This causes an exception to be thrown and the connection is not created. Need to catch the exception and set to null. -- 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

15 years, 10 months

5
15
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1197) support HTTP transport

by Jeff Mesnil (JIRA)

support HTTP transport ---------------------- Key: JBMESSAGING-1197 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1197 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Remoting Reporter: Jeff Mesnil Assigned To: Jeff Mesnil Fix For: 2.0.0 Alpha the new remoting code based on MINA currently supports only TCP transport. It must also support HTTP transport. MINA provides an HTTP package we can use for both the JMS clients (send requests/receive responses) and the JMS servers (receive request/send response). Message delivery must also be taken into account. The client can use polling (and remains a simple HTTP client). However since MINA code is used on both the client and ther server, we need to check if we can send HTTP requests to the client on the same TCP connection (the ideabeing that we MUST NOT open a server connection on the client in any way) -- 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

15 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-5682) Profile service does not include newly added content in getModifiedDeployments()

by Brian Stansberry (JIRA)

Profile service does not include newly added content in getModifiedDeployments() -------------------------------------------------------------------------------- Key: JBAS-5682 URL: http://jira.jboss.com/jira/browse/JBAS-5682 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Brian Stansberry Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.CR2 If a new deployment is added to a profile via Profile.addDeployment(VFSDeployment, DeploymentPhase), a subsequent call to Profile.getModifiedDeployments() will not include that deployment. Basically, the various getModifiedDeployments() impls do a VFS scan for new content, but ignore anything that they already know about from an addDeployment(...) call. See forum thread for more in depth discussion. -- 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

15 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1394) Refactor messaging buffer interface for netty integration

by Tim Fox (JIRA)

Refactor messaging buffer interface for netty integration --------------------------------------------------------- Key: JBMESSAGING-1394 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1394 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta MessagingBuffer needs to be refactored to work more like netty3 - i.e. no limit() or flip() -- 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

15 years, 10 months

2
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1438) Auto expand broken on invm message buffer

by Tim Fox (JIRA)

Auto expand broken on invm message buffer ----------------------------------------- Key: JBMESSAGING-1438 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1438 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0 Beta The current invm message buffer does not allow auto expand, this means using invm is currently broken unless you never need to auto expand a buffer. We should refactor our MessageBuffer so it does not require auto expanding -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1846) Create Style Guide for renaissance theme and for global styles

by Wesley Hales (JIRA)

Create Style Guide for renaissance theme and for global styles -------------------------------------------------------------- Key: JBPORTAL-1846 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1846 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Wesley Hales Fix For: 2.6.4 Final -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2236) Increase the size of the text field when editing a preference on a portlet instance

by Chris Laprun (JIRA)

Increase the size of the text field when editing a preference on a portlet instance ----------------------------------------------------------------------------------- Key: JBPORTAL-2236 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2236 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

15 years, 10 months

2
2
0 / 0

[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

15 years, 10 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

15 years, 10 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

15 years, 10 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008