[
https://issues.apache.org/jira/browse/OFBIZ-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623419#comment-13623419
]
Adrian Crum commented on OFBIZ-5169:
Varun,
Thank you for getting started on this.
Jacques,
What are your requirements? What are you looking for in the logs?
-Adrian
On 4/4/2013 10:54 PM, Jacques Le Roux wrote:
These numbers are from experience of hours and hours staring at clusters logs,
but yes it's arbitrary and depend on context (as I guess were picked the
initial numb
[
https://issues.apache.org/jira/browse/OFBIZ-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623393#comment-13623393
]
Jacopo Cappellato commented on OFBIZ-5169:
--
Using ArrayList, rather than LinkedLi
[
https://issues.apache.org/jira/browse/OFBIZ-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623373#comment-13623373
]
Jacques Le Roux commented on OFBIZ-5168:
Ha ok, then I agree
> Un
[
https://issues.apache.org/jira/browse/OFBIZ-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Bhansaly updated OFBIZ-5169:
--
Attachment: framework-FastList-removed.patch
This patch removes all instances of FastList and r
[
https://issues.apache.org/jira/browse/OFBIZ-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Bhansaly updated OFBIZ-5169:
--
Summary: Removing Javolution from framework components (was: Removing
Javolution from framewor
Varun Bhansaly created OFBIZ-5169:
-
Summary: Removing Javolution from framework
Key: OFBIZ-5169
URL: https://issues.apache.org/jira/browse/OFBIZ-5169
Project: OFBiz
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/OFBIZ-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622868#comment-13622868
]
Adrian Crum commented on OFBIZ-5168:
I tend to believe the entity engine when it tells
These numbers are from experience of hours and hours staring at clusters logs,
but yes it's arbitrary and depend on context (as I guess were picked the
initial numbers which are there for years
Then why not the obvious solution Jacopo proposed of properties, easy to change
even dynamically...
I
[
https://issues.apache.org/jira/browse/OFBIZ-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622829#comment-13622829
]
Jacques Le Roux commented on OFBIZ-5168:
Adrian,
Those are not errors and I belie
Adrian Crum created OFBIZ-5168:
--
Summary: Unexpected Errors Logged While Running Unit Tests
Key: OFBIZ-5168
URL: https://issues.apache.org/jira/browse/OFBIZ-5168
Project: OFBiz
Issue Type: Bug
While you are at it, we can fix it. Can you please check if the changes
suggested in the diff below are satisfactory. The additional comments are
just to explain the changes and are not meant to be committed.
Index: framework/service/src/org/ofbiz/service/ServiceDispatcher.java
=
I agree that bit of code is messy and confusing.
if ((Debug.verboseOn()...
...
Debug.logTiming(...
Huh? Shouldn't that be
Debug.logVerbose(...
?
If I have verbose on and timing off, then I will never see the log messages.
I really don't understand all of this complicated decision-making
On Apr 4, 2013, at 12:25 PM, Adrian Crum
wrote:
> No, please don't think I'm being adversarial or dismissive. This is a good
> discussion, and I appreciate your input.
That's great Adrian, thank you... and thanks to you I am also learning a lot of
new English words :-)
Jacopo
On 4/4/2013 11:18 AM, Jacopo Cappellato wrote:
On Apr 4, 2013, at 11:27 AM, Adrian Crum
wrote:
Isn't that what the next block of code does? If you want to have a message that
appears based on a set of conditions, then you can fuss around with the if
statement that follows the timing messag
On Apr 4, 2013, at 11:27 AM, Adrian Crum
wrote:
> Isn't that what the next block of code does? If you want to have a message
> that appears based on a set of conditions, then you can fuss around with the
> if statement that follows the timing message.
Yeah, of course everyone can easily add
Isn't that what the next block of code does? If you want to have a
message that appears based on a set of conditions, then you can fuss
around with the if statement that follows the timing message.
-Adrian
On 4/4/2013 9:58 AM, Jacopo Cappellato wrote:
This would be resolved by changing the me
This would be resolved by changing the message into something that clarifies
that the service took longer than a given threshold X; in this case the message
would be clear and could be useful to the new user (even if of course a message
based on a threshold is kind of arbitrary and doesn't tell
Having a condition like that is unfair to end users.
Let's say I'm a new OFBiz user. I just wrote my first service and I try
it out. I run the service, and check the logs. Weird - the service
engine says my service didn't run. I check my data - it appears the
service ran. I put some logging me
I agree it is arbitrary and sub-optimal solution but maybe I still liked it
more before the last commit: the risk now is that we have too much information
and no one will ever look at it.
The obvious workaround could be to set the threshold in a property file but
there are probably better soluti
Why not 20 or 30 or 40?
That's the problem with arbitrary values - they don't mean anything.
From my perspective, if anyone has timing enabled, then they want to
see what's going on in the system.
Feel free to change it.
-Adrian
On 4/3/2013 9:22 AM, Jacques Le Roux wrote:
Hi Adrian, All,
21 matches
Mail list logo
