You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Jean-Louis Monteiro (Jira)" <ji...@apache.org> on 2021/04/26 14:43:01 UTC

[jira] [Assigned] (TOMEE-3217) servlet.ee.spec.security.permissiondd ValidateLocalPermsInvalidNameInLib

     [ https://issues.apache.org/jira/browse/TOMEE-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Louis Monteiro reassigned TOMEE-3217:
------------------------------------------

    Assignee: Jean-Louis Monteiro

> servlet.ee.spec.security.permissiondd ValidateLocalPermsInvalidNameInLib
> ------------------------------------------------------------------------
>
>                 Key: TOMEE-3217
>                 URL: https://issues.apache.org/jira/browse/TOMEE-3217
>             Project: TomEE
>          Issue Type: Sub-task
>            Reporter: David Blevins
>            Assignee: Jean-Louis Monteiro
>            Priority: Major
>
> Follow setup instructions in TOMEE-3140.  Then run:
> {code}
> ./runtests --ee91 -c -j --web tomee-plume com.sun.ts.tests.servlet.ee.spec.security.permissiondd.Client#ValidateLocalPermsInvalidNameInLib
> {code}
> At the time this issue was filed, the test failed with the following in {{target/logs/javatest.log}}
> {code}
> 04-11-2021 21:00:47:  TRACE: ** GOT RUN METHOD!
> 04-11-2021 21:00:47:  TRACE: **runmethod=ValidateLocalPermsInvalidNameInLib
> 04-11-2021 21:00:47:  TRACE: ABOUT TO GET SETUP METHOD!
> 04-11-2021 21:00:47:  TRACE: No setupMethod annotation present
> 04-11-2021 21:00:47:  TRACE: getSetupMethod - checking for testcase specific setup method:  ValidateLocalPermsInvalidNameInLib_setup
> 04-11-2021 21:00:47:  TRACE: getSetupMethod - checking for default class specific setup method
> 04-11-2021 21:00:47:  TRACE: GOT SETUP METHOD!
> 04-11-2021 21:00:47:  TRACE: No cleanupMethod annotation present
> 04-11-2021 21:00:47:  TRACE: getCleanupMethod - checking for testcase specific cleanup method:  ValidateLocalPermsInvalidNameInLib_cleanup
> 04-11-2021 21:00:47:  TRACE: getCleanupMethod - checking for default class specific cleanup method
> 04-11-2021 21:00:47:  TRACE: GOT CLEANUP METHOD!
> 04-11-2021 21:00:47:  TRACE: ABOUT TO INVOKE SETUP METHOD!
> 04-11-2021 21:00:47:  setup(): appContextHostname = Catalina/localhost
> 04-11-2021 21:00:47:  setup(): servletAppContext = null
> 04-11-2021 21:00:47:  TRACE: INVOKED SETUP METHOD!
> 04-11-2021 21:00:47:  TRACE: ABOUT TO INVOKE EETEST RUN METHOD!
> 04-11-2021 21:00:47:  sContext = /servlet_ee_spec_securitypermissiondd/TestServlet?method.under.test=ValidateLocalPermsInvalidNameInLib
> 04-11-2021 21:00:47:  passing to servlet:  testMethod = ValidateLocalPermsInvalidNameInLib
> 04-11-2021 21:00:47:  authData : j2ee:j2ee
> 04-11-2021 21:00:47:  encoded authData : ajJlZTpqMmVl
> 04-11-2021 21:00:47:  called HttpURLConnection.connect() for url: http://localhost:55103/servlet_ee_spec_securitypermissiondd/TestServlet?method.under.test=ValidateLocalPermsInvalidNameInLib
> in TestServlet.doPost()
> in TestServlet.doTests()
> ERROR:  Security Manager is NOT enabled and must be for these tests.  If you have passed these tests while running with Security Manager enabled, you can use keywords to bypass the running of these tests when Security Manager is disabled.
> 04-11-2021 21:00:47:  Got response string of: null
> 04-11-2021 21:00:47:  ERROR:  Security Manager is NOT enabled and must be for these tests.  If you have passed these tests while running with Security Manager enabled, you can use keywords to bypass the running of these tests when Security Manager is disabled.
> 04-11-2021 21:00:47:  ValidateLocalPermsInvalidNameInLib : str = null
> ERROR:  Security Manager is NOT enabled and must be for these tests.  If you have passed these tests while running with Security Manager enabled, you can use keywords to bypass the running of these tests when Security Manager is disabled.
> 04-11-2021 21:00:47:  ERROR: ValidateLocalPermsInvalidNameInLib : FAILED
> 04-11-2021 21:00:47:  ERROR: Test case throws exception: ValidateLocalPermsInvalidNameInLib : FAILED
> 04-11-2021 21:00:47:  ERROR: Exception at:  
> 04-11-2021 21:00:47:  ERROR: com.sun.ts.lib.harness.EETest$Fault: ValidateLocalPermsInvalidNameInLib : FAILED
> 	at com.sun.ts.tests.servlet.ee.spec.security.permissiondd.Client.ValidateLocalPermsInvalidNameInLib(Client.java:555)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at com.sun.ts.lib.harness.EETest.run(EETest.java:596)
> 	at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:115)
> 	at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:486)
> 	at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:209)
> 	at com.sun.ts.lib.harness.EETest.run(EETest.java:285)
> 	at com.sun.ts.tests.servlet.ee.spec.security.permissiondd.Client.main(Client.java:69)
> 04-11-2021 21:00:48:  TRACE: SLEPT FOR:  1000
> 04-11-2021 21:00:48:  TRACE: in custom vehicle so call on EETest.
> 04-11-2021 21:00:48:  TRACE: *** in EETest.run(argv,p)
> 04-11-2021 21:00:48:  TRACE: TESTCLASS=com.sun.ts.tests.servlet.ee.spec.security.permissiondd.Client
> 04-11-2021 21:00:48:  TRACE: ** IN getRunMethod: testClass=com.sun.ts.tests.servlet.ee.spec.security.permissiondd.Client
> 04-11-2021 21:00:48:  TRACE: ** IN getRunMethod: testname=ValidateLocalPermsInvalidNameInLib
> 04-11-2021 21:00:48:  TRACE: ** GOT RUN METHOD!
> 04-11-2021 21:00:48:  TRACE: **runmethod=ValidateLocalPermsInvalidNameInLib
> 04-11-2021 21:00:48:  TRACE: ABOUT TO GET SETUP METHOD!
> 04-11-2021 21:00:48:  TRACE: No setupMethod annotation present
> 04-11-2021 21:00:48:  TRACE: getSetupMethod - checking for testcase specific setup method:  ValidateLocalPermsInvalidNameInLib_setup
> 04-11-2021 21:00:48:  TRACE: getSetupMethod - checking for default class specific setup method
> 04-11-2021 21:00:48:  TRACE: GOT SETUP METHOD!
> 04-11-2021 21:00:48:  TRACE: No cleanupMethod annotation present
> 04-11-2021 21:00:48:  TRACE: getCleanupMethod - checking for testcase specific cleanup method:  ValidateLocalPermsInvalidNameInLib_cleanup
> 04-11-2021 21:00:48:  TRACE: getCleanupMethod - checking for default class specific cleanup method
> 04-11-2021 21:00:48:  TRACE: GOT CLEANUP METHOD!
> 04-11-2021 21:00:48:  TRACE: ABOUT TO INVOKE SETUP METHOD!
> 04-11-2021 21:00:48:  setup(): appContextHostname = Catalina/localhost
> 04-11-2021 21:00:48:  setup(): servletAppContext = null
> 04-11-2021 21:00:48:  TRACE: INVOKED SETUP METHOD!
> 04-11-2021 21:00:48:  TRACE: ABOUT TO INVOKE EETEST RUN METHOD!
> 04-11-2021 21:00:48:  sContext = /servlet_ee_spec_securitypermissiondd/TestServlet?method.under.test=ValidateLocalPermsInvalidNameInLib
> 04-11-2021 21:00:48:  passing to servlet:  testMethod = ValidateLocalPermsInvalidNameInLib
> 04-11-2021 21:00:48:  authData : j2ee:j2ee
> 04-11-2021 21:00:48:  encoded authData : ajJlZTpqMmVl
> 04-11-2021 21:00:48:  called HttpURLConnection.connect() for url: http://localhost:55103/servlet_ee_spec_securitypermissiondd/TestServlet?method.under.test=ValidateLocalPermsInvalidNameInLib
> in TestServlet.doPost()
> in TestServlet.doTests()
> ERROR:  Security Manager is NOT enabled and must be for these tests.  If you have passed these tests while running with Security Manager enabled, you can use keywords to bypass the running of these tests when Security Manager is disabled.
> 04-11-2021 21:00:48:  Got response string of: null
> 04-11-2021 21:00:48:  ERROR:  Security Manager is NOT enabled and must be for these tests.  If you have passed these tests while running with Security Manager enabled, you can use keywords to bypass the running of these tests when Security Manager is disabled.
> 04-11-2021 21:00:48:  ValidateLocalPermsInvalidNameInLib : str = null
> ERROR:  Security Manager is NOT enabled and must be for these tests.  If you have passed these tests while running with Security Manager enabled, you can use keywords to bypass the running of these tests when Security Manager is disabled.
> 04-11-2021 21:00:48:  ERROR: ValidateLocalPermsInvalidNameInLib : FAILED
> 04-11-2021 21:00:48:  ERROR: Test case throws exception: ValidateLocalPermsInvalidNameInLib : FAILED
> 04-11-2021 21:00:48:  ERROR: Exception at:  
> 04-11-2021 21:00:48:  ERROR: com.sun.ts.lib.harness.EETest$Fault: ValidateLocalPermsInvalidNameInLib : FAILED
> 	at com.sun.ts.tests.servlet.ee.spec.security.permissiondd.Client.ValidateLocalPermsInvalidNameInLib(Client.java:555)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at com.sun.ts.lib.harness.EETest.run(EETest.java:596)
> 	at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:115)
> 	at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:486)
> 	at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:209)
> 	at com.sun.ts.lib.harness.EETest.run(EETest.java:285)
> 	at com.sun.ts.tests.servlet.ee.spec.security.permissiondd.Client.main(Client.java:69)
> 04-11-2021 21:00:49:  TRACE: SLEPT FOR:  1000
> STATUS:Failed.Test case throws exception: ValidateLocalPermsInvalidNameInLib : FAILED
> Failed. Test case throws exception: ValidateLocalPermsInvalidNameInLib : FAILED
> ********************************************************************************
> Finished Test:  FAILED........com/sun/ts/tests/servlet/ee/spec/security/permissiondd/Client.java#ValidateLocalPermsInvalidNameInLib
> {code}
> For tips on debugging/fixing tests, see https://github.com/apache/tomee-tck/blob/master/DEBUGGING.adoc
> *If you have any thoughts about what the test is expecting/testing, please add them to the comments.*



--
This message was sent by Atlassian Jira
(v8.3.4#803005)