December 2008 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: FailoverTests consuming a lot of memory...

by timfox

"clebert.suconic(a)jboss.com" wrote : | I'm changing RandomFailoverTest and MultiThreadRandomFailoverTest to disable JMX on Management. | | . How about fixing management, rather than disabling it in the tests? :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197453#4197453 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197453

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: FailoverTests consuming a lot of memory...

by clebert.suconic＠jboss.com

It's actually quite funny... MultiThreadFailvoerTest was taking about 7 minutes to run before disabling JMX on the test, and 3 minutes after the change. (I ran all these without my changes for largeMessage & clustering) I have seen this MessageReferences following this path: MessagingReferenceImpl <- ConcurrentHashMaps <- QueueImpl <- MessageCounter <- ManagementImpl <- Somewhere_I_couldn't find (Probably JMX on the JVM) (This is a summarized graph of course.... the real profiler shows many more objects in between) I was only seeing MessageReferenceImpl growing on those tests, like the old JMXManagement Object was not being released. Maybe it would worth taking a look if management is not leaving objects after a server is stopped. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197452#4197452 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197452

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - FailoverTests consuming a lot of memory...

by clebert.suconic＠jboss.com

I was checking to what was causing an OME on my box, and I figured out the problem was on Management registering few objects on JMX making few objects reachable and holding several MessageReferenceImpl on the memory. I'm changing RandomFailoverTest and MultiThreadRandomFailoverTest to disable JMX on Management. That shouldn't be a problem but I wanted to communicate why I'm doing that here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197442#4197442 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197442

17 years, 3 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: VerifyError when using seam

by jesper.pedersen

If you could make a sample application that fails and create a JIRA issue under JBPROFILER it would be great. Also note, that JBoss Profiler 2.0 is mainly about CPU, so if you only need memory 1.0 would be your best bet. TIA ! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197432#4197432 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197432

17 years, 3 months

1
0
0 / 0

[Design of JBoss Profiler] - VerifyError when using seam

by ngtdave

JBoss 4.2.3.GA JBoss Profiler 2.0.Beta3.SP1 Seam 1.0.1 GA Once I turn on the profiler, and hit the first page of my seam app, I get this stack trace: | javax.servlet.ServletException: Servlet execution threw an exception | org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147) | org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:30) | org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:45) | org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | | root cause | | java.lang.VerifyError: (class: com/mycompany/presentation/action/LoginAction$$EnhancerByCGLIB$$edc38196, method: viewOrder signature: ()Ljava/lang/String;) Inconsistent stack height 2 != 1 | java.lang.Class.getDeclaredConstructors0(Native Method) | java.lang.Class.privateGetDeclaredConstructors(Class.java:2328) | java.lang.Class.getConstructor0(Class.java:2640) | java.lang.Class.newInstance0(Class.java:321) | java.lang.Class.newInstance(Class.java:303) | org.jboss.seam.Component.instantiate(Component.java:766) | org.jboss.seam.Component.newInstance(Component.java:731) | org.jboss.seam.Component.newInstance(Component.java:1308) | org.jboss.seam.Component.getInstance(Component.java:1263) | org.jboss.seam.Component.getInstance(Component.java:1246) | org.jboss.seam.jsf.SeamVariableResolver.resolveVariable(SeamVariableResolver.java:44) | com.sun.faces.el.VariableResolverChainWrapper.getValue(VariableResolverChainWrapper.java:100) | javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) | com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64) | org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:45) | org.apache.el.parser.AstValue.getTarget(AstValue.java:42) | org.apache.el.parser.AstValue.invoke(AstValue.java:127) | org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) | com.sun.faces.application.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77) | org.jboss.seam.core.Pages.callAction(Pages.java:161) | org.jboss.seam.core.Pages.callAction(Pages.java:143) | org.jboss.seam.jsf.AbstractSeamPhaseListener.callPageActions(AbstractSeamPhaseListener.java:128) | org.jboss.seam.jsf.AbstractSeamPhaseListener.beforeRender(AbstractSeamPhaseListener.java:98) | org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:50) | com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) | com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) | javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) | org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147) | org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:30) | org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:45) | org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | My jboss-profiler.properies: enable=yes | cpu=no | memory=yes | includes=com.mycompany.* | excludes=* | visibility=private | save=yes | startup=yes | repository=no | remote=yes | store=memory | location=. | host=localhost | port=5400 | ejb=yes | servlet=yes | jsf=yes | jmx=yes | rmi=yes | corba=yes | plugin.1=org.jboss.profiler.plugins.Hibernate | plugin.2=org.jboss.profiler.plugins.Seam | Non-seam apps seem to work fine. Any help would be great! Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197430#4197430 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197430

17 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Build Failure in ejb3-embedded

by ALRubinger

Java version: 1.6.0_06 This is a JDK6 thing. Odd. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197425#4197425 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197425

17 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Build Failure in ejb3-embedded

by ALRubinger

>From the POM: <properties> | <version.org.jboss.deployers>[2.0.0.CR5]</version.org.jboss.deployers> | <version.org.jboss.microcontainer>[2.0.0.GA]</version.org.jboss.microcontainer> | </properties> My Hudson doesn't report, but I have locally: Caused by: org.apache.maven.artifact.versioning.OverConstrainedVersionException: No versions are present in the repository for the artifact with a range [2.0.0.CR5,2.0.0.CR5] | org.jboss.deployers:jboss-deployers-core-spi:jar:null What's up, doc? ]$ mvn -version | Maven version: 2.0.9 | Java version: 1.6.0_06 | OS name: "linux" version: "2.6.27.5-117.fc10.x86_64" arch: "i386" Family: "unix" S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197423#4197423 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197423

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: infinite loop when connecting to a stopped acceptor

by jmesnil

I've added a test to show the infinite loop in org.jboss.messaging.tests.integration.basic.ClientSessionFactoryImplTest The test is named _testCreateSessionFailureWithDefaultValuesWhenNoServer with a leading '_' so that it is not run by our test suites View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197403#4197403 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197403

17 years, 3 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: JBIDE-3394, hot deployment management api

by max.andersen＠jboss.com

I would *really* like to avoid us having to deploy *anything* on a server to manage these things. Deploying something like that is a road to endless support issues. I would rather not have this feature in the tools if there is no other way - but from the sound of Scott it sounds like we could do something ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197369#4197369 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197369

17 years, 3 months

1
0
0 / 0

[Design of the JBoss EJB Container] - JBOSS / DEPLOY

by marcoamv3000

Caros amigos gostaria de saber porque o JBOSS faz o deploy dentro da pasta .../tmp/deploy/... e nÃ£o dentro da pasta /deploy/... como deveria ser? E mais uma coisa porque que toda vez que paro o JBOSS e inicio ele de novo ele remove todo o conteudo da pasta .../tmp/deploy/...? O que eu preciso Ã© o seguinte preciso que o meu JBOSS extraia o projeto dentro da pasta /deploy/ e que a pasta do meu projeto nÃ£o seja deletada quando eu para o JBOSS? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197326#4197326 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197326

17 years, 3 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-dev-forums December 2008