Hi Aakarsh Goel,

I understand that you're experiencing an issue where attaching the remote debugger to Module B in Eclipse is causing the entire JBoss server to suspend, rather than just the thread you intended to debug. This can be quite frustrating, especially when working with multiple modules.

Here are some suggestions that might help resolve this issue:

1. Check Debug Configuration:

   • Ensure that in your debug configuration, under the "Source" tab, you have the correct source attachments for your modules. Sometimes, incorrect source mappings can lead to unexpected behavior.

2. Thread Suspension Settings:

   • Double-check your breakpoint settings. In the breakpoint properties, confirm that the option "Suspend" is set to "Thread" and not "All".

3. Use a Different Debug Port:

   • If possible, try using a different debug port for Module B to see if that resolves the suspension of other threads.

4. Update Eclipse and JBoss:

   • Make sure that both Eclipse and JBoss are up to date. Sometimes, bugs in earlier versions can cause issues that have been resolved in updates.

5. Review JBoss Configuration:

   • Look into the JBoss server's configuration files to ensure that there are no settings that might interfere with remote debugging.

If these suggestions do not resolve the issue, could you provide more details about your setup? For instance, the specific JBoss version you are using and any relevant logs or error messages would be helpful.

Additionally, you might find the following resources useful:

• Eclipse Debugging Documentation

• JBoss Remote Debugging Guide

I hope this helps! Let me know if you have any further questions.

Best,
T S Samarth