December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-588) Improve documentation to provide guidance for large rulesets over 10K

by peter lin (JIRA)

Improve documentation to provide guidance for large rulesets over 10K --------------------------------------------------------------------- Key: JBRULES-588 URL: http://jira.jboss.com/jira/browse/JBRULES-588 Project: JBoss Rules Issue Type: Patch Security Level: Public (Everyone can see) Components: Documentation Reporter: peter lin Assigned To: Mark Proctor Priority: Trivial Last week someone contacted me directly and asked whether JBossRules could handle 50K+ rules. I think it would be good to expand "5.1.8. Large drl files" of the documentation to provide some practical strategies and guidance to users. The docs already recommend increasing the permGen, but more guidance should be provided. Most users aren't going to know what to do when they really have to load 50K rules in the same appserver or jvm. I will try to write something up and check it in this weekend. hopefully when my brain is marginally functional. -- 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

15 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-419) Test with 80-node cluster

by Bela Ban (JIRA)

Test with 80-node cluster ------------------------- Key: JGRP-419 URL: http://jira.jboss.com/jira/browse/JGRP-419 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 Test in the Tyson's Corner lab (10 8-core boxes) -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3852) Redundant output in the test401Compatibility() method of SerialVersionUIDUnitTestCase

by Pavel Tsekov (JIRA)

Redundant output in the test401Compatibility() method of SerialVersionUIDUnitTestCase ------------------------------------------------------------------------------------- Key: JBAS-3852 URL: http://jira.jboss.com/jira/browse/JBAS-3852 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Pavel Tsekov Priority: Trivial See the forum reference for further information. -- 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

15 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3570) SSLUnitTestCase testsuite failures when using the IBM JVM

by Matt Wringe (JIRA)

SSLUnitTestCase testsuite failures when using the IBM JVM --------------------------------------------------------- Key: JBAS-3570 URL: http://jira.jboss.com/jira/browse/JBAS-3570 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Environment: IBM 1.4.2 JDK RHEL 4, Linux Kernel 2.6.9 Arch: i386 Reporter: Matt Wringe The org.jboss.test.web.test.ssl.SSLUnitTestCase tests fail when the IBM JDK is used. testHttpRedirect Error: Connection refused testHttpRedirectSecurityDomain Error: Connection refused testHttps Error: Connection refused testHttpsSecurityDomain Error: Connection refused Stack Trace: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:336) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:201) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:188) at java.net.Socket.connect(Socket.java:478) at java.net.Socket.connect(Socket.java:428) at java.net.Socket.<init>(Socket.java:335) at java.net.Socket.<init>(Socket.java:150) at com.ibm.jsse.bv.<init>(Unknown Source) at com.ibm.jsse.JSSESocketFactory.createSocket(Unknown Source) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:93) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:652) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:628) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:497) at org.jboss.test.web.test.ssl.SSLUnitTestCase.doHttps(SSLUnitTestCase.java:117) at org.jboss.test.web.test.ssl.SSLUnitTestCase.testHttpsSecurityDomain(SSLUnitTestCase.java:85) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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

15 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-4386) OutOfMemory Errors

by Richard Achmatowicz (JIRA)

OutOfMemory Errors ------------------ Key: JBAS-4386 URL: http://jira.jboss.com/jira/browse/JBAS-4386 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.2.0.GA Environment: x86_64, Windows 2003, Sun JVM Reporter: Richard Achmatowicz Priority: Blocker The AS testsuite is encountering OOMEs during testing against the 'all' configuration. The testsuite completes its run, and the problem is detected by noting that only 4022 of the 4103 tests in the testsuite have completed - the remainder have timed out due to an unresponsive server. Upon inspection of the server logs, the OOME messages are discovered. I have attached the server.log and output.log from the AS server, as well as the test.log from the client side testsuite. These logs are not complete, as I terminated the testsuite run after noticing the error. It is not clear which tests are causing the OOME. By looking at the timestamps on both logs, and noting that the first OOME occurred at 14:49:05 in the server log, this was at the time that the test org.jboss.test.jmx.test.RedeployStressTestCase was executing on the client side, but rerunning that test with a newly started AS did not reproduce the error. -- 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

15 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-3551) JBAS 4.0.4GA Test suite Error on Java 1.5 - org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase(testRMMResourceImplementsMBean)

by Vivek Lakshmanan (JIRA)

JBAS 4.0.4GA Test suite Error on Java 1.5 - org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase(testRMMResourceImplementsMBean) ------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3551 URL: http://jira.jboss.com/jira/browse/JBAS-3551 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Environment: Sun Java 1.5.0_08, Java VM Version 1.5.0_08-b03 OS: RHEL4 U3 Kernel 2.6.9-34.EL Arch: i386 Reporter: Vivek Lakshmanan The above test (ModelMBeanTestCase-testRMMResourceImplementsMBean) fails on Sun 1.5 JVM. The stacktrace produced follows: 04:06:15,472 DEBUG [ModelMBeanTestCase] failed javax.management.MBeanException: Operation setpojoAttribute not in ModelMBeanInfo at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:859) at javax.management.modelmbean.RequiredModelMBean.setAttribute(RequiredModelMBean.java:1692) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.setAttribute(DynamicMetaDataImpl.java:180) at com.sun.jmx.mbeanserver.MetaDataImpl.setAttribute(MetaDataImpl.java:206) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.setAttribute(DefaultMBeanServerInterceptor.java:737) at com.sun.jmx.mbeanserver.JmxMBeanServer.setAttribute(JmxMBeanServer.java:722) at org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase.testRMMResourceImplementsMBean(ModelMBeanTestCase.java:142) 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:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) 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:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567) Caused by: javax.management.ServiceNotFoundException: Operation setpojoAttribute not in ModelMBeanInfo ... 22 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

15 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-4468) Refactor org.jboss.test.pooled.test.SSLSocketsUnitTestCase to avoid random failures

by Dimitris Andreadis (JIRA)

Refactor org.jboss.test.pooled.test.SSLSocketsUnitTestCase to avoid random failures ----------------------------------------------------------------------------------- Key: JBAS-4468 URL: http://jira.jboss.com/jira/browse/JBAS-4468 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security, Test Suite Affects Versions: JBossAS-4.2.0.GA Reporter: Dimitris Andreadis Assigned To: Anil Saldhana org.jboss.test.pooled.test.SSLSocketsUnitTestCase randomly fails on some platform so the test needs refactoring. At the moment it has been excluded from the testsuite run (badtests.excludes) -- 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

15 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3567) MissingMethodUnitTestCase testsuite failures when using the IBM JVM

by Matt Wringe (JIRA)

MissingMethodUnitTestCase testsuite failures when using the IBM JVM ------------------------------------------------------------------- Key: JBAS-3567 URL: http://jira.jboss.com/jira/browse/JBAS-3567 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Environment: IBM 1.4.2 JDK RHEL 4, Linux Kernel 2.6.9 Reporter: Matt Wringe The following MissingMethodUnitTestCase tests fail when using the 1.4.2 IBM JVM: org.jboss.test.jacc.test.MissingMethodUnitTestCase(JACC) - testMissingIsUnchecked org.jboss.test.jacc.test.MissingMethodUnitTestCase(JACC)- testMissingIsExcluded org.jboss.test.jacc.test.MissingMethodUnitTestCase(JACC+SecurityMgr) - testMissingIsUnchecked org.jboss.test.jacc.test.MissingMethodUnitTestCase(JACC+SecurityMgr) - testMissingIsExcluded Each of these tests fail with the same error: SecurityException; nested exception is: java.lang.SecurityException: Denied: (javax.security.jacc.EJBMethodPermission MissingMethodBean create,Home,)[Home:create()], caller=Subject: Principal: jduke Principal: Roles(members:AuthorizedUser,ServletUserRole) -- 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

15 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3543) org.jboss.test.entity.test.EntityUnitTestCase fails because "test" is not bound

by Jaroslaw Kijanowski (JIRA)

org.jboss.test.entity.test.EntityUnitTestCase fails because "test" is not bound ------------------------------------------------------------------------------- Key: JBAS-3543 URL: http://jira.jboss.com/jira/browse/JBAS-3543 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.0.0.Beta Environment: win xp Reporter: Jaroslaw Kijanowski org.jboss.test.entity.test.EntityUnitTestCase because "test" is not bound at the beginning of the test nor at startup of the server. FIX: Create directory META-INF in testsuite/src/resources/entity/entity In META-INF create two xml files: ejb-jar.xml ********************************************** <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd"> <ejb-jar > <description><![CDATA[No Description.]]></description> <display-name>Generated by XDoclet</display-name> <enterprise-beans>    <entity > <description><![CDATA[An entity.]]></description> <ejb-name>TestEntity</ejb-name> <home>org.jboss.test.entity.interfaces.TestEntityHome</home> <remote>org.jboss.test.entity.interfaces.TestEntity</remote> <local-home>org.jboss.test.entity.interfaces.TestEntityLocalHome</local-home> <local>org.jboss.test.entity.interfaces.TestEntityLocal</local> <ejb-class>org.jboss.test.entity.beans.TestEntityCMP</ejb-class> <persistence-type>Container</persistence-type> <prim-key-class>java.lang.String</prim-key-class> <reentrant>False</reentrant> <cmp-version>2.x</cmp-version> <abstract-schema-name>test</abstract-schema-name> <cmp-field > <description><![CDATA[]]></description> <field-name>entityID</field-name> </cmp-field> <cmp-field > <description><![CDATA[]]></description> <field-name>value1</field-name> </cmp-field> <primkey-field>entityID</primkey-field>  </entity>    </enterprise-beans>   <assembly-descriptor >    <container-transaction > <method > <ejb-name>TestEntity</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Required</trans-attribute> </container-transaction>  </assembly-descriptor> </ejb-jar> ************************************* ************************************* ************************************* jboss.xml ************************************* <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd"> <jboss> <enterprise-beans>  <entity> <ejb-name>TestEntity</ejb-name> <jndi-name>test/entity/TestEntity</jndi-name> <local-jndi-name>test/entity/TestEntityLocal</local-jndi-name> <configuration-name>TestEntity Container Configuration</configuration-name> </entity> </enterprise-beans> <resource-managers> </resource-managers> <container-configurations>  <container-configuration extends="Standard CMP 2.x EntityBean"> <container-name>TestEntity Container Configuration</container-name> <commit-option>B</commit-option> </container-configuration> </container-configurations> </jboss> -- 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

15 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3534) "javax.ejb.EJBException: Error performing store" in test org.jboss.test.hibernate.test.HibernateIntgUnitTestCase

by Jaroslaw Kijanowski (JIRA)

"javax.ejb.EJBException: Error performing store" in test org.jboss.test.hibernate.test.HibernateIntgUnitTestCase ---------------------------------------------------------------------------------------------------------------- Key: JBAS-3534 URL: http://jira.jboss.com/jira/browse/JBAS-3534 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.0.0.Beta Environment: win xp Reporter: Jaroslaw Kijanowski This test contains two methods ( testRedeployment() and testCurrentSession() ). The first one creates an user with a handle "myHandle" and stores him in a database. The second one creates a user too, with the same handle. This is the reason for the EJBException. Deeper in the stacktrace there is an "org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update" so it's is not an JBAS issue, right? If yes here's the fix for the testsuite test, so it can run successfully: In the testCurrentSession() method replace following lines of code: *************** current: user.setHandle("myHandle"); has to be: user.setHandle("myHandle-testCurrentSession"); *************** current: assertEquals( "Incorrect result size", 1, users.size() ); has to be: assertEquals( "Incorrect result size", 2, users.size() ); // This is because we have now two users in the database, one created with the first method, and a second one created inside this method *************** current: Long userId = ( ( User ) users.get( 0 ) ).getId(); assertEquals( "Saved used not returned", savedUserId, userId ); has to be: Long userId = ( ( User ) users.get( 1 ) ).getId(); assertEquals( "Saved user not returned", savedUserId, userId ); // We need the second user from the database, to comapare his id with that one returned by the method getId() -- 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

15 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007