September 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-761) Set the max allowed packet for mysql

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/ARTIF-761?page=com.atlassian.jira.plugin.... ] David virgil naranjo resolved ARTIF-761. ---------------------------------------- Fix Version/s: 1.1.0.Final Resolution: Done > Set the max allowed packet for mysql > ------------------------------------ > > Key: ARTIF-761 > URL: https://issues.jboss.org/browse/ARTIF-761 > Project: Artificer > Issue Type: Bug > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 1.1.0.Final > > > There is an exception executing the demos/webapp-multimodule/web deployment: > https://gist.github.com/dvirgiln/883d1682c500c324b579 > Please add in the documentation the information of how to set the maximum size per tuple. THis needs to be done for all the supported databases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-760) Init DDL called several times by different threads

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/ARTIF-760?page=com.atlassian.jira.plugin.... ] David virgil naranjo resolved ARTIF-760. ---------------------------------------- Resolution: Done > Init DDL called several times by different threads > -------------------------------------------------- > > Key: ARTIF-760 > URL: https://issues.jboss.org/browse/ARTIF-760 > Project: Artificer > Issue Type: Bug > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > When the initDDL is called in the Artifacts page, then it is called the getStoredQueries from different threads. > It makes that the entityManager() method is called at the same time(more or less) by 2 different threads and the initDDLs is called by the 2 threads. One of them execute correctly the DDL script but the other fails: > https://gist.github.com/dvirgiln/5b42bf372254ac400ba5 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-567) [resubmit] missing security context propagation with RemoteMessage

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-567?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-567: ---------------------------------- Now that credentials can now be passed, the outstanding question is where do we obtain this information from. One option would be to prompt for the username and password when performing the resubmit? > [resubmit] missing security context propagation with RemoteMessage > ------------------------------------------------------------------ > > Key: RTGOV-567 > URL: https://issues.jboss.org/browse/RTGOV-567 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Michael Clay > Assignee: Gary Brown > Fix For: 2.2.0.Alpha3 > > > currently there is no way to retry/resubmit switchyard services with a clientAuthentication policy because the context is not propagated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-662) RTGov properties are not logged in elasticsearch for external invocations

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-662?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-662. ------------------------------ Fix Version/s: 2.2.0.Alpha3 Resolution: Done > RTGov properties are not logged in elasticsearch for external invocations > ------------------------------------------------------------------------- > > Key: RTGOV-662 > URL: https://issues.jboss.org/browse/RTGOV-662 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha3 > > > Properties associated with an external invocation in switchyard are being reported in activity information, but not logged in the response time information stored in elasticsearch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-662) RTGov properties are not logged in elasticsearch for external invocations

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-662?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-662: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> changed the Status of [bug 1232188|https://bugzilla.redhat.com/show_bug.cgi?id=1232188] from NEW to MODIFIED > RTGov properties are not logged in elasticsearch for external invocations > ------------------------------------------------------------------------- > > Key: RTGOV-662 > URL: https://issues.jboss.org/browse/RTGOV-662 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > > Properties associated with an external invocation in switchyard are being reported in activity information, but not logged in the response time information stored in elasticsearch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-669) Remove situation manager and reports

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-669?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-669: ----------------------------- Description: Remove deprecated situation manager and reports, as no longer required and has been deprecated for last couple of releases. was: Remove deprecated situation manager, as no longer required and has been deprecated for last couple of releases. > Remove situation manager and reports > ------------------------------------ > > Key: RTGOV-669 > URL: https://issues.jboss.org/browse/RTGOV-669 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha3 > > > Remove deprecated situation manager and reports, as no longer required and has been deprecated for last couple of releases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-669) Remove situation manager and reports

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-669?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-669: ----------------------------- Summary: Remove situation manager and reports (was: Remove situation manager) > Remove situation manager and reports > ------------------------------------ > > Key: RTGOV-669 > URL: https://issues.jboss.org/browse/RTGOV-669 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha3 > > > Remove deprecated situation manager, as no longer required and has been deprecated for last couple of releases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-669) Remove situation manager

by Gary Brown (JIRA)

Gary Brown created RTGOV-669: -------------------------------- Summary: Remove situation manager Key: RTGOV-669 URL: https://issues.jboss.org/browse/RTGOV-669 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.2.0.Alpha3 Remove deprecated situation manager, as no longer required and has been deprecated for last couple of releases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-669) Remove situation manager

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-669?page=com.atlassian.jira.plugin.... ] Work on RTGOV-669 started by Gary Brown. ---------------------------------------- > Remove situation manager > ------------------------ > > Key: RTGOV-669 > URL: https://issues.jboss.org/browse/RTGOV-669 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha3 > > > Remove deprecated situation manager, as no longer required and has been deprecated for last couple of releases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-761) Set the max allowed packet for mysql

by David virgil naranjo (JIRA)

David virgil naranjo created ARTIF-761: ------------------------------------------ Summary: Set the max allowed packet for mysql Key: ARTIF-761 URL: https://issues.jboss.org/browse/ARTIF-761 Project: Artificer Issue Type: Bug Reporter: David virgil naranjo Assignee: David virgil naranjo There is an exception executing the demos/webapp-multimodule/web deployment: https://gist.github.com/dvirgiln/883d1682c500c324b579 Please add in the documentation the information of how to set the maximum size per tuple. THis needs to be done for all the supported databases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues September 2015