October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBSER-90) Add the ability to switch context class loaders on a per-invocation basis when using JBossObjectInputStreamSharedTree.read()

by Manik Surtani (JIRA)

Add the ability to switch context class loaders on a per-invocation basis when using JBossObjectInputStreamSharedTree.read() ---------------------------------------------------------------------------------------------------------------------------- Key: JBSER-90 URL: http://jira.jboss.com/jira/browse/JBSER-90 Project: JBoss Serialization Issue Type: Feature Request Affects Versions: 1.0.2 GA, 1.0.1 GA Reporter: Manik Surtani Assigned To: Clebert Suconic At the moment, in JBoss Cache, I need to be able to perform a read(), switch class loaders, and read() again. To make this work (using JBoss-Serialization-1.0.3.GA at the moment) I subclass JBossObjectInputStreamSharedTree as such: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jboss/JBossCache/src/org/jboss... It would be nice if I did not have to do this, and could use a version of JBossObjectInputStreamSharedTree that was in the jboss-serialization distro that provided this functionality. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1092) "Create a new file" tooltip says "Create a Directory"

by Ian White (JIRA)

"Create a new file" tooltip says "Create a Directory" ------------------------------------------------------ Key: JBPORTAL-1092 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1092 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.DR1 Environment: XP Reporter: Ian White Assigned To: Roy Russo Wrong text in the "Create a new file" tooltip. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3459) Remove the jms module

by Ruel Loehr (JIRA)

Remove the jms module --------------------- Key: JBAS-3459 URL: http://jira.jboss.com/jira/browse/JBAS-3459 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta Reporter: Ruel Loehr Assigned To: Ruel Loehr Fix For: JBossAS-5.0.0.Beta Remove the jms module from the build and source tree. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1090) fix testsuite build to include db driver jars for portal testing

by Prabhat Jha (JIRA)

fix testsuite build to include db driver jars for portal testing ---------------------------------------------------------------- Key: JBPORTAL-1090 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1090 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Test Reporter: Prabhat Jha Assigned To: Julien Viet This is related to automating portal tests against different database. Please see the details at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977826#3977826 and http://jira.jboss.com/jira/browse/JBQA-452, -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBAS-3368) jmx-console and other webapps are broken

by Scott M Stark (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3368?page=all ] Scott M Stark closed JBAS-3368. ------------------------------- Resolution: Done The jmx-console is working fine for me in trunk. > jmx-console and other webapps are broken > ---------------------------------------- > > Key: JBAS-3368 > URL: http://jira.jboss.com/jira/browse/JBAS-3368 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Dimitris Andreadis > Assigned To: Remy Maucherat > Priority: Critical > Fix For: JBossAS-5.0.0.Beta > > > The jmx-console, or the normal tomcat status pages are broken, probably due to the tomcat6 upgrade. > E.g. accessing the jmx-console: > 2006-07-05 14:10:18,350 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console].[jsp]] Servlet.service() for servlet jsp threw exception > java.lang.NoClassDefFoundError: org/apache/commons/el/ExpressionEvaluatorImpl > at org.apache.jasper.compiler.JspUtil.<clinit>(JspUtil.java:61) > at org.apache.jasper.JspCompilationContext.getServletClassName(JspCompilationContext.java:334) > at org.apache.jasper.JspCompilationContext.getClassFileName(JspCompilationContext.java:484) > at org.apache.jasper.compiler.Compiler.isOutDated(Compiler.java:379) > at org.apache.jasper.compiler.Compiler.isOutDated(Compiler.java:332) > at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:560) > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303) > at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > 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:174) > 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:104) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:222) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:823) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:444) > at java.lang.Thread.run(Thread.java:595) > Accessing the tomcat status page: > 2006-07-05 14:13:44,356 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/].[Status Servlet]] Servlet.service() for servlet Status Servlet threw exception > javax.management.AttributeNotFoundException: Cannot find attribute minSpareThreads > at org.apache.tomcat.util.modeler.BaseModelMBean.getAttribute(BaseModelMBean.java:259) > at org.jboss.mx.server.RawDynamicInvoker.getAttribute(RawDynamicInvoker.java:117) > at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:565) > at org.apache.catalina.manager.StatusTransformer.writeConnectorState(StatusTransformer.java:250) > at org.jboss.web.tomcat.tc6.StatusServlet.doGet(StatusServlet.java:255) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > 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:174) > 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:104) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:222) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:823) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:444) > at java.lang.Thread.run(Thread.java:595) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-794) Eviction Queue hard limit can cause deadlocks

by Owen Taylor (JIRA)

Eviction Queue hard limit can cause deadlocks --------------------------------------------- Key: JBCACHE-794 URL: http://jira.jboss.com/jira/browse/JBCACHE-794 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Owen Taylor Assigned To: Manik Surtani if the eviction queue fills up, you can get the situation where: - The eviction queue processing task calls evict() which needs to get a write lock on a node - A different thread has a read lock on that node and is blocking to put something into the eviction queue Once this starts happening the evication queue thread is procesing events *very* slowly because it repeatedly stalls while the lock times out, so the queue will stay full. Without digging into the code too much, possible fixes that occur to me include: 1) Don't have a hard limit on the size of the eviction queue, and just warn when it gets too big 2) Use a timeout of 0 when trying to get the write lock to evict a node, after all, if a node is locked when we try to evict it, it probably shouldn't be evicted anyways. -- 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, 6 months

2
8
0 / 0

[JBoss JIRA] Assigned: (JBAS-3348) Patch for JBAS-3347, %C log4j format problem

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3348?page=all ] Ryan Campbell reassigned JBAS-3348: ----------------------------------- Assignee: Jaroslaw Kijanowski (was: JBoss QA Lead) > Patch for JBAS-3347, %C log4j format problem > -------------------------------------------- > > Key: JBAS-3348 > URL: http://jira.jboss.com/jira/browse/JBAS-3348 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Components: Logging > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Jaroslaw Kijanowski > Attachments: commons-logging.jar > > > The %C classname format of the log4j pattern layout was broke by the 1.0.5.GA-jboss commons-logging release because the Log4jProxy was not using a FQCN that allowed the log4j LayoutInfo to find the caller. This has been corrected in the 1.0.5.SP1-jboss commons-logging release. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3791) NPE in org.jboss.mq.server.BasicQueue.setupMessageAcknowledgement()

by J?rg von Frantzius (JIRA)

NPE in org.jboss.mq.server.BasicQueue.setupMessageAcknowledgement() ------------------------------------------------------------------- Key: JBAS-3791 URL: http://jira.jboss.com/jira/browse/JBAS-3791 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.3 SP1 Environment: OS: Linux 2.6.9-22.0.2.ELsmp (amd64) JVM Version: 1.5.0_08-b03 (Sun Microsystems Inc.) JVM Name: Java HotSpot(TM) 64-Bit Server VM Reporter: J?rg von Frantzius Assigned To: Adrian Brock In a clustered system with 4 server instances, and after having received a couple of thousand of messages, we got the following exception in our logs. Afterwards, one subscribing MDB won't be called in onMessage() anymore. The stuff I wrote in the forum probably really is just unducated guessing. 2006-10-24 18:53:24,187 ERROR [UIL2(SocketManager.MsgPool@a52a72a client=192.168.100.214:53381)#4 SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.ReceiveMsg2084258688[msgType: m_receive, msgID: -2147361440, error: null] java.lang.NullPointerException at org.jboss.mq.server.BasicQueue.setupMessageAcknowledgement(BasicQueue.java:945) at org.jboss.mq.server.BasicQueue.receive(BasicQueue.java:516) at org.jboss.mq.server.JMSTopic.receive(JMSTopic.java:320) at org.jboss.mq.server.ClientConsumer.receive(ClientConsumer.java:222) at org.jboss.mq.server.JMSDestinationManager.receive(JMSDestinationManager.java:656) at org.jboss.mq.server.JMSServerInvoker.receive(JMSServerInvoker.java:226) at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:155) at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:369) at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748) at java.lang.Thread.run(Thread.java:595) 2006-10-24 18:53:24,251 WARN [Connection Consumer for dest Subscription[subId=-2147483648connection=ConnectionToken:ID:23/null destination=TOPIC.sgw/MOCacheInvalidationTopic messageSelector=null Local Create] id=12 SpyConnectionConsumer] Connection consumer closing due to error in listening thread SpyConnectionConsumer[sub=Subscription[subId=-2147483648connection=ConnectionToken:ID:23/null destination=TOPIC.sgw/MOCacheInvalidationTopic messageSelector=null Local Create] messages=0 waitingForMessage=false internalThread=Thread[Connection Consumer for dest Subscription[subId=-2147483648connection=ConnectionToken:ID:23/null destination=TOPIC.sgw/MOCacheInvalidationTopic messageSelector=null Local Create] id=12,5,jboss] sessionPool=org.jboss.jms.asf.StdServerSessionPool@6c6fff7a connection=Connection@753785396[token=ConnectionToken:ID:23/null rcvstate=STARTED]] org.jboss.mq.SpyJMSException: Cannot receive ; - nested throwable: (java.lang.NullPointerException) at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:66) at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:51) at org.jboss.mq.Connection.receive(Connection.java:916) at org.jboss.mq.SpyConnectionConsumer.run(SpyConnectionConsumer.java:238) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at org.jboss.mq.server.BasicQueue.setupMessageAcknowledgement(BasicQueue.java:945) at org.jboss.mq.server.BasicQueue.receive(BasicQueue.java:516) at org.jboss.mq.server.JMSTopic.receive(JMSTopic.java:320) at org.jboss.mq.server.ClientConsumer.receive(ClientConsumer.java:222) at org.jboss.mq.server.JMSDestinationManager.receive(JMSDestinationManager.java:656) at org.jboss.mq.server.JMSServerInvoker.receive(JMSServerInvoker.java:226) at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:155) at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:369) at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748) ... 1 more -- 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, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-828) PojoCache to move deprecated codes to old directory

by Ben Wang (JIRA)

PojoCache to move deprecated codes to old directory --------------------------------------------------- Key: JBCACHE-828 URL: http://jira.jboss.com/jira/browse/JBCACHE-828 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0.GA I have decided to move the old deprecated codes to old directory under JBossCache root (along with corresponding unit tests). This means that in 2.0 release, we will support only the new API s for PojoCache. Furthermore, only JDK5.0 is supported along with annotation (no 1.4 style annotation support). -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-299) Investigate failures using JRockit

by Kabir Khan (JIRA)

Investigate failures using JRockit ---------------------------------- Key: JBAOP-299 URL: http://jira.jboss.com/jira/browse/JBAOP-299 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha2 -- 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, 6 months

1
1
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 October 2006