Skip to content
[Jenkins]Jenkins
log in

Regression

jakartaeetck-run / jms_servlet / com.sun.ts.tests.jms.core.topictests.TopicTests.durableSubscriberChangeSelectorTest_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:32:25 UTC 2021
#-----testdescription-----
$file=/root/jakartaeetck/src/com/sun/ts/tests/jms/core/topictests/TopicTests.java
$root=/root/jakartaeetck/src
assertion_ids=JMS\:JAVADOC\:99  Publishes a message to the topic. Uses the TopicPublisher's default delivery mode, priority, and time to live.\nJMS\:JAVADOC\:122  Gets the string containing this message's data. The default value is null.\nJMS\:JAVADOC\:256  Creates an unshared durable subscription on the specified topic (if one does not already exist), specifying a message selector and the noLocal parameter, and creates a consumer on that durable subscription. A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The JMS provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired. A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe method. This method may only be used with unshared durable subscriptions. Any durable subscription created using this method will be unshared. This means that only one active (i.e. not closed) consumer on the subscription may exist at a time. The term "consumer" here means a TopicSubscriber, MessageConsumer or JMSConsumer object in any client. An unshared durable subscription is identified by a name specified by the client and by the client identifier, which must be set. An application which subsequently wishes to create a consumer on that unshared durable subscription must use the same client identifier. If an unshared durable subscription already exists with the same name and client identifier, and the same topic, message selector and noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this method creates a TopicSubscriber on the existing durable subscription. If an unshared durable subscription already exists with the same name and client identifier, and there is a consumer already active (i.e. not closed) on the durable subscription, then a JMSException will be thrown. If an unshared durable subscription already exists with the same name and client identifier but a different topic, message selector or noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a new one. If noLocal is set to true then any messages published to the topic using this session's connection, or any other connection with the same client identifier, will not be added to the durable subscription. A shared durable subscription and an unshared durable subscription may not have the same name and client identifier. If a shared durable subscription already exists with the same name and client identifier then a JMSException is thrown. There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId. Such subscriptions would be completely separate. This method is identical to the corresponding createDurableConsumer method except that it returns a TopicSubscriber rather than a MessageConsumer to represent the consumer.\nJMS\:JAVADOC\:334  Receives the next message that arrives within the specified timeout interval. This call blocks until a message arrives, the timeout expires, or this message consumer is closed. A timeout of zero never expires, and the call blocks indefinitely.\nJMS\:SPEC\:164  A durable subscription is used by a client which needs to receive all the messages published on a topic, including the ones published when there is no MessageConsumer or TopicSubscriber associated with it. The JMS provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a MessageConsumer or TopicSubscriber on the durable subscription or until they have expired.\nA durable subscription is created, and a MessageConsumer created on that durable subscription, using the createDurableConsumer methods on a Session or TopicSession. The same methods may be used to create a MessageConsumer on an existing durable subscription. There are also createDurableSubscriber methods which have the same behavior as createDurableConsumer but which return a TopicSubscriber. These methods are deprecated since the object they return is deprecated. A durable subscription which has a MessageConsumer or TopicSubsc riber associated with it is described as being active. A durable subscription which has no MessageConsumer or TopicSubscriber associated with it is described as being inactive. Only one session at a time can have a MessageConsumer or TopicSubscriber for a particular durable subscription. A durable subscription is identified by a name specified by the client and by the client identifier if set. If the client identifier was set when the durable subscription was first created then a client which subsequently wishes to create a MessageConsumer or TopicSubscriber on that durable subscription must use the same client identifier.\nJMS\:SPEC\:165  A client can change an existing durable subscription by calling one of the createDurableConsumer methods with the same name and client identifier (if used), and a new topic and/or message selector. Changing a durable subscriber is equivalent to unsubscribing (deleting) the old one and creating a new one.
classname=com.sun.ts.tests.jms.core.topictests.TopicTests
direction=forward
finder=cts
id=durableSubscriberChangeSelectorTest_from_servlet
keywords=all jms javaee jms_web_profile javaee_web_profile_optional durableSubscriberChangeSelectorTest servlet_vehicle forward
service_eetest=yes
testName=durableSubscriberChangeSelectorTest
testProps=\ jms_timeout user  password  platform.mode
test_directory=com/sun/ts/tests/jms/core/topictests

#-----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/topictests/TopicTests.java\#durableSubscriberChangeSelectorTest_from_servlet
end=Wed Oct 13 06\:32\:25 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\:32\:25 UTC 2021
test=com/sun/ts/tests/jms/core/topictests/TopicTests.java\#durableSubscriberChangeSelectorTest_from_servlet
timeoutSeconds=1200
totalTime=15
work=/root/jakartaeetck-work/jms/com/sun/ts/tests/jms/core/topictests

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

#section:Deployment
----------messages:(0/0)----------
----------log:(27/1885)----------
Undeploying apps...
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
Search for s1as runtime files match:`topictests_ejb_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/topictests/topictests_ejb_vehicle_client.jar.sun-application-client.xml
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/topictests/topictests_ejb_vehicle_ejb.jar.sun-ejb-jar.xml
Search for s1as runtime files match:`topictests_jsp_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/topictests/topictests_jsp_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`topictests_servlet_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/topictests/topictests_servlet_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`topictests_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core/topictests/topictests_appclient_vehicle_client.jar.sun-application-client.xml
Deploying apps for forward rebuildable...
Search for s1as runtime files match:`topictests_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../tmp/topictests_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/topictests 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/topictests.  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.