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

[Design of JBoss internal QA (Test Suite)] - testsuite's log4j configuration leads to large reports

by jaroslaw.kijanowski

Testsuite's log4j was configured to print DEBUG messages to system.out. This leads to a large TESTS-TestSuites.xml file. There are two targets in build.xml: tests-report-xml tests-report-text The first one generates testsuite/output/reports/text/TESTS-TestSuites.txt The second one testsuite/output/reports/xml/TESTS-TestSuites.xml Both files are small summaries (see below). Both targets uses a XSL Transformation to transform this huge TESTS-TestSuites.xml file. If this file is larger than 100MB, JAVA's embedded XSLT is unable finish this process: 812 tests = 98 MB = 11 minutes 27 seconds 813 tests = 100 MB = 21 minutes 26 seconds 817 tests (the whole testsuite) = 111MB = OOME after over 80 minutes So we can: - use another XSLT - STX, but this needs new stylesheets, new libraries - make the noisiest tests less verbose by commenting log.debug() - make log4j less verbose (this was already done by changing level from DEBUG to FATAL) - skip both targets above - do we need these files generated by that targets? TESTS-TestSuites.txt: ********************** <?xml version="1.0" encoding="UTF-8"?> <time-of-test>2007-01-25.10-47</time-of-test><jdk-vendor>Sun Microsystems Inc.</jdk-vendor><jdk-version>1.4.2_09</jdk-version><jvm-vm-spec-version>1.0</jvm-vm-spec-version><jvm-name>Java HotSpot(TM) Client VM</jvm-name><jvm-version>1.4.2_09-b05</jvm-version><jvm-info>mixed mode</jvm-info><java-spec-version>1.4</java-spec-version><java-class-version>48.0</java-class-version><os-name>Linux</os-name><os-arch>i386</os-arch><os-version>2.6.9-42.0.2.ELsmp</os-version>4167416511 ********************** TESTS-TestSuites.txt: ********************** JBoss daily test results SUMMARY Number of tests run: 4167 -------------------------------------------- Successful tests: 4165 Errors: 1 Failures: 1 -------------------------------------------- [time of test: 2007-01-25.10-47 GMT] [java.version: 1.4.2_09] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_09-b05] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.6.9-42.0.2.ELsmp] Useful resources: - http://jboss.sourceforge.net/junit-results/32/2007-01-25.10-47 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! -------------------------------------------- DETAILS OF ERRORS Suite: org.jboss.test.pooled.test.SSLSocketsUnitTestCase Test: testClientCertSSLAccess Type: error Exception: java.rmi.AccessException Message: SecurityException; nested exception is: javax.security.auth.login.FailedLoginException: Supplied Credential did not match existing credential for null --------------------------------- Suite: org.jboss.test.security.test.SRPLoginModuleUnitTestCase Test: testSRPLoginWithAuxChallenge Type: failure Exception: junit.framework.AssertionFailedError Message: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt aux challenge --------------------------------- ********************** View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006616#4006616 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006616

17 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - JBPM_LOG issue

by prassib

I wrote a test program that runs against an in-memory database. I can successfully create a LoggingInstance by calling the method getLoggingInstance on the ProcessInstance. I can catch hold of the NodeLogs from the LoggingInstance & get the Node_Enter & Node_leave times. when we run similar code inside my application against my production database(DB2), my NodeLogs List size is always 0. I checked the database, there are no records in the JBPM_LOG table. Other tables like JBPM_PROCESSINSTANCE, JBPM_TOKEN, JBPM_TRANSITION show all the appropriate records but the JBPM_LOG table is always empty. Could anyone throw some light, why this could be happening? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006607#4006607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006607

17 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Guidance for JBPM-725? Applies to 3.2?

by zipwow

I ran into the issue described in JBPM-725 in jbpm 3.1: http://jira.jboss.com/jira/browse/JBPM-725 Set auto-import="false" for all hibernate-mapping elements in hibernate mapping files. >From a cursory glance of the 3.1 code, it looks like all (or the majority) of the hibernate queries are already written with fully qualified names, so I'm willing to tackle this change. Before I begin: Would it make sense to do this against the 3.2 codebase instead? Are there any pitfalls I should be aware of? Where should I look for the baseline of expected passing unit tests? (I seem to get some failures out of the box for 3.1) Thanks, Kevin Klinemeier View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006603#4006603 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006603

17 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - what are the new features in JBPM 3.2?

by prassib

Is there any documentation available? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006591#4006591 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006591

17 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: JAXBDeployer

by jason.greene＠jboss.com

"jason.greene(a)jboss.com" wrote : | So the big difference here is that unlike JBossXB, there is no way to override the java annotations with schema annotations. This loss of flexibility is for performance reasons (no need to read/parse the schema at runtime). | So this creates a problem if the object model needs to be fixed (public API etc), but the schema needs to change significantly. Or different schemas need to be associated with the same object model. Under these scenarios, it's better to use the JAXB object model as an intermediary that directly represents the xml (in object form), and then copy / merge this information into a more elegant public API. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006588#4006588 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006588

17 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: JAXBDeployer

by jason.greene＠jboss.com

"scott.stark(a)jboss.org" wrote : How can this be specified via schema level annotations? | It reads everything directly from the Java annotations. The schema bindings just control the Java annotations that are generated when xjc is ran on the schema. So in order to have a plugable schema extension mechanism, you would have to have a way to register annotationed JAXB objects with some kind of MC context, and that would then be used to generate the JAXBContext that is responsible for unmarshalling the deployment descriptor. So the big difference here is that unlike JBossXB, there is no way to override the java annotations with schema annotations. This loss of flexibility is for performance reasons (no need to read/parse the schema at runtime). -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006579#4006579 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006579

17 years, 5 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: XAExpectionUnitTestCase Failures/JBossTS/JBoss 4.2

by weston.price＠jboss.com

A bit more. What is actually happening is because the tests required to matchManagedConnections to fail, when the test originally runs, the pool is empty. A connection is successfully created and enlisted/delisted in the tranasction and returned to the pool. The second attempt to acquire the connection fails in the match and the connection is destroeyd. Howerve,r JBossTS rightfully 'remembers' this guy and when JBossTS attempts to finish the txn protocol the connection has already been destroyed. This is where the error occurs. So, effectively the <track-connection-by-txn> really should be here and in fact, I believe it's a bug that it's not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006519#4006519 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006519

17 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: JAXBDeployer

by scott.stark＠jboss.org

How can this be specified via schema level annotations? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006518#4006518 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006518

17 years, 5 months

1
0
0 / 0

[Design of JCA on JBoss] - XAExpectionUnitTestCase Failures/JBossTS/JBoss 4.2

by weston.price＠jboss.com

In one of our unit tests | org.jboss.test.jca.test.XAExceptionUnitTestCase | we have two tests that simulate errors when a JCA resource is used in an EJB. One is a resource exception, the other a runtime exception. Both occur in the matchManagedConnections() method of of the TestManagedConnectionFactory. Being that an error/excpetion occurs, the underlying connection is destroyed prior to use; no problems here. Howerver, in one test the transaction is rolled back at the end of the in the finally block. Because the | <track-by-transaction> | flag is set to false when JBossTS attempts any sort of activity on the underlying resource it fails because the resource has already been destroyed. JBossTM seemed to either mask this condition, or just ignore it all together whileJBossTS reports a failure which is causing an ERROR in the tests. From what I understand, it seems that the | <track-by-transaction> | flag should really be true by default for XA connections(we already do this for local resources). I can't envision why this shouldn't be set as the default moving forward with the new transaction manager stuff. In fact, most JDBC based resources from the big RDBMS vendors (Oracle, DB2) and some of the open source guys (Postgres most notably but for other reasons) already require this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006507#4006507 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006507

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Error loading Web Services

by sacramentojoe

I should have stated I'm on Windows XP Pro. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006503#4006503 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006503

17 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2007