October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HIBERNATE-139) [HHH-7629] Initialize PersistentCollection with fetchType LAZY returns NPE

by Ricardo Martinelli Oliveira (JIRA)

Ricardo Martinelli Oliveira created HIBERNATE-139: ----------------------------------------------------- Summary: [HHH-7629] Initialize PersistentCollection with fetchType LAZY returns NPE Key: HIBERNATE-139 URL: https://issues.jboss.org/browse/HIBERNATE-139 Project: Hibernate Integration Issue Type: Support Patch Reporter: Ricardo Martinelli Oliveira Assignee: Steve Ebersole @JoinTable(name = "JOIN_TABLE", joinColumns = { @JoinColumn(name = "JOIN_TABLE_ID", referencedColumnName = "ID") }, inverseJoinColumns = { @JoinColumn(name = "ENTITY_ID", referencedColumnName = "ID") }) @ManyToMany(fetch = FetchType.LAZY) private Set<JoinTable> aProperty; When fetching this entity, and after initialize, I get all the valid attribute values but the aProperty is defined as PersistenceCollection. This collection is not intialized yet. When I initialize this collection as follow: (PersistentCollection) entity).forceInitialization(); Or Hibernate.initialize(entity); I got NullPointerException: Caused by: java.lang.NullPointerException at org.hibernate.engine.internal.StatefulPersistenceContext.getLoadedCollectionOwnerOrNull(StatefulPersistenceContext.java:790) at org.hibernate.event.spi.AbstractCollectionEvent.getLoadedOwnerOrNull(AbstractCollectionEvent.java:75) at org.hibernate.event.spi.InitializeCollectionEvent.<init>(InitializeCollectionEvent.java:36) at org.hibernate.internal.SessionImpl.initializeCollection(SessionImpl.java:1803) at org.hibernate.collection.internal.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:489) at org.hibernate.Hibernate.initialize(Hibernate.java:77) When I check source code of class org.hibernate.engine.internal.StatefulPersistenceContext.getLoadedCollectionOwnerOrNull(StatefulPersistenceContext.java:790) CollectionEntry ce = getCollectionEntry( collection ); 790 if ( ce.getLoadedPersister() == null ) { 791 return null; // early exit... 792 } Looks like the CollectionEntry ce is null. This collection entry is fetched from collectionEntries.get(coll); // Identity map of CollectionEntry instances, by the collection wrapper 121 private IdentityMap<PersistentCollection, CollectionEntry> collectionEntries; I checked Jboss docs, it mentioned the way to initilialize the collection is as I have done above. http://docs.jboss.org/hibernate/orm/3.3/reference/en/html/performance.htm... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-5733) Domain "Runtime" navigation (LHS) not refreshed when the number of server configurations is changed

by Heiko Braun (JIRA)

Heiko Braun created AS7-5733: -------------------------------- Summary: Domain "Runtime" navigation (LHS) not refreshed when the number of server configurations is changed Key: AS7-5733 URL: https://issues.jboss.org/browse/AS7-5733 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 Remove all server configurations on a host to see what I mean -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] (AS7-2371) Web Console: In the past the JMX console could flush queues/topics, etc, can that be added to the console

by Jim Tyrrell (Created) (JIRA)

Web Console: In the past the JMX console could flush queues/topics, etc, can that be added to the console ---------------------------------------------------------------------------------------------------------- Key: AS7-2371 URL: https://issues.jboss.org/browse/AS7-2371 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] (AS7-5752) Ability to manage path references on standalone servers

by Heiko Braun (JIRA)

Heiko Braun created AS7-5752: -------------------------------- Summary: Ability to manage path references on standalone servers Key: AS7-5752 URL: https://issues.jboss.org/browse/AS7-5752 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] (AS7-5750) Support expressions in unmanaged deployment "path"

by Heiko Braun (JIRA)

Heiko Braun created AS7-5750: -------------------------------- Summary: Support expressions in unmanaged deployment "path" Key: AS7-5750 URL: https://issues.jboss.org/browse/AS7-5750 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.2.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] (AS7-5101) Support unmanaged deployments in the console

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5101: ------------------------------------- Summary: Support unmanaged deployments in the console Key: AS7-5101 URL: https://issues.jboss.org/browse/AS7-5101 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Brian Stansberry Assignee: Heiko Braun The AS supports the notion of "unmanaged" deployments, where, rather than uploading the deployment content to the server, which then serves it from its internal content repo, instead the filesystem path to the content is provided and the content is served directly from that location. This mechanism is particularly helpful with exploded deployments; it's what the filesystem deployment scanner uses when it detects an exploded deployment. The CLI supports this via the --unmanaged flag that can be passed to the "deploy" command. The console should expose this functionality as well. If this were used in a managed domain, it's the responsibility of the user to ensure that the content is available at the provided path on all relevant hosts in the domain. EAP itself takes no responsibility for managing that content. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] (AS7-5751) Properly report module load failures while adding JDBC driver

by jaikiran pai (JIRA)

jaikiran pai created AS7-5751: --------------------------------- Summary: Properly report module load failures while adding JDBC driver Key: AS7-5751 URL: https://issues.jboss.org/browse/AS7-5751 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.3.Final (EAP) Environment: AS7 upstream Reporter: jaikiran pai Assignee: jaikiran pai I've seen many users running into issues when they are trying to configure a datasource and end up pointing to an incorrect module name for the JDBC driver. No where in the logs do we report why the JDBC driver install failed and users find it difficult to understand the real cause until someone points them to the incorrect module name. Looking at the code which adds the JDBC driver (JdbcDriverAdd) I see that we aren't reporting the real module load failure correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-5748) Indicate failed deployment sin the web console

by Heiko Braun (JIRA)

Heiko Braun created AS7-5748: -------------------------------- Summary: Indicate failed deployment sin the web console Key: AS7-5748 URL: https://issues.jboss.org/browse/AS7-5748 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-5638) Verify interaction with filesystem deployments

by Heiko Braun (JIRA)

Heiko Braun created AS7-5638: -------------------------------- Summary: Verify interaction with filesystem deployments Key: AS7-5638 URL: https://issues.jboss.org/browse/AS7-5638 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 It seems possible to modify filesystem deployments from within the console. This should not be the case -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] (AS7-5747) Enforce OSGi wiring symetry accros nodes

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5747: ----------------------------------- Summary: Enforce OSGi wiring symetry accros nodes Key: AS7-5747 URL: https://issues.jboss.org/browse/AS7-5747 Project: Application Server 7 Issue Type: Feature Request Components: Clustering, OSGi Reporter: Thomas Diesler Assignee: Paul Ferraro Using a distributed cache in a multinode environment would require a mapping for the classloader. With symetric wiring only the top level cl needs to be mapped. Unsymentric wiring may lead to a number of unforeseeable issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2012