Skip to main content

Home/ SoftwareEngineering/ Group items tagged control

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
kuni katsuya

Cargo - Home - 0 views

cargo.codehaus.org

cargo javaee container control

shared by kuni katsuya on 12 Jun 12 - Cached
  • Cargo is a thin wrapper that allows you to manipulate Java EE containers in a standard way.  
kuni katsuya

NetBeansUserFAQ - NetBeans Wiki - 0 views

wiki.netbeans.org/NetBeansUserFAQ

netbeans faq

shared by kuni katsuya on 15 Jun 12 - Cached
kuni katsuya

Admin Guide - JBoss AS 7.1 - Project Documentation Editor - 0 views

docs.jboss.org/...Admin+Guide

jbossas7 admin guide documentation

shared by kuni katsuya on 22 Jun 12 - No Cached
  • -b=<value> Sets system property jboss.bind.address to <value>. See Controlling the Bind Address with -b for further details.
kuni katsuya

Class Loading in AS7 - JBoss AS 7.1 - Project Documentation Editor - 0 views

docs.jboss.org/...Class+Loading+in+AS7

jboss deployment

shared by kuni katsuya on 19 Jul 13 - No Cached
  • JBoss Deployment Structure File
  • jboss-deployment-structure.xml
  • control class loading in a fine grained manner
  • ...3 more annotations...
  • Prevent automatic dependencies from being added Add additional dependencies Define additional modules  Change an EAR deployments isolated class loading behaviour Add additional resource roots to a module
  • Class Loading in AS7
  • Automatic dependencies can be excluded through the use of jboss-deployment-structure.xml
kuni katsuya

MySQL :: MySQL 5.7 Reference Manual :: 5.4.4.2 Configurable InnoDB Auto-Increment Locking - 0 views

dev.mysql.com/...to-increment-configurable.html

shared by kuni katsuya on 08 Aug 13 - No Cached
  • Configurable
    • kuni katsuya
      kuni katsuya on 08 Aug 13
       
      new and improved!(?)
  • table-level locks held until the end of a statement make INSERT statements using auto-increment safe for use with
  • statement-based replication
  • ...24 more annotations...
  • However, those locks limit concurrency and scalability when multiple transactions are executing insert statements at the same time
  • For INSERT statements where the number of rows to be inserted is known at the beginning of processing the statement, InnoDB quickly allocates the required number of auto-increment values without taking any lock, but only if there is no concurrent session already holding the table-level AUTO-INC lock (because that other statement will be allocating auto-increment values one-by-one as it proceeds)
  • obtains auto-increment values under the control of a mutex (a light-weight lock) that is not held until the statement completes, but only for the duration of the allocation process
  • innodb_autoinc_lock_mode = 0 (“traditional” lock mode)
  • special table-level AUTO-INC lock is obtained and held to the end of the statement
  • lock mode is provided for:
  • Backward compatibility.
  • innodb_autoinc_lock_mode = 1 (“consecutive” lock mode)
  • important impact of this lock mode is significantly better scalability
  • This mode is safe for use with
  • statement-based replication
  • innodb_autoinc_lock_mode = 2 (“interleaved” lock mode)
  • This is the fastest and most scalable lock mode
  • but it is
  • not safe
  • when using
  • statement-based replication
  • recovery scenarios when SQL statements are replayed from the binary log
  • Using auto-increment with replication
  • set innodb_autoinc_lock_mode to 0 or 1 and use the same value on the master and its slaves
  • Auto-increment values are not ensured to be the same on the slaves as on the master if you use innodb_autoinc_lock_mode = 2 (“interleaved”) or configurations where the master and slaves do not use the same lock mode
  • If you are using
  • row-based replication
  • all of the auto-increment lock modes are safe
« First ‹ Previous 41 - 45 of 45
Showing 20▼ items per page