java match thread query to identify a suspended java thread that originates from business integration components i e part of the test environment 404 when a java debug event arrives from the test environment 404 the jdm 402 will try to filter the event in particular the jdm 402 will send a query to the test environment 404 to determine if the thread originated from one of the debug tools 204 208 the result of the query is returned to the jdm 402 which combines the event with other debug information e g information vectors and route the information to the cda 202 for handling the cda 202 would in turn delegate any required handling back to one of the debug tools 204 208 as required the individual debug tools 202 208 handles the java mixed stack frame by identifying where the java code is called from the results from the debug tools 202 208 are rerouted to the cda 202 for further mixed stack frame handling if required the cda 202 then provides the complete merged stack frame as the common suspended stack frame in the debug view through the ui module 214 as previously discussed assuming a server not shown in the test environment 404 e g business integration tool is started in a debug mode and appropriate breakpoints have been added various breakpoints would occur if a breakpoint occurs at a first component in the test environment 404 which is called by a second component in the test environment 404 a merged stack frame will be shown under the wiring thread in a debug tree 500 shown in fig5 in this example a wiring editor calls adaptive entity ae which then calls business rule br the merged stack frame has.