November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4955) All the known bind address properties should be set to the default bind address

by Adrian Brock (JIRA)

All the known bind address properties should be set to the default bind address ------------------------------------------------------------------------------- Key: JBAS-4955 URL: http://jira.jboss.com/jira/browse/JBAS-4955 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.2.2.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-4.2.3.GA Currently in jboss-4.2 the jboss.bind.address is set to "localhost" by default. There's also some code to fixup the java.rmi.server.hostname to "localhost" when not configured. This code should be changed to set the java.rmi.server.hostname to the jboss.bind.address when not configured and the other known bind addresses bind.address (legacy name) jgroups.bind.address (for clustering) should also be updated to the jboss.bind.address when not configured. -- 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

18 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4954) Consoles and invokers need to accept local connections only in jboss5

by Adrian Brock (JIRA)

Consoles and invokers need to accept local connections only in jboss5 --------------------------------------------------------------------- Key: JBAS-4954 URL: http://jira.jboss.com/jira/browse/JBAS-4954 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alex Pinkin Assigned To: Dimitris Andreadis Priority: Critical Fix For: JBossAS-4.2.0.CR1 - jmx console - web console - jmx-invoker - rmi/http invoker -- 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

18 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4953) Support for JMS_JBOSS_REDELIVERY_LIMIT when using something other than MQ

by Carlo de Wolf (JIRA)

Support for JMS_JBOSS_REDELIVERY_LIMIT when using something other than MQ ------------------------------------------------------------------------- Key: JBAS-4953 URL: http://jira.jboss.com/jira/browse/JBAS-4953 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Support the JMS_JBOSS_REDELIVERY_LIMIT property for JMS providers other than MQ. http://wiki.jboss.org/wiki/Wiki.jsp?page=WhatVendorSpecificPropertiesDoes... -- 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

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-602) Update FLUSH diagrams for joining and for state transfer

by Bela Ban (JIRA)

Update FLUSH diagrams for joining and for state transfer -------------------------------------------------------- Key: JGRP-602 URL: http://jira.jboss.com/jira/browse/JGRP-602 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.6 Update the 2 png files to reflect the new simplified FLUSH protocol -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4945) Messages transfered from DLQ to working queue will never be resent to DLQ

by Mike Clark (JIRA)

Messages transfered from DLQ to working queue will never be resent to DLQ ------------------------------------------------------------------------- Key: JBAS-4945 URL: http://jira.jboss.com/jira/browse/JBAS-4945 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA Reporter: Mike Clark Assigned To: Adrian Brock Messages that are retreived from the DLQ have their JMSXDeliveryCount set to 1. Inside org.jboss.ejb.plugins.jms.DLQHander, this leads to the code that redirects failed messages to the DLQ. Starting on line 454, the count gets set to 1, then is decremented to zero. On the next redelivery, the same thing happens again. The JMS_JBOSS_REDELIVERY_COUNT is incremented on each cylce but never gets checked: try { if (msg.propertyExists(PROPERTY_DELIVERY_COUNT)) // Is 1 for a message transferred from DLQ <<<< count = msg.getIntProperty(PROPERTY_DELIVERY_COUNT); } catch (JMSException ignored) { } if (count > 0) { // The delivery count is one too many --count; // Becomes zero for message transferred from DLQ <<< } else if (msg.propertyExists(JMS_JBOSS_REDELIVERY_COUNT)) count = msg.getIntProperty(JMS_JBOSS_REDELIVERY_COUNT); else { id = msg.getJMSMessageID(); if (id == null) { // if we can't get the id we are basically f**ked log.error("Message id is null, can't handle message"); return false; } count = incrementResentCount(id); fromMessage = false; } if (count > max) // Count is always zero for a message that has been transfered from DLQ <<<< { id = msg.getJMSMessageID(); log.warn("Message resent too many times; sending it to DLQ; message id=" + id); sendMessage(msg); deleteFromBuffer(id); handled = true; } Cheers, Mike C. -- 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

18 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4903) EJB 2.1 view cannot be realized

by Thomas Diesler (JIRA)

EJB 2.1 view cannot be realized ------------------------------- Key: JBAS-4903 URL: http://jira.jboss.com/jira/browse/JBAS-4903 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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

18 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1783) Handling Oracle (OC4J) WSRP Producers - Preference Information

by Dave Rowe (JIRA)

Handling Oracle (OC4J) WSRP Producers - Preference Information -------------------------------------------------------------- Key: JBPORTAL-1783 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1783 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.2 Final Environment: Oracle OC4J 10.1.3.3.0, JBoss bundled 2.6 release (downloaded yesterday 11/06/2007) Reporter: Dave Rowe Assigned To: Chris Laprun Currently the Oracle WSRP implementation doesn't support PortletPropertyDescriptions, so when trying to use Oracle portlets, exceptions are thrown "Not yet implemented". In org.jboss.portal.wsrp.consumer.portlet.info.WSRPPortletInfo, there needs to be a try / catch or something around the ' originatingProducer.getPropertyDescriptionsFor(portletHandle); to fail safely. -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1786) WSRP Producer should Portal's portal:service=PortletInvoker, type=Producer instead of defining its own for no good reason

by Chris Laprun (JIRA)

WSRP Producer should Portal's portal:service=PortletInvoker,type=Producer instead of defining its own for no good reason ------------------------------------------------------------------------------------------------------------------------ Key: JBPORTAL-1786 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1786 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.2 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.3 Final WSRP Producer is currently using a custom PortletInvoker with a minimally configured interceptor stack when there really isn't any good reasons to do so. This is in particular causing issues with portlet requiring control over transactions as it's currently missing the transaction interceptor to suspend Portal's transaction for the duration of the portlet execution... -- 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

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4947) Externalize ClusterConfigMetaData defaults

by Brian Stansberry (JIRA)

Externalize ClusterConfigMetaData defaults ------------------------------------------ Key: JBAS-4947 URL: http://jira.jboss.com/jira/browse/JBAS-4947 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, EJB2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 The org.jboss.metadata.ejb.jboss.ClusterConfigMetaData class is inconsistent in how it obtains default values, and in many cases falls back on hard-coded values. There should be no hard-coded defaults, with default values coming from a container-configuration, usually from standardjboss.xml. See forum discussion for details. -- 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

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1093) create tutorial for validating jboss.xml

by William DeCoste (JIRA)

create tutorial for validating jboss.xml ---------------------------------------- Key: EJBTHREE-1093 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1093 Project: EJB 3.0 Issue Type: Task Components: Documentation Reporter: William DeCoste Assigned To: William DeCoste -- 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

18 years, 8 months

1
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 November 2007