October 2006 - jboss-jira - Jboss List Archives

[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, 3 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, 3 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, 3 months

2
1
0 / 0

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

by Matt Wringe (JIRA)

SSLSocket testsuite failures when using the IBM JVM --------------------------------------------------- Key: JBAS-3569 URL: http://jira.jboss.com/jira/browse/JBAS-3569 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 SSLSocket tests frequently fail when using the IBM JDK org.jboss.test.jrmp.test.SSLFailuresSocketsUnitTestCase testClientCertSSLAccessFailure Error: javax.naming.NameNotFoundException: StatelessSessionWithSSL not bound org.jboss.test.jrmp.test.SSLSocketsUnitTestCase testClientCertSSLAccess Error: javax.naming.NameNotFoundException: StatelessSessionWithSSL not bound org.jboss.test.pooled.test.SSLSocketsUnitTestCase testClientCertSSLAccess Error: javax.naming.NameNotFoundException: StatelessSessionWithPooledSSL not bound -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3559) SerialVersionUIDUnitTestCase (test401Compatibility) testsuite failure with a 1.5 JVM

by Matt Wringe (JIRA)

SerialVersionUIDUnitTestCase (test401Compatibility) testsuite failure with a 1.5 JVM ------------------------------------------------------------------------------------ Key: JBAS-3559 URL: http://jira.jboss.com/jira/browse/JBAS-3559 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 1.5.0_08 JVM RHEL 4, Linux Kernel 2.6.9 Reporter: Matt Wringe The org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase test401Compatibility test fails when using with the Sun 1.5.0 JVM. >From the test report: "Failures on SerialVersionComparisson:javax.management.loading.MLet, org.jboss.monitor.alarm.AlarmNotification, org.jboss.monitor.alarm.AlarmTableNotification junit.framework.AssertionFailedError: Failures on SerialVersionComparisson:javax.management.loading.MLet, org.jboss.monitor.alarm.AlarmNotification, org.jboss.monitor.alarm.AlarmTableNotification at org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase.test401Compatibility(SerialVersionUIDUnitTestCase.java:175)" This appears to be very similar to issue JBAS-2965 (http://jira.jboss.com/jira/browse/JBAS-2965) which was fixed for JBossAS-4.0.4GA -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-655) Refactor @Service beans

by Bill Burke (JIRA)

Refactor @Service beans ----------------------- Key: EJBTHREE-655 URL: http://jira.jboss.com/jira/browse/EJBTHREE-655 Project: EJB 3.0 Issue Type: Task Reporter: Bill Burke Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC9 - FD Refactor @Service beans to fix a number of problems: * magic methods for lifecycle methods: - create/start/stop/destroy * lifecycle methods are not required to be in @Management (MBean) interface. * @Management interface is not registered with the ServiceController (Controller in MC land). It *IS* registered as a regular MBean though. * If lifecycle methods exist on @Management interface, they must be intercepted on the container so that the appropriate Controler start/stop is done on the container. This would mean that you have to specify a <bind> in the Service aspect domain in ejb3-interceptors-aop.xml -- 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, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-3495) Windows service for JBossAS

by Luc Texier (JIRA)

Windows service for JBossAS --------------------------- Key: JBAS-3495 URL: http://jira.jboss.com/jira/browse/JBAS-3495 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Environment: Win32 Reporter: Luc Texier Fix For: JBossAS-5.0.0.Beta Windows users have a hard time deploying JBossAS as a Windows service. Most of them try to use JavaService from ObjectWeb which is too generic to support properly an application server instance. For exemple, generating thread dumps is impossible. Also the experience has shown that this tool is fairly broken causing hang-ups. -- 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, 4 months

5
9
0 / 0

[JBoss JIRA] Created: (JBAS-3425) Remove ClusterPartition's creation of a unique node name

by Brian Stansberry (JIRA)

Remove ClusterPartition's creation of a unique node name -------------------------------------------------------- Key: JBAS-3425 URL: http://jira.jboss.com/jira/browse/JBAS-3425 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 With the completion of JGRP-129, a unique node name can be obtained from the JGroups layer, so we should remove the creation of the name by cluster partition. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3764) Benchmark effect of JBoss Serialization in http session repl

by Brian Stansberry (JIRA)

Benchmark effect of JBoss Serialization in http session repl ------------------------------------------------------------ Key: JBAS-3764 URL: http://jira.jboss.com/jira/browse/JBAS-3764 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Benchmark to help decide whether to use it and whether to make it an option. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-738) @SecurityDomain should throw Exception if "java:/jaas/..."

by Wolfgang Knauf (JIRA)

@SecurityDomain should throw Exception if "java:/jaas/..." ---------------------------------------------------------- Key: EJBTHREE-738 URL: http://jira.jboss.com/jira/browse/EJBTHREE-738 Project: EJB 3.0 Issue Type: Feature Request Components: EJB3 Extensions Affects Versions: EJB 3.0 RC9 - FD Reporter: Wolfgang Knauf Priority: Minor Security Domains in J2EE 1.4 environment were always specified as "java:/jaas/MySecurityDomain", but the @SecurityDomain requires only "MySecurityDomain". To avoid this trapdoor a simple check "if (value.startsWith ("java:/jaas/") ) throw Exception" would probably avoid some errors in updating from EJB2.1 to EJB3. Same check makes sense for the annotation "<security-domain>" in jboss.xml. -- 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, 4 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 October 2006