November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6209) DelegatingClassloader is trying to get the parent in an unprivileged block

by Anil Saldhana (JIRA)

DelegatingClassloader is trying to get the parent in an unprivileged block -------------------------------------------------------------------------- Key: JBAS-6209 URL: https://jira.jboss.org/jira/browse/JBAS-6209 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.CR2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossAS-5.0.0.GA This JIRA issue is for the "integration" component/project. -- 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

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCOMMON-74) Release jboss-common-core 2.2.10.GA

by Dimitris Andreadis (JIRA)

Release jboss-common-core 2.2.10.GA ----------------------------------- Key: JBCOMMON-74 URL: https://jira.jboss.org/jira/browse/JBCOMMON-74 Project: JBoss Common Issue Type: Release Security Level: Public (Everyone can see) Components: common-core (2.x) Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: 2.2.10.GA -- 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

17 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCOMMON-75) DelegatingClassloader is trying to get the parent in an unprivileged block

by Anil Saldhana (JIRA)

DelegatingClassloader is trying to get the parent in an unprivileged block -------------------------------------------------------------------------- Key: JBCOMMON-75 URL: https://jira.jboss.org/jira/browse/JBCOMMON-75 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.9.GA Reporter: Anil Saldhana Fix For: 2.2.10.GA Forum thread. -- 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

17 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1853) Drools failing with exception when timestamp attribute is java.util.Date

by Edson Tirelli (JIRA)

Drools failing with exception when timestamp attribute is java.util.Date ------------------------------------------------------------------------ Key: JBRULES-1853 URL: https://jira.jboss.org/jira/browse/JBRULES-1853 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M2 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.0.0.M3 Reported by Jeff. -- 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

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1050) HTTPClientInvoker does not support BASIC authentication for proxies when use of proxy is configured by system properties

by Ron Sigal (JIRA)

HTTPClientInvoker does not support BASIC authentication for proxies when use of proxy is configured by system properties ------------------------------------------------------------------------------------------------------------------------ Key: JBREM-1050 URL: https://jira.jboss.org/jira/browse/JBREM-1050 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP10 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11 The use of a proxy can be communicated to the HTTP transport in two ways. 1. The parameters "http.proxyHost" and "http.proxyPort" can be configured in the invocation metadata map, or 2. the system properties "http.proxyHost" and "http.proxyPort" can be set. In the former case, org.jboss.remoting.transport.http.HTTPClientInvoker will attempt to call java.net.URL.openConnection(java.net.Proxy) (which exists only in jdk 1.5 and above). If the call succeeds, HTTPClientInvoker will go on to create a "Proxy-Authorization" request header, based on the values associated with ""http.proxy.username" and "http.proxy.password", either in the invocation metadata map or as system properties. In the latter case, the java.net.URL class will configure proxy information based on the system properties. The problem is that, in the latter case, HTTPClientInvoker does not check for the existence of the "http.proxyHost" and "http.proxyPort" system properties, and so never checks to see if it should create a "Proxy-Authorization" request header. -- 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

17 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-1056) Fix race condition in InvokerRegistry

by Ron Sigal (JIRA)

Fix race condition in InvokerRegistry ------------------------------------- Key: JBREM-1056 URL: https://jira.jboss.org/jira/browse/JBREM-1056 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP10 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11 In org.jboss.remoting.InvokerRegistry.createClientInvoker() there is a reference to serverLocators which is in a synchronized(clientLock) block but which is not protected by a synchronized(serverLock) block. Under heavy load, when org.jboss.remoting.Client.addCallbackListener() is creating a connection to the callback Connector (which is necessarily colocated in the same JVM), serverLocators has been seen to return null. -- 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

17 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-212) Use Hibernate style format for the property names

by Galder Zamarreno (JIRA)

Use Hibernate style format for the property names ------------------------------------------------- Key: JBCLUSTER-212 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-212 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Hibernate-Cache-Provider Reporter: Galder Zamarreno Assignee: Brian Stansberry Galder Zamarreno wrote: Hi, Chris Bredesen wrote: > I have to nit-pick though, because I'm crazy like that. > > Why choose a property name like "local.puts.only" when the rest of the Hibernate code base is consistent > with using '_', like "use_second_level_cache" or "provider_configuration_file_resource_path"? Because I didn't realise of that :) and clustering projects generally use '.' as separator more than '_'. More an oversight rather than anything else. Same with hibernate.treecache.querycache.local.writes.only. Let me figure out where to open a JIRA for this. Cheers, > > -CB > > Galder Zamarreno wrote: >> Hi, >> >> The news is out, there's a new cache provider implementation for the HB 3.2.x and JBC 1.4.x series as >> you can read from http://galder.zamarreno.com/?p=56 and and http://blog.jboss-portal.org/2008/09/scaling-jboss-portal-to-new-height.html >> >> This is of interest to Portal Clustering users and customers who're using Hibernate entities but not EJB3 >> beans (for EJB3 beans some of the improvements are already present there) with JBC as 2nd level cache. >> >> Cheers, -- 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

17 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-217) org.jboss.hibernate.jbc.cacheprovider.TreeCacheProvider DEFAULT_CONFIG should be treecache.xml

by Galder Zamarreno (JIRA)

org.jboss.hibernate.jbc.cacheprovider.TreeCacheProvider DEFAULT_CONFIG should be treecache.xml ---------------------------------------------------------------------------------------------- Key: JBCLUSTER-217 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-217 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Components: Hibernate-Cache-Provider Affects Versions: 1.0.0.GA Reporter: Galder Zamarreno Assignee: Galder Zamarreno I've noted that in org/jboss/hibernate/jbc/cacheprovider/TreeCacheProvider.java, the DEFAULT_CONFIG is treecache-optimistic.xml. Having looked through TCP in HB 3.2.x series, this was actually treecache.xml and some people are relying on this. So, I'd suggest that for 1.0.1.GA, we use treecache.xml as default but still checking whether if treecache.xml not present, old default (treecache-optimistic.xml) is present. -- 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

17 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-216) org.jboss.hibernate.jbc.cacheprovider.TreeCacheProvider should be calling stopService()/startService() instead of stop()/start()

by Galder Zamarreno (JIRA)

org.jboss.hibernate.jbc.cacheprovider.TreeCacheProvider should be calling stopService()/startService() instead of stop()/start() -------------------------------------------------------------------------------------------------------------------------------- Key: JBCLUSTER-216 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-216 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Components: Hibernate-Cache-Provider Affects Versions: 1.0.0.GA Reporter: Galder Zamarreno Assignee: Galder Zamarreno org.jboss.hibernate.jbc.cacheprovider.TreeCacheProvider should be calling stopService()/startService() instead of stop()/start() in order to avoid ServiceController MBean lookups when running standalone or in a non managed environment. -- 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

17 years, 8 months

1
4
0 / 0

[JBoss JIRA] Deleted: (JBAS-6208) compatibility-matrix - org.jboss.test.client.test.AppClientUnitTestCase tests

by Dimitris Andreadis (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6208?page=com.atlassian.jira.plug... ] Dimitris Andreadis deleted JBAS-6208: ------------------------------------- > compatibility-matrix - org.jboss.test.client.test.AppClientUnitTestCase tests > ----------------------------------------------------------------------------- > > Key: JBAS-6208 > URL: https://jira.jboss.org/jira/browse/JBAS-6208 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Dimitris Andreadis > Assignee: Kabir Khan > Priority: Blocker > > The appclient tests in the compatibility-matrix testsuite are failing with: > http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Comp... > java.lang.IllegalStateException: Incompletely deployed: > *** DEPLOYMENTS IN ERROR: Name -> Error > ClassLoaderSystem -> java.lang.NoSuchMethodError: org.jboss.aop.AspectManager.addArrayReplacement(Lorg/jboss/aop/array/ArrayReplacement;)V > ClientLauncherClassPath:0.0.0$MODULE -> java.lang.NoSuchMethodError: org.jboss.aop.AspectManager.getManagerFQN()Ljava/lang/String; > ClassLoading -> java.lang.NoSuchMethodError: org.jboss.aop.AspectManager.getManagerFQN()Ljava/lang/String; > ClientLauncherClassPath:0.0.0 -> java.lang.NoSuchMethodError: org.jboss.aop.AspectManager.getManagerFQN()Ljava/lang/String; > *** DEPLOYMENTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} > ClientContainer -> ClientLauncherClassPath:0.0.0{Installed:**ERROR**}, null{Installed:** UNRESOLVED JndiDepends: 'test-client/metaData' **} > at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalValidate(AbstractKernelDeployer.java:290) > at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(AbstractKernelDeployer.java:174) > at org.jboss.ejb3.client.ClientLauncher.validate(ClientLauncher.java:471) > at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:269) > at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:174) > at org.jboss.test.client.test.AppClientUnitTestCase.testClientLauncher(AppClientUnitTestCase.java:67) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) > at junit.extensions.TestSetup$1.protect(TestSetup.java:21) > at junit.extensions.TestSetup.run(TestSetup.java:25) > at org.jboss.test.compatibility.test.matrix.MatrixTestContainer$TestProxy.run(MatrixTestContainer.java:185) > at org.jboss.test.compatibility.test.matrix.MatrixTestContainer$TestSuiteProxy.run(MatrixTestContainer.java:85) -- 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

17 years, 8 months

1
0
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 November 2008