Re: [PROPOSAL] Backporting bugs Re: [jira] [Commented] (OFBIZ-9459) Wrong screen redirection after adding note on Lead profile screen

2017-07-12 Thread Jacques Le Roux 

Thanks Michael

Jacques


Le 12/07/2017 à 22:05, Michael Brohl a écrit :

Dear developers,

thanks for your suggestions and support for the backporting proposal!

I have documented the proposed process in the Wiki [1] and also added a section 
[2] to the release management guide.

Cheers,

Michael Brohl
ecomify GmbH
www.ecomify.de


[1] 
https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Committers+Roles+and+Responsibilities#OFBizCommittersRolesandResponsibilities-Howshouldcommittershandlebackporting?


[2] 
https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz#ReleaseManagementGuideforOFBiz-Thingstocheckbeforearelease


Am 12.07.17 um 18:07 schrieb Jacopo Cappellato:

1. bugfixes should be backported by the committer who does the bugfix in
trunk if possible

2. if he does not, for an reason, backport the bugfix, he should either
open a new Jira for a task to backport or leave the original issue open
with a remark that a backport is needed.

  (I tend to leave the issue open).

In no case should we close a Jira issue without doing 1. or 2.

Re: [PROPOSAL] Backporting bugs Re: [jira] [Commented] (OFBIZ-9459) Wrong screen redirection after adding note on Lead profile screen

2017-07-12 Thread Michael Brohl 

Dear developers,

thanks for your suggestions and support for the backporting proposal!

I have documented the proposed process in the Wiki [1] and also added a 
section [2] to the release management guide.


Cheers,

Michael Brohl
ecomify GmbH
www.ecomify.de


[1] 
https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Committers+Roles+and+Responsibilities#OFBizCommittersRolesandResponsibilities-Howshouldcommittershandlebackporting?


[2] 
https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz#ReleaseManagementGuideforOFBiz-Thingstocheckbeforearelease



Am 12.07.17 um 18:07 schrieb Jacopo Cappellato:

1. bugfixes should be backported by the committer who does the bugfix in
trunk if possible

2. if he does not, for an reason, backport the bugfix, he should either
open a new Jira for a task to backport or leave the original issue open
with a remark that a backport is needed.

  (I tend to leave the issue open).

In no case should we close a Jira issue without doing 1. or 2.





smime.p7s
Description: S/MIME Cryptographic Signature

Re: [PROPOSAL] Backporting bugs Re: [jira] [Commented] (OFBIZ-9459) Wrong screen redirection after adding note on Lead profile screen

2017-07-12 Thread Jacopo Cappellato 
Yes, we will see how it goes and I like the idea of checking the the
"backport-needed" issues during the release preparation phase.

Jacopo

On Wed, Jul 12, 2017 at 5:07 PM, Michael Brohl 
wrote:

> Hi Jacopo,
>
> I hope that we will apply rule 1. in most cases so maybe it's not getting
> too much of a problem.
>
> Maybe we should also have a process to check the "backport-needed" issues
> some time before a planned release to avoid this?
>
> Michael
>
>
> Am 12.07.17 um 16:16 schrieb Jacopo Cappellato:
>
>> +1 to the agreed upon output of this conversation (thank you Michael).
>> One little problem we will have to face is that, with the new workflow, a
>> bug that has been fixed in one branch and left open (waiting for a
>> backport) will not appear in the release notes of the branch.
>>
>> Jacopo
>>
>> On Mon, Jul 10, 2017 at 2:02 PM, Michael Brohl 
>> wrote:
>>
>> Hi everyone,
>>>
>>> I think we should setup some kind of policy for the bugfixing in the
>>> project.
>>>
>>> While every committer is free to decide if he does a backport himself, we
>>> should make sure that bugfixes go into the supported release branches
>>> also.
>>>
>>> I propose to define the following policies:
>>>
>>> 1. bugfixes should be backported by the committer who does the bugfix in
>>> trunk if possible
>>>
>>> 2. if he does not, for an reason, backport the bugfix, he should either
>>> open a new Jira for a task to backport or leave the original issue open
>>> with a remark that a backport is needed.
>>>
>>>  (I tend to leave the issue open).
>>>
>>> In no case should we close a Jira issue without doing 1. or 2.
>>>
>>> What do you think?
>>>
>>> Regards,
>>>
>>> Michael Brohl
>>> ecomify GmbH
>>> www.ecomify.de
>>>
>>>
>>> Am 10.07.17 um 13:26 schrieb Jacques Le Roux (JIRA):
>>>
>>>   [ https://issues.apache.org/jira/browse/OFBIZ-9459?page=com.
 atlassian.jira.plugin.system.issuetabpanels:comment-tabpane
 l=16080188#comment-16080188 ]

 Jacques Le Roux commented on OFBIZ-9459:
 

 Hi Arun, I noticed that, like few other issues (at least OFBIZ-9473,
 OFBIZ-9316, OFBIZ-9317) that you did not backport this bug. Is there a
 reason? Do you want me to do it? Thanks.

 Wrong screen redirection after adding note on Lead profile screen

> -
>
>   Key: OFBIZ-9459
>   URL: https://issues.apache.org/jira
> /browse/OFBIZ-9459
>   Project: OFBiz
>Issue Type: Bug
>Components: marketing
>  Reporter: Jagpreet Kaur
>  Assignee: Arun Patidar
>   Fix For: Upcoming Release
>
>   Attachments: Create Note.png, OFBIZ-9459.patch,
> Screenredirection.png
>
>
> 1) Go to SFA component.
> 2) Click on Leads tab [https://demo-trunk-ofbiz.apac
> he.org:8443/sfa/control/FindLeads|https://demo-trunk-ofbiz
> .
> apache.org:8443/sfa/control/FindLeads].
> 3) Choose any partyId from All Lead list, you will be navigated to Lead
> profile. [https://demo-trunk-ofbiz.apache.org:8443/sfa/control/viewpr
> ofile?roleTypeId=LEAD=DemoLead|https://demo-trunk-
> ofbiz.apache.org:8443/sfa/control/viewprofile?roleTypeId
> =LEAD=DemoLead]
> 4) Click on "Create New" button in the Notes section.
> 5) Add the Note content.
> 6) Click on "Save Button".
> View redirection should be profile but it shows the blank screen.
>
>
 --
 This message was sent by Atlassian JIRA
 (v6.4.14#64029)


>>>
>>>
>
>

buildbot success in on ofbiz-branch14

2017-07-12 Thread buildbot 
The Buildbot has detected a restored build on builder ofbiz-branch14 while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-branch14/builds/379

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz14-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release14.12] 1801746
Blamelist: jleroux

Build succeeded!

Sincerely,
 -The Buildbot

Re: svn commit: r1801744 [2/3] - in /ofbiz/branches: release14.12/applications/product/src/org/ofbiz/product/imagemanagement/Ima geManagementServices.java release15.12/applications/product/src/org/ofb

2017-07-12 Thread Jacques Le Roux 

OK this was wrong, I reverted and don't care about fixing R14

Jacques


Le 12/07/2017 à 17:21, Jacques Le Roux a écrit :

Hi,

I'm not sure what happened with all these false changes in R14. I guess EOL  diff. ANyway I can guarantee only the Javolution imports and the fix 
are the real changes (checked in Eclipse before committing)


I think I'll tend to less backport in R14 and 15 :/

Jacques


Le 12/07/2017 à 17:08, jler...@apache.org a écrit :

Modified: 
ofbiz/branches/release14.12/applications/product/src/org/ofbiz/product/imagemanagement/ImageManagementServices.java
URL: 
http://svn.apache.org/viewvc/ofbiz/branches/release14.12/applications/product/src/org/ofbiz/product/imagemanagement/ImageManagementServices.java?rev=1801744=1801743=1801744=diff

==
--- 
ofbiz/branches/release14.12/applications/product/src/org/ofbiz/product/imagemanagement/ImageManagementServices.java
 (original)
+++ 
ofbiz/branches/release14.12/applications/product/src/org/ofbiz/product/imagemanagement/ImageManagementServices.java
 Wed Jul 12 15:08:03 2017
@@ -1,923 +1,923 @@
-/***
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- 
***/
-package org.ofbiz.product.imagemanagement;
-
-import java.awt.Image;
-import java.awt.image.BufferedImage;
-import java.awt.image.ImagingOpException;
-import java.awt.image.RenderedImage;
-import java.io.File;
-import java.io.FileNotFoundException;
-import java.io.IOException;
-import java.io.RandomAccessFile;
-import java.nio.ByteBuffer;
-import java.util.List;
-import java.util.Locale;
-import java.util.Map;
-
-import javax.imageio.ImageIO;
-
-import javolution.util.FastList;
-import javolution.util.FastMap;
-
-import org.jdom.JDOMException;
-import org.ofbiz.base.util.Debug;
-import org.ofbiz.base.util.UtilDateTime;
-import org.ofbiz.base.util.UtilGenerics;
-import org.ofbiz.base.util.UtilMisc;
-import org.ofbiz.base.util.UtilProperties;
-import org.ofbiz.base.util.UtilValidate;
-import org.ofbiz.base.util.string.FlexibleStringExpander;
-import org.ofbiz.common.image.ImageTransform;
-import org.ofbiz.entity.Delegator;
-import org.ofbiz.entity.GenericEntityException;
-import org.ofbiz.entity.GenericValue;
-import org.ofbiz.entity.util.EntityQuery;
-import org.ofbiz.entity.util.EntityUtil;
-import org.ofbiz.entity.util.EntityUtilProperties;
-import org.ofbiz.service.DispatchContext;
-import org.ofbiz.service.GenericServiceException;
-import org.ofbiz.service.LocalDispatcher;
-import org.ofbiz.service.ServiceUtil;
-
-/**
- * Product Services
- */
-public class ImageManagementServices {
-
-public static final String module = 
ImageManagementServices.class.getName();
-public static final String resource = "ProductErrorUiLabels";
-private static int imageCount = 0;
-private static String imagePath;
-
-public static Map addMultipleuploadForProduct(DispatchContext 
dctx, Map context)
-throws IOException, JDOMException {
-
-Map result = FastMap.newInstance();
-LocalDispatcher dispatcher = dctx.getDispatcher();
-Delegator delegator = dctx.getDelegator();
-GenericValue userLogin = (GenericValue) context.get("userLogin");
-String productId = (String) context.get("productId");
-productId = productId.trim();
-String productContentTypeId = (String) 
context.get("productContentTypeId");
-ByteBuffer imageData = (ByteBuffer) context.get("uploadedFile");
-String uploadFileName = (String) context.get("_uploadedFile_fileName");
-String imageResize = (String) context.get("imageResize");
-Locale locale = (Locale) context.get("locale");
-
-if (UtilValidate.isNotEmpty(uploadFileName)) {
-String imageFilenameFormat = 
EntityUtilProperties.getPropertyValue("catalog", "image.filename.format", 
delegator);
-String imageServerPath = FlexibleStringExpander.expandString(EntityUtilProperties.getPropertyValue("catalog", "image.management.path",

Re: svn commit: r1801744 [2/3] - in /ofbiz/branches: release14.12/applications/product/src/org/ofbiz/product/imagemanagement/Ima geManagementServices.java release15.12/applications/product/src/org/ofb

2017-07-12 Thread Jacques Le Roux 

Hi,

I'm not sure what happened with all these false changes in R14. I guess EOL  diff. ANyway I can guarantee only the Javolution imports and the fix are 
the real changes (checked in Eclipse before committing)


I think I'll tend to less backport in R14 and 15 :/

Jacques


Le 12/07/2017 à 17:08, jler...@apache.org a écrit :

Modified: 
ofbiz/branches/release14.12/applications/product/src/org/ofbiz/product/imagemanagement/ImageManagementServices.java
URL: 
http://svn.apache.org/viewvc/ofbiz/branches/release14.12/applications/product/src/org/ofbiz/product/imagemanagement/ImageManagementServices.java?rev=1801744=1801743=1801744=diff
==
--- 
ofbiz/branches/release14.12/applications/product/src/org/ofbiz/product/imagemanagement/ImageManagementServices.java
 (original)
+++ 
ofbiz/branches/release14.12/applications/product/src/org/ofbiz/product/imagemanagement/ImageManagementServices.java
 Wed Jul 12 15:08:03 2017
@@ -1,923 +1,923 @@
-/***
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- 
***/
-package org.ofbiz.product.imagemanagement;
-
-import java.awt.Image;
-import java.awt.image.BufferedImage;
-import java.awt.image.ImagingOpException;
-import java.awt.image.RenderedImage;
-import java.io.File;
-import java.io.FileNotFoundException;
-import java.io.IOException;
-import java.io.RandomAccessFile;
-import java.nio.ByteBuffer;
-import java.util.List;
-import java.util.Locale;
-import java.util.Map;
-
-import javax.imageio.ImageIO;
-
-import javolution.util.FastList;
-import javolution.util.FastMap;
-
-import org.jdom.JDOMException;
-import org.ofbiz.base.util.Debug;
-import org.ofbiz.base.util.UtilDateTime;
-import org.ofbiz.base.util.UtilGenerics;
-import org.ofbiz.base.util.UtilMisc;
-import org.ofbiz.base.util.UtilProperties;
-import org.ofbiz.base.util.UtilValidate;
-import org.ofbiz.base.util.string.FlexibleStringExpander;
-import org.ofbiz.common.image.ImageTransform;
-import org.ofbiz.entity.Delegator;
-import org.ofbiz.entity.GenericEntityException;
-import org.ofbiz.entity.GenericValue;
-import org.ofbiz.entity.util.EntityQuery;
-import org.ofbiz.entity.util.EntityUtil;
-import org.ofbiz.entity.util.EntityUtilProperties;
-import org.ofbiz.service.DispatchContext;
-import org.ofbiz.service.GenericServiceException;
-import org.ofbiz.service.LocalDispatcher;
-import org.ofbiz.service.ServiceUtil;
-
-/**
- * Product Services
- */
-public class ImageManagementServices {
-
-public static final String module = 
ImageManagementServices.class.getName();
-public static final String resource = "ProductErrorUiLabels";
-private static int imageCount = 0;
-private static String imagePath;
-
-public static Map addMultipleuploadForProduct(DispatchContext 
dctx, Map context)
-throws IOException, JDOMException {
-
-Map result = FastMap.newInstance();
-LocalDispatcher dispatcher = dctx.getDispatcher();
-Delegator delegator = dctx.getDelegator();
-GenericValue userLogin = (GenericValue) context.get("userLogin");
-String productId = (String) context.get("productId");
-productId = productId.trim();
-String productContentTypeId = (String) 
context.get("productContentTypeId");
-ByteBuffer imageData = (ByteBuffer) context.get("uploadedFile");
-String uploadFileName = (String) context.get("_uploadedFile_fileName");
-String imageResize = (String) context.get("imageResize");
-Locale locale = (Locale) context.get("locale");
-
-if (UtilValidate.isNotEmpty(uploadFileName)) {
-String imageFilenameFormat = 
EntityUtilProperties.getPropertyValue("catalog", "image.filename.format", 
delegator);
-String imageServerPath = 
FlexibleStringExpander.expandString(EntityUtilProperties.getPropertyValue("catalog", 
"image.management.path", delegator), context);
-String imageServerUrl =

buildbot exception in on ofbiz-branch14

2017-07-12 Thread buildbot 
The Buildbot has detected a build exception on builder ofbiz-branch14 while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-branch14/builds/378

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz14-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release14.12] 1801744
Blamelist: jleroux

BUILD FAILED: exception compile upload

Sincerely,
 -The Buildbot

Re: [PROPOSAL] Backporting bugs Re: [jira] [Commented] (OFBIZ-9459) Wrong screen redirection after adding note on Lead profile screen

2017-07-12 Thread Michael Brohl 

Hi Jacopo,

I hope that we will apply rule 1. in most cases so maybe it's not 
getting too much of a problem.


Maybe we should also have a process to check the "backport-needed" 
issues some time before a planned release to avoid this?


Michael


Am 12.07.17 um 16:16 schrieb Jacopo Cappellato:

+1 to the agreed upon output of this conversation (thank you Michael).
One little problem we will have to face is that, with the new workflow, a
bug that has been fixed in one branch and left open (waiting for a
backport) will not appear in the release notes of the branch.

Jacopo

On Mon, Jul 10, 2017 at 2:02 PM, Michael Brohl 
wrote:


Hi everyone,

I think we should setup some kind of policy for the bugfixing in the
project.

While every committer is free to decide if he does a backport himself, we
should make sure that bugfixes go into the supported release branches also.

I propose to define the following policies:

1. bugfixes should be backported by the committer who does the bugfix in
trunk if possible

2. if he does not, for an reason, backport the bugfix, he should either
open a new Jira for a task to backport or leave the original issue open
with a remark that a backport is needed.

 (I tend to leave the issue open).

In no case should we close a Jira issue without doing 1. or 2.

What do you think?

Regards,

Michael Brohl
ecomify GmbH
www.ecomify.de


Am 10.07.17 um 13:26 schrieb Jacques Le Roux (JIRA):


  [ https://issues.apache.org/jira/browse/OFBIZ-9459?page=com.
atlassian.jira.plugin.system.issuetabpanels:comment-tabpane
l=16080188#comment-16080188 ]

Jacques Le Roux commented on OFBIZ-9459:


Hi Arun, I noticed that, like few other issues (at least OFBIZ-9473,
OFBIZ-9316, OFBIZ-9317) that you did not backport this bug. Is there a
reason? Do you want me to do it? Thanks.

Wrong screen redirection after adding note on Lead profile screen

-

  Key: OFBIZ-9459
  URL: https://issues.apache.org/jira/browse/OFBIZ-9459
  Project: OFBiz
   Issue Type: Bug
   Components: marketing
 Reporter: Jagpreet Kaur
 Assignee: Arun Patidar
  Fix For: Upcoming Release

  Attachments: Create Note.png, OFBIZ-9459.patch,
Screenredirection.png


1) Go to SFA component.
2) Click on Leads tab [https://demo-trunk-ofbiz.apac
he.org:8443/sfa/control/FindLeads|https://demo-trunk-ofbiz.
apache.org:8443/sfa/control/FindLeads].
3) Choose any partyId from All Lead list, you will be navigated to Lead
profile. [https://demo-trunk-ofbiz.apache.org:8443/sfa/control/viewpr
ofile?roleTypeId=LEAD=DemoLead|https://demo-trunk-
ofbiz.apache.org:8443/sfa/control/viewprofile?roleTypeId
=LEAD=DemoLead]
4) Click on "Create New" button in the Notes section.
5) Add the Note content.
6) Click on "Save Button".
View redirection should be profile but it shows the blank screen.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)









smime.p7s
Description: S/MIME Cryptographic Signature

Re: [PROPOSAL] Backporting bugs Re: [jira] [Commented] (OFBIZ-9459) Wrong screen redirection after adding note on Lead profile screen

2017-07-12 Thread Jacopo Cappellato 
+1 to the agreed upon output of this conversation (thank you Michael).
One little problem we will have to face is that, with the new workflow, a
bug that has been fixed in one branch and left open (waiting for a
backport) will not appear in the release notes of the branch.

Jacopo

On Mon, Jul 10, 2017 at 2:02 PM, Michael Brohl 
wrote:

> Hi everyone,
>
> I think we should setup some kind of policy for the bugfixing in the
> project.
>
> While every committer is free to decide if he does a backport himself, we
> should make sure that bugfixes go into the supported release branches also.
>
> I propose to define the following policies:
>
> 1. bugfixes should be backported by the committer who does the bugfix in
> trunk if possible
>
> 2. if he does not, for an reason, backport the bugfix, he should either
> open a new Jira for a task to backport or leave the original issue open
> with a remark that a backport is needed.
>
> (I tend to leave the issue open).
>
> In no case should we close a Jira issue without doing 1. or 2.
>
> What do you think?
>
> Regards,
>
> Michael Brohl
> ecomify GmbH
> www.ecomify.de
>
>
> Am 10.07.17 um 13:26 schrieb Jacques Le Roux (JIRA):
>
>>  [ https://issues.apache.org/jira/browse/OFBIZ-9459?page=com.
>> atlassian.jira.plugin.system.issuetabpanels:comment-tabpane
>> l=16080188#comment-16080188 ]
>>
>> Jacques Le Roux commented on OFBIZ-9459:
>> 
>>
>> Hi Arun, I noticed that, like few other issues (at least OFBIZ-9473,
>> OFBIZ-9316, OFBIZ-9317) that you did not backport this bug. Is there a
>> reason? Do you want me to do it? Thanks.
>>
>> Wrong screen redirection after adding note on Lead profile screen
>>> -
>>>
>>>  Key: OFBIZ-9459
>>>  URL: https://issues.apache.org/jira/browse/OFBIZ-9459
>>>  Project: OFBiz
>>>   Issue Type: Bug
>>>   Components: marketing
>>> Reporter: Jagpreet Kaur
>>> Assignee: Arun Patidar
>>>  Fix For: Upcoming Release
>>>
>>>  Attachments: Create Note.png, OFBIZ-9459.patch,
>>> Screenredirection.png
>>>
>>>
>>> 1) Go to SFA component.
>>> 2) Click on Leads tab [https://demo-trunk-ofbiz.apac
>>> he.org:8443/sfa/control/FindLeads|https://demo-trunk-ofbiz.
>>> apache.org:8443/sfa/control/FindLeads].
>>> 3) Choose any partyId from All Lead list, you will be navigated to Lead
>>> profile. [https://demo-trunk-ofbiz.apache.org:8443/sfa/control/viewpr
>>> ofile?roleTypeId=LEAD=DemoLead|https://demo-trunk-
>>> ofbiz.apache.org:8443/sfa/control/viewprofile?roleTypeId
>>> =LEAD=DemoLead]
>>> 4) Click on "Create New" button in the Notes section.
>>> 5) Add the Note content.
>>> 6) Click on "Save Button".
>>> View redirection should be profile but it shows the blank screen.
>>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.4.14#64029)
>>
>
>
>

Re: Deadlock on InventoryItem during load test

2017-07-12 Thread Arun Patidar 
Hello Taher,

Created a JIRA ticket OFBIZ-9491
 and added some more
details.

-- 
Thanks & Regards
---
Arun Patidar
Manager, Enterprise Software Development


HotWax Systems Pvt Ltd.www.hotwaxsystems.com


On Wed, Jul 12, 2017 at 5:45 PM, Arun Patidar <
arun.pati...@hotwaxsystems.com> wrote:

> Thanks Taher for showing interest. I will create a Jira issue with more
> details and share it with you.
>
> --
> Thanks & Regards
> ---
> Arun Patidar
> Manager, Enterprise Software Development
>
>
> HotWax Systems Pvt Ltd.www.hotwaxsystems.com
>
>
> On Wed, Jul 12, 2017 at 4:12 PM, Taher Alkhateeb <
> slidingfilame...@gmail.com> wrote:
>
>> If there is a JIRA with exact repeat steps then I would be interested
>> in working on this issue as it sounds like a good place to do some
>> proper refactoring on many moving parts.
>>
>> On Wed, Jul 12, 2017 at 12:08 PM, Arun Patidar
>>  wrote:
>> > Hello All,
>> >
>> > I was trying to load test OFBiz with huge numbers of order creation and
>> > fulfilment. During test, I found a deadlock on InventoryItem enttiy.
>> > Current system, invoke 'UpdateInventoryItemFromDetail' service to
>> update
>> > InventoryItem QOH total and ATP total record. There is an Eca rule on
>> > create/update of InventoryItemDetail entity record which triggers
>> service
>> > 'UpdateInventoryItemFromDetail'. So, with heavy load, InventoryItem
>> record
>> > get lock and create deadlock condition.
>> >
>> > I know that most of you are already aware with this issue. Please let me
>> > know if someone worked on it and have any idea to avoid this type of
>> > deadlock.
>> >
>> > --
>> > Thanks & Regards
>> > ---
>> > Arun Patidar
>> > Manager, Enterprise Software Development
>> >
>> >
>> > HotWax Systems Pvt Ltd.www.hotwaxsystems.com
>>
>
>

Re: Deadlock on InventoryItem during load test

2017-07-12 Thread Arun Patidar 
Thanks Taher for showing interest. I will create a Jira issue with more
details and share it with you.

-- 
Thanks & Regards
---
Arun Patidar
Manager, Enterprise Software Development


HotWax Systems Pvt Ltd.www.hotwaxsystems.com


On Wed, Jul 12, 2017 at 4:12 PM, Taher Alkhateeb  wrote:

> If there is a JIRA with exact repeat steps then I would be interested
> in working on this issue as it sounds like a good place to do some
> proper refactoring on many moving parts.
>
> On Wed, Jul 12, 2017 at 12:08 PM, Arun Patidar
>  wrote:
> > Hello All,
> >
> > I was trying to load test OFBiz with huge numbers of order creation and
> > fulfilment. During test, I found a deadlock on InventoryItem enttiy.
> > Current system, invoke 'UpdateInventoryItemFromDetail' service to update
> > InventoryItem QOH total and ATP total record. There is an Eca rule on
> > create/update of InventoryItemDetail entity record which triggers service
> > 'UpdateInventoryItemFromDetail'. So, with heavy load, InventoryItem
> record
> > get lock and create deadlock condition.
> >
> > I know that most of you are already aware with this issue. Please let me
> > know if someone worked on it and have any idea to avoid this type of
> > deadlock.
> >
> > --
> > Thanks & Regards
> > ---
> > Arun Patidar
> > Manager, Enterprise Software Development
> >
> >
> > HotWax Systems Pvt Ltd.www.hotwaxsystems.com
>

Re: Deadlock on InventoryItem during load test

2017-07-12 Thread Taher Alkhateeb 
If there is a JIRA with exact repeat steps then I would be interested
in working on this issue as it sounds like a good place to do some
proper refactoring on many moving parts.

On Wed, Jul 12, 2017 at 12:08 PM, Arun Patidar
 wrote:
> Hello All,
>
> I was trying to load test OFBiz with huge numbers of order creation and
> fulfilment. During test, I found a deadlock on InventoryItem enttiy.
> Current system, invoke 'UpdateInventoryItemFromDetail' service to update
> InventoryItem QOH total and ATP total record. There is an Eca rule on
> create/update of InventoryItemDetail entity record which triggers service
> 'UpdateInventoryItemFromDetail'. So, with heavy load, InventoryItem record
> get lock and create deadlock condition.
>
> I know that most of you are already aware with this issue. Please let me
> know if someone worked on it and have any idea to avoid this type of
> deadlock.
>
> --
> Thanks & Regards
> ---
> Arun Patidar
> Manager, Enterprise Software Development
>
>
> HotWax Systems Pvt Ltd.www.hotwaxsystems.com

Deadlock on InventoryItem during load test

2017-07-12 Thread Arun Patidar 
Hello All,

I was trying to load test OFBiz with huge numbers of order creation and
fulfilment. During test, I found a deadlock on InventoryItem enttiy.
Current system, invoke 'UpdateInventoryItemFromDetail' service to update
InventoryItem QOH total and ATP total record. There is an Eca rule on
create/update of InventoryItemDetail entity record which triggers service
'UpdateInventoryItemFromDetail'. So, with heavy load, InventoryItem record
get lock and create deadlock condition.

I know that most of you are already aware with this issue. Please let me
know if someone worked on it and have any idea to avoid this type of
deadlock.

-- 
Thanks & Regards
---
Arun Patidar
Manager, Enterprise Software Development


HotWax Systems Pvt Ltd.www.hotwaxsystems.com