[JBoss JIRA] (RTGOV-485) Fabric container restart fails to find all dependencies
by Gary Brown (JIRA)
Gary Brown created RTGOV-485:
--------------------------------
Summary: Fabric container restart fails to find all dependencies
Key: RTGOV-485
URL: https://issues.jboss.org/browse/RTGOV-485
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.Final
When 'all' profile is first added to the container it is fine (apart from intermittent rtgov-ui web app deploy issue).
However when the container is stopped and started again, it has the following errors:
{noformat}
2014-05-30 13:04:48
ERROR
org.apache.aries.blueprint.container.BlueprintContainerImpl
Unable to start blueprint container for bundle activity-embedded due to unresolved dependencies [(objectClass=org.overlord.rtgov.activity.collector.CollectorContext)]
2014-05-30 13:04:48
ERROR
org.apache.aries.blueprint.container.BlueprintContainerImpl
Unable to start blueprint container for bundle activity-server-epn due to unresolved dependencies [(objectClass=org.overlord.rtgov.epn.EPNManager)]
2014-05-30 13:04:49
ERROR
org.overlord.rtgov.epn.EPNManagerAccessor
EPNManager is not available
2014-05-30 13:04:49
ERROR
org.overlord.rtgov.active.collection.epn.EPNActiveCollectionSource
Failed to obtain Event Processor Network Manager
2014-05-30 13:04:49
ERROR
org.overlord.rtgov.acs.loader.osgi.ACSActivator
Failed to register active collection sources
2014-05-30 13:04:49
INFO
io.fabric8.agent.DeploymentAgent
ep-keyvaluestore / 2.0.0.SNAPSHOT
2014-05-30 13:04:49
INFO
io.fabric8.agent.DeploymentAgent
overlord-rtgov-epn-osgi / 2.0.0.SNAPSHOT
2014-05-30 13:09:49
ERROR
org.overlord.rtgov.epn.EPNManagerAccessor
EPNManager is not available
2014-05-30 13:09:49
ERROR
org.overlord.rtgov.epn.loader.osgi.EPNActivator
Failed to obtain reference to EPNManager
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (RTGOV-483) Kibana console cannot access elasticsearch in Karaf
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-483?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-483.
------------------------------
Fix Version/s: (was: 2.0.0.Final)
Resolution: Rejected
Port configuration issue - the Elasticsearch Java client needs to use the internal transport port, not the same port used by http clients.
In the default ports, the http port is 9200 while the transport port is 9300.
> Kibana console cannot access elasticsearch in Karaf
> ---------------------------------------------------
>
> Key: RTGOV-483
> URL: https://issues.jboss.org/browse/RTGOV-483
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
>
> Get the following exception in Elasticsearch console when being accessed with Kibana via the proxy:
> {noformat}
> [2014-05-29 14:01:01,073][WARN ][transport.netty ] [Brynocki] exception caught on transport layer [[id: 0xe20d9657, /127.0.0.1:36983 :> /127.0.0.1:9700]], closing connection
> java.io.StreamCorruptedException: invalid internal transport message format
> at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:46)
> at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (RTGOV-483) Kibana console cannot access elasticsearch in Karaf
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-483?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-483:
----------------------------------
Looks like it might have been a problem in the server, as a curl GET request also failed. Whereas doing the same request on a different ES server (default port) worked fine.
> Kibana console cannot access elasticsearch in Karaf
> ---------------------------------------------------
>
> Key: RTGOV-483
> URL: https://issues.jboss.org/browse/RTGOV-483
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
>
> Get the following exception in Elasticsearch console when being accessed with Kibana via the proxy:
> {noformat}
> [2014-05-29 14:01:01,073][WARN ][transport.netty ] [Brynocki] exception caught on transport layer [[id: 0xe20d9657, /127.0.0.1:36983 :> /127.0.0.1:9700]], closing connection
> java.io.StreamCorruptedException: invalid internal transport message format
> at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:46)
> at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (RTGOV-483) Kibana console cannot access elasticsearch in Karaf
by Gary Brown (JIRA)
Gary Brown created RTGOV-483:
--------------------------------
Summary: Kibana console cannot access elasticsearch in Karaf
Key: RTGOV-483
URL: https://issues.jboss.org/browse/RTGOV-483
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.Final
Get the following exception in Elasticsearch console when being accessed with Kibana via the proxy:
{noformat}
[2014-05-29 14:01:01,073][WARN ][transport.netty ] [Brynocki] exception caught on transport layer [[id: 0xe20d9657, /127.0.0.1:36983 :> /127.0.0.1:9700]], closing connection
java.io.StreamCorruptedException: invalid internal transport message format
at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:46)
at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (RTGOV-476) java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator@
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-476?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-476:
-----------------------------
Steps to Reproduce:
Unpack jboss fuse.
Unpack the overlord-commons and rtgov profile zips into the fabric profiles folder.
Start fuse.
fabric:create --zookeeper-password admin
(this will prompt for username and passwd, just use admin/admin)
jaas:manage --index 3
jaas:useradd karaf karaf
jaas:roleadd karaf admin
jaas:update
fabric:container-create-child --jvm-opts '-Xms1000m -Xmx1000m' root child
fabric:container-add-profile child overlord-rtgov-all
(this final command can be done in the console, but I logged into localhost:8181/hawtio and added the overlord/rtgov 'all' profile via the UI).
was:
Unpack jboss fuse.
Unpack the overlord-commons and rtgov profile zips into the fabric profiles folder.
Start fuse.
fabric:create --zookeeper-password admin
(this will prompt for username and passwd, just use admin/admin)
jaas:manage --index 3
jaas:useradd karaf karaf
jaas:roleadd karaf admin
jaas:update
fabric:container-create-child --jvm-opts '-Xms1000m -Xmx1000m' root child
fabric:container-add-profile child overlord-rtgov-all
(this final command can be done in the console, but I looked into localhost:8181/hawtio and added the overlord/rtgov 'all' profile via the UI).
> java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator@
> -----------------------------------------------------------------------------------------------------------------
>
> Key: RTGOV-476
> URL: https://issues.jboss.org/browse/RTGOV-476
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: David virgil naranjo
> Fix For: 2.0.0.Final
>
>
> When RTGov all configuration is deployed in a fabric child container we get the following exception:
> java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator@3afffabb in org.eclipse.jetty.security.ConstraintSecurityHandler@7ba6293f
> at org.eclipse.jetty.security.authentication.LoginAuthenticator.setConfiguration(LoginAuthenticator.java:61)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months