Performance problem with TCP & RMI Cache loaders
------------------------------------------------
Key: JBCACHE-800
URL: http://jira.jboss.com/jira/browse/JBCACHE-800
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Cache loaders
Affects Versions: 1.4.0.SP1
Environment: All platforms
Reporter: Tomas Topinka
Assigned To: Manik Surtani
Using of basic Output/Input stream leads to fatal performance problems.
Solution :
Using of BufferedOutput/InputStream in TcpDelegatingCacheLoader/TcpCacheServer as well as in RMI increase the performace rapidly.
--
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
TcpCacheServer never gets out of STARTING state, and doesn't shut down socket when stop() is called.
----------------------------------------------------------------------------------------------------
Key: JBCACHE-690
URL: http://jira.jboss.com/jira/browse/JBCACHE-690
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Cache loaders
Affects Versions: 1.3.0, 1.4.0
Reporter: Manik Surtani
Assigned To: Manik Surtani
Fix For: 2.0.0
Looks like a bug in the lifecycle methods, doesn't stop normal operations though.
--
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
Wrong "Specification-Version: 1.0.0.GA" in jboss-common.jar
-----------------------------------------------------------
Key: JBAS-3782
URL: http://jira.jboss.com/jira/browse/JBAS-3782
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: JBoss AS 4.0.5.GA
Reporter: Steven Deng
Priority: Trivial
"Specification-Version: 1.0.0.GA" in MANEFEST.MF of <jboss4.0.5 install dir>\lib\jboss-common.jar while this entry
should be "Specification-Version: 4.0.5.GA".
--
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
Simplify GossipRouter, GossipClient and RouterStub
--------------------------------------------------
Key: JGRP-342
URL: http://jira.jboss.com/jira/browse/JGRP-342
Project: JGroups
Issue Type: Task
Affects Versions: 2.3 SP1
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.4
- Remove unneeded threads in GossipRouter
- Make GossipRouter, GossipClient and RouterStub use the same marshalling code (GossipData), based on Streamable
--
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
javax.ejb.EJBNoSuchObjectException should be javax.ejb.NoSuchEJBException
-------------------------------------------------------------------------
Key: EJBTHREE-758
URL: http://jira.jboss.com/jira/browse/EJBTHREE-758
Project: EJB 3.0
Issue Type: Bug
Reporter: Carlo de Wolf
Priority: Critical
Fix For: EJB 3.0 RC10 - FD
--
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
use InitialContext props everywhere (TxUtil) for e-ejb3
-------------------------------------------------------
Key: EJBTHREE-756
URL: http://jira.jboss.com/jira/browse/EJBTHREE-756
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
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
[ http://jira.jboss.com/jira/browse/JBCACHE-35?page=all ]
Manik Surtani closed JBCACHE-35.
--------------------------------
Resolution: Duplicate Issue
JBCACHE-684
> Externalize the buffer queue size in LRUAlgorithm
> -------------------------------------------------
>
> Key: JBCACHE-35
> URL: http://jira.jboss.com/jira/browse/JBCACHE-35
> Project: JBoss Cache
> Issue Type: Feature Request
> Affects Versions: 1.2
> Reporter: Ben Wang
> Assigned To: Manik Surtani
> Priority: Minor
> Fix For: 2.0.0
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Currently, the LRUAlgorithm use a hard size of 5000 on the buffer queue to process node eviction. We should make this configurable so it can adapt to different enviornment.
--
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
JACC layer should generate unchecked permissions for methods with no security annotations
-----------------------------------------------------------------------------------------
Key: EJBTHREE-755
URL: http://jira.jboss.com/jira/browse/EJBTHREE-755
Project: EJB 3.0
Issue Type: Bug
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Consider the following usecases:
1) There are @RolesAllowed annotations on multiple methods(set X). Some methods (set Y) do not have @RolesAllowed, @PermitAll, @DenyAll annotations. For these methods in set Y, unchecked permissions need to be created for the roles for the ejb3 app.
2) There is a @DeclareRoles annotation at the class level. Methods may define annotations (set x) as in usecase 1. For the methods with missing security annotations, create unchecked permissions.
--
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