[ 
https://issues.apache.org/jira/browse/TOMEE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745352#comment-17745352
 ] 

Yugandher reddy vonteddu commented on TOMEE-4105:
-------------------------------------------------

Hi [~rzo1] ,

 

Thanks for the quick response.

 

for linux we have pinpointed the issue with a JAVA_OPTS set in demon.sh which 
we had in place from long time.

 
{code:java}
# Add OpenEJB javaagent
if [ -r "$CATALINA_HOME"/lib/openejb-javaagent.jar ]; then
  JAVA_OPTS="\"-javaagent:$CATALINA_HOME/lib/openejb-javaagent.jar\" $JAVA_OPTS"
fi {code}
 

 

this was placed because we had an issue earlier for which we have raised a 
TomEE bug too https://issues.apache.org/jira/browse/TOMEE-1508

 

as of now without the patch provided in the above bug TomEE is working fine.

 

But for windows same JAVA_OPTS is being set from catalina.bat and service.bat 
files.

 

if we remove it before installing TomEE and add the JMX properties we are able 
to test the JMX properly and TomEE is also running fine.

Any idea why we use the above java agent and how it is effecting the JMX 
property.

 

it is easily reproducing in windows but i know that you are working 
specifically on linux.

 

Thanks.

 

> jmxremote enabled from java options in tomee not working
> --------------------------------------------------------
>
>                 Key: TOMEE-4105
>                 URL: https://issues.apache.org/jira/browse/TOMEE-4105
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 8.0.13
>            Reporter: Yugandher reddy vonteddu
>            Priority: Major
>         Attachments: TomEE.2023-01-17.log, catalina.err, catalina.out, 
> image-2022-10-31-13-00-33-841.png, image-2022-10-31-13-04-44-626.png, 
> image-2023-03-16-16-04-46-556.png
>
>
> Hello Team,
>  
> we where using 8.0.12 earlier and below jmx remote java properties where 
> added then TomEE started properly without any error 
> -Dcom.sun.management.jmxremote.port=8686
> -Dcom.sun.management.jmxremote.ssl=false
> -Dcom.sun.management.jmxremote.authenticate=false
>  
> but when we do the same from 8.0.13 then we are getting below error 
> !image-2022-10-31-13-00-33-841.png!
> did something chnage reagrding this in new TomEE?
>  
> we see when we add the below property its working fine again 
> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=0.0.0.0:8000
> !image-2022-10-31-13-04-44-626.png!
>  
> can you help us with this if its mandatory so that we can document in our 
> product 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to