February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-2823) Upgrade commons-logging to v1.1

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2823?page=all ] Dimitris Andreadis updated JBAS-2823: ------------------------------------- Issue Type: Task (was: Feature Request) > Upgrade commons-logging to v1.1 > ------------------------------- > > Key: JBAS-2823 > URL: http://jira.jboss.com/jira/browse/JBAS-2823 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Logging > Affects Versions: JBossAS-4.0.2 Final, JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1 > Environment: Windows XP Professional, JDK 1.5.0 > Reporter: Martin Lui > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.0.CR1 > > > The Apache commons-logging package has release version 1.1.0. > Please upgrade this library to take advantage of items listed in the release notes: > http://jakarta.apache.org/commons/logging/RELEASE-NOTES.txt > It would be helpful if this upgrade can be done to upgrade the server libraries since individual EAR files cannot overwrite this particular library. > Also, looking through the notes and searching for information on the 1.0.4 patch, it appears that the WeakHashTables memory-leak fix is included in 1.1.0. (Bug 31286: http://issues.apache.org/bugzilla/show_bug.cgi?id=31286) > Depending on how JBoss uses this package, upgrading should be as simple as replacing the current package (though I admit I had not try doing so yet). -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-248) Smart copying for message references

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-248?page=all ] Tim Fox closed JBMESSAGING-248. ------------------------------- Fix Version/s: 1.2.0.CR1 (was: 1.2.1) Resolution: Won't Fix Not applicable any more. Message Reference no longer extends the same super class as MessageSupport > Smart copying for message references > ------------------------------------ > > Key: JBMESSAGING-248 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-248 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Optional > Fix For: 1.2.0.CR1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently when a mesage reference is copied, all the headers and properties are copied. In most cases this is unnecessar since they aren't changed. > Introduce a smart proxr around the reference that lazily copies the headers and properties as and when needed similar to message delegates. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-266) Remove Routable

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-266?page=all ] Tim Fox closed JBMESSAGING-266. ------------------------------- Resolution: Done Routable has been removed anyway now as part of message model / persistence refactoring > Remove Routable > --------------- > > Key: JBMESSAGING-266 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-266 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Remove Routable interface. > Have interface MessageReference which represents things that can be routed. > Have interface Payload (TBD) which every MessageReference has, this contains data that is not necessarty for routing. > We would then have a subclass of Payload called JMSPayload which contains all the jms stuff,not needed for routing. > A jms message would extend Message Reference and contain fields such as delivery count. > The jms message would contain a Payload interface and delegate for that for other attributes -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-330) Consider using remoting raw invocations

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-330?page=all ] Tim Fox closed JBMESSAGING-330. ------------------------------- Fix Version/s: 1.2.0.CR1 (was: 1.2.1) Resolution: Won't Fix After investigation, there seems to be no advantage in doing this. > Consider using remoting raw invocations > --------------------------------------- > > Key: JBMESSAGING-330 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-330 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.CR1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently we are not using raw remoting invocations so have to package/unpackage the invocation in the marshaller which cause unnecessary code and object creation and is generally messy. If we used remoting raw invocations we could simplify the wire format code. > Pings would still use normal non raw invocations so the session id is passed which is needed on the server side. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-695) We need to be able to run our functional testsuite with other databses besides HSQLDB

by Clebert Suconic (JIRA)

We need to be able to run our functional testsuite with other databses besides HSQLDB ------------------------------------------------------------------------------------- Key: JBMESSAGING-695 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-695 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 Right now we can't as part of the database is different when we run Clustered or non Clustered tests. Maybe we should aways use the same DDL to simplify things. (I'm not sure aobut that.. just guessing) Also... it looks like we will have some residual data on the database in between tests. -- 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

19 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-4084) Webservice Proxy (org.jboss.ws.jaxrpc.CallProxy) is not thread safe

by Amine Belkoura (JIRA)

Webservice Proxy (org.jboss.ws.jaxrpc.CallProxy) is not thread safe ------------------------------------------------------------------- Key: JBAS-4084 URL: http://jira.jboss.com/jira/browse/JBAS-4084 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: JBossAS-4.0.5.GA Environment: Windows Reporter: Amine Belkoura Assigned To: Thomas Diesler Fix For: JBossAS-4.2.0.CR1 We are performing load tests with webservices at the moment and we discovered the following issue: If multiple threads use the same CallProxy instance (the proxy is fetched once with a jndi lookup) then the following exception occured: 12:24:19,990 ERROR [WSWork] Error while calling the web service java.rmi.RemoteException: Call invocation failed with code [Client] because of: Request struct cannot be null; nested exception is: javax.xml.rpc.soap.SOAPFaultException: Request struct cannot be null at org.jboss.ws.common.CommonClient.invoke(CommonClient.java:331) at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:560) at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:338) at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:148) at $Proxy211.perform(Unknown Source) at com.winterthur.jackpot.j2eeperf.work.WSWork.perform(WSWork.java:50) at com.winterthur.jackpot.j2eeperf.PerfImpl.dispatch(PerfImpl.java:141) at com.winterthur.jackpot.j2eeperf.PerfImpl.execute(PerfImpl.java:102) at com.winterthur.jackpot.j2eeperf.web.PerfServlet.doGetOrPost(PerfServlet.java:122) at com.winterthur.jackpot.j2eeperf.web.PerfServlet.doGet(PerfServlet.java:58) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at sun.reflect.GeneratedMethodAccessor844.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275) at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:245) at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50) at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152) at com.winterthur.jackpot.servlet.util.RequestEncodingFilter.doFilter(RequestEncodingFilter.java:47) at sun.reflect.GeneratedMethodAccessor843.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275) at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:217) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:197) at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50) at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152) at com.winterthur.jackpot.servlet.util.StrippedSessionIdFilter.doFilter(StrippedSessionIdFilter.java:35) at sun.reflect.GeneratedMethodAccessor842.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275) at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:217) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:197) at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50) at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152) at com.winterthur.jackpot.servlet.util.Log4JMDCPropagationFilter.doFilter(Log4JMDCPropagationFilter.java:70) at sun.reflect.GeneratedMethodAccessor841.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275) at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:217) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:197) at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50) at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at com.winterthur.jackpot.tomcat.valves.SubjectDelegationCheckValve.invoke(SubjectDelegationCheckValve.java:125) at com.winterthur.jackpot.tomcat.valves.ClusterFailureValve.invoke(ClusterFailureValve.java:134) at com.winterthur.jackpot.tomcat.valves.ResetServernameValve.invoke(ResetServernameValve.java:88) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: javax.xml.rpc.soap.SOAPFaultException: Request struct cannot be null at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.getSOAPFaultException(SOAPFaultExceptionHelper.java:100) at org.jboss.ws.common.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:574) at org.jboss.ws.common.CommonClient.invoke(CommonClient.java:319) ... 85 more The soap request was invoked with an incomplete body element (second message). -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-812) "Cannot find object in dispatcher..." intermittent failures

by Tim Fox (JIRA)

"Cannot find object in dispatcher..." intermittent failures ----------------------------------------------------------- Key: JBMESSAGING-812 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-812 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Priority: Critical Fix For: 1.2.0.CR1 Attachments: cannot_find_object.log Intermittently when running the test suite in remote socket mode (and http?) we obtain errors as invocations hit the server but the target object cannot be found. After inspecting the logs it seems the JBoss Remoting is detecting a problem on an actually healthy connection, causing it to be closed. The connection is actually still alive and some time later the client makes an invocation resulting in the target object not being found. See attached logs. I will be running with remoting trace, to get more info sine the logs do not have enough information as to why remoting thinks the connection has a problem. -- 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

19 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-739) Make sure db schema is correct

by Tim Fox (JIRA)

Make sure db schema is correct ------------------------------ Key: JBMESSAGING-739 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-739 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.CR1 When 1.2 is released we want to make sure the db schema is optimal, since we don't want to have to change it again unless we really have to. We may be able to trim some fields from the message table. -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-870) Check state in PersistenceUnitRegistry

by Carlo de Wolf (JIRA)

Check state in PersistenceUnitRegistry -------------------------------------- Key: EJBTHREE-870 URL: http://jira.jboss.com/jira/browse/EJBTHREE-870 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf PersistenceUnitRegistry should have the same checks as Ejb3Registry. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4073) failing org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTestCase ------------------------------------------------------------------------ Key: JBAS-4073 URL: http://jira.jboss.com/jira/browse/JBAS-4073 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_10 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Client VM Java VM Version 1.5.0_10-b03 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-42.0.2.EL OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.CR1 New test added by Brian - just so we keep a record of the fix. -- 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

19 years, 3 months

3
4
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 February 2007