August 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-560) Exception deployment on Fuse and Fuse Fabric

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-560?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on SRAMP-560: -------------------------------------------- I ll check, because it seems that it is not related with my code changes. The code I commited was just removing 3 packages that are not exported in the s-ramp-atom artifact. I am going to test this, because yesterday I was able to go to the s-ramp dashboard page, that as I understand, you are not being able to enter. > Exception deployment on Fuse and Fuse Fabric > -------------------------------------------- > > Key: SRAMP-560 > URL: https://issues.jboss.org/browse/SRAMP-560 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > There is an exception in the deployment of s-ramp in Fuse and Fuse Fabric. Some packages has been removed from the project s-ramp-atom > at org.apache.karaf.shell.console.jline.DelayedStarted.run(DelayedStarted.java:61)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379] > Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.overlord.sramp.s-ramp-server-fuse61 [409]: Unable to resolve 409.0: missing requirement [409.0] osgi.wiring.package; (osgi.wiring.package=org.overlord.sramp.atom.services.brms.packages) > at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379] > ... 15 more > Remove the non existing packages in the Import-Package tag, of the s-ramp-server pom.xml -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-560) Exception deployment on Fuse and Fuse Fabric

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-560?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-560: ----------------------------------- Hey [~virchete], the pull request corrected the initial startup issue, but now the UI is broken. The IDP page works, but once you log in and are forwarded to S-RAMP, you get this stack: https://gist.github.com/brmeyer/f2d21aace36e603dfce8 > Exception deployment on Fuse and Fuse Fabric > -------------------------------------------- > > Key: SRAMP-560 > URL: https://issues.jboss.org/browse/SRAMP-560 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > There is an exception in the deployment of s-ramp in Fuse and Fuse Fabric. Some packages has been removed from the project s-ramp-atom > at org.apache.karaf.shell.console.jline.DelayedStarted.run(DelayedStarted.java:61)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379] > Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.overlord.sramp.s-ramp-server-fuse61 [409]: Unable to resolve 409.0: missing requirement [409.0] osgi.wiring.package; (osgi.wiring.package=org.overlord.sramp.atom.services.brms.packages) > at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379] > ... 15 more > Remove the non existing packages in the Import-Package tag, of the s-ramp-server pom.xml -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-560) Exception deployment on Fuse and Fuse Fabric

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-560?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-560: --------------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/481 > Exception deployment on Fuse and Fuse Fabric > -------------------------------------------- > > Key: SRAMP-560 > URL: https://issues.jboss.org/browse/SRAMP-560 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > There is an exception in the deployment of s-ramp in Fuse and Fuse Fabric. Some packages has been removed from the project s-ramp-atom > at org.apache.karaf.shell.console.jline.DelayedStarted.run(DelayedStarted.java:61)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379] > Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.overlord.sramp.s-ramp-server-fuse61 [409]: Unable to resolve 409.0: missing requirement [409.0] osgi.wiring.package; (osgi.wiring.package=org.overlord.sramp.atom.services.brms.packages) > at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379] > ... 15 more > Remove the non existing packages in the Import-Package tag, of the s-ramp-server pom.xml -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-560) Exception deployment on Fuse and Fuse Fabric

by David virgil naranjo (JIRA)

David virgil naranjo created SRAMP-560: ------------------------------------------ Summary: Exception deployment on Fuse and Fuse Fabric Key: SRAMP-560 URL: https://issues.jboss.org/browse/SRAMP-560 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David virgil naranjo Assignee: David virgil naranjo There is an exception in the deployment of s-ramp in Fuse and Fuse Fabric. Some packages has been removed from the project s-ramp-atom at org.apache.karaf.shell.console.jline.DelayedStarted.run(DelayedStarted.java:61)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379] Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.overlord.sramp.s-ramp-server-fuse61 [409]: Unable to resolve 409.0: missing requirement [409.0] osgi.wiring.package; (osgi.wiring.package=org.overlord.sramp.atom.services.brms.packages) at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379] ... 15 more Remove the non existing packages in the Import-Package tag, of the s-ramp-server pom.xml -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-433: ----------------------------------- I believe I came up with a solution that will still allow us to run on non-EE app servers, as well as utilize configured JMS/JNDI resources on EE servers. When the s-ramp-events-jms lifecycle starts up, it checks for the existence of a JMS ConnectionFactory and the default S-RAMP topic, both through JNDI. If they exist, it means we're in EE land and things are correctly configured. Simply use them, in addition to any other configured topics/queues. If not, assume we're on Tomcat/Jetty. s-ramp-events-jms will then create an embedded ActiveMQ broker over a TCP port, then programmatically create all topics/queues. Clients can then connect to it in one of two ways: 1.) Simply use the ActiveMQ libs and API. 2.) The ActiveMQ broker provides a lightweight JNDI implementation and automatically exposes the ConnectionFactory. To expose the topics/queues, the *client app* needs to include a jndi.properties file (and ActiveMQ jar) on the classpath. The contents contain something like "topic.[jndi name] = [activemq topic name]". [jndi name] is then available to the client. Other than that properties file, the client is able to use generic JNDI and JMS, without any ActiveMQ APIs. > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. > Event design thoughts: https://community.jboss.org/message/884274 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-433: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/480 > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. > Event design thoughts: https://community.jboss.org/message/884274 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-559) Support TomEE

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-559: --------------------------------- Summary: Support TomEE Key: SRAMP-559 URL: https://issues.jboss.org/browse/SRAMP-559 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Eric Wittmann Fix For: 0.6.0 Theoretically, the S-RAMP server war should be able to simply run as-is in TomEE (using all S-RAMP's Tomcat modules). But, s-ramp-ui-war-tomcat7 does not work since TomEE provides CDI on its own, conflicting with the Weld distro included in the war. Presumably we'll need a new TomEE-specific war project, installer target, etc. Eric, assigning to you initially (bowing to your Weld-fu), but feel free to re-assign and coach me through it if you're swamped. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0

by Michael Clay (JIRA)

[ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.... ] Michael Clay commented on RTGOV-556: ------------------------------------ hi Gary, i have tried the build an there are switchyard-*.jar version 2.x jar's in the WEB-INF/lib directory of overlord-rtgov-ui.war which are not compatible with the 1.x version of fsw 6.0.0_ga i.e. the serializing api/protocol has changed which causes a NPE in SwitchYardRemotingServlet - we have to provide the latest compatible 1.x version of the switchyard jars here. cheers, michael > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

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

by Michael Clay (JIRA)

Michael Clay created RTGOV-567: ---------------------------------- Summary: [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 Security Level: Public (Everyone can see) Components: User Interface Reporter: Michael Clay Assignee: Gary Brown 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.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-566) [resubmit] RemoteMessage#context is empty

by Michael Clay (JIRA)

Michael Clay created RTGOV-566: ---------------------------------- Summary: [resubmit] RemoteMessage#context is empty Key: RTGOV-566 URL: https://issues.jboss.org/browse/RTGOV-566 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Components: User Interface Reporter: Michael Clay Assignee: Gary Brown because RemoteMessage#context is empty/not used there is no way to pass properties required for the implementation of the resubmitted/retried service invocation (e.g. SOAPHeader are stored as message properties) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues August 2014