March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1461) Number of relivery attempts does not match with my settings

by Nicolas Laporte (JIRA)

Number of relivery attempts does not match with my settings ----------------------------------------------------------- Key: JBMESSAGING-1461 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1461 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.SP4 Environment: JBoss 4.0.4.GA Windows server 2003 Reporter: Nicolas Laporte Assignee: Tim Fox Priority: Minor I set <attribute name="MaxDeliveryAttempts">15</attribute> The time-to-live parameter used by the client is 1 hour. We call the setRollbackOnly() method of our CMT MDB if an recoverable exception occurrs. The number of redelivery is 5. I expected 15. Could you tell me if this problem is known and if it is fixed in an upper version ? Thanks a lot for your support. Nicolas Laporte PDF Solutions -- 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

14 years, 10 months

2
6
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-1729) JMS Topic::listAllMessages JMX operation returns empty list.

by Howard Gao (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1729?page=com.atlassian.ji... ] Howard Gao updated JBMESSAGING-1729: ------------------------------------ Fix Version/s: 1.4.0.SP3.CP11 (was: 1.4.0.SP3.CP10) > JMS Topic::listAllMessages JMX operation returns empty list. > ------------------------------------------------------------ > > Key: JBMESSAGING-1729 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1729 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.4.4.GA > Reporter: Ondrej Žižka > Assignee: Howard Gao > Fix For: 1.4.0.SP3.CP11, 1.4.6.GA.SP1, 1.4.7.GA > > > SSIA . Rep. steps: > 1) Create a topic (MyTopic) > 2) Send few durable messages to it (Ejb3TestApps can be used) > 3) Find the "name=MyTopic,service=Topic" Mbean > 4) Ensure that messages count is not zero > 5) Perform the listAllMessages operation > 6) See that the result is an empty list. > Tested with EAP 5 CR3, "all" config, default DB (HSQL) -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7710) memory leak in DeadlockDetector

by Michal Borowiecki (JIRA)

memory leak in DeadlockDetector ------------------------------- Key: JBAS-7710 URL: https://jira.jboss.org/jira/browse/JBAS-7710 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: JBoss 4.0.5.GA with JBOSSTS_4_2_3_SP7 Reporter: Michal Borowiecki Heap dump diagnostics revealed a memory leak in org.jboss.util.deadlock.DeadlockDetector. The more deadlocks are detected the more "waiting" HashMap is growing. In our case the HashMap is >311MB in size. It contains 20 entries, 15 of them are > 20MB in size. The large size is not caused by map values but rather map keys which are of type com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple and contain a large number (couple thousand) of org.jboss.ejb.EntityEnterpriseContext references in its _txLocalResources variable. -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBXB-240) XmlJavaTypeAdapter is not supported on a property bound to an attribute

by Alexey Loubyansky (JIRA)

XmlJavaTypeAdapter is not supported on a property bound to an attribute ----------------------------------------------------------------------- Key: JBXB-240 URL: https://jira.jboss.org/jira/browse/JBXB-240 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.2.Beta4 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA E.g. the following is not supported @XmlAttribute() @XmlJavaTypeAdapter(value = StringWrapperAdapter.class) public StringWrapper getAttr() { return attr; } -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Assigned: (JBAS-1429) Reauthentication Support

by Vicky Kak (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-1429?page=com.atlassian.jira.plug... ] Vicky Kak reassigned JBAS-1429: ------------------------------- Assignee: Vicky Kak (was: Mike Clark) > Reauthentication Support > ------------------------ > > Key: JBAS-1429 > URL: https://jira.jboss.org/jira/browse/JBAS-1429 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Andrew Oliver > Assignee: Vicky Kak > Attachments: JBAS-1429, MySqlReauthenticationMechansimImpl.java, ReauthenticationMechansim.java > > > Add support for the reauthentication support (in particular MySQLChangeUser) -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1200) Rescanning for SASL providers on every connection in or out

by David Lloyd (JIRA)

Rescanning for SASL providers on every connection in or out ----------------------------------------------------------- Key: JBREM-1200 URL: https://jira.jboss.org/jira/browse/JBREM-1200 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta2 We should only scan for SASL providers when the protocol provider is constructed, and make up a map of mechanism to sasl*factory. This also allows us to add in a server-side EXTERNAL handler, which is necessarily tied to the protocol implementation in order to extract authentication data from the TLS layer. -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Assigned: (JBAS-1429) Reauthentication Support

by Mike Clark (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-1429?page=com.atlassian.jira.plug... ] Mike Clark reassigned JBAS-1429: -------------------------------- Assignee: Mike Clark (was: Vicky Kak) > Reauthentication Support > ------------------------ > > Key: JBAS-1429 > URL: https://jira.jboss.org/jira/browse/JBAS-1429 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Andrew Oliver > Assignee: Mike Clark > Attachments: JBAS-1429, MySqlReauthenticationMechansimImpl.java, ReauthenticationMechansim.java > > > Add support for the reauthentication support (in particular MySQLChangeUser) -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1748) hot deploying JMX invoker service fails

by Mike Clark (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-1748?page=com.atlassian.jira.plug... ] Mike Clark reassigned JBAS-1748: -------------------------------- Assignee: Mike Clark (was: Vicky Kak) > hot deploying JMX invoker service fails > --------------------------------------- > > Key: JBAS-1748 > URL: https://jira.jboss.org/jira/browse/JBAS-1748 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Management services > Affects Versions: JBossAS-4.0.2 Final > Reporter: Norman Richards > Assignee: Mike Clark > Priority: Minor > Fix For: JBossAS-6.0.0.M3 > > > jmx-invoker-service.xml cannot be hot deployed. Trying to hot deploy it causes a failure when redeploying the web console. After this failure, I the JMX invoker cannot be contacted. Here's the resulting web console error: > 22:49:04,904 ERROR [WebModule] Starting failed jboss.web.deployment:id=-1500951031,war=web-console.war > java.lang.NullPointerException > at org.jboss.web.WebModule.startModule(WebModule.java:67) > at org.jboss.web.WebModule.startService(WebModule.java:46) > at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:911) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:416) > at org.jboss.system.ServiceController.start(ServiceController.java:438) > at org.jboss.system.ServiceController.start(ServiceController.java:438) > at org.jboss.system.ServiceController.start(ServiceController.java:438) > at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy4.start(Unknown Source) > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) > at sun.reflect.GeneratedMethodAccessor50.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy8.deploy(Unknown Source) > at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325) > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:483) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194) -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2034) Require JDK6

by Andrew Lee Rubinger (JIRA)

Require JDK6 ------------ Key: EJBTHREE-2034 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2034 Project: EJB 3.0 Issue Type: Task Components: build Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger We no longer support any JDK5 runtimes, so bump to JDK6 and enforce as part of the build -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1202) Allow realm specification in connect URI

by David Lloyd (JIRA)

Allow realm specification in connect URI ---------------------------------------- Key: JBREM-1202 URL: https://jira.jboss.org/jira/browse/JBREM-1202 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: r3 core: api Reporter: David Lloyd Assignee: David Lloyd Priority: Minor Fix For: 3.1.0.Beta2 Syntax is: remote://host:123/ - use the user/realm configured in the OptionMap or client callback remote://user@host:123/ - use "user" as the authorization ID, realm is configured in the OptionMap or client callback remote://user;realm@host:123/ - user "user" as the authorization ID and "realm" as the default authentication realm -- 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

14 years, 10 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010