August 2009 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: New ClassPool sub-project; structure

by alesj

What's the reason those are package-protected ctors? Perhaps you can extract some (abstract) super classes from those who access those pckg-prot ctors / methods and place them in the spi pckg. Or all of them can be spi, and only have proper api to expose them - via some factory. The bottom point is that there is no magic bullet. Only common sense and logic. :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249794#4249794 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249794

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Why are HTTP integration test excluded from test suite?

by timfox

| <fileset dir="${test.classes.dir}"> | <exclude name="**/integration/http/*" /> | <include name="${tests.param}"/> | </fileset> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249790#4249790 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249790

16 years, 7 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Help needed to create a patch.

by ZeroTolerance

Hi, Can't help it. I wanted to know if it all worked so tried it at home too. Build everything on my own Mac OS X. Replaced the aop jars in the JBoss build and ran the tests. Before placing all kinds of stack traces and logging output I want to ask something. When running the tests I can see all kinds of exceptions flying across the jboss log window while the window in which I started the tests keeps saying that the tests are successful! This happens in both the ./build.sh test -Dtest=aop and ./build.sh smoke-tests-raw. Is that expected behaviour? Kind reagrds, Werner View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249785#4249785 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249785

16 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: AS-5 Files to watch for application redeployment

by jaikiran

anonymous wrote : This is now done in Deployers trunk - JBDEPLOY-210. Is the deployers trunk (2.2.x) compatible with AS 5_x branch and do we have plans to upgrade 5_x branch with 2.2.x or are we planning to continue with 2.0.x series in AS 5_x branch? I can give this a try on 5_x branch if 2.2.x is compatible there. I could have given this a quick try there but don't know what other things might break if 2.2.x is not supposed to be in 5_x :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249778#4249778 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249778

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Memory on test suite

by timfox

I've also added some diagnostics to aid in diagnosing where sessions were created that subsequently weren't closed. When gc closes a connection you will see something like this in the logs: | Finalizer] 20:14:43,244 WARNING [org.jboss.messaging.core.client.impl.DelegatingSession] I'm closing a ClientSession you left open. Please make sure you close all ClientSessions explicitly before letting them go out of scope! | [Finalizer] 20:14:43,244 WARNING [org.jboss.messaging.core.client.impl.DelegatingSession] The session you didn't close was created here: | java.lang.Exception | at org.jboss.messaging.core.client.impl.DelegatingSession.<init>(DelegatingSession.java:83) | at org.jboss.messaging.core.client.impl.ConnectionManagerImpl.createSession(ConnectionManagerImpl.java:375) | at org.jboss.messaging.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:968) | at org.jboss.messaging.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:758) | at org.jboss.messaging.tests.integration.client.CommitRollbackTest.testReceiveWithCommit(CommitRollbackTest.java:62) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at junit.framework.TestCase.runTest(TestCase.java:164) | at junit.framework.TestCase.runBare(TestCase.java:130) | at junit.framework.TestResult$1.protect(TestResult.java:106) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.framework.TestResult.run(TestResult.java:109) | at junit.framework.TestCase.run(TestCase.java:120) | at junit.framework.TestSuite.runTest(TestSuite.java:230) | at junit.framework.TestSuite.run(TestSuite.java:225) | at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) | at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:912) | at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:743) | The stack trace will tell you where in the code the session was created, that later wasn't closed. So we just need to run the test suite and look through the logs for these stack traces and fix the tests that don't close the sessions. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249764#4249764 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249764

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Memory on test suite

by timfox

One othing I noticed: Now if you don't close your jms connections or core client sessions you'll see a warning in the logs when it's closed at gc. You'll notice that *lots* of tests in the test suite are throwing warnings - in other words we have many poorly written tests that don't close connections properly! And yes you're right. If you don't close a connection, with the invm transport, it will keep a reference right through to the server and back which will mean whole servers won't be garbage collected. This should be fixed now (when I commit in the next few hours) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249759#4249759 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249759

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Memory on test suite

by timfox

I've the current gc issues - so now if ClientSession or JBossConnection instances are kept open they will not cause connections to leak. This may have been causing the leak you are seeing. Just running tests now, will commit soon. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249758#4249758 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249758

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Memory on test suite

by clebert.suconic＠jboss.com

At the end of the tests, there is about 900 PostOffice instances hanging around. I will run some tests later this weekend trying to identify the places that are probably holding the instances. It would be better for this diagnose if the Pingrunnable was shutdown right after the close call... It would be better to identify when the leak happened opposed to a regular delayed shutdown. On the InVM transport, the PintRunnable will indirectly hold an instance to the Server. (somewhere through InVMConnection). I will post more details later this weekend. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249757#4249757 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249757

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Wrapped JNDI Server

by timfox

In the JMS tests we're now using a small wrapper around the org.jnp.server.Main class which introduces a small delay on stop(). This is because there appears to be a bug in the class which means if you start() it again quickly after stopping it, you can get a java.rmi.server.ExportException: Port already in use: 1098; nested exception is: java.net.BindException: Address already in use exception, as the socket doesn't seem to get closed synchronously with the close() method. I think this has been causing intermittent test suite failures View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249756#4249756 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249756

16 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Problem with Portlet Container

by bromokun

I solved it ... :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249744#4249744 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249744

16 years, 7 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 August 2009