Permalink
Commits on Apr 18, 2012
  1. Don't require torquebox-web since RackRuntimeInitializer does (TORQUE…

    bbrowning committed Apr 18, 2012
    …-775)
    
    The require is harmless under 1.8 but due to a bug in JRuby's 1.9
    LoadService implementation (JRUBY-6610) this throws a LoadError if
    Bundler is used and torquebox or torquebox-web are not in the app's
    Gemfile. Since torquebox-web is already required by
    RackRuntimeInitializer, this was a no-op anyway.
  2. Can't inject messaging destinations without torquebox-messaging avail…

    bbrowning committed Apr 18, 2012
    …able (TORQUE-775)
    
    JRuby's LoadService is more strict and correct, in this case. This
    shouldn't have worked before but it did. You always need the torquebox
    or torquebox-messaging gem in your Gemfile to inject messaging
    destinations, since they call code inside the TorqueBox::Messaging module.
  3. Use reflection in ScriptAnalyzer so it works under JRuby 1.7 (TORQUE-…

    bbrowning committed Apr 17, 2012
    …775)
    
    We should figure out why LocalStaticScope's constructor is no longer
    public in JRuby 1.7 and either adjust our code or submit a patch to
    make it public again.
  4. Remove VFSLoadService in favor of NonLeakingLoadService (TORQUE-775)

    bbrowning committed Apr 17, 2012
    This is not only because I enjoy prefixing more classes with
    NonLeaking, which I do, but also to greatly simplify our custom
    LoadService logic. All VFS references are removed and no longer
    needed, at least according to our unit and integration tests.
    
    This is the first of several changes to get TorqueBox working with
    JRuby 1.6.7 and 1.7.
Commits on Apr 17, 2012
  1. removing appMetaData reference

    Bruno Oliveira committed with tobias Feb 19, 2012
  2. Removing useless methods

    Bruno Oliveira committed with tobias Feb 17, 2012
  3. Minor doc edits.

    tobias committed Apr 17, 2012
Commits on Apr 16, 2012
  1. Another doc typo

    bbrowning committed Apr 16, 2012
Commits on Apr 13, 2012
  1. fix typo

    bbrowning committed Apr 13, 2012
  2. Remove reference to advertise-security-key and aliased hostnames from…

    bbrowning committed Apr 13, 2012
    … production setup docs
  3. Allow connecting to remote HornetQ destinations when inside TorqueBox…

    bbrowning committed Apr 13, 2012
    … (TORQUE-769)
    
    A new spec was added to ensure that if a user specifies a host or port
    to connect to that we don't use the TorqueBox internal connection
    factory and instead explicitly create one for that host/port combination.
  4. Preserve permissions for jboss/bin/ in server gem [TORQUE-766]

    tobias committed Apr 13, 2012
    maven-resources-plugin doesn't preserve permissions, so we
    punt to jruby.
  5. Default consumer-window-size to 0 for the HornetQ InVmConnectionFacto…

    bbrowning committed Apr 13, 2012
    …ry (TORQUE-748)
    
    The value of 0 disables buffering which gives us the expected behavior
    when using concurrency settings higher than 1 at the expense of
    theoretical lower maximum throughput. Theoretical because the
    InVmConnectionFactory shouldn't be making network trips between
    clients and servers so the actual throughput difference may be
    negligible.
    
    Advanced users can always tune this value, knowing that if they do so
    it will take a large message backlog to fully utilize multiple
    concurrent consumers.
Commits on Apr 12, 2012
  1. Ensure nodes without an instance-id set use a UUID in mod_cluster (TO…

    bbrowning committed Apr 12, 2012
    …RQUE-755)
    
    This is a hack to essentially backport the fix for JBPAPP-8451 in
    commit
    ctomc/jboss-as@167f41f
    to TorqueBox so we can release with this issue fixed before AS 7.1.2
    comes out. Once 7.1.2 is out, this commit can be reverted.
Commits on Apr 11, 2012
Commits on Apr 5, 2012
  1. Fixed TORQUE-758: Capistrano support should use deploy:create_symlink…

    nirvdrum committed with lance Apr 5, 2012
    … hook.
    
    Signed-off-by: Lance Ball <lball@redhat.com>
  2. Fixed TORQUE-757: Capistrano no longer fully deploys.

    nirvdrum committed with lance Apr 5, 2012
    There's no need to override the default deploy task.  Letting Capistrano do its thing fixes the underlying problem.
    
    Signed-off-by: Lance Ball <lball@redhat.com>
  3. Fixed TORQUE-756: Capistrano-based deploys break in MRI 1.9.3p125.

    nirvdrum committed with lance Apr 4, 2012
    Signed-off-by: Lance Ball <lball@redhat.com>