Java and lazy loading

Hello all!
I have three question regarding lazy loading:
Question one: Can it be said that java works by lazy loading by default?
Question two: What is the opposite of lazy loading?
Question three: How can I change this default behavior to the opposite of lazy loading?
Thanks in advance,
Julien.

1. Yes.
2. Eager loading.
3. You can't. You can get a half-decent approximation using a suitable classloader, though. After defining your class, you parse the string table and load the classes referred to therein. BCEL may useful for the parsing.

Similar Messages

SAP JPA and lazy loading

Dear experts,
I have a WD application with EJB model. I have faced strange JPA exception (I am using SAP JPA implementation).
This is 2 Entities with relationship
@Entity
@Table( schema = "dbo", name = "class")
public class ClassEntity {
private Long id;
        @Id
     @Column(name="id")
     @GeneratedValue(strategy= GenerationType.IDENTITY)
    public Long getId() {
          return id;
     public void setId(Long id) {
          this.id = id;
private Collection<ClassAttributeEntity> classAttributesById;
    @OneToMany(mappedBy = "classByClassId", fetch=FetchType.LAZY)
    public Collection<ClassAttributeEntity> getClassAttributesById() {
        return classAttributesById;
    public void setClassAttributesById(Collection<ClassAttributeEntity> classAttributesById) {
        this.classAttributesById = classAttributesById;
@Entity
@Table( schema = "dbo", name = "class_attribute")
public class ClassAttributeEntity{
private Long id;
        @Id
     @Column(name="id")
     @GeneratedValue(strategy= GenerationType.IDENTITY)
    public Long getId() {
          return id;
     public void setId(Long id) {
          this.id = id;
    private ClassEntity classByClassId;
    @ManyToOne
    @JoinColumn(name = "class_id", referencedColumnName = "id")
    public ClassEntity getClassByClassId() {
        return classByClassId;
    public void setClassByClassId(ClassEntity classByClassId) {
        this.classByClassId = classByClassId;
I want to execute JPQL query
"SELECT c FROM ClassEntity c"
; But I get this exception:
javax.persistence.PersistenceException: The relationship >>classAttributesById<< of entity {test.ClassEntity(id=1686)}cannot be loaded because the entity is detached
I can overcome it using EAGER loading -
@OneToMany(mappedBy = "classByClassId", fetch=FetchType.EAGER)
, but I really dont need ClassAttributes in this situation! I have many thousands of classes and eager loading provides extremly poor perfomance. What can I do with this problem?
Thanks in advance for any advice.

Hi Andrey,
I assume you are getting the exception if you atempt to access "classAttributesById" ouside the transaction, in which you executed the query, i.e. after the persistence context, in which the query has been executed is closed.
You have got to make sure that all entities you need to access are read as long as the persistence context executing the query is still open.
How to address this depends a bit on whether you need to access all related entites or only some.
If you need to access the relationship "classAttributesById" for only some instances of "ClassEntity", you could for example call size() on "classAttributesById" for these selected instances of "ClassEntity" (within the same transaction/persistence context".
If you need to access all related entities, theoretically, fetchType = EAGER would be the right choice. However, as you have observed, SAP JPA can't handle this efficiently at the time beeing. Therefore,
I'd rather suggest that you firstly load all related attributes with a query
"SELECT ca FROM ClassAttributeEntity ca"
and secondly load the "ClassEntity"s
"SELECT c FROM ClassEntity c"
this should execute efficiently.
Sorry for the inconvenience.
-Adrian

Equals and lazy loading

Hi all,
We have an application in which we use lazy loading on our client, so we can't be sure that both objects have the same objects reference loaded already. While implementing the equals method I came to the problem if it makes sense to compare the lazy loaded objects as well, because this might lead to a very deep object comparison through the whole object tree which might be very unperformant if I load this references on demand. Otherwise not comparing the references might be an incomplete comparision of these objects and makes the usage of the equals method very difficult.
Has anyone experience using the equals method with lazy loading?
Thanks in advance
Marco

Okay - here comes a little more detail about our architecture to give you a deeper understanding. Currently we are working with EJB3 / JBoss environment but our intention is to encapsulate this through a DAO-layer. Anyways we have special object-dependencies as per example a customer has it�s orders. So in my understanding a customer with the an address, a name etc. with NO orders is not the same as a customer with the same address and the same name and let�s say 2 orders. So I can stick with comparing simply the name and the address, but this wouldn�t give you an exact comparison.
The other way would be to compare the orders as well, but what if the orders have a number of invoices behind them. The conclusion would be, that I�d have to compare them as well. Additionally I have the problem, that I have totally equal customers with the same number of orders and invoices, but the first one has a null-value in its orders, because they have not been loaded from database yet and the other one has. So my technique with comparing the lazy-loaded references would not work here. A complete loading of all references for a comparison cannot be the solution here either.
So it is hard to say if they are I/O intensive. Worst case would be, that we have to load the complete object-tree for comparison from database and send them between client and server (jboss). This is part of our question? Should this be the consequence of lazy loading or is it best pratice to stick with the local attributes and let the client do the work, so that he has to work through the whole object-tree if he wants to know the exact equality.
Does this give you a more detailled view of our question? I guess I am not the first to deal with this problem, so I�d like to share your experiences with you about what is "wise" to do.
Thanks for your help
Marco

Vo initialization and lazy loading.

I need to execute some initialization work then a VO is loaded.
To do that work I need the AM and then I can't do this work in constructor.
My implementation was realized doing that work in the AM prepareSession method wich loops all VO and execute an init method : all works OK.
Now my project is growing up and the load time is very long then I thought I can use lazy loading.
Doing that, however, my initialization proces fails because in prepare session no Vo is present and then I don't know when the VO is loaded.
Is there any event in VO called when the VO is loaded ?
Could someone suggest a cleaner solution to my initialization problem ?
Tks
Tullio

Maybe you could try to intercept findViewObject() in the AM, keep track of the not initialized VOs and perform the initialization stuff for a VO first time it is used (i.e., when created).
Nevertheless, this is not easy management in lazy loading - you will have to "manually" load related objects (i.e., VLs).
In 9.0.3/9.0.4 we finally gave up. Didn't check if in 9.0.5 this behaves better...
HTH,
Adrian

Issues with Java and not loading correctly

Hoping someone can help. I've recently loaded the latest revision of Java from the Java website, however when I try to validate the installation using the Java Validate page or try other Java enabled pages, I get a General Exception Error or the normal RED X and no applet.
I'm getting this error (I've tried changing the internet options, script running, enabling Java, Connection methods etc and nothing)
Sorry - cant find the exact error at the moment, but something like
JBM.Class not found (Exception Error). Java seems to install OK, but it's almost as though it is not install properly and the registry is wrong?
Hope someone can help as it's frustrating!

If you want assistance, you need to provide exact details of the problem, and the code involved. A general statement/information is of no value.
Read about classpath usage, and how Java finds classes, here:
http://java.sun.com/j2se/1.5.0/docs/tooldocs/index.html#general
The information you need is contained therein - if the problem is that Java is not finding a class.

Tour de Flex Sample - Managing Associations and Lazy Loading - 13800

comments

For that number of sections, you may want to consider leveraging an MVC framework like Mate ( http://mate.asfusion.com/ ). Mate (and, in general, most MVC frameworks) is more about application structure than application layout, but it provides some really useful guidelines for organizing your code for maintainability and testability. Mate even has a Google Code project of example applications: http://code.google.com/p/mate-examples/ .

Lazy Loading, Muse, and Scripts

Hi, I'm trying to integrate Lazy loading with Muse in a Web Site.
I would like know if anyone has a better workflow...
So, first I uploaded to the server the "lazy loading content"
http://dandalo.net/teste/lazy-patricia/lazy-pat.html
Then, in Muse, I inserted the html from the page source that I had uploaded.
http://dandalo.net/teste/export-muse/detalhes-old.html
But it didn't work... : (
So...
I have started looking at the html code that Muse created and fond this special phrase... 
Then, I tried this:
Coping the scripts from the "lazy loading content" page and pasting it after this special line:
http://dandalo.net/teste/export-muse/detalhes.html
And it Worked !!!
PS: The java scrips should be in root folder, not in the Scripts folder that Muse created
Does anyone have any tip or workflow not to have to edit the html file to add these script lines?

Hi
Do you have the link to the "lazy loading content"?
I can't find a proper way to do it.
Thanks

Toplink JPA LAZY loading in Java SE works without javaagent?

hi there,
I tought that mappings like
@JoinColumn(name = "join_col_name")
@ManyToOne(cascade=CascadeType.ALL, fetch=FetchType.LAZY)
private RelatedObject relObj;
with TopLink JPA in Java SE environment works ONLY with the
-javaagent:toplink-essentials-agent.jar
JVM parameter?
the strange thing is: I did 2 test runs, with and without the java agent parameter. I also could see that in the first case the weaver is working, in the second the property "toplink.weaving=false" is printed to the console BUT if I access the LAZY mapped attribute of the object instance it works in both cases - I expected a NullPointerEx. in the case without the javaagent.
Is there anything I missed?
Hans

Chris,
thank for for the tip about verifying lazy or eager fetching. The results are interesting - or better: confusing - to me:
I have built a test project with 3 entities:
Entity A hast @OneToMany to Entity B and
Entity B has ManyToONe to Entity C
A <-- B --> C
ALL relations are marked with FetchType.LAZY in all directions.
When I simply run the test project via main()-method out of eclipse, WITHTOUT specifycing a -javaagent parameter in the run dialog, I can confirm using your test case that the realtion IS LAZILY FETCHED.
So, I do not really know how this should work without the javaagent.
You mentioned statically weaved classed - is this the default case when no agent is present, how is it done? Toplink logging says that weaving is NOT active:
ServerSession(16821027)--Thread(Thread[main,5,main])--property=toplink.weaving; value=false
so how can the lazy loading work then?
regards,
Hans

Lazy loading, EntityManager and concurrency.

I need advice which strategy to use with lazy loading.
My project is based on Spring, Struts 2 and Hibernate JPA. I have enough OneToMany and ManyToMany relationships and it's reasonable to use lazy loading. It seems very convenient to load data in Struts Actions with OpenEntityManagerInViewFilter in such way like:
Style style = user.getStyle()
But to avoid LazyLoadException I have to use:
@PersistenceContext(type=PersistenceContextType.EXTENDED)
Unfortunately, EntityManager in this case becomes not thread-safe, according to Spring docs: "+Extended EntityManagers are not thread-safe, hence they must not be used in concurrently accessed beans (which Spring-managed singletons usually are).+" EXTENDED means that EntityManager is shared in user session and my EntityManager is injected in singleton services.
I've found this issue when tried to make quick sequential page reloading which call some selects and got:
java.sql.SQLException: You can't operate on a closed Statement!!!
What's the best practice in this situation:
1. Try synchronize session access to EntityManager by myself or put each user database requests in separate queue (something terrible I suppose).
2. Use HQL queries with join fetch to preload data for access outside of transaction (maybe overhead).
3. Or something else???
And why we need EXTENDED context if it's so unreliable??
Thanks for help!

Hi
Do you have the link to the "lazy loading content"?
I can't find a proper way to do it.
Thanks

JDev 11.1.2.3.0 and ADF Hierarchy Viewer - Lazy Loading?

Hi,
I have a simple application that shows data from one table using the Hierarchy Viewer component.
My table has more than 100,000 rows.
It appears that the control tries to query all data at once and never loads.
I have reduced the number of rows to 5K and it works.
So, is there a way that I can configure the control/application to only retrieve data from the database for a particular node, when a node is expanded?
thanks for your help.

Thanks,
I changed the Hierarchy Viewer's property called "Content Delivery" to lazy.
This is found in the Behavior section.
That appears to have resolved the issue.

How to use Lazy and Eager loading dynamically

Hi
I am using JPA.I have a table which has one to many realtionship with another table. I want lazy loading by default and eager loading in a speciific case.
Can we change this fetch type at the time of query?
Thanks
Sateesh

In EclipseLink 2.1 there is also a LoadPolicy that allows a relationship to be loaded on a query.
query.setHint("eclipselink.load-group.attribute", "d.employees");
The difference between it and fetch, is that it is loaded normally (or as configured) not fetch joined.
James : http://www.eclipselink.org

EJB Class loader and regular Java files class loader.

Hi,
Is the EJB's class loader the same as a "regular" java files class loader OR weblogic
has 2 class loaders, one for each???
Thanks,
les.

les <[email protected]> wrote:
Hi,
Is the EJB's class loader the same as a "regular" java files class loader OR weblogic
has 2 class loaders, one for each???Yes. Exact classloading architecture depends on which WebLogic version you use. If you
use 6.x+, you may want to read this article:
http://www.onjava.com/pub/a/onjava/2001/07/25/ejb.html
Thanks,
les.--
Dimitri

It doesn�t work lazy loading with remote client (toplink)

I am trying to use lazy loading in a @ManyToOne field but I get an exception. I have been reading in some oracle tutorials that it's necesary use -javaagent:.../lib/toplink-essentials-agent.jar for that it works because this argument activate dynamic weaving in JavaSE. I have put this command line argument javaagent but it doesn't work. Why? Can I have to do another thing? I have done a lot of tests in base to comments read in another forums but I only obtains an exception.
Caused by: java.io.IOException: Mismatched serialization UIDs
NOTE: The server use toplink and the remote client query the entitties through a session bean of the server. Besides, I am using Glassfish (Sun application server and toplink).
Thanks in advance.
hayken

At first, thank you for your reply.
I know that I haven´t explained the problem too well. I have a stateless bean with one remote method that execute a query an returns an entity like this
@Entity
public class ModuloEntity extends Serializable
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long idModulo;
private String nombre;
@ManyToOne(fetch=FetchType.LAZY)
@JoinColumn(name="IdProyecto")
private ProyectoEntity proyecto;
The remote client invoke this method and in that moment I get this exception.
21-may-2007 18:55:48 com.sun.corba.ee.impl.encoding.CDRInputStream_1_0 read_value
ADVERTENCIA: "IOP00810211: (MARSHAL) Exception from readValue on ValueHandler in CDRInputStream"
org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 211 completed: Maybe
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.valuehandlerReadException(ORBUtilSystemException.java:7053)
Caused by: java.io.IOException: Mismatched serialization UIDs : Source (Rep. IDRMI:com.syskonic.gesplan.entities.ModuloEntity:6D06A8C14D488FFF:8E6FC8687EA9E512) = 8E6FC8687EA9E512 whereas Target (Rep. ID RMI:com.syskonic.gesplan.entities.ModuloEntity:1C6925798CDFD3DF:3455DBF4457AE337) = 3455DBF4457AE337
at com.sun.corba.ee.impl.util.RepositoryId.useFullValueDescription(RepositoryId.java:573)
If I look the server log, I can see that the call has not been produced, it doesn´t show any exception. It looks that the object managed by the server and the remote client aren´t the same and the corba service doesn´t work when remote client call session method. If I change the ModuloEntity and remove the fetch attribute then all this process executes correctly. The problem is in this attribute.
NOTE: I am using the javaagent command line argument.
Hayken

Facing problem with lazy loading in ejb3.0

The following error is coming up when i try to access the collection in the entity entity bean. i am using entitymanager.find() to retrieve the entity. intial set of values are coming fine but when try to access the collection in the entity the error is coming up. one solution is to make the fetch type=eager. but can we do lazy loading with out any problem. the following is the error. kindly help me in this. do i need to do anything extra that mean have to add any annotations or anything.
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.lucid.erp.entities.EmployeeDTO.addresses, no session or session was closed
     at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:358)
     at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:350)
     at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:343)
     at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86)
     at org.hibernate.collection.PersistentBag.get(PersistentBag.java:422)
     at com.lucidlabs.erp.actions.EmployeeAction.view(EmployeeAction.java:20)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:404)
     at com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:267)
     at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:229)
     at com.opensymphony.xwork2.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:221)
     at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at com.opensymphony.xwork2.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:150)
     at org.apache.struts2.interceptor.validation.AnnotationValidationInterceptor.doIntercept(AnnotationValidationInterceptor.java:48)
     at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at com.opensymphony.xwork2.interceptor.ConversionErrorInterceptor.intercept(ConversionErrorInterceptor.java:123)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:184)
     at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at com.opensymphony.xwork2.interceptor.StaticParametersInterceptor.intercept(StaticParametersInterceptor.java:105)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at org.apache.struts2.interceptor.CheckboxInterceptor.intercept(CheckboxInterceptor.java:83)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at org.apache.struts2.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:207)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at com.opensymphony.xwork2.interceptor.ModelDrivenInterceptor.intercept(ModelDrivenInterceptor.java:74)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at

this is transactions 101 material. Do you know about transactions and how they work? Do you know about managed entities?
The problem you are having is that the addresses are accessed outside of the transaction in which the entity was fetched. That means there is no more database session and thus the lazy fetch cannot work. If you really need the addresses, you can at least force fetch them by calling getAddresses().size() right after you fetch the entity from the database; assuming that the transaction is still active at that point.

ConcurrentModificationException - concurrent requests while lazy loading a relationship without server warmup

Hello,
We are running into a ConcurrentModificationException when we are firing 100 concurrent requests without warming up the server.
Looks like the error is coming up when a a relationship is being lazy loaded.
We are seeing this behavior consistently. Once the server is warmed up, we are not seeing any issues under concurrency.
I am attaching the two DAOs that are related to the issue.
ExtensionPointRulesetDAO has a M:1 relationship with RuleSetEntityDAO and we are getting the error when ExtensionPointRuleSetDAO._persistence_get_ruleSetEntity() is called.
2015-02-13 12:14:24,021 ERROR [uimadmin] [[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] [ExtensionRuleMediator] [INV-180012] Failed to retrieve the extension point ruleset: null.
java.util.ConcurrentModificationException
    at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
    at java.util.ArrayList$Itr.next(ArrayList.java:831)
    at org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
    at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:574)
    at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:535)
    at org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:1717)
    at org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:253)
    at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:207)
    at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193)
    at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.selectOneRow(DatasourceCallQueryMechanism.java:666)
    at org.eclipse.persistence.internal.queries.ExpressionQueryMechanism.selectOneRowFromTable(ExpressionQueryMechanism.java:2656)
    at org.eclipse.persistence.internal.queries.ExpressionQueryMechanism.selectOneRow(ExpressionQueryMechanism.java:2627)
    at org.eclipse.persistence.queries.ReadObjectQuery.executeObjectLevelReadQuery(ReadObjectQuery.java:450)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:1081)
    at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:844)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:1040)
    at org.eclipse.persistence.queries.ReadObjectQuery.execute(ReadObjectQuery.java:418)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:1128)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2871)
    at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1516)
    at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1498)
    at org.eclipse.persistence.internal.indirection.QueryBasedValueHolder.instantiate(QueryBasedValueHolder.java:98)
    at org.eclipse.persistence.internal.indirection.QueryBasedValueHolder.instantiateForUnitOfWorkValueHolder(QueryBasedValueHolder.java:113)
    at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiateImpl(UnitOfWorkValueHolder.java:156)
    at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiate(UnitOfWorkValueHolder.java:222)
    at org.eclipse.persistence.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:88)
    at oracle.communications.platform.entity.impl.ExtensionPointRuleSetDAO._persistence_get_ruleSetEntity(ExtensionPointRuleSetDAO.java)
    at oracle.communications.platform.entity.impl.ExtensionPointRuleSetDAO.getRuleSetEntity(ExtensionPointRuleSetDAO.java:272)
    at oracle.communications.inventory.extensibility.extension.util.ExtensionRuleMediator.findExtensionPointRule(ExtensionRuleMediator.java:267)
    at oracle.communications.inventory.extensibility.extension.util.ExtensionRuleMediator.initialize(ExtensionRuleMediator.java:134)
    at oracle.communications.inventory.extensibility.extension.SpecBasedArgumentExtension.configureMediator(SpecBasedArgumentExtension.aj:134)
Thanks,
Ravindra

Hi,
Found a note explaining the significance of these errors.
It says:
"NZE-28862: SSL connection failed
Cause: This error occurred because the peer closed the connection.
Action: Enable Oracle Net tracing on both sides and examine the trace output. Contact Oracle Customer support with the trace output."
For further details you may refer the Note: 244527.1 - Explanation of "SSL call to NZ function nzos_Handshake failed" error codes
Thanks & Regards,
Sindhiya V.

Java and lazy loading

Similar Messages

Maybe you are looking for