June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3914) Thread dumps from ServerInfo MBean do not contain line breaks.

by Darran Lofthouse (JIRA)

Thread dumps from ServerInfo MBean do not contain line breaks. -------------------------------------------------------------- Key: JBAS-3914 URL: http://jira.jboss.com/jira/browse/JBAS-3914 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.5.GA Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: JBossAS-4.2.0.CR1 Thread dumps from ServerInfo MBean do not contain line breaks, as the output HTML and displayed in a browser this is generally not a problem as the browser formats the output using the HTML tags not based on the presence of line breaks. If users copy the data from the web browser to a text editor as there are no line breaks in the original output the data is pasted to the text editor without breaks which causes everything to be on one line. The ouput thread dumps should have line breaks added to get round this. -- 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

5
7
0 / 0

[JBoss JIRA] Created: (JGRP-528) NAKACK: spurious retransmission requests

by Bela Ban (JIRA)

NAKACK: spurious retransmission requests ----------------------------------------- Key: JGRP-528 URL: http://jira.jboss.com/jira/browse/JGRP-528 Project: JGroups Issue Type: Task Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 Every now and then, spurious retransmission requests are received: NAKACK.handleXmitReq(): (requester=192.168.5.2:4397, local_addr=192.168.5.2:4393) message 192.168.5.2:4393::600 not found in retransmission table of 192.168.5.2:4393: [650 : 1050 (1100) (size=x, missing=0, highest stability=650)] It turns out that message #600 *was* actually retransmitted correctly, but the retransmission timer was cancelled too late, so that we got 1 or 2 spurious retransmit requests for the same message. This doesn't happen very frequently, and only under heavy load (e.g. 8 nodes, every node sends 5M 5K messages with 500 threads). Note that this issue DOES NOT LEAD TO INCORRECT BEHAVIOR ! -- 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
4
0 / 0

[JBoss JIRA] Created: (JBAS-4083) Ejb timers fire before the ear completely deploys

by Vadim Kopichenko (JIRA)

Ejb timers fire before the ear completely deploys ------------------------------------------------- Key: JBAS-4083 URL: http://jira.jboss.com/jira/browse/JBAS-4083 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2, Scheduling/Timers Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Environment: WinNT, Sun JDK 1.5 Reporter: Vadim Kopichenko Assigned To: Scott M Stark Consider the following usecase. The is an ear containing several ejb modules. One of them has a ejb2.1 timed cmp entity bean. If the timer associated with the bean fires during application deployment unexpected errors happen, cause other beans could be not already deployed. This breaks application logic. The problem happens both while server starts/stops and while hot ear's redeployment. It would be much better if timers began to fire after the application had completely deployed. I've also experienced a similar problem with undeployment. Timer code was executed about a half of second after the undeployment had begun. Several ejb modules had been already undeployed by that moment. I guess that timer actually fired exactly before the undeployment had begun but the ejbTimeout executed later due to threads syncronization issue. Please, try also to investigate if this can be avoided. PS Some kind of patch or workaround for 4.0.5 (or even a hint about how this can be fixed) would be greatly appreciated. -- 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, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (JBWEB-84) Class Cast Exception - when using CometProcessor - Jboss 4.2.0

by Vali Dumitru (JIRA)

Class Cast Exception - when using CometProcessor - Jboss 4.2.0 -------------------------------------------------------------- Key: JBWEB-84 URL: http://jira.jboss.com/jira/browse/JBWEB-84 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Environment: Windows Reporter: Vali Dumitru Assigned To: Mladen Turk I have a servlet that implements CometProcessor interface. Whenever I try to access it I get : java.lang.ClassCastException: org.jboss.web.tomcat.filters.ReplyHeaderFilter at org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:398) at org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:363) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:227) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:896) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:701) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2031) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) What is this? Is there a workaround? -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4508) Add a way to defined dependencies for a JCA adapter

by Georges Berscheid (JIRA)

Add a way to defined dependencies for a JCA adapter --------------------------------------------------- Key: JBAS-4508 URL: http://jira.jboss.com/jira/browse/JBAS-4508 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.0.GA Environment: Any Reporter: Georges Berscheid Currently there is no way to define that a resource adapter has a dependency on different component. Adrian has suggested to add support for a jboss-ra.xml file that let you define those dependencies (see forum entry). -- 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, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-4382) EnterpriseContext lock counting is not synchronized

by Adrian Brock (JIRA)

EnterpriseContext lock counting is not synchronized --------------------------------------------------- Key: JBAS-4382 URL: http://jira.jboss.com/jira/browse/JBAS-4382 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Reporter: Adrian Brock Assigned To: Scott M Stark Fix For: JBossAS-4.2.0.GA The lock counting in org.jboss.ejb.EnterpriseContext is not synchronized. The lock ivar is not even volatile. This variable needs replacing with synchronized method blocks or an oswego concurrent SynchronizedInt. This bug could either cause passivation to be invoked when it shouldn't or vice versa. Additionally, even with this fix, the usage in StatefulSessionInstanceInterceptor needs replacing with something more atomic! if (!ctx.isLocked()) { //take it! ctx.lock(); } -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1108) Move CacheListeners to their own thread pool

by Jason T. Greene (JIRA)

Move CacheListeners to their own thread pool -------------------------------------------- Key: JBCACHE-1108 URL: http://jira.jboss.com/jira/browse/JBCACHE-1108 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assigned To: Manik Surtani Fix For: 2.0.0.CR3 User CacheListeners should be dispatched in their own thread pool to prevent reentrancy problems and delays on cache operations. Evection listeners should still be executed in the app thread. -Jason -- 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, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-991) Non-JTA based mechanism for batching invocations

by Brian Stansberry (JIRA)

Non-JTA based mechanism for batching invocations ------------------------------------------------ Key: JBCACHE-991 URL: http://jira.jboss.com/jira/browse/JBCACHE-991 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Currently JBC uses the lifecycle of a JTA Transaction to scope a series of cache invocations doing things like lock release, replication and cache loader storage as part of the transaction commit. Need a mechanism to do this kind of invocation batching that doesn't depend on JTA. Needed to allow callers that don't wish their work to be associated with an active JTA transaction to still get the batching behavior JBC provides. AS web session replication is an example use case. It uses BatchModeTransactionManger to ensure its activity doesn't impact any ongoing transaction. But BatchModeTransactionManager isn't a good JTA transaction manager even though it implements the JTA interfaces. So using it is problematic; it can easily be misused by those who don't understand it's limitations (e.g. hooking it up to a JTA Datasource.) A couple of possible approaches have been discussed: 1) A new API added to Cache. Methods like startBatch(), commitBatch(), rollbackBatch(), along with some internal mechanism to timeout a batch that's been started but never committed/rolled-back. 2) Abstract away the JTA API such that JBC doesn't use JTA directly, but rather its own interfaces that largely parallel TransactionManager and Transaction. Provide an impl that simply wraps a real JTA TransactionManager. BatchModeTransactionManger would be another impl. API includes a method like 'boolean isJTACompliant()' that things like CacheLoader impls can check at startup to confirm they are working with a compatible impl (e.g. if JBDCCacheLoader is configured to use a JTA Datasource but isJTACompliant() returns false, throw an exception at startup.) Apologies if this is a duplicate issue. Thought there was something like this but couldn't find it. -- 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, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys

by Elias Ross (JIRA)

Be able to set the internal ordering of child nodes and data keys ----------------------------------------------------------------- Key: JBCACHE-841 URL: http://jira.jboss.com/jira/browse/JBCACHE-841 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani I believe that this issue is required to resolve JBCACHE-166 satisfactorily. But it would also be a useful (and easily added) feature for JBossCache 2.0. The attached .java file explains two additional methods to add. The internal implementation would likely need to rely on the JDK1.6 java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change to other code that rely on iteration to work on concurrently modified sets. As JDK 1.6 is new, this might require use of http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support from the jbossretro to change these JDK1.6 classes to use the backport for 1.5. -- 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, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-941) org.jboss.cache.Caches, which allows for users to access a Cache using various collection interfaces

by Elias Ross (JIRA)

org.jboss.cache.Caches, which allows for users to access a Cache using various collection interfaces ---------------------------------------------------------------------------------------------------- Key: JBCACHE-941 URL: http://jira.jboss.com/jira/browse/JBCACHE-941 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani The java.util.Collections utility class supplies useful methods for dealing with legacy interfaces and wrapping collection classes for concurrency, type safety, read-only, etc. In a simiilar vein, I wrote a "Caches" class that returns java.util.Map instances for a Node, which allow data to be modified through the standard Map interface. This I expect to be extremely useful for allowing uses to integrate their existing application with JBoss Cache, and will eliminate some of the confusion of using a new API and they can use the API they know best. Users also often demand an API which is "generic" so that their code is not tied to a particular vendor. There are basically two methods in Caches, one looks like this: Cache cache = DefaultCacheFactory.getInstance().createCache(); Map m = Caches.asMap(cache); m.put("foo", "bar"); The API and examples explain themselves. "Caches" could also include other useful methods for printing or reporting. Note that this functionality could be considered duplicated from PojoCache...) -- 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, 5 months

3
13
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007