[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, 4 months
[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, 4 months
[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, 4 months
[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>
<!-- Session Beans -->
<!--
To add session beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called session-beans.xml that contains
the <session></session> markup for those beans.
-->
<!-- Entity 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>
<!-- Write a file named ejb-finders-TestEntityBean.xml if you want to define extra finders. -->
</entity>
<!--
To add entity beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called entity-beans.xml that contains
the <entity></entity> markup for those beans.
-->
<!-- Message Driven Beans -->
<!--
To add message driven beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called message-driven-beans.xml that contains
the <message-driven></message-driven> markup for those beans.
-->
</enterprise-beans>
<!-- Relationships -->
<!-- Assembly Descriptor -->
<assembly-descriptor >
<!--
To add additional assembly descriptor info here, add a file to your
XDoclet merge directory called assembly-descriptor.xml that contains
the <assembly-descriptor></assembly-descriptor> markup.
-->
<!-- finder permissions -->
<!-- transactions -->
<container-transaction >
<method >
<ejb-name>TestEntity</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<!-- finder transactions -->
</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>
<!--
To add beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called jboss-beans.xml that contains
the <session></session>, <entity></entity> and <message-driven></message-driven>
markup for those 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>
<!-- Commit option B CMP Bean -->
<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, 4 months
[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, 4 months
[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, 4 months
[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, 4 months
[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, 4 months
[JBoss JIRA] Created: (GPD-10) can't find resource
by Tom Baeyens (JIRA)
can't find resource
-------------------
Key: GPD-10
URL: http://jira.jboss.com/jira/browse/GPD-10
Project: JBoss jBPM GPD
Issue Type: Bug
Reporter: Tom Baeyens
Assigned To: Koen Aers
i don't know why, but when trying to deploy the example process websale after modifying the form.create.xhtml, i got this exception that disabled depoyment of the process.
java.lang.NullPointerException
at org.jbpm.ui.util.ProcessDeployer.addClassOrResource(Unknown Source)
at org.jbpm.ui.util.ProcessDeployer.addClassesAndResources(Unknown Source)
at org.jbpm.ui.util.ProcessDeployer.createParBytes(Unknown Source)
at org.jbpm.ui.util.ProcessDeployer.access$1(Unknown Source)
at org.jbpm.ui.util.ProcessDeployer$1.run(Unknown Source)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:479)
at org.jbpm.ui.util.ProcessDeployer.showProgressMonitorDialog(Unknown Source)
at org.jbpm.ui.util.ProcessDeployer.deploy(Unknown Source)
at org.jbpm.ui.editor.form.deployment.DeploymentForm$1.widgetSelected(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
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 org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
--
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