June 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-729) Enable query caching and hibernate-infinispan 2LC by default

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-729?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-729. ------------------------------- Resolution: Done > Enable query caching and hibernate-infinispan 2LC by default > ------------------------------------------------------------ > > Key: ARTIF-729 > URL: https://issues.jboss.org/browse/ARTIF-729 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > > Profiling has shown that repeated queries are a huge CPU hot spot. Example: when uploading the Artificer distro ZIP itself, the HibernateRelationshipFactory makes repeated queries (by UUID) to set up relationship targets. Since many of them are repeats (ex: find the parent distro artifact), the query cache and 2LC would be immensely helpful. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ARTIF-690) Switch to BMT JTA

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-690?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-690. ------------------------------- Fix Version/s: 1.0.0.Beta2 (was: 1.1.0.Final) Resolution: Done > Switch to BMT JTA > ----------------- > > Key: ARTIF-690 > URL: https://issues.jboss.org/browse/ARTIF-690 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > > Rather than simply using JDBC transactions, switch to using BMT JTA -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ARTIF-729) Enable query caching and hibernate-infinispan 2LC by default

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-729: --------------------------------- Summary: Enable query caching and hibernate-infinispan 2LC by default Key: ARTIF-729 URL: https://issues.jboss.org/browse/ARTIF-729 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta2 Profiling has shown that repeated queries are a huge CPU hot spot. Example: when uploading the Artificer distro ZIP itself, the HibernateRelationshipFactory makes repeated queries (by UUID) to set up relationship targets. Since many of them are repeats (ex: find the parent distro artifact), the query cache and 2LC would be immensely helpful. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ARTIF-690) Switch to BMT JTA

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-690?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-690: ------------------------------ Comment: was deleted (was: WIP: https://github.com/brmeyer/s-ramp/tree/ARTIF-690 (simply the JPA config)) > Switch to BMT JTA > ----------------- > > Key: ARTIF-690 > URL: https://issues.jboss.org/browse/ARTIF-690 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > Rather than simply using JDBC transactions, switch to using BMT JTA -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ARTIF-690) Switch to BMT JTA

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-690?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-690: ------------------------------ Comment: was deleted (was: Note that the EJB services currently include a BMT annotation!) > Switch to BMT JTA > ----------------- > > Key: ARTIF-690 > URL: https://issues.jboss.org/browse/ARTIF-690 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > Rather than simply using JDBC transactions, switch to using BMT JTA -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ARTIF-690) Switch to BMT JTA

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-690?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-690: ------------------------------ Description: Rather than simply using JDBC transactions, switch to using BMT JTA (was: Rather than simply using JDBC transactions at the persistence level, switch to using CMT JTA at the REST/EJB level.) > Switch to BMT JTA > ----------------- > > Key: ARTIF-690 > URL: https://issues.jboss.org/browse/ARTIF-690 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > Rather than simply using JDBC transactions, switch to using BMT JTA -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ARTIF-690) Switch to BMT JTA

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-690?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-690: ------------------------------ Summary: Switch to BMT JTA (was: Switch to CMT JTA) > Switch to BMT JTA > ----------------- > > Key: ARTIF-690 > URL: https://issues.jboss.org/browse/ARTIF-690 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > Rather than simply using JDBC transactions at the persistence level, switch to using CMT JTA at the REST/EJB level. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ARTIF-728) Add upload endpoint that takes a local file path

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-728: --------------------------------- Summary: Add upload endpoint that takes a local file path Key: ARTIF-728 URL: https://issues.jboss.org/browse/ARTIF-728 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer On the server and all clients, add a new upload endpoint that takes a local file path, instead of an InputStream/byte[]. If the file is available on/to the server's machine, there should be no reason why we can't simply use it, rather than pass it through the web service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ARTIF-727) Add non-blocking upload endpoints

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-727: --------------------------------- Summary: Add non-blocking upload endpoints Key: ARTIF-727 URL: https://issues.jboss.org/browse/ARTIF-727 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Uploading large archives can take a while, due to expansion, processing, and derivation. For instance, uploading the entire Artificer distro ZIP takes around 4 minutes. While that's reasonable (at least in my opinion), all of our upload endpoints are currently blocking. Blocking may be desirable for some client apps, so definitely don't remove that. But, adding additional, non-blocking methods to the web service, java client, cli, web browser, and ejb would be helpful. The non-blocking method should at least block until the primary artifact is persisted, returning its metadata. But the rest should be async. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ARTIF-498) Provide a mechanism to consume "seed data"

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-498?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-498. ----------------------------- Resolution: Won't Fix > Provide a mechanism to consume "seed data" > ------------------------------------------ > > Key: ARTIF-498 > URL: https://issues.jboss.org/browse/ARTIF-498 > Project: Artificer > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Brett Meyer > > This is a feature request from David based on his testing of 1.3.0.Beta1 of dtgov: > "Would be very nice for the user, that the first time dtgov is executed, the cli-commands file is loaded and all the dtgov artifacts are installed in s-ramp." > I think the idea is that currently the user must do this manually after installing and launching s-ramp/dtgov. Instead, it would be interesting to have a way to consume this data on startup. I'm adding this as a suggested enhancment to s-ramp. If we decide this feature is not appropriate for s-ramp, then we should move it to a DTGov feature request and consider it in that context. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2015