Jboss port configuration on Intellij Idea error

V

16

38

I'm trying to run my application on Jboss App Server by Intellij Idea12. I've done configuration: enter image description here

but As you can see in the picture I got the error Management Port Configuration not found.

Vestryman answered 29/3, 2014 at 10:21 Comment(0)

E

47

Possible cause maybe an invalid configuration file "standalone.xml" or any other config file that you are using. I've put a tag at the wrong place and got the same error.

Errhine answered 19/8, 2014 at 9:34 Comment(3)

That will teach me for editing the standalone.xml with just notepad :) – Shetler 27/1, 2017 at 8:6

My case is that coworker (win7) sent me (Ubuntu) standalone.xml and encoding got messed up. – Architecture 15/2, 2017 at 8:51

Starting the standalone.bat (/bin/standalone.bat) can give a clue to where the invalid character is, in my case spelling out the offending character and line number – Anniceannie 7/7, 2017 at 14:10

M

14

It seems that IntelliJ IDEA was not able to read offset value from "standalone.xml". to solve it, just set Port offset to 0 in Configuration window, it will manually add additional VM option: -Djboss.socket.binding.port-offset=0

Machmeter answered 27/2, 2019 at 7:54 Comment(0)

C

9

Your standalone xml may be malformed in some way. Check to see if you have special characters that you will have to escape or extra closing or opening tags etc.

Coucal answered 9/2, 2015 at 1:18 Comment(1)

I mixed up xml with vim – Coelenteron 17/1, 2016 at 16:49

M

3

look for this in your standalone.xml

socket-binding name="management-native" interface="management" port="9999"

Source: http://youtrack.jetbrains.com/issue/IDEA-77592

Mckeown answered 4/4, 2014 at 13:19 Comment(0)

R

3

My case was that there was no config.

Folder c:\jboss-eap-6.4.6\standalone\configuration\ was without configuration files. There was only one folder org.6.4.0, where was the configuration.

The solution was to copy configuration files from c:\jboss-eap-6.4.6\standalone\configuration\org.6.4.0\ to c:\jboss-eap-6.4.6\standalone\configuration\

Remotion answered 20/5, 2016 at 17:14 Comment(0)

N

2

In my case, standalone.xml was corrupted (probably cause Idea froze and had to do hard shutdown). So I went to standalone_xml_history and copied standalone.xml from the day before. And it started to work normally again.

Newell answered 13/9, 2019 at 4:44 Comment(0)

D

1

In my case: I typed 9990 in port offset of Run/Debug Configurations and it solved. :)

Delmerdelmor answered 5/10, 2019 at 14:47 Comment(0)

R

0

I had the same problem, but have no idea what your setup looks like so the solution might not be the same. Also since your question is quite old you've probably figured out the answer by now.

Anyways.. In case anyone else happens to stumble upon this issue, I solved it this way: We use Puppet in our project and I had changed a couple of .yaml files where I added some URLs. The URLs contained & which had to be & and IntelliJ didn't notify me that this was the issue. It broke JBoss and everything.

Try running JBoss standalone.sh in the terminal and see if you get a Stacktrace.

Runagate answered 2/9, 2014 at 7:54 Comment(0)

T

0

In my case was added in standalone.xml in <deployments> section the following:

<deployment name="xxx-ear-1.0.ear" runtime-name="xxx-ear-1.0.ear">
 <fs-archive path="path\xxx-ear-1.0.ear"/>
</deployment>

I've removed this and worked.

Transarctic answered 9/6, 2017 at 11:11 Comment(0)

F

0

This is likely to be happening due to a parsing error in your configuration files.

Start your JBoss/WildFly in the command line, so that you would see more details if this is happening because of a configuration (or parsing) error.

On Windows run {JBOSS_HOME}/bin/standalone.bat file so that it would open up a console window and try to start up your application server.
Look for any ERROR in the log and see if it is related to configuration.
For example:

ERROR [org.jboss.as.server] WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration

If this doesn't help, have a look at open the ports - maybe the port JBoss/WildFly is configured to is already used by some other application.

Fascist answered 23/1, 2018 at 15:37 Comment(0)

A

0

Please make sute you had provided valid configuration file, may be your configuration file contains misplaced tag/element entries.

Azote answered 9/1, 2019 at 10:18 Comment(0)

N

0

I had the same problem and when I went to the standalone directory, I saw that the standalone.xml file was renamed as standalone.xml.tmp.

So I just renamed it as standalone.xml and when I started my Intellij again, everything was ok. If it's already not after that, you can delete and build a new running configuration after starting Intellij

Ninnyhammer answered 3/11, 2019 at 11:49 Comment(0)

H

0

As shown below, adding the VM options to point to standalone config files fixed my issue

/Users/XXX/dev/apps/wildfly/wildfly-16.0.0.Final.XXX.2019.152-node1/standalone/configuration/

Hetrick answered 26/11, 2019 at 16:55 Comment(0)

L

0

I had the same error "Management Port Configuration not found" when i was trying to boot up my jboss.

In my case i had accidentally deleted my standalone.xml. When i put it back all went fine. Another person had same issue turned out was some malformed tag in the standalone.xml.

Lubumbashi answered 6/3, 2020 at 16:13 Comment(0)

I

0

My standalone.xml file has been renamed to standalone.xml.tmp automatically. Rename it back to standalone.xml and it will fix the issue.

Intendment answered 20/2, 2022 at 10:25 Comment(0)

S

0

IntelliJ can't overwrite standalone.xml. That means that you have opened standalone.xml with other editor. Close standalone.xml and try again.

Sapindaceous answered 8/12, 2023 at 15:18 Comment(0)

Recommended topics

Hot tags