January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-788) Default SFSB timeout should be longer than the default tomcat HttpSession timeout.

by Gavin King (JIRA)

Default SFSB timeout should be longer than the default tomcat HttpSession timeout. ---------------------------------------------------------------------------------- Key: EJBTHREE-788 URL: http://jira.jboss.com/jira/browse/EJBTHREE-788 Project: EJB 3.0 Issue Type: Bug Reporter: Gavin King Priority: Critical This bites every user who tries to use Seam. -- 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, 6 months

6
18
0 / 0

[JBoss JIRA] Created: (JBAS-3767) Create a canonical "JndiServiceMBeanSupport" useful for binding objects to JNDI

by Elias Ross (JIRA)

Create a canonical "JndiServiceMBeanSupport" useful for binding objects to JNDI ------------------------------------------------------------------------------- Key: JBAS-3767 URL: http://jira.jboss.com/jira/browse/JBAS-3767 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Reporter: Elias Ross Assigned To: Scott M Stark A common application integration pattern is to create MBean services that bind objects (or themselves) to JNDI. These objects bound to JNDI are then used in EJBs. It seems generally useful to provide a class with JBoss, similar to ServiceMBeanSupport, which allows users to bind objects to the local JNDI. A lot of JBoss services do bind objects to JNDI and could probably extend from this base class. http://wiki.jboss.org/wiki/Wiki.jsp?page=BindMBeanToJNDI Additional ideas: Create an attribute "BindObject". Then users could do something like: <attribute name="BindObject" attributeClass="..." serialDataType="javaBean"> </attribute> -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1055) minimize/maximize causes portlet to return to initial state

by Johnny Healey (JIRA)

minimize/maximize causes portlet to return to initial state ----------------------------------------------------------- Key: JBPORTAL-1055 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1055 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Server Affects Versions: 2.4 Final Environment: CentOS release 4.4 (Final), jdk1.5.0_06 Reporter: Johnny Healey Assigned To: Julien Viet This has been noticed in a handful of custom portlets, but can be duplicated in the "event test" page that ships with the portal. "Test Event A" can change the color of the text in "Test Event B", but minimizing or maximizing "Test Event B" causes the text to return to the original color, black. -- 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, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1004) Jboss Portal to support virtual hosts

by Sverker Abrahamsson (JIRA)

Jboss Portal to support virtual hosts ------------------------------------- Key: JBPORTAL-1004 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1004 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sverker Abrahamsson JBoss Portal is today unable to support multiple virtual hosts, i.e. it's not possible to create a portal bound to the address www.foo.com and one that is bound to www.bar.com. This is a major problem for real world usage of 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

17 years, 7 months

5
14
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-784) Add Active/Passive deployment feature for JBoss Messaging in 2 node cluster (Need HA part and not Clustering part)

by Rohit Chowdhary (JIRA)

Add Active/Passive deployment feature for JBoss Messaging in 2 node cluster (Need HA part and not Clustering part) ------------------------------------------------------------------------------------------------------------------ Key: JBMESSAGING-784 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-784 Project: JBoss Messaging Issue Type: Task Components: JMS Clustering Affects Versions: 1.2.1 Reporter: Rohit Chowdhary Assigned To: Ovidiu Feodorov Need to be able to deploy JBoss Messaging nodes in a HA configuration, but not load-balanced. Such that only one node is actively serving all the requests, if the current active node goes down, then the passive node picks up the load. Reason would be: To use the available h/w resources at best. We have one dedicated physical server for running JBoss msg. Another physical server that hosts existing JBoss instance running some application. We want to use this second server running a passive JBossMsg instance. So in case when the dedicated JBossMsg goes down, then the second shared server can take the load temporarily automatically, till we bring back the dedicated up again. Other reason would be that we bring down the dedicated JBossMsg server for OS level patching, essentially minimizing the app downtime and increase availablity. -- 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, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-742) Message.getJMSDestination could be null on redeployment of a queue

by Clebert Suconic (JIRA)

Message.getJMSDestination could be null on redeployment of a queue ------------------------------------------------------------------ Key: JBMESSAGING-742 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-742 Project: JBoss Messaging Issue Type: Support Patch Affects Versions: 1.0.1.SP2 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.0.2.CR1, 1.0.2.GA, 1.0.1.SP2 -- 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, 7 months

3
27
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1194) 'Self' producer fails to be registered at server start

by Matt Wringe (JIRA)

'Self' producer fails to be registered at server start ------------------------------------------------------ Key: JBPORTAL-1194 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1194 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha1 Environment: Linux 1.5.0 JVM 4.0.5 JBoss AS Reporter: Matt Wringe Assigned To: Chris Laprun Attachments: server_output.txt When the server is started and the portal-wsrp.sar is located within the deploy directory, the portal cannot cannot load the 'self' wsrp producer. This is due to the portal trying to reference the 'self' producer before 'self' has been bound to the jndi. 15:40:14,739 INFO [WSRPDeploymentFactory] Added consumer for producer 'self' 15:40:14,956 ERROR [STDERR] org.jboss.portal.portlet.InvokerUnavailableException: Problem getting service description for producer self 15:40:14,957 ERROR [STDERR] at org.jboss.portal.wsrp.consumer.ProducerInfo.getServiceDescription(ProducerInfo.java:444) ... 15:40:15,226 ERROR [STDERR] Caused by: javax.naming.NameNotFoundException: wsrp-client not bound 15:40:15,226 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) ... Soon after this step, 'self' becomes bound: 15:40:33,666 INFO [ClientDeployer] Client ENC bound under: wsrp-client Note: if the wsrp-portal.sar is hot deployed after the server has started, then it will load the producer successfully. -- 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, 7 months

7
11
0 / 0

[JBoss JIRA] Created: (JGRP-376) TLS: use priority based queue rather than BoundedLinkedQueue for default thread pool

by Bela Ban (JIRA)

TLS: use priority based queue rather than BoundedLinkedQueue for default thread pool ------------------------------------------------------------------------------------ Key: JGRP-376 URL: http://jira.jboss.com/jira/browse/JGRP-376 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 This will allow us to dispatch incoming messages to threads from the pool based on criteria. - The impl implements interface BoundedChannel - It has N queues, 1 for each sender (possibly those are BoundedLinkedQueues) - There is a max size in bytes for the priority queue, each internal queue has max_size / N bytes where N = number of members. This is dynamically adjusted ADDITION - An internal queue maintains the number of bytes (Message.length()), an offer() or put() increases that amount by the size of the message, a take() or poll() decreases the amount. When a put() or offer() would exceed the max amount, it will block until a take() or poll() decreases it such that the new message can be added to the queue. We might also discard messages to full queues, or implement somthing akin to RED (random early detection), which starts discarding messages *before* the queue is full REMOVAL - Strategy pluggable, e.g. - Take from the fullest queue - Take from the least full queue - Round robin - Weighted round robin (weighted by capacity of each queue), e.g. take relative to capacity from each queue. Example: Queues A (2MB), B (2MB), C (6MB): we take 2 from A, 2 from B and 6 from C - Random robin 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

17 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JGRP-381) TLS: all queues for thread pools should use number of bytes rather than number of messages

by Bela Ban (JIRA)

TLS: all queues for thread pools should use number of bytes rather than number of messages ------------------------------------------------------------------------------------------ Key: JGRP-381 URL: http://jira.jboss.com/jira/browse/JGRP-381 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Instead of defining a max number of elements in a queue BoundedBlockingQueue (used by thread pool), we define a number of bytes. If that number is exceeded, we block on put()/offer(), and only unblock if a take() has removed N number of bytes so we can add our message without exceeding the limit -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-670) PreDestroy called multiple times

by Carlo de Wolf (JIRA)

PreDestroy called multiple times -------------------------------- Key: EJBTHREE-670 URL: http://jira.jboss.com/jira/browse/EJBTHREE-670 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf The PreDestroy callback is called multiple times. Once from the container and once from the pool. IMHO only the pool should call PreDestroy. Other callbacks are already handled by the pool. Unit test is in regression/ejbthree... -- 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, 7 months

3
8
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