{'fraction_non_alphanumeric': 0.020833333333333332, 'fraction_numerical': 0.0024509803921568627, 'mean_word_length': 5.007352941176471, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Non-intrusive end-to-end runtime path tracing for J2EE systems

An end-to-end runtime path-tracing approach for J2EE systems has been introduced. The approach is non-intrusive and thus does not require instrumentation of middleware or application source code. The implementation of the system has been realised in the COMPAS Java end-to-end monitoring tool that extends and integrates a number of open source projects. The first set of results shows the performance overhead associated with the tool. Further results show the portability of this approach, by applying it to a number of different application server implementations. Finally, it is also shown that runtime paths collected by the implementation can be used for reasoning about the overall system structure and design of complex enterprise applications.