method1
and method2
have been called but have completed their work, so there's no reason for them to be in the trace. A stack trace's job is to show you what functions are in progress (what calls are outstanding on the stack).
If you're looking for something that will tell you they were called (but have finished), the category of tool you're looking for is called a "code coverage" testing tool. That's not part of what the exception and stack trace aspects of the Java runtime are for.