![[Jenkins]](/jakartaee-tck/static/46529f7b/images/svgs/logo.svg){kind=logo}
Regression
jakartaeetck-run / jms_servlet / com.sun.ts.tests.jms.core.sessiontests.SessionTests.ackTests_from_servlet (from jms_servlet)
Failing for the past 1 build
(Since Aborted
)
Error Message
test result: Failed. An error occurred during the Deployment phase for tests in this directory.
Stacktrace
test result: Failed. An error occurred during the Deployment phase for tests in this directory.
Standard Output
#Test Results (version 2)
#Wed Oct 13 05:43:33 UTC 2021
#-----testdescription-----
$file=/root/jakartaeetck/src/com/sun/ts/tests/jms/core/sessiontests/SessionTests.java
$root=/root/jakartaeetck/src
assertion_ids=JMS\:JAVADOC\:227 Returns the acknowledgement mode of the session. The acknowledgement mode is set at the time that the session is created. If the session is transacted, the acknowledgement mode is ignored.\nJMS\:JAVADOC\:242 Creates a MessageProducer to send messages to the specified destination. A client uses a MessageProducer object to send messages to a destination. Since Queue and Topic both inherit from Destination, they can be used in the destination parameter to create a MessageProducer object.\nJMS\:JAVADOC\:502 Creates a connection with the default user identity. The connection is created in stopped mode. No messages will be delivered until the Connection.start method is explicitly called.\nJMS\:JAVADOC\:504 Creates a connection with the specified user identity. The connection is created in stopped mode. No messages will be delivered until the Connection.start method is explicitly called.\nJMS\:JAVADOC\:510 Creates a Session object, specifying transacted and acknowledgeMode. This method has been superseded by the method createSession(int sessionMode) which specifies the same information using a single argument, and by the method createSession() which is for use in a Java EE JTA transaction. Applications should consider using those methods instead of this one. The effect of setting the transacted and acknowledgeMode arguments depends on whether this method is called in a Java SE environment, in the Java EE application client container, or in the Java EE web or EJB container. If this method is called in the Java EE web or EJB container then the effect of setting the transacted} and acknowledgeMode arguments also depends on whether or not there is an active JTA transaction in progress. In a Java SE environment or in the Java EE application client container\: If transacted is set to true then the session will use a local transaction which may subsequently be committed or rolled back by calling the session's commit or rollback methods. The argument acknowledgeMode is ignored. If transacted is set to false then the session will be non-transacted. In this case the argument acknowledgeMode is used to specify how messages received by this session will be acknowledged. The permitted values are Session.CLIENT_ACKNOWLEDGE, Session.AUTO_ACKNOWLEDGE and Session.DUPS_OK_ACKNOWLEDGE. For a definition of the meaning of these acknowledgement modes see the links below. In a Java EE web or EJB container, when there is an active JTA transaction in progress\: Both arguments transacted and acknowledgeMode are ignored. The session will participate in the JTA transaction and will be committed or rolled back when that transaction is committed or rolled back, not by calling the session's commit or rollback methods. Since both arguments are ignored, developers are recommended to use createSession(), which has no arguments, instead of this method. In the Java EE web or EJB container, when there is no active JTA transaction in progress\: The argument transacted is ignored. The session will always be non-transacted, using one of the two acknowledgement modes AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE. The argument acknowledgeMode is used to specify how messages received by this session will be acknowledged. The only permitted values in this case are Session.AUTO_ACKNOWLEDGE and Session.DUPS_OK_ACKNOWLEDGE. The value Session.CLIENT_ACKNOWLEDGE may not be used. For a definition of the meaning of these acknowledgement modes see the links below. Applications running in the Java EE web and EJB containers must not attempt to create more than one active (not closed) Session object per connection. If this method is called in a Java EE web or EJB container when an active Session object already exists for this connection then a JMSException will be thrown.\nJMS\:SPEC\:195 This chapter describes the semantics of the Point-to-Point model. These semantics must be supported regardless of whether the client programmer uses the PTP domain-specific interfaces, or the common interfaces that are described in Chapter 4, JMS Common Facilities. The following table shows the interfaces that are specific to the PTP domain and the JMS common interfaces.The common interfaces are preferred for creating JMS client programs, because they are domain-independent.\nJMS\:SPEC\:196 This chapter describes the semantics of the Pub/Sub model. These semantics must be supported regardless of whether the client programmer uses the Pub/Sub domain interfaces, or the JMS common interfaces that are described in Chapter 4, JMS Common Facilities. The following table shows the interfaces that are specific to the Pub/Sub domain, and the JMS common interfaces. It is preferable to use the common interfaces when creating client programs, as they are domain-independent.
classname=com.sun.ts.tests.jms.core.sessiontests.SessionTests
direction=forward
finder=cts
id=ackTests_from_servlet
keywords=all jms javaee jms_web_profile javaee_web_profile_optional ackTests servlet_vehicle forward
service_eetest=yes
testName=ackTests
testProps=\ jms_timeout user password platform.mode
test_directory=com/sun/ts/tests/jms/core/sessiontests
#-----environment-----
EJBServer1TxInteropEnabled=true
EJBServer2TxInteropEnabled=true
deployment_host.1=${orb.host}
deployment_host.2=${orb.host.ri}
deployment_port.1=${impl.vi.port}
deployment_port.2=${impl.ri.port}
derby.dbName=derbyDB
derby.driver=org.apache.derby.jdbc.ClientDriver
derby.passwd=cts1
derby.port=1527
derby.server=${orb.host}
derby.url=jdbc\:derby\://${derby.server}\:${derby.port}/${derby.dbName};create\=true
derby.user=cts1
harness.executeMode=0
harness.log.delayseconds=1
harness.log.port=2000
harness.log.traceflag=false
harness.socket.retry.count=10
harness.temp.directory=${ts.home}/tmp
http.server.supports.endpoint.publish=false
http.server.supports.endpoint.publish.2=false
impl.ri.port=${ri.admin.port}
impl.vi.port=${s1as.admin.port}
jakarta.persistence.jdbc.driver=${derby.driver}
jakarta.persistence.jdbc.password=${derby.passwd}
jakarta.persistence.jdbc.url=${derby.url}
jakarta.persistence.jdbc.user=${derby.user}
jakarta.persistence.provider=org.eclipse.persistence.jpa.PersistenceProvider
javaee.level=full
jms_timeout=10000
jpa.provider.implementation.specific.properties=eclipselink.logging.level\=OFF
namingServiceHost1=${orb.host}
namingServiceHost2=${orb.host.ri}
namingServicePort1=${orb.port}
namingServicePort2=${orb.port.ri}
orb.host=localhost
orb.host.ri=localhost
orb.port=3699
orb.port.ri=3701
password=j2ee
password1=${derby.passwd}
password2=${derby.passwd}
persistence.second.level.caching.supported=true
persistence.unit.name=CTS-EM
persistence.unit.name.2=JPATCK2
platform.mode=jakartaEE
porting.ts.HttpsURLConnection.class.1=com.sun.ts.lib.implementation.sun.javaee.SunRIHttpsURLConnection
porting.ts.HttpsURLConnection.class.2=com.sun.ts.lib.implementation.sun.javaee.SunRIHttpsURLConnection
porting.ts.deploy.class.1=com.sun.ts.lib.implementation.sun.javaee.glassfish.AutoDeployment
porting.ts.deploy.class.2=com.sun.ts.lib.implementation.sun.javaee.glassfish.AutoDeploymentSeparateVM
porting.ts.jms.class.1=com.sun.ts.lib.implementation.sun.javaee.SunRIJMSAdmin
porting.ts.jms.class.2=com.sun.ts.lib.implementation.sun.javaee.SunRIJMSAdmin
porting.ts.login.class.1=com.sun.ts.lib.implementation.sun.javaee.GlassFishLoginContext
porting.ts.login.class.2=com.sun.ts.lib.implementation.sun.javaee.GlassFishLoginContext
porting.ts.url.class.1=com.sun.ts.lib.implementation.sun.common.SunRIURL
porting.ts.url.class.2=com.sun.ts.lib.implementation.sun.common.SunRIURL
ri.admin.port=5858
s1as.admin.port=4848
securedWebServicePort=1044
securedWebServicePort.2=1045
ts.home=/root/jakartaeetck/bin/xml/../..
user=j2ee
user1=${derby.user}
user2=${derby.user}
variable.mapper=com.sun.el.lang.VariableMapperImpl
vi.admin.passwd=
vi.admin.user=admin
webServerHost=${orb.host}
webServerHost.2=${orb.host.ri}
webServerPort=8001
webServerPort.2=8002
wsdlRepository1=${harness.temp.directory}/wsdlRepository1
wsdlRepository2=${harness.temp.directory}/wsdlRepository2
#-----testresult-----
description=file\:/root/jakartaeetck/src/com/sun/ts/tests/jms/core/sessiontests/SessionTests.java\#ackTests_from_servlet
end=Wed Oct 13 05\:43\:33 UTC 2021
environment=ts_unix
execStatus=Failed. An error occurred during the Deployment phase for tests in this directory.
harnessLoaderMode=Classpath Loader
harnessVariety=Full Bundle
javatestOS=Linux 5.12.7-300.fc34.x86_64 (amd64)
javatestVersion=5.0
script=com.sun.ts.lib.harness.TSScript
sections=script_messages Deployment TestRun
start=Wed Oct 13 05\:43\:33 UTC 2021
test=com/sun/ts/tests/jms/core/sessiontests/SessionTests.java\#ackTests_from_servlet
timeoutSeconds=1200
totalTime=18
work=/root/jakartaeetck-work/jms/com/sun/ts/tests/jms/core/sessiontests
#section:script_messages
----------messages:(0/0)----------
#section:Deployment
----------messages:(0/0)----------
----------log:(24/1617)----------
Undeploying apps...
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
Search for s1as runtime files match:`sessiontests_ejb_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/sessiontests/sessiontests_ejb_vehicle_client.jar.sun-application-client.xml
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/sessiontests/sessiontests_ejb_vehicle_ejb.jar.sun-ejb-jar.xml
Search for s1as runtime files match:`sessiontests_jsp_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/sessiontests/sessiontests_jsp_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`sessiontests_servlet_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/sessiontests/sessiontests_servlet_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`sessiontests_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/sessiontests/sessiontests_appclient_vehicle_client.jar.sun-application-client.xml
Deploying apps for forward rebuildable...
Search for s1as runtime files match:`sessiontests_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../tmp/sessiontests_appclient_vehicle_client.jar.sun-application-client.xml
getAppNameFromApplicationXML() returning "null"
Deployment of app(s) from: /root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/sessiontests failed!
result: Passed. Deployment phase completed. However, check the output above to see if actual deployment passed or failed.
#section:TestRun
----------messages:(0/0)----------
----------log:(15/1136)----------
com.sun.ts.lib.porting.TSDeploymentException: The following error occurred while executing this line:
/root/jakartaeetck/bin/xml/impl/glassfish/deploy.xml:152: The following error occurred while executing this line:
/root/jakartaeetck/bin/xml/impl/glassfish/deploy.xml:200: Deployment timeout reached - 480 seconds.
at com.sun.ts.lib.implementation.sun.javaee.glassfish.AutoDeployment.deploy(AutoDeployment.java:227)
at com.sun.ts.lib.harness.SuiteSynchronizer.continueToDeployApps(SuiteSynchronizer.java:1104)
at com.sun.ts.lib.harness.SuiteSynchronizer.deployApps(SuiteSynchronizer.java:716)
at com.sun.ts.lib.harness.SuiteSynchronizer.doDeployment(SuiteSynchronizer.java:387)
at com.sun.ts.lib.harness.TSHarnessObserver.startingTest(TSHarnessObserver.java:367)
at com.sun.javatest.Harness$Notifier.startingTest(Harness.java:995)
at com.sun.javatest.TestRunner.notifyStartingTest(TestRunner.java:212)
at com.sun.javatest.DefaultTestRunner.runTest(DefaultTestRunner.java:167)
at com.sun.javatest.DefaultTestRunner.access$100(DefaultTestRunner.java:43)
at com.sun.javatest.DefaultTestRunner$1.run(DefaultTestRunner.java:66)
result: Not run. Test running...
test result: Failed. An error occurred during the Deployment phase for tests in this directory.