March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-874) INVM persistent message optimisation

by Tim Fox (JIRA)

INVM persistent message optimisation ------------------------------------ Key: JBMESSAGING-874 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-874 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 For persistent messages sent in vm, the message gets converted to a byte[] before db storage, it then gets converted back to a payload on recepipt - this is unnecessary - for the invm case. We should deal with it optimally. -- 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
4
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-838) Test scenario where no failover has occurred on server side...

by Tim Fox (JIRA)

Test scenario where no failover has occurred on server side... -------------------------------------------------------------- Key: JBMESSAGING-838 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-838 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta2 Reporter: Tim Fox Fix For: 1.2.0.GA When a client thinks the server has failed e.g. the netwrk between client--server temporarily fails but the network between server--server is ok, the server will return -1 to say no failover is occurring or times out then the client will retry the orginal node after a pause. The pause needs to be made configurable and a test devised to test this situation -- 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
11
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-933) NPE when deploying web service beans

by Heiko Braun (JIRA)

NPE when deploying web service beans ------------------------------------ Key: EJBTHREE-933 URL: http://jira.jboss.com/jira/browse/EJBTHREE-933 Project: EJB 3.0 Issue Type: Bug Reporter: Heiko Braun The exception: java.lang.NullPointerException at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:74) at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:172) at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:100) at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:221) at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:107) at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:83) at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124) at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:94) The bean that get's deployed: package com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest; import javax.ejb.Stateless; import javax.jws.WebService; @WebService( portName="Hello", serviceName="HelloService", targetNamespace="http://Hello.org", wsdlLocation="META-INF/wsdl/HelloService.wsdl", endpointInterface="com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest.Hello") @Stateless(name="WSEjbPortFieldInjectionTest") public class HelloBean { public String hello(String str) { return "WebSvcTest-Hello " + str; } public String bye(String str) { return "WebSvcTest-Bye and take care " + str; } } The spec: Session bean's business interface(s), if the session bean provides an EJB 3.0 local or remote client view. -- 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
11
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

[JBoss JIRA] Created: (JBRULES-401) add ability to lock a node to prevent concurrent editing

by Michael Neale (JIRA)

add ability to lock a node to prevent concurrent editing -------------------------------------------------------- Key: JBRULES-401 URL: http://jira.jboss.com/jira/browse/JBRULES-401 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben -- 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
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 March 2007