[bussien]

maybe its the order of the argument:

-mp "C:/jboss-as-7.1.0.CR1b/modules" -logmodule org.jboss.logmanager -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone  --server-config=standalone.xml   

my server starts fasts and correct but after a while it 'encountered a problem' (Server JBoss 7.1 Runtime Server failed to start. )

[sskirpekar]

Hi ,

I am also getting the same error ..

The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")#

where exactly I need to set

• -mp "c:/jboss-as-7.1.0.CR1b/modules" -jaxpmodule javax.xml.jaxp-provider -logmodule org.jboss.logmanager org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml

where I will get the launch configuration  ...

i mean where I will see the launch configuration ..

[peterox]

I had the same problem and found that removing the following VM parameters fixed it for me.

-Dcom.sun.management.jmxremote

-Dcom.sun.management.jmxremote.port=6789

-Dcom.sun.management.jmxremote.ssl=false

-Dcom.sun.management.jmxremote.authenticate=false

[maxandersen]

where did you see those ? in jboss tools launch configuration for AS ?

[iqgeo1]

HI

I also have the same issue , i configured the jboss server arguments but it still receive this errors:

"

WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java

WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager

Exception in thread "main" java.lang.ExceptionInInitializerError

        at org.jboss.as.server.Main.main(Main.java:73)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.modules.Module.run(Module.java:260)

        at org.jboss.modules.Main.main(Main.java:291)

Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "j

        at org.jboss.logmanager.Logger.getLogger(Logger.java:60)

        at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)

"

I am  using jboss-7.1.1 can you help my with the corect settings :

My standalone.conf.abt file config i add the line

"

set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.snmp.port=6559 -Dcom.sun.management.snmp.acl.file=jre/lib/management/snmp.acl -Dcom.sun.management.snmp.interface=0.0.0.0"

"

and on the config file standalone.bat I addes

"

"-Dorg.jboss.boot.log.file=%JBOSS_LOG_DIR%\boot.log" ^

"-Dlogging.configuration=file:%JBOSS_CONFIG_DIR%/logging.properties" ^

    -jar "%JBOSS_HOME%\jboss-modules.jar" ^

    -mp "%JBOSS_MODULEPATH%" ^

    -jaxpmodule "javax.xml.jaxp-provider" ^

      -logmodule org.jboss.logmanager ^

     org.jboss.as.standalone ^

    -Djboss.home.dir="%JBOSS_HOME%" ^

     %*

"

but nothing can you help me ??

[shaler]

I had this issue after attempting to migrate from geronimo. My layout was an Ear that contained 2 wars. I had all my dependencies defined in the war pom files, and nothing in the ear pom files. I moved all my dependencies to the ear except for a SOA server dependency and an impl project. The dependencies in the war are all marked as provided.

Hope this helps.

[zamrokk]

i had same problem and i confirm this hack works

[maxandersen]

which of the three hacks shown did you do  ?

[zamrokk]

Open the launch configuration for the server definition.

Add: -logmodule org.jboss.logmanager to the program arguments before org.jboss.as.standalone