I am using JBOSS EAP 7.2 on STS 3.4 with JDK 1.8. STS 3.4 do not have adapter specific to JBOSS EAP 3.4, So I am using it in the JBoss EAP 6.1+ Runtime Server adapter service itself.
And when I try to start my server, the server gets started. It shows on console like this,
17:22:18,999 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.2.0.GA (WildFly Core 6.0.11.Final-redhat-00001) started in 16013ms - Started 628 of 815 services (356 services are lazy, passive or on-demand)
But on the Eclipse(STS 3.4) processes it shows that it starting. It keeps in that state until it reaches timeout and then it stops.
I tried many of the solutions but nothing seems to working. I tried changing the the startup poller in server state detectors to web port instead of JBOSS 7 manager service. It gives the server status as started as soon as the server gets started.
But then It gives another error,
An internal error occurred during: "Connecting to JBoss EAP 6.1+ Runtime Server via JMX".
org/jboss/remotingjmx/RemotingConnectorProvider : Unsupported major.minor version 52.0
And then, It also gives problem in the stopping process. After changing this the server is unable to stop
I want to know why this is happening and what is prominent solution for this. And is there any links available regarding this issue which I can refer.
I found out that this was happening because of my STS version. So I upgraded the STS and the issue is now resolved.