Skip to content

Regression

jakartaeetck-run / jms_servlet / com.sun.ts.tests.jms.core20.jmsproducerqueuetests.Client.msgHdrJMSDeliveryTimeTest_from_servlet (from jms_servlet)

Failing for the past 1 build (Since Aborted #5 )
Took 0 ms.

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 07:13:12 UTC 2021
#-----testdescription-----
$file=/root/jakartaeetck/src/com/sun/ts/tests/jms/core20/jmsproducerqueuetests/Client.java
$root=/root/jakartaeetck/src
assertion_ids=JMS\:JAVADOC\:875  Gets the message's delivery time value. When a message is sent, the JMSDeliveryTime header field is left unassigned. After completion of the send or publish method, it holds the delivery time of the message. This is the the difference, measured in milliseconds, between the delivery time and midnight, January 1, 1970 UTC. A message's delivery time is the earliest time when a JMS provider may deliver the message to a consumer. The provider must not deliver messages before the delivery time has been reached.\nJMS\:JAVADOC\:1257  Sets the minimum length of time in milliseconds that must elapse after a message is sent before the JMS provider may deliver the message to a consumer. For transacted sends, this time starts when the client sends the message, not when the transaction is committed. deliveryDelay is set to zero by default.\nJMS\:SPEC\:246  How Message Header Values Are Set\nJMS\:SPEC\:246.11  Header Field JMSDeliveryTime Set By Provider\nJMS\:SPEC\:256  When a message is sent, its delivery time is calculated as the sum of the delivery delay value specified on the send method and the current GMT value. On return from the send method, the message's JMSDeliveryTime header field contains this value. When a message is received its JMSDeliveryTime header field contains this same value. A message's delivery time is the earliest time when a provider may make the message visible on the target destination and available for delivery to consumers. Clients must not receive messages before the delivery time is reached.\nJMS\:SPEC\:261  A client can specify a delivery delay value in milliseconds for each message it sends. This value defines a message delivery time which is the sum of the message's delivery delay and the GMT it is sent (for transacted sends, this is the time the client sends the message, not the time the transaction is committed). A message's delivery time is the earliest time when a JMS provider may make the message visible on the target destination and available for delivery to consumers. The provider must not deliver messages before the delivery time has been reached. For more information on message delivery delay, see Section 3.4.13 "JMSDeliveryTime".
classname=com.sun.ts.tests.jms.core20.jmsproducerqueuetests.Client
direction=forward
finder=cts
id=msgHdrJMSDeliveryTimeTest_from_servlet
keywords=all jms javaee jms_web_profile javaee_web_profile_optional msgHdrJMSDeliveryTimeTest servlet_vehicle forward
service_eetest=yes
testName=msgHdrJMSDeliveryTimeTest
testProps=\ jms_timeout  user  password  platform.mode
test_directory=com/sun/ts/tests/jms/core20/jmsproducerqueuetests

#-----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/core20/jmsproducerqueuetests/Client.java\#msgHdrJMSDeliveryTimeTest_from_servlet
end=Wed Oct 13 07\:13\:12 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 07\:13\:12 UTC 2021
test=com/sun/ts/tests/jms/core20/jmsproducerqueuetests/Client.java\#msgHdrJMSDeliveryTimeTest_from_servlet
timeoutSeconds=1200
totalTime=16
work=/root/jakartaeetck-work/jms/com/sun/ts/tests/jms/core20/jmsproducerqueuetests

#section:script_messages
----------messages:(0/0)----------

#section:Deployment
----------messages:(0/0)----------
----------log:(39/3357)----------
Undeploying apps...
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
Search for s1as runtime files match:`jmsproducerqueuetests_ejb_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmsproducerqueuetests/jmsproducerqueuetests_ejb_vehicle_client.jar.sun-application-client.xml
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmsproducerqueuetests/jmsproducerqueuetests_ejb_vehicle_ejb.jar.sun-ejb-jar.xml
Search for s1as runtime files match:`jmsproducerqueuetests_jsp_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmsproducerqueuetests/jmsproducerqueuetests_jsp_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`jmsproducerqueuetests_servlet_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmsproducerqueuetests/jmsproducerqueuetests_servlet_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`jmsproducerqueuetests_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmsproducerqueuetests/jmsproducerqueuetests_appclient_vehicle_client.jar.sun-application-client.xml
Deploying apps for forward rebuildable...
Search for s1as runtime files match:`jmsproducerqueuetests_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../tmp/jmsproducerqueuetests_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/core20/jmsproducerqueuetests failed!
harness.executeMode is set to "0"
keywords (to be passed to tests) set to:  servlet_vehicle
An error ocurred during deployment of apps in this directory:  /root/jakartaeetck/bin/xml/../../src/com/sun/ts/tests/jms/core20/jmsproducerqueuetests.  Thus, all other tests in this directory will fail with the same error.
harness.executeMode is set to "0"
keywords (to be passed to tests) set to:  servlet_vehicle
An error ocurred during deployment of apps in this directory:  /root/jakartaeetck/bin/xml/../../src/com/sun/ts/tests/jms/core20/jmsproducerqueuetests.  Thus, all other tests in this directory will fail with the same error.
harness.executeMode is set to "0"
keywords (to be passed to tests) set to:  servlet_vehicle
An error ocurred during deployment of apps in this directory:  /root/jakartaeetck/bin/xml/../../src/com/sun/ts/tests/jms/core20/jmsproducerqueuetests.  Thus, all other tests in this directory will fail with the same error.
harness.executeMode is set to "0"
keywords (to be passed to tests) set to:  servlet_vehicle
An error ocurred during deployment of apps in this directory:  /root/jakartaeetck/bin/xml/../../src/com/sun/ts/tests/jms/core20/jmsproducerqueuetests.  Thus, all other tests in this directory will fail with the same error.
harness.executeMode is set to "0"
keywords (to be passed to tests) set to:  servlet_vehicle
An error ocurred during deployment of apps in this directory:  /root/jakartaeetck/bin/xml/../../src/com/sun/ts/tests/jms/core20/jmsproducerqueuetests.  Thus, all other tests in this directory will fail with the same error.
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.