October 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-257) Use application realm instead of overlord-idp-*.properties in EAP

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-257: ----------------------------------- Summary: Use application realm instead of overlord-idp-*.properties in EAP Key: SRAMP-257 URL: https://issues.jboss.org/browse/SRAMP-257 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 0.3.0 - JBPM6 Integration Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.3.1 - jBPM - bugfix 1 Currently the overlord apps use their own properties files for authentication. Change this to use the application realm for authentication. This will allow users to configure EAP in a more standard way, and it removes the need for those two additional config files. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-256) ontology with spaces in ID break everything

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-256: ------------------------------- Summary: ontology with spaces in ID break everything Key: SRAMP-256 URL: https://issues.jboss.org/browse/SRAMP-256 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kurt Stam Assignee: Eric Wittmann Fix For: 0.4.0 - API Management I mistakenly added a space to a new ontology ID. You can't do much after you upload that: s-ramp> ontology:delete feed:2 FAILED to get the list of ontologies. No ontology found with UUID: f5968fe6-088b-46d2-af67-094057da0e99 s-ramp> ontology:list FAILED to get the list of ontologies. Illegal character in path at index 6: Review Status It should be possible to recover from this; or don't the upload should fail. Either one of the two. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-112) Properly handle logged-out errors

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-112?page=com.atlassian.jira.plugi... ] Work on SRAMPUI-112 started by Eric Wittmann. > Properly handle logged-out errors > --------------------------------- > > Key: SRAMPUI-112 > URL: https://issues.jboss.org/browse/SRAMPUI-112 > Project: S-RAMP UI > Issue Type: Bug > Components: View > Affects Versions: 0.3.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > > If the user has been logged out of the UI session (e.g. by explicitly logging out on another browser tab) then all sorts of things might break. Any of the RPC calls (errai) will likely fail. Additionally, the download and upload servlets will no longer work. > Need better handling of this situation. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-71) Occasional ConcurrentModificationException when starting up gadget web UI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GADGETS-71?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated GADGETS-71: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1018757 > Occasional ConcurrentModificationException when starting up gadget web UI > ------------------------------------------------------------------------- > > Key: GADGETS-71 > URL: https://issues.jboss.org/browse/GADGETS-71 > Project: Gadget Server and Gadgets > Issue Type: Bug > Reporter: Gary Brown > Assignee: Eric Wittmann > > This exception occurs periodically when starting up the gadget server and adding the gadgets to a page. It appears to be related to the service overview gadget, as that does not display any content when this exception occurs. > {noformat} > 10:23:09,459 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/gadget-web].[js]] (http-/127.0.0.1:8080-4) JBWEB000236: Servlet.service() for servlet js threw exception: java.util.ConcurrentModificationException > at java.util.TreeMap$NavigableSubMap$SubMapIterator.prevEntry(TreeMap.java:1605) [rt.jar:1.7.0_07] > at java.util.TreeMap$NavigableSubMap$DescendingSubMapKeyIterator.next(TreeMap.java:1682) [rt.jar:1.7.0_07] > at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:99) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.ComposeWarningsGuard.addGuard(ComposeWarningsGuard.java:89) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:100) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.ComposeWarningsGuard.<init>(ComposeWarningsGuard.java:79) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.Compiler.initOptions(Compiler.java:277) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.Compiler.initModules(Compiler.java:332) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.Compiler.init(Compiler.java:312) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.Compiler.compile(Compiler.java:511) [closure-compiler-r1741.jar:] > at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.doCompile(ClosureJsCompiler.java:205) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.compile(ClosureJsCompiler.java:172) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.shindig.gadgets.js.CompilationProcessor.process(CompilationProcessor.java:48) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.shindig.gadgets.js.DefaultJsProcessorRegistry.process(DefaultJsProcessorRegistry.java:53) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.shindig.gadgets.js.DefaultJsServingPipeline.execute(DefaultJsServingPipeline.java:41) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.shindig.gadgets.servlet.JsServlet.doGet(JsServlet.java:93) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.shindig.gadgets.servlet.ETagFilter.doFilter(ETagFilter.java:55) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.shindig.common.servlet.HostFilter.doFilter(HostFilter.java:39) [shindig-common-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > {noformat} -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-111) Upgrade to Errai 2.4.0.Final

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-111?page=com.atlassian.jira.plugi... ] Eric Wittmann resolved SRAMPUI-111. ----------------------------------- Resolution: Done > Upgrade to Errai 2.4.0.Final > ---------------------------- > > Key: SRAMPUI-111 > URL: https://issues.jboss.org/browse/SRAMPUI-111 > Project: S-RAMP UI > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-111) Upgrade to Errai 2.4.0.Final

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-111?page=com.atlassian.jira.plugi... ] Eric Wittmann closed SRAMPUI-111. --------------------------------- > Upgrade to Errai 2.4.0.Final > ---------------------------- > > Key: SRAMPUI-111 > URL: https://issues.jboss.org/browse/SRAMPUI-111 > Project: S-RAMP UI > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-111) Upgrade to Errai 2.4.0.Final

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-111?page=com.atlassian.jira.plugi... ] Eric Wittmann updated SRAMPUI-111: ---------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/348 > Upgrade to Errai 2.4.0.Final > ---------------------------- > > Key: SRAMPUI-111 > URL: https://issues.jboss.org/browse/SRAMPUI-111 > Project: S-RAMP UI > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-111) Upgrade to Errai 2.4.0.Final

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-111?page=com.atlassian.jira.plugi... ] Work on SRAMPUI-111 started by Eric Wittmann. > Upgrade to Errai 2.4.0.Final > ---------------------------- > > Key: SRAMPUI-111 > URL: https://issues.jboss.org/browse/SRAMPUI-111 > Project: S-RAMP UI > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-99) Overlord IDP session timeout problem

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-99?page=com.atlassian.jira.plugin... ] Eric Wittmann closed SRAMPUI-99. -------------------------------- > Overlord IDP session timeout problem > ------------------------------------ > > Key: SRAMPUI-99 > URL: https://issues.jboss.org/browse/SRAMPUI-99 > Project: S-RAMP UI > Issue Type: Bug > Affects Versions: 0.3.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > > The session timeout of the IDP will kick in causing the user to have to re-authenticate. The SSO session should probably last 8 hours by default. > See: https://access.redhat.com/site/solutions/283763 -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-99) Overlord IDP session timeout problem

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-99?page=com.atlassian.jira.plugin... ] Eric Wittmann resolved SRAMPUI-99. ---------------------------------- Resolution: Done > Overlord IDP session timeout problem > ------------------------------------ > > Key: SRAMPUI-99 > URL: https://issues.jboss.org/browse/SRAMPUI-99 > Project: S-RAMP UI > Issue Type: Bug > Affects Versions: 0.3.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > > The session timeout of the IDP will kick in causing the user to have to re-authenticate. The SSO session should probably last 8 hours by default. > See: https://access.redhat.com/site/solutions/283763 -- 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues October 2013