Skip to content
[Jenkins]Jenkins
log in

Regression

jakartaeetck-run / jms_servlet / com.sun.ts.tests.jms.core.topicMsgProperties.TopicPropertyTests.msgPropertiesTopicTest_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:24:17 UTC 2021
#-----testdescription-----
$file=/root/jakartaeetck/src/com/sun/ts/tests/jms/core/topicMsgProperties/TopicPropertyTests.java
$root=/root/jakartaeetck/src
assertion_ids=JMS\:JAVADOC\:387  Clears a message's properties. The message's header fields and body are not cleared.\nJMS\:JAVADOC\:391  Returns the value of the boolean property with the specified name.\nJMS\:JAVADOC\:393  Returns the value of the byte property with the specified name.\nJMS\:JAVADOC\:395  Returns the value of the short property with the specified name.\nJMS\:JAVADOC\:397  Returns the value of the int property with the specified name.\nJMS\:JAVADOC\:399  Returns the value of the long property with the specified name.\nJMS\:JAVADOC\:401  Returns the value of the float property with the specified name.\nJMS\:JAVADOC\:403  Returns the value of the double property with the specified name.\nJMS\:JAVADOC\:405  Returns the value of the String property with the specified name.\nJMS\:JAVADOC\:407  Returns the value of the Java object property with the specified name. This method can be used to return, in objectified format, an object that has been stored as a property in the message with the equivalent setObjectProperty method call, or its equivalent primitive settypeProperty method.\nJMS\:JAVADOC\:409  Returns an Enumeration of all the property names. Note that JMS standard header fields are not considered properties and are not returned in this enumeration.\nJMS\:JAVADOC\:411  Sets a boolean property value with the specified name into the message.\nJMS\:JAVADOC\:413  Sets a byte property value with the specified name into the message.\nJMS\:JAVADOC\:415  Sets a short property value with the specified name into the message.\nJMS\:JAVADOC\:417  Sets an int property value with the specified name into the message.\nJMS\:JAVADOC\:419  Sets a long property value with the specified name into the message.\nJMS\:JAVADOC\:421  Sets a float property value with the specified name into the message.\nJMS\:JAVADOC\:423  Sets a double property value with the specified name into the message.\nJMS\:JAVADOC\:425  Sets a String property value with the specified name into the message.\nJMS\:JAVADOC\:427  Sets a Java object property value with the specified name into the message. Note that this method works only for the objectified primitive object types (Integer, Double, Long ...) and String objects.\nJMS\:JAVADOC\:500  Gets an enumeration of the JMSX property names.\nJMS\:JAVADOC\:516  Gets the metadata for this connection.\nJMS\:JAVADOC\:776  if properties are read-only\nJMS\:JAVADOC\:778  if properties are read-only\nJMS\:JAVADOC\:780  if properties are read-only\nJMS\:JAVADOC\:782  if properties are read-only\nJMS\:JAVADOC\:784  if properties are read-only\nJMS\:JAVADOC\:786  if properties are read-only\nJMS\:JAVADOC\:788  if properties are read-only\nJMS\:JAVADOC\:790  if properties are read-only\nJMS\:JAVADOC\:792  if the object is invalid\nJMS\:JAVADOC\:793  if properties are read-only\nJMS\:SPEC\:10  A null value is returned (by the getObjectProperty method) if a property by the specified name does not exist.\nJMS\:SPEC\:19  Property values are set prior to sending a message.\nJMS\:SPEC\:20  Property Values\nJMS\:SPEC\:20.1  Property values can be boolean\nJMS\:SPEC\:20.2  Property values can be byte\nJMS\:SPEC\:20.3  Property values can be short\nJMS\:SPEC\:20.4  Property values can be int\nJMS\:SPEC\:20.5  Property values can be long\nJMS\:SPEC\:20.6  Property values can be float\nJMS\:SPEC\:20.7  Property values can be double\nJMS\:SPEC\:20.8  Property values can be String\nJMS\:SPEC\:21  When a client receives a message, its properties are in read-only mode. If a client attempts to set properties at this point, a MessageNotWriteableException is thrown.\nJMS\:SPEC\:23  The String to numeric conversions must throw the java.lang.NumberFormatException if the numeric's valueOf() method does not accept the String value as a valid representation.\nJMS\:SPEC\:24  Attempting to read a null value as a Java primitive type must be treated as calling the primitive's corresponding valueOf(String) conversion method with a null value.\nJMS\:SPEC\:25  The setObjectProperty method accepts values of Boolean, Byte, Short, Integer, Long, Float, Double and String. An attempt to use any other class must throw a JMS MessageFormatException.\nJMS\:SPEC\:26  The getObjectProperty method only returns values of null, Boolean, Byte, Short, Integer, Long, Float, Double and String.\nJMS\:SPEC\:27  To iterate through a message's property values, use getPropertyNames to retrieve a property name enumeration and then use the various property get methods to retrieve their values.\nJMS\:SPEC\:28  A message's properties are deleted by the clearProperties method. This leaves the message with an empty set of properties. New property entries can then be both created and read.\nJMS\:SPEC\:29  Clearing a message's property entries does not clear the value of its body.\nJMS\:SPEC\:31  The Enumeration ConnectionMetaData.getJMSXPropertyNames() method returns the names of the JMSX properties supported by a connection.\nJMS\:SPEC\:32  JMSXGroupID and JMSXGroupSeq are standard properties clients should use if they want to group messages. All providers must support them.\nJMS\:SPEC\:34  JMS Defined Properties\nJMS\:SPEC\:34.4  JMSX property JMSXGroupID set by client with value type String\nJMS\:SPEC\:34.5  JMSX property JMSXGroupSeq set by client with value type int\nJMS\:SPEC\:70  When a message is received, its header field values can be changed;\nJMS\:SPEC\:71  A consumer can modify a received message after calling either the clearBody or clearProperties method to make the body or properties writable. If the consumer modifies a received message, and the message is subsequently redelivered, the redelivered message must be the original, unmodified message (except for headers and properties modified by the JMS provider as a result of the redelivery, such as the JMSRedelivered header and the JMSXDeliveryCount property).
classname=com.sun.ts.tests.jms.core.topicMsgProperties.TopicPropertyTests
direction=forward
finder=cts
id=msgPropertiesTopicTest_from_servlet
keywords=all jms javaee jms_web_profile javaee_web_profile_optional msgPropertiesTopicTest servlet_vehicle forward
service_eetest=yes
testName=msgPropertiesTopicTest
testProps=\ jms_timeout  user  password  platform.mode
test_directory=com/sun/ts/tests/jms/core/topicMsgProperties

#-----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/topicMsgProperties/TopicPropertyTests.java\#msgPropertiesTopicTest_from_servlet
end=Wed Oct 13 06\:24\:17 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\:24\:17 UTC 2021
test=com/sun/ts/tests/jms/core/topicMsgProperties/TopicPropertyTests.java\#msgPropertiesTopicTest_from_servlet
timeoutSeconds=1200
totalTime=16
work=/root/jakartaeetck-work/jms/com/sun/ts/tests/jms/core/topicMsgProperties

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

#section:Deployment
----------messages:(0/0)----------
----------log:(30/2339)----------
Undeploying apps...
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
Search for s1as runtime files match:`topicMsgProperties_ejb_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/topicMsgProperties/topicMsgProperties_ejb_vehicle_client.jar.sun-application-client.xml
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/topicMsgProperties/topicMsgProperties_ejb_vehicle_ejb.jar.sun-ejb-jar.xml
Search for s1as runtime files match:`topicMsgProperties_jsp_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/topicMsgProperties/topicMsgProperties_jsp_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`topicMsgProperties_servlet_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/topicMsgProperties/topicMsgProperties_servlet_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`topicMsgProperties_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/topicMsgProperties/topicMsgProperties_appclient_vehicle_client.jar.sun-application-client.xml
Deploying apps for forward rebuildable...
Search for s1as runtime files match:`topicMsgProperties_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../tmp/topicMsgProperties_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/topicMsgProperties 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/core/topicMsgProperties.  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/core/topicMsgProperties.  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.