Remote Debugging Plugin-Unable to start JBOSS

georgej over 7 years ago

Hi Team,
We are trying to set up remote debugging for one of the custom plugins(SMART Service). In the standalone.conf we have put the below line

JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n -jar /hosting/products/appian7.11/_admin/plugins/SomePlugin.jar"

After changing the standalone.conf we tried to restart JBOSS ,but it is not coming up and following is noticed in the log.

//quote
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=512m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; support was removed in 8.0
Listening for transport dt_socket at address: 8787
no main manifest attribute, in /hosting/products/appian7.11/_admin/plugins/SomePlugin.jar
1380 "
//unquote

Discussion posts and replies are publicly visible

Parents

0 georgej over 7 years ago

Hi, Thanks for the providing some guidance ; I have few questions. If we set up the statement without "-jar" then how will the JBOSS identify that which component should be subjected to remote debugging. We don't want the entire apps to be under remote debugging configuration ,only the custom smart service which we have created.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 georgej over 7 years ago

Hi, Thanks for the providing some guidance ; I have few questions. If we set up the statement without "-jar" then how will the JBOSS identify that which component should be subjected to remote debugging. We don't want the entire apps to be under remote debugging configuration ,only the custom smart service which we have created.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data