Skip to content
Tag: 0.10.0
Commits on Nov 11, 2015
Commits on Nov 10, 2015
  1. Use a concurrency of 1 for response routers [IMMUTANT-593]

    tobias committed Nov 10, 2015
    Using numProcs is wasteful, since the listener just satisfies a future.
Commits on Nov 6, 2015
  1. Use the simple election policy for singletons when in WF 8/9

    tobias committed Nov 6, 2015
    There is a bug ( that can
    cause non-deterministic election policies to result in an inconsistent
    singleton state (multiple nodes running the singleton, or no nodes
    running the singleton are both possible). This caused an intermittent
    integ failure in Immutant's cluster tests. We're still using the random
    election policy with WF10 - the Immutant tests should catch it if it
    also has the same behavior.
Commits on Nov 5, 2015
  1. Invoke the WS init handler before the socket is connected

    tobias committed Nov 5, 2015
    Otherwise, the init handler can't set headers, since the headers have
    been written by the time the socket is connected.
    This change also lets us get rid of that silly threadLocal hack.
Commits on Nov 3, 2015
Commits on Oct 29, 2015
  1. Explicitly depend on WF10's messaging-activemq extension

    tobias committed Oct 29, 2015
    We need this for messaging to work in wildfly-swarm.
    This also reorgs the file a bit to group related modules together.
  2. Detect if we are inside wildfly-swarm

    tobias committed Oct 29, 2015
    And treat it as WildFly 10.
Commits on Oct 22, 2015
  1. Adjust CI script to new path

    tobias committed Oct 22, 2015
  2. Remove unneeded module dir

    tobias committed Oct 22, 2015
    This moves all of the modules to the top-level, removing the extra dir &
  3. Break wildfly up in to multiple modules

    tobias committed Oct 22, 2015
    This is the first step in allowing wunderboss-based apps to properly
    take advantage of swarm, since wildfly functionality can be brought in
    piecemeal, instead of as one dep. This also means that we don't assume a
    full WF is available, and each piece only assumes what it needs is
    There is still an org.projectodd.wunderboss/wunderboss-wildfly, but it
    is an aggregator for all of the other WF modules.
Commits on Oct 9, 2015
  1. Use WildFly's built-in singleton support.

    tobias committed Oct 7, 2015
    This greatly simplifies our own singleton implementation, and makes it
    more reliable, in theory.
Commits on Oct 7, 2015
Commits on Oct 6, 2015
  1. Notify stop callback whenever stop is called

    tobias committed Oct 6, 2015
    even if the daemon is no longer running.
  2. Minor renaming/rewording.

    tobias committed Oct 6, 2015
  3. Allow detecting if a component exists.

    tobias committed Oct 5, 2015
    We need this to prevent creating multiple daemons with the same name.
Commits on Sep 4, 2015
Commits on Sep 1, 2015
Commits on Aug 31, 2015
Commits on Aug 28, 2015
  1. Oops!

    jcrossley3 committed Aug 28, 2015
Commits on Aug 26, 2015
  1. Force the container to use "/" instead of "" when looking up Endpoints

    tobias committed Aug 26, 2015
    This works around a bug in EAP where ServerEndpoints mounted at "/"
    won't be activated if the Servlet has a mapping of "/*".
Commits on Aug 24, 2015
  1. Adjustments to support WildFly 10 [IMMUTANT-574]

    tobias committed Aug 24, 2015
    WF 10 uses ActiveMQ instead of HornetQ, which really only affects us on
    queue creation and deletion. We still use the same WF API for doing
    that, but it has moved to a new package in WF 10.
Commits on Aug 21, 2015
Commits on Aug 13, 2015
  1. Set content-length to zero when data is null.

    tobias committed Aug 13, 2015
    Undertow does this for us automatically, but we shouldn't rely on that
    since we now support other platforms (EAP/jbossweb).
Commits on Aug 10, 2015
  1. Wait for an actual value from JNDI

    tobias committed Aug 10, 2015
    Context.lookup() will sometimes return null instead of throwing a
    NameNotFoundException under EAP, so we now continue to wait for a
    non-null value. This should resolve occasional "timeout" issues when
    deploying destinations.
  2. Don't allow setting a stream timeout on WF 8.2

    tobias committed Aug 10, 2015
    Setting a stream timeout triggers the same session deadlock bug as async
    sending in WF 8.2, so we throw if you try to use it in 8.2. This
    requires changing the init order of the stream, because if we throw
    after the request is converted to async, we can never return a response
    to the client.
You can’t perform that action at this time.