February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-813) Test failover (and clustering in general) on a QA lab network with several physical machines involved

by Ovidiu Feodorov (JIRA)

Test failover (and clustering in general) on a QA lab network with several physical machines involved ----------------------------------------------------------------------------------------------------- Key: JBMESSAGING-813 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-813 Project: JBoss Messaging Issue Type: Task Components: JMS Clustering Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.CR1 -- 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

19 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCOMMON-17) org.jboss.util.file.JarUtils needs to be made more bullet-proof

by Pete Bennett (JIRA)

org.jboss.util.file.JarUtils needs to be made more bullet-proof --------------------------------------------------------------- Key: JBCOMMON-17 URL: http://jira.jboss.com/jira/browse/JBCOMMON-17 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: core Environment: JBoss IDE 2.0.0beta2 Fedora Core 6 (2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686 i686 i386 GNU/Linux) J2SE6 (1.6.0-b105) JBoss Portal 2.6alpha2 non-clustered with JBoss AS bundle Reporter: Pete Bennett Assigned To: Dimitris Andreadis Deploying the attached WAR file creates the following stack trace, which is related to issue BIDE-124. This file was created using the package builder in JBoss IDE. 11:17:04,216 ERROR [Tomcat5] Problem in init java.lang.StringIndexOutOfBoundsException: String index out of range: 0 at java.lang.String.charAt(String.java:687) at org.jboss.util.file.JarUtils.unjar(JarUtils.java:273) at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:325) ... I have re-raised this issue as BIDE-124 has been acted on and the file in question has moved considerably since then. Having looked at http://anonsvn.jboss.org/repos/common/common-core/trunk/src/main/java/org... I think that line 273 in the file needs to be modified to protect against the case where the first entry in a JAR file is simply "/" as in the attached WAR. < if (fileName.charAt(0) == '/') > if (fileName.length() > 0 && fileName.charAt(0) == '/') Otherwise line 269 produces a fileName of length 0 which causes charAt(0) to fail. Pete -- 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

19 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-446) getTemporaryReplyTo broken

by Mark Little (JIRA)

getTemporaryReplyTo broken -------------------------- Key: JBESB-446 URL: http://jira.jboss.com/jira/browse/JBESB-446 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.0 Reporter: Mark Little Assigned To: Esteban Schifman Fix For: 4.0 Maintenance Pack 1 In some circumstances getTemporaryReplyTo can generate an EPR that will be functionally identical to the original To EPR. If the client and service share the same transport mechanism (e.g., JMS queue) then it's possible that replies to the client may be lost because they get picked up by the service again. -- 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4046) jboss_init_redhat.sh has no easy way of undefining the -b option in startup

by Jon Stevens (JIRA)

jboss_init_redhat.sh has no easy way of undefining the -b option in startup --------------------------------------------------------------------------- Key: JBAS-4046 URL: http://jira.jboss.com/jira/browse/JBAS-4046 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.5.GA Reporter: Jon Stevens >From the jboss_init_redhat.sh script... #bind address for jboss services, by default bind to *all* NICs JBOSS_HOST=${JBOSS_HOST:-"0.0.0.0"} #define the script to use to start jboss JBOSSSH=${JBOSSSH:-"$JBOSS_HOME/bin/run.sh -c $JBOSS_CONF -b $JBOSS_HOST"} Now, if I comment out JBOSS_HOST, then when JBOSSSH is defined, then it will end with -b and it will be empty. I'm trying to setup clustering, so I need to do that. It would be nice if all I had to do was comment out JBOSS_HOST. Right now, I have to comment out JBOSS_HOST and modify JBOSSSH. That's not a nice solution. -- 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

19 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-424) pbcast.STATE_TRANSFER throws NullPointerException during serialization of StateHeader

by Daniel Hasler (JIRA)

pbcast.STATE_TRANSFER throws NullPointerException during serialization of StateHeader ------------------------------------------------------------------------------------- Key: JGRP-424 URL: http://jira.jboss.com/jira/browse/JGRP-424 Project: JGroups Issue Type: Bug Environment: JDK 1.4.2_13 Reporter: Daniel Hasler Assigned To: Bela Ban The pbcast.STATE_TRANSFER.StateHeader class does not check if state_id is null during serialization. This leads in my case to a NullPointerException which stops the complete state transfer and results in two members that are not in sync. -- 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

19 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-902) Abort the installation script if there are no permissions to create temporary files

by Ovidiu Feodorov (JIRA)

Abort the installation script if there are no permissions to create temporary files ----------------------------------------------------------------------------------- Key: JBMESSAGING-902 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-902 Project: JBoss Messaging Issue Type: Task Components: Configuration and Management Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA This could lead to a corrupt installation (wrong service binding manager file, etc), so better to fail early, with a clear error message. -- 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-701) Optimisation - Allow onMessage to be executed on the remoting thread

by Tim Fox (JIRA)

Optimisation - Allow onMessage to be executed on the remoting thread -------------------------------------------------------------------- Key: JBMESSAGING-701 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-701 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 As an optimisation we should allow message listeners to be executed straight through using the same thread that delivers the message to the message callback handler. This would avoid an extra context switch.. Currently the thread used is from an executor per session - so as to be strictly JMS compliant. -- 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

19 years, 2 months

3
4
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-307) Down cache optimisation

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-307?page=all ] Ovidiu Feodorov closed JBMESSAGING-307. --------------------------------------- Resolution: Duplicate Issue > Down cache optimisation > ----------------------- > > Key: JBMESSAGING-307 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-307 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.GA > > Original Estimate: 3 days > Remaining Estimate: 3 days > > If there are no persistent messages in storage then when paging we can avoid flushing the downCache and loading from the db > and just transfer from the downcache to the in memory list when loading -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-437) Non durable subscription optimization

by Tim Fox (JIRA)

Non durable subscription optimization ------------------------------------- Key: JBMESSAGING-437 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-437 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.0.1.CR3 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.0.2 Since non durable subscriptions only live for the life-time of the consumer the it's struck me that we don't actually need to send any acks from the client to the server as messages are acknowledged for non durable subs. Basically I think we can acknowledge them before they are sent from server to client. This is because there's no case where messages will be redelivered from the server to the non durable sub, therefore no need for acks. On session recovery and session rollback messages are redelivered locally (i.e. they are already on the client) so no need for the server to redeliver. This also means we don't need to maintain a delivery list in the server consumer endpoint in this case, and the server consumer endpoint can return a done delivery every time. -- 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

19 years, 2 months

4
6
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-268) Convert destinations to ints in message instance

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-268?page=all ] Ovidiu Feodorov closed JBMESSAGING-268. --------------------------------------- Resolution: Duplicate Issue > Convert destinations to ints in message instance > ------------------------------------------------ > > Key: JBMESSAGING-268 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-268 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.GA > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Destination implementations JBossQueue and JBossTopic are currently not much more than just Strings identifiers. > When sending a message the destination (and possibly the replyto) need to be serialized with the message. > If the Destinations are just identifiers then they could represented as ints making there less bytes to serialize. > This could be significant for destinations with long names, e.g. 100 bytes -> 4 bytes (per message) -- 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

19 years, 2 months

1
0
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 February 2007