TL;DR The F5 BigPipe LTM uses HTTP/0.9 to send its HTTP monitoring requests by default. Wildfly 9.0 does not like this; moving to a monitor request of HTTP/1.1 fixed the problem. Caution: LTM 10.2.x and 11.x do not append a CR/LF to the end unless you are using Basic Authentication. This is contrary to previous …
Category Archive: jboss
rvm, despite being wonderful, doesn’t play very well with torquebox under cygwin. In particular, the gem paths are not working. So, in order to fix this, simply do: rvm use system And then it will work right. Once you’re done with the torquebox work, you can go back to using rvm.
Prior to JBoss 5, the jboss-all-client.jar was pretty much all you needed. However, the JBoss 5 Getting Started Guide states the following: The client/jbossall-client.jar library that used to bundle the majority of jboss client libraries, is now referencing them instead through the Class-Path manifest entry. This allows swapping included libraries (e.g. jboss-javaee.jar) without having to …
Torquebox and Cygwin don’t work as nicely together as one might hope. That said, here are a couple of findings: In order to deploy, you need to set the $JBOSS_HOME with the Windows path. You can do this via export JBOSS_PATH=cygpath -w PATH_TO_JBOSS. Additionally, the JRUBY_HOME needs to be a windows path as well. Otherwise …
jnp is a JBoss protocol which exposes jndi. It is, by default, bound to port 1099. I’d been using that port as a heartbeat, but “cheating” — I would open a socket and then close it immediately. However, this caused problems. jnp is chatty. And it got upset at my not letting it say ‘hi’ …
Sometimes, JBoss reports that it is unable to bind to a port, saying it is already in use. However, this is not always the case.
One, One database record! Two, Two database record! Muahahaha! By default, when using datasources with JBoss, it does a count to validate a connection, both on creation and when it is requested from the connection pool. It looks something like: select count(*) from x Now, this can take take a while when working with tables …
A coworker and I discovered an issue with jboss’ run.sh (which starts the app server). The problem lies in different flavours of unix (or unix-like) shells returning different values for wait. The relevant code is:
# Wait until the background process exits
while [ "$WAIT_STATUS" -ne 127 ]; do
wait $JBOSS_PID 2>/dev/null
This is all well and good in linux — redhat uses /bin/bash and ubuntu uses /bin/dash for /bin/sh — …