jboss7.x

Deploying a Jersey webapp on Jboss AS 7

by

it has already been mentioned in this post : https://community.jboss.org/message/744530#744530 , you can just ask the resteasy module to not scan for other JAX RS implementations in your webapp; just add this to your web.xml : <context-param> <param-name>resteasy.scan</param-name> <param-value>false</param-value> </context-param> <context-param> <param-name>resteasy.scan.providers</param-name> <param-value>false</param-value> </context-param> <context-param> <param-name>resteasy.scan.resources</param-name> <param-value>false</param-value> </context-param> worked fine for me

Start JBoss 7 as a service on Linux

by

After spending a couple of hours of snooping around I ended up creating /etc/init.d/jboss with the following contents #!/bin/sh ### BEGIN INIT INFO # Provides: jboss # Required-Start: $local_fs $remote_fs $network $syslog # Required-Stop: $local_fs $remote_fs $network $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start/Stop JBoss AS v7.0.0 … Read more

Spring3.2 and jboss as 7

by

Apparently this is “normal”, everything should still work. Likely there’s an (anonymous) inner class in StandardServletAsyncWebRequest. See also Applicaiton is deployed in JBoss7.0.2 Final (Arc ) but failed to in 7.1.1 Final (Brontes) and metadata-complete=”true” not respected. Basically it’s just a warning, everything is fine.

How to change port number in jboss-7

by

The file is $JBOSS_HOME/standalone/configuration/standalone.xml. Find <socket-binding-group> and <socket-binding> there. EDIT There’s multiple ways to do this. The recommended way is to use the management console. If JBoss AS runs on your local computer, open the URL http://localhost:9990/console/App.html#socket-bindings and edit the socket-bindings there. I tested it on Wildfly 8.1.0 Final, don’t know if the URL is … Read more

“HTTPS required” while logging in to Keycloak as admin

by

I was running the key cloak inside a docker container, The keycloak command line tool was avaialble inside the keycloak container. docker exec -it {contaierID} bash cd keycloak/bin ./kcadm.sh config credentials –server http://localhost:8080/auth –realm master –user admin ./kcadm.sh update realms/master -s sslRequired=NONE If the admin user is not created, then the user can be created … Read more

Logback and Jboss 7 – don’t work together?

by

You need to exclude the servers version of slf4j from your deployment. Create a jboss-deployment-structure.xml file and place it in either your WARS META-INF or WEB-INF directory. The contents of the file should look like this: <jboss-deployment-structure> <deployment> <!– Exclusions allow you to prevent the server from automatically adding some dependencies –> <exclusions> <module name=”org.slf4j” … Read more

How do I shutdown JBoss AS 7 server?

by

For some reason the JBoss team decided to reorganize the scripts between minor revision upgrades. In any case, jboss-cli.sh is the replacement for jboss-admin.sh (they are for all intents and purposes the exact same script). So your new shutdown command is: ./jboss-cli.sh –connect command=:shutdown

Jboss AS7 Deployment warning : does not point to a valid jar for a Class-Path reference

by

This is just a warning that you can in most cases safely ignore. What it tells you is that in your struts-1.2.9.jar has in META-INF/MANIFEST.MF in Class-Path reference to “commons-beanutils.jar” and that this file/jar cannot be referenced. But given that you have commons-beanutils-1.7.0.jar there everything will work fine. To get rid of the warning you … Read more