[jira] [Updated] (ARIES-851) Multiple IllegalStateException when deploying a new PersistenceUnit
[
https://issues.apache.org/jira/browse/ARIES-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Gritschenberger updated ARIES-851:
Attachment: test.jpa.bundle-0.1.0-SNAPSHOT.jar
jpa-test-bundle-src.zip
persistence-feature.xml
Multiple IllegalStateException when deploying a new PersistenceUnit
---
Key: ARIES-851
URL: https://issues.apache.org/jira/browse/ARIES-851
Project: Aries
Issue Type: Bug
Components: JPA
Environment: Linux-3.0.0, Karaf-3.0.0-SNAPSHOT with Felix, openjdk-6
Reporter: Christoph Gritschenberger
Attachments: jpa-test-bundle-src.zip, persistence-feature.xml,
test.jpa.bundle-0.1.0-SNAPSHOT.jar
Steps to reproduce
* Compile or get a karaf-3.0.0-SNAPSHOT and unpack it
* Install openjpa-2.2.0 (using the attached feature-file)
* Deploy a bundle containing a persistence-unit (attached jar for example)
get the following Exception 4 times:
{code}
ERROR: Bundle org.apache.aries.jpa.container [78] EventDispatcher: Error
during dispatch. (java.lang.IllegalStateException: Unable to create
persistence units for the bundle test.jpa.test.jpa.bundle/0.1.0.SNAPSHOT as
previous persistence units already exist.)
java.lang.IllegalStateException: Unable to create persistence units for the
bundle test.jpa.test.jpa.bundle/0.1.0.SNAPSHOT as previous persistence units
already exist.
{code}
See attachment for full stacktrace
In subsequent startups the Exception is still thrown but the stacktrace does
not show in the console or the log.
Also when using equinox the Stacktrace does not appear in either the console
or the log ever, but it's still thrown.
The problem is that the PersistenceBundleManager#addingBundle is called
multiple times for the newly installed bundle.
The PersistenceBundleManager is passed as a BundleTrackerCustomizer to a
BundleHookBundleTracker.
The BundleHookBundleTracker stores it in it's own private attribute and also
passes it to it's super-constructor.
So the customizer is stored in the instance twice.
It's called by both BundleTracker$Tracked.customizerAdding and
BundleHookBundleTracker$Tracked.customizerAdding.
Both Tracked recognize the bundle as untracked and call the
addingBundle-method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (ARIES-851) Multiple IllegalStateException when deploying a new PersistenceUnit
Christoph Gritschenberger created ARIES-851:
---
Summary: Multiple IllegalStateException when deploying a new
PersistenceUnit
Key: ARIES-851
URL: https://issues.apache.org/jira/browse/ARIES-851
Project: Aries
Issue Type: Bug
Components: JPA
Environment: Linux-3.0.0, Karaf-3.0.0-SNAPSHOT with Felix, openjdk-6
Reporter: Christoph Gritschenberger
Attachments: jpa-test-bundle-src.zip, persistence-feature.xml,
test.jpa.bundle-0.1.0-SNAPSHOT.jar
Steps to reproduce
* Compile or get a karaf-3.0.0-SNAPSHOT and unpack it
* Install openjpa-2.2.0 (using the attached feature-file)
* Deploy a bundle containing a persistence-unit (attached jar for example)
get the following Exception 4 times:
{code}
ERROR: Bundle org.apache.aries.jpa.container [78] EventDispatcher: Error during
dispatch. (java.lang.IllegalStateException: Unable to create persistence units
for the bundle test.jpa.test.jpa.bundle/0.1.0.SNAPSHOT as previous persistence
units already exist.)
java.lang.IllegalStateException: Unable to create persistence units for the
bundle test.jpa.test.jpa.bundle/0.1.0.SNAPSHOT as previous persistence units
already exist.
{code}
See attachment for full stacktrace
In subsequent startups the Exception is still thrown but the stacktrace does
not show in the console or the log.
Also when using equinox the Stacktrace does not appear in either the console or
the log ever, but it's still thrown.
The problem is that the PersistenceBundleManager#addingBundle is called
multiple times for the newly installed bundle.
The PersistenceBundleManager is passed as a BundleTrackerCustomizer to a
BundleHookBundleTracker.
The BundleHookBundleTracker stores it in it's own private attribute and also
passes it to it's super-constructor.
So the customizer is stored in the instance twice.
It's called by both BundleTracker$Tracked.customizerAdding and
BundleHookBundleTracker$Tracked.customizerAdding.
Both Tracked recognize the bundle as untracked and call the
addingBundle-method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ARIES-851) Multiple IllegalStateException when deploying a new PersistenceUnit
[
https://issues.apache.org/jira/browse/ARIES-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Gritschenberger updated ARIES-851:
Attachment: ARIES-851-stacktrace.TXT
Multiple IllegalStateException when deploying a new PersistenceUnit
---
Key: ARIES-851
URL: https://issues.apache.org/jira/browse/ARIES-851
Project: Aries
Issue Type: Bug
Components: JPA
Environment: Linux-3.0.0, Karaf-3.0.0-SNAPSHOT with Felix, openjdk-6
Reporter: Christoph Gritschenberger
Attachments: ARIES-851-stacktrace.TXT,
BundleHookBundleTracker-solution1.patch,
BundleHookBundleTracker-solution2.patch, jpa-test-bundle-src.zip,
persistence-feature.xml, test.jpa.bundle-0.1.0-SNAPSHOT.jar
Steps to reproduce
* Compile or get a karaf-3.0.0-SNAPSHOT and unpack it
* Install openjpa-2.2.0 (using the attached feature-file)
* Deploy a bundle containing a persistence-unit (attached jar for example)
get the following Exception 4 times:
{code}
ERROR: Bundle org.apache.aries.jpa.container [78] EventDispatcher: Error
during dispatch. (java.lang.IllegalStateException: Unable to create
persistence units for the bundle test.jpa.test.jpa.bundle/0.1.0.SNAPSHOT as
previous persistence units already exist.)
java.lang.IllegalStateException: Unable to create persistence units for the
bundle test.jpa.test.jpa.bundle/0.1.0.SNAPSHOT as previous persistence units
already exist.
{code}
See attachment for full stacktrace
In subsequent startups the Exception is still thrown but the stacktrace does
not show in the console or the log.
Also when using equinox the Stacktrace does not appear in either the console
or the log ever, but it's still thrown.
The problem is that the PersistenceBundleManager#addingBundle is called
multiple times for the newly installed bundle.
The PersistenceBundleManager is passed as a BundleTrackerCustomizer to a
BundleHookBundleTracker.
The BundleHookBundleTracker stores it in it's own private attribute and also
passes it to it's super-constructor.
So the customizer is stored in the instance twice.
It's called by both BundleTracker$Tracked.customizerAdding and
BundleHookBundleTracker$Tracked.customizerAdding.
Both Tracked recognize the bundle as untracked and call the
addingBundle-method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ARIES-851) Multiple IllegalStateException when deploying a new PersistenceUnit
[
https://issues.apache.org/jira/browse/ARIES-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Gritschenberger updated ARIES-851:
Attachment: BundleHookBundleTracker-solution2.patch
BundleHookBundleTracker-solution1.patch
Two solutions that prevent, that addingBundle is called too often.
Multiple IllegalStateException when deploying a new PersistenceUnit
---
Key: ARIES-851
URL: https://issues.apache.org/jira/browse/ARIES-851
Project: Aries
Issue Type: Bug
Components: JPA
Environment: Linux-3.0.0, Karaf-3.0.0-SNAPSHOT with Felix, openjdk-6
Reporter: Christoph Gritschenberger
Attachments: ARIES-851-stacktrace.TXT,
BundleHookBundleTracker-solution1.patch,
BundleHookBundleTracker-solution2.patch, jpa-test-bundle-src.zip,
persistence-feature.xml, test.jpa.bundle-0.1.0-SNAPSHOT.jar
Steps to reproduce
* Compile or get a karaf-3.0.0-SNAPSHOT and unpack it
* Install openjpa-2.2.0 (using the attached feature-file)
* Deploy a bundle containing a persistence-unit (attached jar for example)
get the following Exception 4 times:
{code}
ERROR: Bundle org.apache.aries.jpa.container [78] EventDispatcher: Error
during dispatch. (java.lang.IllegalStateException: Unable to create
persistence units for the bundle test.jpa.test.jpa.bundle/0.1.0.SNAPSHOT as
previous persistence units already exist.)
java.lang.IllegalStateException: Unable to create persistence units for the
bundle test.jpa.test.jpa.bundle/0.1.0.SNAPSHOT as previous persistence units
already exist.
{code}
See attachment for full stacktrace
In subsequent startups the Exception is still thrown but the stacktrace does
not show in the console or the log.
Also when using equinox the Stacktrace does not appear in either the console
or the log ever, but it's still thrown.
The problem is that the PersistenceBundleManager#addingBundle is called
multiple times for the newly installed bundle.
The PersistenceBundleManager is passed as a BundleTrackerCustomizer to a
BundleHookBundleTracker.
The BundleHookBundleTracker stores it in it's own private attribute and also
passes it to it's super-constructor.
So the customizer is stored in the instance twice.
It's called by both BundleTracker$Tracked.customizerAdding and
BundleHookBundleTracker$Tracked.customizerAdding.
Both Tracked recognize the bundle as untracked and call the
addingBundle-method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (ARIES-851) Multiple IllegalStateException when deploying a new PersistenceUnit
[
https://issues.apache.org/jira/browse/ARIES-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276712#comment-13276712
]
Christoph Gritschenberger edited comment on ARIES-851 at 5/16/12 12:59 PM:
---
Attached two possible solutions that prevent, that addingBundle is called too
often.
was (Author: christophg):
Two solutions that prevent, that addingBundle is called too often.
Multiple IllegalStateException when deploying a new PersistenceUnit
---
Key: ARIES-851
URL: https://issues.apache.org/jira/browse/ARIES-851
Project: Aries
Issue Type: Bug
Components: JPA
Environment: Linux-3.0.0, Karaf-3.0.0-SNAPSHOT with Felix, openjdk-6
Reporter: Christoph Gritschenberger
Attachments: ARIES-851-stacktrace.TXT,
BundleHookBundleTracker-solution1.patch,
BundleHookBundleTracker-solution2.patch, jpa-test-bundle-src.zip,
persistence-feature.xml, test.jpa.bundle-0.1.0-SNAPSHOT.jar
Steps to reproduce
* Compile or get a karaf-3.0.0-SNAPSHOT and unpack it
* Install openjpa-2.2.0 (using the attached feature-file)
* Deploy a bundle containing a persistence-unit (attached jar for example)
get the following Exception 4 times:
{code}
ERROR: Bundle org.apache.aries.jpa.container [78] EventDispatcher: Error
during dispatch. (java.lang.IllegalStateException: Unable to create
persistence units for the bundle test.jpa.test.jpa.bundle/0.1.0.SNAPSHOT as
previous persistence units already exist.)
java.lang.IllegalStateException: Unable to create persistence units for the
bundle test.jpa.test.jpa.bundle/0.1.0.SNAPSHOT as previous persistence units
already exist.
{code}
See attachment for full stacktrace
In subsequent startups the Exception is still thrown but the stacktrace does
not show in the console or the log.
Also when using equinox the Stacktrace does not appear in either the console
or the log ever, but it's still thrown.
The problem is that the PersistenceBundleManager#addingBundle is called
multiple times for the newly installed bundle.
The PersistenceBundleManager is passed as a BundleTrackerCustomizer to a
BundleHookBundleTracker.
The BundleHookBundleTracker stores it in it's own private attribute and also
passes it to it's super-constructor.
So the customizer is stored in the instance twice.
It's called by both BundleTracker$Tracked.customizerAdding and
BundleHookBundleTracker$Tracked.customizerAdding.
Both Tracked recognize the bundle as untracked and call the
addingBundle-method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (ARIES-852) Blueprint Property Override Support
James Carman created ARIES-852: -- Summary: Blueprint Property Override Support Key: ARIES-852 URL: https://issues.apache.org/jira/browse/ARIES-852 Project: Aries Issue Type: Improvement Components: Blueprint Affects Versions: blueprint-0.3.1 Reporter: James Carman Priority: Minor We already have property-placeholder support (a la Spring), but can we also get property-override too? I can probably submit a patch. I just wanted to get this idea jotted down so that I didn't forget. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ARIES-827) ARIES-778 broke the ability to use a composite bundles isolation implementation on equinox 3.7
[ https://issues.apache.org/jira/browse/ARIES-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated ARIES-827: --- Attachment: ARIES-827-1.diff This patch uses one or two trackers to track both 4.3 bundle wiring events and composite bundle events or regular 4.2 events. I'll see if I can figure out how to test it in a 4.3 environment with composite bundles in use. ARIES-778 broke the ability to use a composite bundles isolation implementation on equinox 3.7 -- Key: ARIES-827 URL: https://issues.apache.org/jira/browse/ARIES-827 Project: Aries Issue Type: Bug Components: Util Reporter: Alasdair Nottingham Assignee: Alasdair Nottingham Attachments: ARIES-827-1.diff The ARIES-778 to use a ResolverHook based solution to the recursive bundle tracker means on equinox 3.7 you can't use the composite bundle based isolation mode. This hardly seems like a good idea. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
