int-accounting-oracle - Build # 2206 - Fixed:

Check console output at 
https://ci.openbravo.com/job/int-accounting-oracle/2206/ to view the results.


Committers since last success:

Changes for Build #2205

    Asier Lostalé <asier.lost...@openbravo.com> null
    related to issue 39362: added test cases covering no DB conns detection
        
src-test/src/org/openbravo/test/db/pool/PoolHasNoConnectionsDetection.java
        src-test/src/org/openbravo/test/AllAntTaskTests.java

    Asier Lostalé <asier.lost...@openbravo.com> null
    fixed issue 39362: can't create tickets if one failed due to pool without 
conns

  After a ticket failed to be imported due to the pool is out of connections, no
  new tickets can be created from that terminal until all import entries are set
  again in Initial status.

  Now in this case instead of setting the import entry as Error preventing new
  tickets from the same terminal to be processed, it's kept in Initial status,
  in this way it will be tried to be processed in next cycle, not exposing the
  problem to users.
        
modules/org.openbravo.apachejdbcconnectionpool/src/org/openbravo/apachejdbcconnectionpool/JdbcExternalConnectionPool.java
        src-core/src/org/openbravo/database/ExternalConnectionPool.java
        src/org/openbravo/service/importprocess/ImportEntryProcessor.java

Changes for Build #2206

    Víctor Martínez Romanos <victor.marti...@openbravo.com> null
    Fixed bug 39391: Movements in same bin for non-attribute product

The goods movement created by AWO when a product has no attribute are 
automatically set with m_attributesetinstance_id = '0'.
In a normal movement the m_attributesetinstanceTO_id is usually null (unless an 
attribute change or a RI related flow involved). Thus the comparation has 
'0'='X' which avoided to raise the expected error.

Note that in Core the m_attributesetinstance_id for non-attribute product is 
NULL, so the issue is not reproducible in Core. Besides the UI controls this 
scenario very well.

The solution is done in the trigger rather than in AWO because it is safer and 
easier to develop.
It runs the locators check only when m_attributesetinstanceTO_id is null.
If m_attributesetinstanceTO_id is not null it implies an attribute change or a 
RI related movement, and in any of these cases it is allowed to run the 
movement within the same bin.
        src-db/database/model/triggers/M_MOVEMENTLINE_TRG.xml




Last 20 lines of the console output:

[...truncated 10054 lines...]
  [ "$(jps | grep Bootstrap || true)" = "" ] && break
  sleep 5
done
[ "$(jps | grep Bootstrap || true)" != "" ] && echo "Tomcat has fail to stop" 
&& exit 1 || true
[ "$i" != "0" ] && secs=$(echo "$i * 5" | bc) && echo "Waiting for $secs secs 
for tomcat to stop"

echo
fi

[int-accounting-oracle] $ /bin/bash -xe /tmp/hudson3760990626408365488.sh
++ jps
++ grep Bootstrap
++ true
+ '[' '' '!=' '' ']'
POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Email was triggered for: Fixed
Trigger Success was overridden by another trigger and will not send an email.
Sending email for trigger: Fixed
_______________________________________________
Openbravo-builds mailing list
Openbravo-builds@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbravo-builds

Reply via email to