Skip to content
[Jenkins]Jenkins
log in

Regression

jakartaeetck-run / jms_servlet / com.sun.ts.tests.jms.core20.jmsconsumertests.Client.queueReceiveBodyTests_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 06:48:43 UTC 2021
#-----testdescription-----
$file=/root/jakartaeetck/src/com/sun/ts/tests/jms/core20/jmsconsumertests/Client.java
$root=/root/jakartaeetck/src
assertion_ids=JMS\:JAVADOC\:1369  Receives the next message produced for this JMSConsumer and returns its body as an object of the specified type. This method may be used to receive any type of message except for StreamMessage and Message, so long as the message has a body which is capable of being assigned to the specified type. This means that the specified class or interface must either be the same as, or a superclass or superinterface of, the class of the message body. If the message is not one of the supported types, or its body cannot be assigned to the specified type, or it has no body, then a MessageFormatRuntimeException is thrown. This method does not give access to the message headers or properties (such as the JMSRedelivered message header field or the JMSXDeliveryCount message property) and should only be used if the application has no need to access them. This call blocks indefinitely until a message is produced or until this JMSConsumer is closed. If this method is called within a transaction, the JMSConsumer retains the message until the transaction commits. The result of this method throwing a MessageFormatRuntimeException depends on the session mode\: AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE\: The JMS provider will behave as if the unsuccessful call to receiveBody had not occurred. The message will be delivered again before any subsequent messages. This is not considered to be redelivery and does not cause the JMSRedelivered message header field to be set or the JMSXDeliveryCount message property to be incremented. CLIENT_ACKNOWLEDGE\: The JMS provider will behave as if the call to receiveBody had been successful and will not deliver the message again. As with any message that is delivered with a session mode of CLIENT_ACKNOWLEDGE, the message will not be acknowledged until acknowledge is called on the JMSContext. If an application wishes to have the failed message redelivered, it must call recover on the JMSContext. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented. Transacted session\: The JMS provider will behave as if the call to receiveBody had been successful and will not deliver the message again. As with any message that is delivered in a transacted session, the transaction will remain uncommitted until the transaction is committed or rolled back by the application. If an application wishes to have the failed message redelivered, it must roll back the transaction. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented.\nJMS\:JAVADOC\:1372  Receives the next message produced for this JMSConsumer that arrives within the specified timeout period and returns its body as an object of the specified type. This method may be used to receive any type of message except for StreamMessage and Message, so long as the message has a body which is capable of being assigned to the specified type. This means that the specified class or interface must either be the same as, or a superclass or superinterface of, the class of the message body. If the message is not one of the supported types, or its body cannot be assigned to the specified type, or it has no body, then a MessageFormatRuntimeException is thrown. This method does not give access to the message headers or properties (such as the JMSRedelivered message header field or the JMSXDeliveryCount message property) and should only be used if the application has no need to access them. This call blocks until a message arrives, the timeout expires, or this JMSConsumer is closed. A timeout of zero never expires, and the call blocks indefinitely. If this method is called within a transaction, the JMSConsumer retains the message until the transaction commits. The result of this method throwing a MessageFormatRuntimeException depends on the session mode\: AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE\: The JMS provider will behave as if the unsuccessful call to receiveBody had not occurred. The message will be delivered again before any subsequent messages. This is not considered to be redelivery and does not cause the JMSRedelivered message header field to be set or the JMSXDeliveryCount message property to be incremented. CLIENT_ACKNOWLEDGE\: The JMS provider will behave as if the call to receiveBody had been successful and will not deliver the message again. As with any message that is delivered with a session mode of CLIENT_ACKNOWLEDGE, the message will not be acknowledged until acknowledge is called on the JMSContext. If an application wishes to have the failed message redelivered, it must call recover on the JMSContext. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented. Transacted session\: The JMS provider will behave as if the call to receiveBody had been successful and will not deliver the message again. As with any message that is delivered in a transacted session, the transaction will remain uncommitted until the transaction is committed or rolled back by the application. If an application wishes to have the failed message redelivered, it must roll back the transaction. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented.\nJMS\:JAVADOC\:1375  Receives the next message produced for this JMSConsumer if one is immediately available and returns its body as an object of the specified type. This method may be used to receive any type of message except for StreamMessage and Message, so long as the message has a body which is capable of being assigned to the specified type. This means that the specified class or interface must either be the same as, or a superclass or superinterface of, the class of the message body. If the message is not one of the supported types, or its body cannot be assigned to the specified type, or it has no body, then a MessageFormatRuntimeException is thrown. This method does not give access to the message headers or properties (such as the JMSRedelivered message header field or the JMSXDeliveryCount message property) and should only be used if the application has no need to access them. If a message is not immediately available null is returned. If this method is called within a transaction, the JMSConsumer retains the message until the transaction commits. The result of this method throwing a MessageFormatRuntimeException depends on the session mode\: AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE\: The JMS provider will behave as if the unsuccessful call to receiveBodyNoWait had not occurred. The message will be delivered again before any subsequent messages. This is not considered to be redelivery and does not cause the JMSRedelivered message header field to be set or the JMSXDeliveryCount message property to be incremented. CLIENT_ACKNOWLEDGE\: The JMS provider will behave as if the call to receiveBodyNoWait had been successful and will not deliver the message again. As with any message that is delivered with a session mode of CLIENT_ACKNOWLEDGE, the message will not be acknowledged until acknowledge is called on the JMSContext. If an application wishes to have the failed message redelivered, it must call recover on the JMSContext. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented. Transacted session\: The JMS provider will behave as if the call to receiveBodyNoWait had been successful and will not deliver the message again. As with any message that is delivered in a transacted session, the transaction will remain uncommitted until the transaction is committed or rolled back by the application. If an application wishes to have the failed message redelivered, it must roll back the transaction. The redelivered message's JMSRedelivered message header field will be set and its JMSXDeliveryCount message property will be incremented.
classname=com.sun.ts.tests.jms.core20.jmsconsumertests.Client
direction=forward
finder=cts
id=queueReceiveBodyTests_from_servlet
keywords=all jms javaee jms_web_profile javaee_web_profile_optional queueReceiveBodyTests servlet_vehicle forward
service_eetest=yes
testName=queueReceiveBodyTests
testProps=\ jms_timeout  user  password  platform.mode
test_directory=com/sun/ts/tests/jms/core20/jmsconsumertests

#-----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/jmsconsumertests/Client.java\#queueReceiveBodyTests_from_servlet
end=Wed Oct 13 06\:48\:43 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 06\:48\:43 UTC 2021
test=com/sun/ts/tests/jms/core20/jmsconsumertests/Client.java\#queueReceiveBodyTests_from_servlet
timeoutSeconds=1200
totalTime=32
work=/root/jakartaeetck-work/jms/com/sun/ts/tests/jms/core20/jmsconsumertests

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

#section:Deployment
----------messages:(0/0)----------
----------log:(33/2627)----------
Undeploying apps...
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
Search for s1as runtime files match:`jmsconsumertests_ejb_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmsconsumertests/jmsconsumertests_ejb_vehicle_client.jar.sun-application-client.xml
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmsconsumertests/jmsconsumertests_ejb_vehicle_ejb.jar.sun-ejb-jar.xml
Search for s1as runtime files match:`jmsconsumertests_jsp_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmsconsumertests/jmsconsumertests_jsp_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`jmsconsumertests_servlet_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmsconsumertests/jmsconsumertests_servlet_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`jmsconsumertests_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmsconsumertests/jmsconsumertests_appclient_vehicle_client.jar.sun-application-client.xml
Deploying apps for forward rebuildable...
Search for s1as runtime files match:`jmsconsumertests_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../tmp/jmsconsumertests_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/jmsconsumertests 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/jmsconsumertests.  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/jmsconsumertests.  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/jmsconsumertests.  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.