[jira] [Updated] (TOMEE-1868) Prevent hot deployment of "filepart" archives
[ https://issues.apache.org/jira/browse/TOMEE-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Gumbrecht updated TOMEE-1868: -- Description: Dropping an application war into webapps sometimes deploys the partially extracted war file with the [appname].filepart and then [appname]. This obviously breaks both deployments and the only solution is to delete both, wait for the undeploy, and then redeploy. This is to do with the transfer over scp - the extension is either '.filepart' or '.partial'. was:Dropping an application war into webapps sometimes deploys the partially extracted war file with the [appname].filepart and then [appname]. This obviously breaks both deployments and the only solution is to delete both, wait for the undeploy, and then redeploy. > Prevent hot deployment of "filepart" archives > - > > Key: TOMEE-1868 > URL: https://issues.apache.org/jira/browse/TOMEE-1868 > Project: TomEE > Issue Type: Bug >Affects Versions: 1.7.4, 7.0.1 >Reporter: Andy Gumbrecht >Priority: Major > Fix For: 7.0.5, 1.7.6 > > > Dropping an application war into webapps sometimes deploys the partially > extracted war file with the [appname].filepart and then [appname]. This > obviously breaks both deployments and the only solution is to delete both, > wait for the undeploy, and then redeploy. > This is to do with the transfer over scp - the extension is either > '.filepart' or '.partial'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TOMEE-2135) ejb state not maintained for user transactions in afterCommit
[ https://issues.apache.org/jira/browse/TOMEE-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Kwakkel updated TOMEE-2135: -- Description: When a ejb is registering a beforeCompletion handler in the transaction synchronization registry when the transaction is started by a user transaction, there is no ejb context in beforeCompletion (run attached test). When using bean javax.ejb.BeforeCompletion it has. Not sure what must be the behaviour according to the jee/ejb specs. (was: When a ejb is registering a beforeCommit handler when the transaction is started by a user transaction, there is no ejb context in beforeCommit (run attached test). ) > ejb state not maintained for user transactions in afterCommit > - > > Key: TOMEE-2135 > URL: https://issues.apache.org/jira/browse/TOMEE-2135 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 1.7.3 >Reporter: Donald Kwakkel >Priority: Critical > Attachments: MoviesTest.java > > > When a ejb is registering a beforeCompletion handler in the transaction > synchronization registry when the transaction is started by a user > transaction, there is no ejb context in beforeCompletion (run attached test). > When using bean javax.ejb.BeforeCompletion it has. Not sure what must be the > behaviour according to the jee/ejb specs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
