March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1140) UNICAST based on negative acks

by Bela Ban (JIRA)

UNICAST based on negative acks ------------------------------ Key: JGRP-1140 URL: https://jira.jboss.org/jira/browse/JGRP-1140 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.10 Currently, UNICAST is based on positive acks: we send an ack for each message received. This causes a lot of ack traffic (piggybacking remedies this to a certain extent). Investigate a version of UNICAST which uses negative acks; the sender never retransmits a message unless the receiver asks it to. The receiver only asks the sender for retransmission if it sees a missing seqno. Issue: the last-message-lost problem. To solve it, we could exchange the last-seqno when there is no traffic any longer, e.g. by a timer task. The task would only run once, unless there's more traffic. This is what NAKACK does, and we could even reuse the NakReceiverWindow class this ay, and eliminate AckSenderWindow and AckReceiverWindow. We could also remove DefaultRetransmitter and also use the RangeBasedRetransmitter (liek NAKACK). -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBNAME-48) Thread leak on server due to WeakReferenced Naming objects in NamingContext

by Oleg Nitz (JIRA)

Thread leak on server due to WeakReferenced Naming objects in NamingContext --------------------------------------------------------------------------- Key: JBNAME-48 URL: https://jira.jboss.org/jira/browse/JBNAME-48 Project: JBoss Naming Issue Type: Bug Reporter: Oleg Nitz Over time the number of threads named "RMI TCP Connection(...)-..." on server grows infinitely. I discovered that this is due garbage collection of Naming objects on client, which are cached in NamingContext.cachedServers map. The correspondent server objects with their threads remain on server waiting for distributed garbage collection, which happens rarely due to "-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000" in run.conf. I propose not use WeakReferences, instead to remove "expired" Naming objects from NamingContext.cachedServers periodically by some Timer, and also to explicitely remove correspondent remote RMI objects from server. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7807) EJB method having QName as an argument fails on jboss

by Rishi Agarwal (JIRA)

EJB method having QName as an argument fails on jboss ------------------------------------------------------ Key: JBAS-7807 URL: https://jira.jboss.org/jira/browse/JBAS-7807 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.1.0.GA Environment: linux Reporter: Rishi Agarwal Assignee: Carlo de Wolf I have a EJB method that has javax.xml.namespace.QName as an argument. On trying to connect to it from the jse client it gives the following exception: Our EJBs are deplyed on JBOSS AS 5. java.lang.RuntimeException: java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = -9120448754896609940, local class serialVersionUID = -711357515002332258 After removing QName class from stax-api.jar in the endorsed\lib directory , i could successfully invoke the EJB method. This is the due to the fact the QName class is available as part of JRE libraries as well and i guess this is a well-known fact that there are issue around it due to incompatible serialVersionUID. Now my point is what is the solution to resolve this.We can't recommend removing QName class from stax-api.jar for EJBs( methods with QName as argument) to work. -- 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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-1169) Use wanem to test network protocols

by Bela Ban (JIRA)

Use wanem to test network protocols ----------------------------------- Key: JGRP-1169 URL: https://jira.jboss.org/jira/browse/JGRP-1169 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.11 http://wanem.sourceforge.net/ -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-250) Update ClassPool to 1.0.0.Alpha4

by Flavia Rainone (JIRA)

Update ClassPool to 1.0.0.Alpha4 -------------------------------- Key: JBDEPLOY-250 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-250 Project: JBoss Deployers Issue Type: Task Affects Versions: JBDEPLOY-2.2.0.Alpha2 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: JBDEPLOY-2.2.0.Alpha3 ClassPool version has to be updated to 1.0.0.Alpha4. This requires a few changes in the tests: - a new test delegate mainly because of changes caused by JBREFLECT-94 - a FilteredClassPool as systemClassPool because of VFS 3 (JBREFLECT-98) -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREFLECT-105) Replace ${artifactId} by ${project.artifactId}

by Flavia Rainone (JIRA)

Replace ${artifactId} by ${project.artifactId} ---------------------------------------------- Key: JBREFLECT-105 URL: https://jira.jboss.org/jira/browse/JBREFLECT-105 Project: JBoss Reflection Issue Type: Task Affects Versions: JBossReflection.2.2.0-Alpha4 Reporter: Flavia Rainone Assignee: Flavia Rainone Priority: Minor Fix For: JBossReflection.2.2.0-Alpha5 The ${artifactId} keyword is deprecated and may be no longer supported by a future release of maven. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-270) Integrating JBoss JCA with Tomcat

by VickyKak (JIRA)

Integrating JBoss JCA with Tomcat --------------------------------- Key: JBJCA-270 URL: https://jira.jboss.org/jira/browse/JBJCA-270 Project: JBoss JCA Issue Type: Feature Request Components: Standalone Reporter: VickyKak Assignee: Jesper Pedersen Priority: Minor -- 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

16 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-4194) Configurable Default TX attribute for CMT

by Vicky Kak (JIRA)

Configurable Default TX attribute for CMT ----------------------------------------- Key: JBAS-4194 URL: http://jira.jboss.com/jira/browse/JBAS-4194 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Vicky Kak Assigned To: Vicky Kak Priority: Minor The default transaction attribute for the CMT is TX_REQUIRED , this should be configurable . -- 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

16 years, 4 months

2
3
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: (was: Mike Clark) > 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 > 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5774) IdleRemover Thread getting added to ApplicationThread group .

by Vicky Kak (JIRA)

IdleRemover Thread getting added to ApplicationThread group . ------------------------------------------------------------- Key: JBAS-5774 URL: https://jira.jboss.org/jira/browse/JBAS-5774 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Reporter: Vicky Kak Assignee: Jesper Pedersen Priority: Minor IdleRemoved thread is getting inserted in the application created thread group . -- 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

16 years, 4 months

2
3
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 2010