[JBoss JIRA] Created: (JBCOMMON-90) Report a potential ClassLoader problem in AbstractBuilder
by Dimitris Andreadis (JIRA)
Report a potential ClassLoader problem in AbstractBuilder
---------------------------------------------------------
Key: JBCOMMON-90
URL: https://jira.jboss.org/jira/browse/JBCOMMON-90
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: common-core (2.x)
Reporter: Dimitris Andreadis
Assignee: Thomas Diesler
Fix For: 2.2.13.GA
Create a JIRA entry for past commits r3131, r3132 to know what changed between releases.
--
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, 10 months
- 1
- 1
[JBoss JIRA] Created: (JBMESSAGING-1728) OrderingGroupMonitor shouldn't hold any MessageReference objects that are paged
by Howard Gao (JIRA)
OrderingGroupMonitor shouldn't hold any MessageReference objects that are paged
-------------------------------------------------------------------------------
Key: JBMESSAGING-1728
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1728
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.4.GA, 1.4.0.SP3.CP08
Reporter: Howard Gao
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
OrderingGroupMonitor registers ordering group messages by holding its messages. In paging mode, it will take up memories.
We need to refactor it to:
1. only register in memory references.
2. don't hold it's reference in the OrderingGroupMonitor, only the MessageID will suffice.
--
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, 10 months
- 2
- 3
[JBoss JIRA] Created: (JBREM-1143) CLONE [JBREM-877] - New Socket Connection is being Created for Every Client Request to the Server
by Ron Sigal (JIRA)
CLONE [JBREM-877] - New Socket Connection is being Created for Every Client Request to the Server
-------------------------------------------------------------------------------------------------
Key: JBREM-1143
URL: https://jira.jboss.org/jira/browse/JBREM-1143
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: transport
Affects Versions: 2.2.2.SP2
Environment: Linux os , Pentium duo Processor with 3.6 Ghz clock Speed, 4GB Ram in this Postgresql Database also Running
Reporter: Kumarselvan Somasundaram
Assignee: Ron Sigal
Priority: Critical
Fix For: 2.4.0.Beta2 (Pinto)
whenever EJB3 client requests the Server new socket is being created. at the client side the socket connection pool is not being used. Hope there is some issue with the socket connection after getting response from the server,becoz of which the server side the connection is being closed. this increases the CPU utilization,
The same code is running fine in jboss 4.0.4 with jboss remoting 1.4.0
new remoting 2.2.2 SP4 only handling 1/4 of the load with high CPU utilization.
--
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, 10 months
- 1
- 4