Tip provided by Qiang Xu, Symphony Developer.

Scenario

Debug Symphony DE java client and service code together.

Steps

1. Add the JVM debug options when create the deploying package.



Note there is warning: The JVM options which you specified will not be validated by plug-in. It means, if your JVM options are wrong, we may still show you your package is created properly. So please make sure your JVM option is right.

Symphony also provide service trouble shooting for this part. But it is not in our plug-in part. Because it is difficult to detect such problem, the customers JVM may be provided by a lot providers or itself. (IBM, BEA, SUN and Microsoft all have their own JVMs)

So we will tell you that information in the runtime. If your options are not correct, there will be a log in the SIM and SSM. You can check the log for these information.

Here we will use the SUN jvm, and its debug options are: -Xdebug -Xrunjdwp:transport=dt_socket,address=6688,server=y ,suspend=y

Please make sure the address is unique, if other application uses this port, then you will get a error which stands for your debug address is in using.

2. Create package and deploy



3. Configure the eclipse remote debugger



Our symphony DE current only support debug on the local host. So we do not need to change the host address. Just change the port number to the address number which we configured in the previous jvm options. Press debug, you will get an error: That is because the service side is not start yet.



4. Debug the client and service now!!! Now you can set some break point in the client code. And click debug as java application.

The client side will halt at the session.fetchTaskOutput(tasksToSend); Then press our previous debug configuration as following.



Or by





You will see the break point at the:



Now you can debug the client and service as you want.

5. You need to redeploy the service if you want to debug again.

Just open the create package and create package and deploy it again. All your previous configuration is recorded in our plug-in. So do not worry to re-input again.



References

1. Developer's Guide -> Application Development -> Using Eclipse as Your Development Environment