![[Jenkins]](/jakartaee-tck/static/46529f7b/images/svgs/logo.svg){kind=logo}
Regression
jakartaeetck-run / jms_servlet / com.sun.ts.tests.jms.core20.jmscontexttopictests.Client.verifyClientIDOnAdminConfiguredIDTest_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 07:05:03 UTC 2021
#-----testdescription-----
$file=/root/jakartaeetck/src/com/sun/ts/tests/jms/core20/jmscontexttopictests/Client.java
$root=/root/jakartaeetck/src
assertion_ids=JMS\:JAVADOC\:970 Gets the client identifier for the JMSContext's connection. This value is specific to the JMS provider. It is either preconfigured by an administrator in a ConnectionFactory object or assigned dynamically by the application by calling the setClientID method.\nJMS\:JAVADOC\:1040 Sets the client identifier for the JMSContext's connection. The preferred way to assign a JMS client's client identifier is for it to be configured in a client-specific ConnectionFactory object and transparently assigned to the Connection object it creates. Alternatively, a client can set the client identifier for the MessageContext's connection using a provider-specific value. The facility to set its client identifier explicitly is not a mechanism for overriding the identifier that has been administratively configured. It is provided for the case where no administratively specified identifier exists. If one does exist, an attempt to change it by setting it must throw an IllegalStateRuntimeException. If a client sets the client identifier explicitly, it must do so immediately after it creates the JMSContext and before any other action on the JMSContext is taken. After this point, setting the client identifier is a programming error that should throw an IllegalStateRuntimeException. The purpose of the client identifier is to associate the JMSContext's connection and its objects with a state maintained on behalf of the client by a provider. The only such state identified by the JMS API is that required to support durable subscriptions. If another connection with the same clientID is already running when this method is called, the JMS provider should detect the duplicate ID and throw an InvalidClientIDException. This method must not be used in a Java EE web or EJB application. Doing so may cause a JMSRuntimeException to be thrown though this is not guaranteed. This method must not be used if the JMSContext is container-managed (injected). Doing so will cause a IllegalStateRuntimeException to be thrown.\nJMS\:SPEC\:91 Connection objects support concurrent use.\nJMS\:SPEC\:173 InvalidClientIDException\: This exception must be thrown when a client attempts to set a connection's client identifier to a value that is rejected by a provider.\nJMS\:SPEC\:198 If a client explicitly does the set(the client identifier) it must do this immediately after creating the connection and before any other action on the connection is taken.\nJMS\:SPEC\:264 JMS applications which run in the Java EE web or EJB container are subject to a number of restrictions in the way the JMS API may be used. These restrictions are necessary for the following reasons\:\n1) In a Java EE web or EJB container, a JMS provider operates as a transactional resource manager which must participate in JTA transactions as defined in the Java EE platform specification. This overrides the behaviour of JMS sessions as defined elsewhere in the JMS specification. For more details see section 12.3 "Behaviour of JMS sessions in the Java EE web or EJB container". \n2) The Java EE web or EJB containers need to be able to manage the threads used to run applications.\n3) The Java EE web and EJB containers perform connection management which may include the pooling of JMS connections. \nThe restrictions described in this section do not apply to the Java EE application client container.\nApplications running in the Java EE web and EJB containers must not attempt to create more than one active (not closed) Session object per connection.\nJMS\:SPEC\:264.5 The following methods may interfere with the container's management of connections and must not be used by applications running in the Java EE web or EJB container\:\n1) jakarta.jms.Connection method setClientID \n2) jakarta.jms.Connection method stop\n3) jakarta.jms.Connection method setExceptionListener \n4) jakarta.jms.JMSContext method setClientID\n5) jakarta.jms.JMSContext method stop \n6) jakarta.jms.JMSContext method setExceptionListener\nApplications which need to use a specific client identifier must set it on the connection factory, as described in section 6.1.2 "Client Identifier" \nAll the methods listed in this section may throw a jakarta.jms.JMSException (if allowed by the method) or a jakarta.jms.JMSRuntimeException (if not) when called by an application running in the Java EE web or EJB container. This is recommended but not required.
classname=com.sun.ts.tests.jms.core20.jmscontexttopictests.Client
direction=forward
finder=cts
id=verifyClientIDOnAdminConfiguredIDTest_from_servlet
keywords=all jms javaee jms_web_profile javaee_web_profile_optional verifyClientIDOnAdminConfiguredIDTest servlet_vehicle forward
service_eetest=yes
testName=verifyClientIDOnAdminConfiguredIDTest
testProps=\ jms_timeout user password platform.mode
test_directory=com/sun/ts/tests/jms/core20/jmscontexttopictests
#-----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/jmscontexttopictests/Client.java\#verifyClientIDOnAdminConfiguredIDTest_from_servlet
end=Wed Oct 13 07\:05\:03 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\:05\:03 UTC 2021
test=com/sun/ts/tests/jms/core20/jmscontexttopictests/Client.java\#verifyClientIDOnAdminConfiguredIDTest_from_servlet
timeoutSeconds=1200
totalTime=16
work=/root/jakartaeetck-work/jms/com/sun/ts/tests/jms/core20/jmscontexttopictests
#section:script_messages
----------messages:(0/0)----------
#section:Deployment
----------messages:(0/0)----------
----------log:(93/8987)----------
Undeploying apps...
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
AutoDeployment.isDeployed()
Search for s1as runtime files match:`jmscontexttopictests_ejb_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmscontexttopictests/jmscontexttopictests_ejb_vehicle_client.jar.sun-application-client.xml
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmscontexttopictests/jmscontexttopictests_ejb_vehicle_ejb.jar.sun-ejb-jar.xml
Search for s1as runtime files match:`jmscontexttopictests_jsp_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmscontexttopictests/jmscontexttopictests_jsp_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`jmscontexttopictests_servlet_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmscontexttopictests/jmscontexttopictests_servlet_vehicle_web.war.sun-web.xml
Search for s1as runtime files match:`jmscontexttopictests_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jms/core20/jmscontexttopictests/jmscontexttopictests_appclient_vehicle_client.jar.sun-application-client.xml
Deploying apps for forward rebuildable...
Search for s1as runtime files match:`jmscontexttopictests_appclient_vehicle.ear`
Valid runtime files after sweep:
/root/jakartaeetck/bin/xml/../../tmp/jmscontexttopictests_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/jmscontexttopictests 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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/jmscontexttopictests. 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.