strange.
When I look on the code it seems that it definitely could NOT be the case that
the EMF is not correctly bound to the JNDI tree as the method
OpenJPAEntityManagerFactory createEntityManagerFactory does no create for
itself.
So somehow the EMF must be bound to the JNDI tree but neverth
My original thought with the code changes is that when the SystemClassLoader
is returned, the processing is no worse than it was before the change.
Granted, it's no better either, but I was focused on the Container-managed
environment...
Marc's suggestion would seem to resolve the issue by provid
> Want me to commit this change?
Go for it.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and
Hi,
What's the word on this issue?
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affilia
What's the word on this issue?
Last record I have is:
Okay, I think we need to back out these last two changes and revert
back to
revision 509885. Dave needs to go back to the drawing board for
this "db2
optimization" change, probably create a JIRA report for this proposed
change, and us
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476219
]
Craig Russell commented on OPENJPA-160:
---
Sweet. The ObjectValue.InstanceFactory is the technique I was going t
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476225
]
Craig Russell commented on OPENJPA-160:
---
As you've coded it, each instance of ObjectValue gets its own Map. Do
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476228
]
John Stecher commented on OPENJPA-160:
--
Patrick - I'll pull your patch and we'll test it out here today on the
> Would it be helpful if I provide the output of
> "Thread.dumpStack()" within
> the invocation of my PersistenceService.getEntityManager() method?
No -- that'll just provide info about your environment. But looking at your
logs in more detail, I'm curious about what your PersistenceService meth
[
https://issues.apache.org/jira/browse/OPENJPA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476232
]
John Stecher commented on OPENJPA-134:
--
I think the links to the mailing list post that Kevin has shows a good
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476234
]
Patrick Linskey commented on OPENJPA-160:
-
> Patrick - I'll pull your patch and we'll test it out here today
> But maybe something funky is happening with JNDI serializing the factory and
> then deserializing it or something.
>From J2EE 1.4 spec, page 59 (J2EE.5.2 Java Naming and Directory Interface:
In general, lookups of objects in the JNDI java: namespace are required to
return a new instance of
Yes, this is a possibility. However, currently, the logging makes it look like
the PersistenceService class is running through logic that identifies that it
needs to create a new instance.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
_
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476295
]
Craig Russell commented on OPENJPA-160:
---
>I put a Map in place to get around any ClassLoader issues. In the co
I have backed out the original changes via svn revision 512327 -- just did
it this morning. Dave will create a JIRA report for this optimization so
that we can work through the issues and then we'll integrate a new set of
changes.
Kevin
On 2/22/07, Abe White <[EMAIL PROTECTED]> wrote:
> 3. Op
All-
I noticed recently that the continuum build at http://
vmbuild.apache.org/continuum is back up and running again (hooray!).
However, it is failing for OpenJPA because we have a new sub-module,
called "openjpa-examples", which I believe needs to be explicitly
added as a module to Conti
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-160:
Attachment: openjpa-160-patch.txt
Craig identified a problem with the patch; after talking
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar resolved OPENJPA-151.
---
Resolution: Fixed
Fixed with SVN revision 511998: http://svn.apache.org/viewvc?view=rev&rev=
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Russell reassigned OPENJPA-160:
-
Assignee: Patrick Linskey
> Reuse BrokerImpl objects
>
>
>
If no one replies, I'd post it to [EMAIL PROTECTED] and see
if anyone over there knows the magic.
Craig
On Feb 27, 2007, at 11:16 AM, Marc Prud'hommeaux wrote:
All-
I noticed recently that the continuum build at http://
vmbuild.apache.org/continuum is back up and running again
(hooray!).
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Stecher updated OPENJPA-160:
-
Attachment: newprofile.jpg
Profile with ObjectValue factory.
> Reuse BrokerImpl objects
> -
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476324
]
John Stecher commented on OPENJPA-160:
--
Our profile is with the first patch.
> Reuse BrokerImpl objects
>
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476320
]
John Stecher commented on OPENJPA-160:
--
Patrick - Tested the patch and it has the same performance as the origi
[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476328
]
Sherry Shen commented on OPENJPA-94:
With openjpa-0.9.7-incubating-SNAPSHOT on 2/26/2007 nightly, I have tried
I know that Mike has some Continuum experience, but he's out sick today...
On 2/27/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
All-
I noticed recently that the continuum build at http://
vmbuild.apache.org/continuum is back up and running again (hooray!).
However, it is failing for OpenJ
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476333
]
John Stecher commented on OPENJPA-160:
--
Tested the second patch but basically the same thing WRT performance.
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476321
]
Craig Russell commented on OPENJPA-160:
---
For the record, the new patch changes a couple of things. The factory
[
https://issues.apache.org/jira/browse/OPENJPA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sutter resolved OPENJPA-138.
--
Resolution: Fixed
Code changes per Issue comments are complete.
> More performance improvemen
[
https://issues.apache.org/jira/browse/OPENJPA-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sutter resolved OPENJPA-141.
--
Resolution: Fixed
Code changes complete per comments in Issue.
> More performance improvement
[
https://issues.apache.org/jira/browse/OPENJPA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sutter resolved OPENJPA-139.
--
Resolution: Fixed
Code changed per Issue comments via SVN revision 505099.
> PersistenceExcep
[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476336
]
Patrick Linskey commented on OPENJPA-94:
What happens if you do:
> Allow MappingTool and persiste
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476335
]
Patrick Linskey commented on OPENJPA-160:
-
Hmm. I don't get it. The only thing in newInstance() is 'new Brok
[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476341
]
Sherry Shen commented on OPENJPA-94:
When I use
my test failed to run with error,
Caused by: java.u
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476343
]
Patrick Linskey commented on OPENJPA-160:
-
Assuming that field initializations aren't being counted in , the
[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476347
]
Patrick Linskey commented on OPENJPA-94:
Hmm sounds like maybe you need to do more backslash-escaping?
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476351
]
John Stecher commented on OPENJPA-160:
--
All performance throughput numbers are run without the profiler on a 2-
[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476352
]
Abe White commented on OPENJPA-94:
--
Single quotes should work -- no need to use escaped double quotes.
> Allow Mapp
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476353
]
Craig Russell commented on OPENJPA-160:
---
The real cost according to the trace is in the dynamically created cl
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476359
]
Abe White commented on OPENJPA-160:
---
FYI, at the bytecode level all field initializations take place in . A
prof
[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476367
]
Sherry Shen commented on OPENJPA-94:
This one works.
However, it doesn't work if deleteTableContents is
[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476374
]
Patrick Linskey commented on OPENJPA-94:
> However, it doesn't work if deleteTableContents is replaced with
[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476376
]
Patrick Linskey commented on OPENJPA-94:
> However, it doesn't work if deleteTableContents is replaced with
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-160:
Attachment: openjpa-160-patch.txt
New version to resolve conflict with Kevin Sutter's chan
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476391
]
John Stecher commented on OPENJPA-160:
--
Patrick what is in the new version? Not sure what Sutter's conflict is
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476390
]
John Stecher commented on OPENJPA-160:
--
Craig - I will try to get it coded up this afternoon. Got side tracked
I've got it coded up and am running sanity tests. I'll post the new
patch as soon as I verify I didn't break anything obvious.
Craig
On Feb 27, 2007, at 1:11 PM, John Stecher (JIRA) wrote:
[ https://issues.apache.org/jira/browse/OPENJPA-160?
page=com.atlassian.jira.plugin.system.issuet
Yeah, that's pretty much what we do most of the time also. For the code
in question, I don't think that it's relevant though.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any att
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476393
]
Patrick Linskey commented on OPENJPA-160:
-
> Patrick what is in the new version? Not sure what Sutter's conf
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476396
]
Abe White commented on OPENJPA-160:
---
> The last time I looked at bytecode in depth (it's been a while) the field
Not sure if this is relevant, but normally, I use explicit, thread
and then system.
-dain
On Feb 26, 2007, at 10:52 PM, Marc Prud'hommeaux wrote:
How about just assigning cl = ClassLoader.getSystemClassLoader()
(which will hopefully never be null) when cl is null?
On Feb 27, 2007, at
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Wisniewski updated OPENJPA-160:
---
Attachment: profile_explicitclass.jpg
I went ahead and made the change that Craig suggested
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476423
]
Patrick Linskey commented on OPENJPA-160:
-
Did you guys get a chance to try setting the ClassLoader field to
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Russell updated OPENJPA-160:
--
Attachment: openjpa-160-patch.txt
This patch uses a regular class instead of an anonymous inne
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476431
]
Rob Wisniewski commented on OPENJPA-160:
Craig -- I coded up pretty much exactly what you have and it didn't
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476433
]
Craig Russell commented on OPENJPA-160:
---
Rob -- thanks, our coding passed in the mail.
All -- WTF?
> Reuse B
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476438
]
John Stecher commented on OPENJPA-160:
--
So here is a thought. Basically this benchmark is performing 5 interac
We had a similar issue with the JDO Reference Implementation. What we
ended up with was implementing the naming.Referenceable interface and
writing our own externalization protocols that basically allowed the
container to create new instances of our Factory that were actually
trivial wrappe
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476470
]
Craig Russell commented on OPENJPA-160:
---
A few questions and a comment.
1. Is the profiling capturing CPU tim
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476471
]
Patrick Linskey commented on OPENJPA-160:
-
So the only thing that I think is left to try to control is the f
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476472
]
Patrick Linskey commented on OPENJPA-160:
-
We can easily get rid of the finalizer for the purposes of explor
The JNDI spec says: "the container knows that the application can't change the
state of the object."
How does one tell the container that the JNDI-bound instance is one such
'application immutable' object?
> What we ended up with was implementing the naming.Referenceable interface
Did the JDO
Hi Pinaki,
On Feb 27, 2007, at 5:06 PM, Pinaki Poddar wrote:
The JNDI spec says: "the container knows that the application
can't change the state of the object."
How does one tell the container that the JNDI-bound instance is one
such 'application immutable' object?
What we ended up with
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476502
]
John Stecher commented on OPENJPA-160:
--
Craig 1) We are using the CPU sampling feature of the profiler to not s
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476520
]
Patrick Linskey commented on OPENJPA-160:
-
In our situation, cloning might not be a nightmare, as almost all
>> -The name used for the lookup is defined to return an instance of the
>> object that might be shared. The name java:comp/ORB is such a name.
does this mean that the name/key with which the EMF is bound into JNDI
affects the sharing/non-sharing of the bound instance?
currently the JNDI-string
If you could send the source for PersistenceService, and details about how you
invoke it if the method takes any arguments, that would be very useful.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email mess
please see below. The method PersistenceService.getEntityManager() is
invoked directly in SLSB's methods if access to the EM is needed, so there
could be multiple invocations within a single transaction spanning multiple
SLSB methods.
hth,
Hans
public class PersistenceService {
private st
67 matches
Mail list logo
