Description of problem: To use different customizations and optimizations it was possible in former version to add entity-commands to the jbosscmp-jdbc.xml DD <defaults> <entity-command name="no-select-before-insert" /> </defaults> ... <entity> <ejb-name>TestEntity</ejb-name> ... <entity-command name="no-select-before-insert"> The current behaviour is that the configuration is checked (it is not possible to declare a non existing command name) but there is no effect if the entity is created at runtime. The default command "SELECT COUNT(*)" is still executed.
Looking into the JDBCCreateEntityCommand class it is extending the JDBCInsertPKCreateCommand which extends the JDBCAbstractCreateCommand. Within JDBCInsertPKCreateCommand following lines made us looking into the details: if (exceptionProcessor == null) { initExistsSQL(); } Esp. as we do not want the exists SQL it needs to be made sure that a exceptionProcessor is set. This handling is implemented in the JDBCAbstractCreateCommand class. With in JDBCAbstractCreateCommand class: JDBCEntityCommandMetaData entityCommand = manager.getMetaData().getEntityCommand(); if (entityCommand == null) { throw MESSAGES.entityCommandIsNull(); } initEntityCommand(entityCommand); So, debugging in runtime shows that JDBCEntityCommandMetaData entityCommand is correctly intialized: [commandName=no-select-before-insert,commandClass=class org.jboss.as.cmp.jdbc.JDBCCreateEntityCommand,attributes={SQLExceptionProcessor=jboss.jdbc:service=SQLExceptionProcessor}] So, then initEntityCommand(entityCommand) is called: protected void initEntityCommand(JDBCEntityCommandMetaData entityCommand) { exceptionProcessor = null; } Here we do not understand: the exceptionProcessor is set to null (even the command has all the details) causing theat the JDBCInsertPKCreateCommand does not find the exceptionProcessor and creates an existsSQL statement - which is always fired ... even we did not want if by setting <entity-command name="no-select-before-insert" />.
As this is related to a customer issue is it possible to have the solution for EAP6.1.1?
Verified the fix in EAP 6.1.1.ER3.
Marking for exclusion from the 6.1.1 Release Notes document as an entry for this bug could not be completed or verified in time.