March 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss internal QA (Test Suite)] - Re: Test suite classpath normalization

by scott.stark＠jboss.org

Yes, that is correct. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026926#4026926 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026926

19 years

1
0
0 / 0

[Design of JBoss Build System] - Re: Aggregate goal

by wolfc

I changed the artifact id to match. I saw in the generated module source jars double entries of all source files with an extra prefix of main (javax/ejb/EJBException.java and main/javax/ejb/EJBException.java). The combined source contains even more prefixes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026918#4026918 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026918

19 years

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Test suite classpath normalization

by mvecera＠redhat.com

Hello, I have an idea I would like to discuss here. I copied tests.classpath to tests.compile.classpath. Then I added all jar files in build/output/JBoss-xxx/client/ at the beginning of test.classpath. Now using tests.compile.classpath for compiling tests and tests.classpath for running tests should result in desired behavior, shouldn't it? Because java searches for the first location of class in classpath it should use maximum of client/*.jar files. Is this correct? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026908#4026908 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026908

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Graphic Installer for Messaging

by vladimir.ralev＠jboss.com

OK, here is the the JEMS Installer (not released) that includes Messaging 1.2.GA (to test it you must run ant in the main folder): http://anonsvn.jboss.org/repos/installer/jems-installer/trunk/ installer output: output/jems-installer-1.2.0.GA.jar Currently we have some issues with the database selection because messaging still suports a limited set of databases. We will probably remove the unsupported dbms' when messaging is selected, and use the full set if the user goes with jbossmq (as before). We may also refactor the Messaging Config panel, because the only real messaging-related config is the security domain. Note that it doesn't include the mysql drivers. This is the upgrade/patch installer which installs messaging on an existing AS: http://anonsvn.jboss.org/repos/installer/jems-installer/branches/Branch_J... installer output: output/messaging-installer-1.2.0.GA.jar Unlike the JEMS Installer it uses directly the release-admin.xml, because it's capable of modifying "dirty" config files (we can't do that without ant in the installer right now). Here, we collect the ant properties database, ports, id from the user and pass them to the script. In installation path you must select the JBOSS_HOME. I'll also create a readme, which explains everything to the user (only mysql out of the box, names of AS configs, etc). Thanks for any suggestions and feedback. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026906#4026906 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026906

19 years

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: Clustering tests in jboss5 trunk

by bstansberry＠jboss.com

I kicked off the tests-clustering target a while ago and it's gotten past cluster-field-udp-SYNC; now through cluster-udp-TOTAL, and running cluster-field-udp-TOTAL with both servers started. I have to go out, so can't continue to monitor, but it looks to be running OK. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026868#4026868 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026868

19 years, 1 month

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Clustering tests in jboss5 trunk

by scott.stark＠jboss.org

I'm getting closer to getting the full testsuite to run by upping the memory limits, but I'm stopping at the cluster-field-udp-SYNC tests: | [server:start] C:\usr\java\jdk1.5.0_09\bin\java -cp C:\home\svn\JBossHead\jboss- | head\build\output\jboss-5.0.0.Beta2\bin\run.jar;C:\usr\java\jdk1.5.0_09\lib\tool | s.jar -Xms128m -Xmx512m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dr | esolve.dns=false -Djgroups.udp.ip_ttl=0 -Djboss.multiplexer.stack=udp-sync org. | jboss.Main -c cluster-field-udp-SYNC-1 -b VALKYRIE | | BUILD FAILED | C:\home\svn\JBossHead\jboss-head\testsuite\build.xml:854: The following error oc | curred while executing this line: | C:\home\svn\JBossHead\jboss-head\testsuite\build.xml:939: The following error oc | curred while executing this line: | C:\home\svn\JBossHead\jboss-head\testsuite\build.xml:1036: Error starting server | "cluster-field-udp-SYNC-1": Server failed to start; see logs. | but the log certainly indicates it started: | 2007-03-10 02:19:55,484 DEBUG [org.jboss.web.tomcat.tc6.deployers.TomcatDeployer | ] Saw org.jboss.system.server.started notification, starting connectors | 2007-03-10 02:19:55,562 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-valkyrie%2F10.11.14.27-8080 | 2007-03-10 02:19:55,625 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-valkyrie%2F10.11.14.27-8009 | 2007-03-10 02:19:55,625 INFO [org.jboss.system.server.profileservice.ServerImpl] JBoss (Microcontainer) [5.0.0.Beta2 (build: SVNTag=JBoss_5_0_0_Beta2 date=2007 | 03100057)] Started in 55s:204ms | If I just run the -c cluster-field-udp-SYNC-1 -b VALKYRIE from the command line it starts fine and the root web app is accessible. Are others failing to run this as well? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026850#4026850 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026850

19 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: Common assembly and module folder names

by scott.stark＠jboss.org

I suppose. I guess the only issue is what are we going to do if we do make minor independent releases of the underlying projects. Say we do a 2.0.1 release of common, and then do 2.0.2 and 2.0.3 release of jboss-common-logging-log4j for whatever reason. Are there going to be jboss-common-2.0.2 and 2.0.3 releases as well, or will we release 2.0.2 and 2.0.3 versions of everything even without changes? We just need a plan on how this is going to be managed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026849#4026849 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026849

19 years, 1 month

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Testsuite checks for classloader leaks

by bstansberry＠jboss.com

The EJB2 SFSB and EJB3 stuff is checked in on Branch_4_2. Not on trunk, where I get all sorts of deployment errors. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026847#4026847 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026847

19 years, 1 month

1
0
0 / 0

[Design of JBoss Profiler] - Stripped down reference reports from JVMTIInterface

by bstansberry＠jboss.com

I'm loving using JVMTIInterface to generate classloader leak reports (see http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassloaderLeakUnitTestCase) but I'm wondering if it makes sense to add a method that produces a report with a lot of the superfluous chains removed. Basically, I'm thinking of something like exploreObject, but instead of writing to a PrintWriter, the method builds up a tree of Node objects that encapsulate the string entry for each explored data point (example class below.) As it's building up the tree, if it finds a data point that refers to a java.lang.Reference or to an object that's already been explored, it throws a ref to the node into a Set. When it's gone through all the data points, it iterates over the nodes in the set, calling removeBranch() on each. That will prune all branches from the tree that lead to Reference pointers or to objects that would be gc'd if the real leak is fixed. Then call toString() on the root node to get the slimmed down report. Does this make sense? | class Node { | final String message; | List<Node> children = new ArrayList<Node>(); | Node parent; | | Node(String msg) { | this.message = msg; | } | | void addChild(Node child) { | children.add(child); | child.setParent(this); | } | | void removeChild(child) { | children.remove(child); | if (children.size() == 0) | removeBranch(); | } | | void removeBranch() { | if (parent != null) | parent.removeChild(this); | } | | void setParent(Node parent) { | this.parent = parent; | } | | String toString() { | String result = msg + "\n"; | for (Iterator it = children.iterator(); it.hasNext();) | result += it.next().toString(); | } | } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026837#4026837 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026837

19 years, 1 month

1
0
0 / 0

[Design of JBoss Portal] - where the portlet container life cycle class located in JBos

by srinivasanj

hai where the Portlet container class located in the JBoss Portal View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026836#4026836 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026836

19 years, 1 month

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 March 2007