/
debug-tips.inc
66 lines (51 loc) · 3.1 KB
/
debug-tips.inc
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
///////////////////////////////////////////////////////////////////////
NOTE TO WRITERS:
The following sections should be customized for the technology.
This text was originally from the JACC TCK. Some references
to JACC have been parameterized to serve as a simple starting
point for customization. There are still many details that will
need to be changed or removed.
///////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////
[[GBFHA]][[troubleshooting-tips]]
6.7 Troubleshooting Tips
~~~~~~~~~~~~~~~~~~~~~~~~
This section provides some tips for troubleshooting errors that may be
encountered.
* Verify that the Ant `config.vi` and `enable.jacc` configuration
targets executed correctly.
* If there are several failures during a test run, check the various
output for hints about what caused the failures. A common problem is the
absence of the {TechnologyShortName} log file. This log file should be created in the
directory defined by the `log.file.location` property in the `ts.jte`
file. There should be a log file called `JACCLog.txt` in this directory.
The `JACCLog.txt` consists of record entries containing permission
infomation that will be used to verify the TCK tests for proper
compliance. This log file typically gets populated with
{TechnologyShortName}-based security information when test archives are
deployed. Then, during test execution, the `JACCLog.txt` file is read
and used for validating that {TechnologyShortName} behavior is
correct.
* Simultaneously deploying all {TechnologyShortName} TCK test archives
may cause false failures. If unexpected failures occur during a TCK run
when all {TechnologyShortName} archives were deployed, these failures
could be caused by interference from tests and archives that are
defined multiple times. If such situational failures do occur, undeploy
all archives, remove the `JACCLog.txt` file, recycle your server (if
necessary), and rerun only the tests in the directory that showed
failures.
* Check that the following JVM variables, which should have been set by
invoking the `enable.jacc` Ant target, have been set in the application
server :
** `-Dlog.file.location` (this comes from the +{jteFileName}+ property)
** `-Djavax.security.jacc.policy.provider=com.sun.ts.tests.jacc.provider.TSPolicy`
** `-Djavax.security.jacc.PolicyConfigurationFactory.provider=com.sun.ts.tests.jacc.provider.TSPolicyConfigurationFactoryImpl`
** `-Dvendor.javax.security.jacc.policy.provider=com.sun.enterprise.security.provider.PolicyWrapper`
** `-Dvendor.javax.security.jacc.PolicyConfigurationFactory.provider=com.sun.enterprise.security.provider.PolicyConfigurationFactoryImpl` +
[NOTE]
=======================================================================
The values for the `-Dvendor.javax.security.jacc.policy.provider` and
`-Dvendor.javax.security.jacc.PolicyConfigurationFactory.provider` JVM
variables will need to be set specific to the application server in use.
=======================================================================
///////////////////////////////////////////////////////////////////////