January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-877) New Socket Connection is being Created for Every Client Request to the Server

by Kumarselvan Somasundaram (JIRA)

New Socket Connection is being Created for Every Client Request to the Server ----------------------------------------------------------------------------- Key: JBREM-877 URL: http://jira.jboss.com/jira/browse/JBREM-877 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 Priority: Critical 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

2
14
0 / 0

[JBoss JIRA] Created: (JBBUILD-446) Create pom for spring-int module.

by Paul Gier (JIRA)

Create pom for spring-int module. --------------------------------- Key: JBBUILD-446 URL: http://jira.jboss.com/jira/browse/JBBUILD-446 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - App Server The spring integration module needs a pom and should be added as a module of the aggregate. -- 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

18 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4446) JGroups file in lib should be named jgroups-all.jar

by Brian Stansberry (JIRA)

JGroups file in lib should be named jgroups-all.jar --------------------------------------------------- Key: JBAS-4446 URL: http://jira.jboss.com/jira/browse/JBAS-4446 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.CR1 Name the file jgroups-all.jar, which is what it's named in the JGroups dist. Using a different name makes it too easy to end up with duplicate jars when upgrading, a mistake I've made several times and which we hear about on support from time to time. -- 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

18 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-128) ClassInfo should be serialzable

by Adrian Brock (JIRA)

ClassInfo should be serialzable ------------------------------- Key: JBMICROCONT-128 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-128 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The ClassInfo objects should be serializable, this is currently not the case because they hold references back to their factory to support lazy initialization. -- 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

18 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-223) Package handling not working properly in new classloader

by Adrian Brock (JIRA)

Package handling not working properly in new classloader -------------------------------------------------------- Key: JBMICROCONT-223 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-223 Project: JBoss MicroContainer Issue Type: Bug Components: General Affects Versions: JBossMC-2.0.0.Beta7 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.CR1 The package handling is not working properly in the new classloader. 1) In the new classloader each classloader has no parent (unlike the old UnifiedClassLoader - UCL). Instead the parent is a Loader. This means that packages in the parent (e.g. the classpath) are not visible 2) In both the old and new classloader, packages are not retrieved across the peers this means that each classloader gets its own package object. This means that package sealing does not work. 3) Since the sealing check is in the URLClassLoader, the new classloader is not performing this check - it uses the SecureClassLoader -- 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

18 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-222) Write tests for the new convience methods in ComponentMutableMetaData

by Adrian Brock (JIRA)

Write tests for the new convience methods in ComponentMutableMetaData --------------------------------------------------------------------- Key: JBMICROCONT-222 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-222 Project: JBoss MicroContainer Issue Type: Sub-task Components: MetaData Affects Versions: JBossMC-2.0.0.Beta7 Reporter: Adrian Brock Fix For: JBossMC-2.0.0.CR1 Need to write tests for the new convience methods defined in ComponentMutableMetaData e.g. addAnnotation(Method, annotation); etc. -- 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

18 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-224) ArrayInfoImpl needs to use Class.forName() to load array classes

by Adrian Brock (JIRA)

ArrayInfoImpl needs to use Class.forName() to load array classes ---------------------------------------------------------------- Key: JBMICROCONT-224 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-224 Project: JBoss MicroContainer Issue Type: Bug Components: Container Reporter: Adrian Brock Assigned To: Ales Justin Fix For: JBossMC-2.0.0.CR1 As shown on the attached problem. ArrayInfoImpl needs to Class.forName(name, true, classloader) to load the array class. -- 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

18 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-229) AbstractBeanInfoFactory throws StringIndexOutOfBoundsException for short method names

by Brian Stansberry (JIRA)

AbstractBeanInfoFactory throws StringIndexOutOfBoundsException for short method names ------------------------------------------------------------------------------------- Key: JBMICROCONT-229 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-229 Project: JBoss MicroContainer Issue Type: Bug Components: Container Affects Versions: JBossMC-2.0.0.Beta7 Reporter: Brian Stansberry Creating a bean of a type that contains a method whose name is 2 chars or less results in the following: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1768) at java.lang.String.substring(String.java:1735) at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getUpperPropertyName(AbstractBeanInfoFactory.java:93) at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getBeanProperties(AbstractBeanInfoFactory.java:234) at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getBeanInfo(AbstractBeanInfoFactory.java:141) at org.jboss.config.plugins.AbstractConfiguration.getBeanInfo(AbstractConfiguration.java:71) at org.jboss.kernel.plugins.config.AbstractKernelConfig.getBeanInfo(AbstractKernelConfig.java:55) at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getBeanInfo(AbstractKernelConfigurator.java:65) at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getBeanInfo(AbstractKernelConfigurator.java:84) at org.jboss.kernel.plugins.dependency.PreInstallAction.installActionInternal(PreInstallAction.java:62) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398) at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:69) ... This is from attempt to create an instance of org.jgroups.JChannel, which includes a method named up(). Problem is in AbstractBeanInfoFactory: protected static String getUpperPropertyName(String name) { int start = 3; if (name.startsWith("is")) start = 2; return name.substring(start); } A simple fix is to make the first line int start = Math.min(3, name.length); which will result in a return value of "" from name.substring(start) if name is 3 chars or less. Alternatively, change getBeanProperties() to not call getUpperPropertyName() until it has already determined the method is a getter or a setter. -- 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

18 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-642) incorrect log level in PersistenceFactory.getInstance()

by Chris Ekberg (JIRA)

incorrect log level in PersistenceFactory.getInstance() ------------------------------------------------------- Key: JGRP-642 URL: http://jira.jboss.com/jira/browse/JGRP-642 Project: JGroups Issue Type: Bug Affects Versions: 2.5.1 Reporter: Chris Ekberg Assigned To: Bela Ban Priority: Trivial in PersistenceFactory.java: public static PersistenceFactory getInstance() { log.error(" getting factory instance "); ... I think that should be log.debug, not log.error. -- 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

18 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-668) Deadlock condition in BARRIER

by Bela Ban (JIRA)

Deadlock condition in BARRIER ----------------------------- Key: JGRP-668 URL: http://jira.jboss.com/jira/browse/JGRP-668 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 Hey Bela et al: We've been fighting a lossy network (UDP receive errors) on a cluster of 50 machines and managed to produce 2 coordinators who refused to MERGE3. A closer examination reviewed http://www.nabble.com/file/p14991972/barrier_deadlock.txt this stack trace which showed that there was one thread trying to satisfy a STATE_REQ msg blocked down in BARRIER.closeBarrier() waiting for the in_flight_threads to empty, another thread was trying to service another STATE_REQ and was blocked trying to lock the state_requesters table up in STATE_TRANSFER.handleStateReq(), and another 12 threads blocked waiting for the barrier to open in BARRIER.up(). We quickly found that we had a deadlock condition in BARRIER that was problematic -- http://www.nabble.com/file/p14991972/BARRIER.java.patch here's the patch to fix this . However, we cannot see an easy way to fix 2 STATE_REQ messages coming right after the other. They will both enter the in_flight_threads set and only one will come back down to lock the barrier and will wait forever for the other one to leave in_flight_threads. If we let the 2nd come down too, it may come back up before the in_flight_threads is clear since all it does is see that the barrer is closed and returns. Although we may have fixed part of the deadlock we saw, we are looking into switching to the FLUSH protocol instead because of the 2 STATE_REQ issue. Just curious as to other's feedback about this issue and whether more folks are using FLUSH or BARRIER? Thanks much for an [otherwise] great code stack. We are excited to be using it in our distributed database system project. gray -- 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

18 years, 4 months

2
9
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 January 2008