December 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Moved: (JBAS-7545) Update to jboss-kernel-2.2.0.M3

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7545?page=com.atlassian.jira.plug... ] Thomas Diesler moved JBOSGI-266 to JBAS-7545: --------------------------------------------- Project: JBoss Application Server (was: JBoss OSGi) Key: JBAS-7545 (was: JBOSGI-266) Component/s: MicroContainer bus (was: Core Framework) Fix Version/s: JBossAS-6.0.0.M2 (was: Framework 1.0.0 Alpha3) > Update to jboss-kernel-2.2.0.M3 > ------------------------------- > > Key: JBAS-7545 > URL: https://jira.jboss.org/jira/browse/JBAS-7545 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: MicroContainer bus > Reporter: Thomas Diesler > Assignee: Ales Justin > Fix For: JBossAS-6.0.0.M2 > > > The kernel need to be released and included in framework so we can ship it as part of osgi Beta6 (1-Feb-2010) -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7538) Intermittent failure on org.jboss.test.cluster.defaultcfg.test.HAInvokerUnitTestCase.testHttpHAProxyFailover

by Brian Stansberry (JIRA)

Intermittent failure on org.jboss.test.cluster.defaultcfg.test.HAInvokerUnitTestCase.testHttpHAProxyFailover ------------------------------------------------------------------------------------------------------------ Key: JBAS-7538 URL: https://jira.jboss.org/jira/browse/JBAS-7538 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Test Suite Affects Versions: JBossAS-6.0.0.M1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M2 Test intermittently fails with: java.lang.IllegalArgumentException: null object name at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:515) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:662) at org.jboss.invocation.http.server.HttpInvokerHA.invoke(HttpInvokerHA.java:135) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.http.servlet.InvokerServlet.processRequest(InvokerServlet.java:162) at org.jboss.invocation.http.servlet.InvokerServlet.doPost(InvokerServlet.java:224) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:336) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:93) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:366) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) at java.lang.Thread.run(Thread.java:619) -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1160) CLONE -Version compatibility problem with leasing

by Ron Sigal (JIRA)

CLONE -Version compatibility problem with leasing ------------------------------------------------- Key: JBREM-1160 URL: https://jira.jboss.org/jira/browse/JBREM-1160 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder) If "useClientConnectionIdentity" is set to "true, then org.jboss.remoting.ServerInvoker.updateClientLease() tries to get a leasePingerId from the request map and compare it to the leasePingerId in a Lease. But if the InvocationRequest came from an older client that doesn't know about connection identity, the value of leasePingerId is null. The test calls leasePingerId.equals(clientLease.getLeasePingerId() which causes a NullPointerException. The test should be reversed. Also, org.jboss.test.remoting.versioning.lease.LeaseVersionTestCase should be strengthened to catch this problem. -- 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

15 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBXB-100) Add support for unmarshal(Source)

by Thomas Diesler (JIRA)

Add support for unmarshal(Source) --------------------------------- Key: JBXB-100 URL: http://jira.jboss.com/jira/browse/JBXB-100 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-1.0.0.CR9 Reporter: Thomas Diesler JBossWS fragments the incomming SOAP message into Source elements. Currently its using DOMSource. The interface to JBossXB is inefficient since the DOMSource needs to be serialized into a String and then into an InputStream. It would be much better if JBossXB could unmarshall the Source directly. Later we could transparently switch from DOMSource to some more efficient implementation. -- 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

15 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-7544) HttpInvokerHA doesn't check reachability of HATarget before invoking

by Brian Stansberry (JIRA)

HttpInvokerHA doesn't check reachability of HATarget before invoking -------------------------------------------------------------------- Key: JBAS-7544 URL: https://jira.jboss.org/jira/browse/JBAS-7544 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-6.0.0.M1, JBossAS-5.1.0.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M2 HttpInvokerHA.invoke is missing logic like this found in the other HA detached invokers: HATarget target = (HATarget)beanMap.get(invocation.getObjectName()); if (target == null) { // We could throw IllegalStateException but we have a race condition that could occur: // when we undeploy a bean, the cluster takes some time to converge // and to recalculate a new viewId and list of replicant for each HATarget. // Consequently, a client could own an up-to-date list of the replicants // (before the cluster has converged) and try to perform an invocation // on this node where the HATarget no more exist, thus receiving a // wrong exception and no failover is performed with an IllegalStateException // throw new GenericClusteringException(GenericClusteringException.COMPLETED_NO, "target is not/no more registered on this node"); } if (!target.invocationsAllowed ()) throw new GenericClusteringException(GenericClusteringException.COMPLETED_NO, "invocations are currently not allowed on this target"); This is why HAInvokerUnitTestCase.testHttpHAProxyFailover intermittently fails with java.lang.IllegalArgumentException: null object name at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:515) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:662) at org.jboss.invocation.http.server.HttpInvokerHA.invoke(HttpInvokerHA.java:135) If the missing code were there, the MBeanServer.invoke call with the null object name would never occur and the client would get a GenericClusteringException that would trigger failover. -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBLOGGING-21) make org.jboss.logging.filter.TCLFilter.isMatchingTCL() non-private for overriding purposes

by Juergen none (JIRA)

make org.jboss.logging.filter.TCLFilter.isMatchingTCL() non-private for overriding purposes ------------------------------------------------------------------------------------------- Key: JBLOGGING-21 URL: https://jira.jboss.org/jira/browse/JBLOGGING-21 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jboss-logging-log4j Affects Versions: 2.1.0.GA-log4j Environment: jboss-5.1.0.GA Reporter: Juergen none Assignee: Dimitris Andreadis Attachments: RegExpTCLFilter.java I wanted to override TCLFilter to implement a RegExpTCLFilter, but because org.jboss.logging.filter.TCLFilter.isMatchingTCL() is declared private I could not subclass TCLFilter and just override that method. might be nice to change from private to protected -- 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

15 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBLOGGING-28) I18n logger does not use bundle

by Alessio Soldano (JIRA)

I18n logger does not use bundle ------------------------------- Key: JBLOGGING-28 URL: https://jira.jboss.org/jira/browse/JBLOGGING-28 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logging-jdk Affects Versions: 2.2.0.CR1-jboss-logging Reporter: Alessio Soldano Assignee: David Lloyd I've tried the recently added feature for using I18n loggers, forcing the JDK14LoggerPlugin being used through system property. My bundle seems not to be taken into consideration thought. -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBLOGGING-32) Add a format character for method name and source line number

by David Lloyd (JIRA)

Add a format character for method name and source line number ------------------------------------------------------------- Key: JBLOGGING-32 URL: https://jira.jboss.org/jira/browse/JBLOGGING-32 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.2.0.CR1-jboss-logmanager They were missed in the initla logmanager impl. Method name should be "%M". Line number should be "%L". -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBLOGGING-20) JDK loggign isLoggable(Level.FINEST) returns false with Log4J backend

by Ondrej Medek (JIRA)

JDK loggign isLoggable(Level.FINEST) returns false with Log4J backend --------------------------------------------------------------------- Key: JBLOGGING-20 URL: https://jira.jboss.org/jira/browse/JBLOGGING-20 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logbridge Environment: JBoss 5.1.0, JDK 1.6u13 Reporter: Ondrej Medek Assignee: Dimitris Andreadis I have code using JDK logging like: if (LOG.isLoggable(Level.FINEST)) { LOG.finest("added into list: " + something); } I have no log. When I use just LOG.finest("added into list: " + something); I got a log in the log file. I use JBoss with Log4J. It is configured to log ALL stuff. -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBAS-7102) Problem sending large files via farm service

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7102?page=com.atlassian.jira.plug... ] Brian Stansberry updated JBAS-7102: ----------------------------------- Fix Version/s: JBossAS-6.0.0.M2 (was: JBossAS-6.0.0.M3) Moving to M2 as I've committed the change to have all but the last fragment of a file sent async. Reenabled the huge deployment test. > Problem sending large files via farm service > -------------------------------------------- > > Key: JBAS-7102 > URL: https://jira.jboss.org/jira/browse/JBAS-7102 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering, ProfileService > Affects Versions: JBossAS-5.1.0.GA > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: JBossAS-6.0.0.M2 > > > Users have reported issues sending large files over the AS 5.1 farming service; see 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

15 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2009