[JBoss JIRA] (DROOLS-2358) Sometimes kie server cannot connect to the server on Windows
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2358?page=com.atlassian.jira.plugi... ]
Tomas David updated DROOLS-2358:
--------------------------------
Description:
Sometimes it happens that kie server cannot get content of repository. Error dialog is displayed. Exception is thrown:
{noformat}
org.eclipse.jgit.api.errors.TransportException: ssh://testadmin@localhost:8001/clonerepo: verify: false
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:250)
at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:304)
at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:201)
at org.kie.eclipse.navigator.view.utils.ActionUtils$1.run(ActionUtils.java:149)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
Caused by: org.eclipse.jgit.errors.TransportException: ssh://testadmin@localhost:8001/clonerepo: verify: false
at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:172)
at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:137)
at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.<init>(TransportGitSsh.java:278)
at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:169)
at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:137)
at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:123)
at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1236)
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:239)
... 4 more
Caused by: com.jcraft.jsch.JSchException: verify: false
at com.jcraft.jsch.Session.connect(Session.java:330)
at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:126)
... 11 more
{noformat}
was:
Sometimes it happens that kie server cannot get content of repository. Error dialog is displayed.
> Sometimes kie server cannot connect to the server on Windows
> ------------------------------------------------------------
>
> Key: DROOLS-2358
> URL: https://issues.jboss.org/browse/DROOLS-2358
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Affects Versions: 7.5.0.Final
> Environment: Windows 10
> Developer studio 11.2.0.GA
> Drools plugin 7.5.0.Final
> RHDM 7.0.0.GA / BPMS 6.4.9.GA
> Reporter: Tomas David
> Assignee: Kris Verlaenen
> Attachments: error_dialog.png
>
>
> Sometimes it happens that kie server cannot get content of repository. Error dialog is displayed. Exception is thrown:
> {noformat}
> org.eclipse.jgit.api.errors.TransportException: ssh://testadmin@localhost:8001/clonerepo: verify: false
> at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:250)
> at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:304)
> at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:201)
> at org.kie.eclipse.navigator.view.utils.ActionUtils$1.run(ActionUtils.java:149)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.eclipse.jgit.errors.TransportException: ssh://testadmin@localhost:8001/clonerepo: verify: false
> at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:172)
> at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:137)
> at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.<init>(TransportGitSsh.java:278)
> at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:169)
> at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:137)
> at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:123)
> at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1236)
> at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:239)
> ... 4 more
> Caused by: com.jcraft.jsch.JSchException: verify: false
> at com.jcraft.jsch.Session.connect(Session.java:330)
> at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:126)
> ... 11 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2358) Sometimes kie server cannot connect to the server on Windows
by Tomas David (JIRA)
Tomas David created DROOLS-2358:
-----------------------------------
Summary: Sometimes kie server cannot connect to the server on Windows
Key: DROOLS-2358
URL: https://issues.jboss.org/browse/DROOLS-2358
Project: Drools
Issue Type: Bug
Components: eclipse plugin
Affects Versions: 7.5.0.Final
Environment: Windows 10
Developer studio 11.2.0.GA
Drools plugin 7.5.0.Final
RHDM 7.0.0.GA / BPMS 6.4.9.GA
Reporter: Tomas David
Assignee: Kris Verlaenen
Attachments: error_dialog.png
Sometimes it happens that kie server cannot get content of repository. Error dialog is displayed. Exception is thrown:
{noformat}
*no* further _formatting_ is done here
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2358) Sometimes kie server cannot connect to the server on Windows
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2358?page=com.atlassian.jira.plugi... ]
Tomas David updated DROOLS-2358:
--------------------------------
Description:
Sometimes it happens that kie server cannot get content of repository. Error dialog is displayed.
was:
Sometimes it happens that kie server cannot get content of repository. Error dialog is displayed. Exception is thrown:
{noformat}
*no* further _formatting_ is done here
{noformat}
> Sometimes kie server cannot connect to the server on Windows
> ------------------------------------------------------------
>
> Key: DROOLS-2358
> URL: https://issues.jboss.org/browse/DROOLS-2358
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Affects Versions: 7.5.0.Final
> Environment: Windows 10
> Developer studio 11.2.0.GA
> Drools plugin 7.5.0.Final
> RHDM 7.0.0.GA / BPMS 6.4.9.GA
> Reporter: Tomas David
> Assignee: Kris Verlaenen
> Attachments: error_dialog.png
>
>
> Sometimes it happens that kie server cannot get content of repository. Error dialog is displayed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-3579) ERROR log occurs during CLI reload operation on server
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3579?page=com.atlassian.jira.plugi... ]
Jason Greene updated WFCORE-3579:
---------------------------------
Fix Version/s: 5.0.0.Alpha1
(was: 4.0.0.Final)
> ERROR log occurs during CLI reload operation on server
> ------------------------------------------------------
>
> Key: WFCORE-3579
> URL: https://issues.jboss.org/browse/WFCORE-3579
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 4.0.0.Alpha9
> Reporter: Marek Kopecký
> Assignee: Brian Stansberry
> Priority: Blocker
> Fix For: 5.0.0.Alpha1
>
> Attachments: cli.script.txt
>
>
> *Description of the issue:*
> ERROR log occurs during CLI reload operation on server:
> {{ERROR \[org.jboss.as.controller.management-operation\] (pool-3-thread-2) WFLYCTL0013: Operation ("read-attribute") failed - address: (\[("host" => "master")\]) - failure description: "WFLYCTL0201: Unknown attribute 'host-state'"}}
> This issue is regression against WF11
> Reload handler and its "host-state" code is [here|https://github.com/wildfly/wildfly-core/blob/master/cli/src/main/jav...], but this issue is probably caused by some "debug -> error" logging change ...
> I'm able to reproduce this only on embedded server. Non-embedded server is probably too slow to hit this issue
> *How reproducible:*
> I see this intermittently on fast virtual machines
> *Steps to Reproduce:*
> # ./jboss-cli.sh --file=cli.script.txt
> *Content of cli.script.txt file*
> This file is attached to this jira, beginning of this file:
> {noformat}
> embed-host-controller --std-out=echo
> reload --host=master --admin-only=true
> reload --host=master --admin-only=true
> reload --host=master --admin-only=true
> reload --host=master --admin-only=true
> reload --host=master --admin-only=true
> reload --host=master --admin-only=true
> reload --host=master --admin-only=true
> {noformat}
> *Actual results:*
> Standard output:
> {noformat}
> ...
> [0m[0m01:36:06,021 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 12.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Alpha9) starting
> [0m[31m01:36:06,061 ERROR [org.jboss.as.controller.management-operation] (CLI command executor) WFLYCTL0013: Operation ("read-attribute") failed - address: ([("host" => "master")]) - failure description: "WFLYCTL0201: Unknown attribute 'host-state'"
> [0m[0m01:36:06,072 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [0m[0m01:36:06,073 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [0m[0m01:36:06,097 INFO [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
> [0m[33m01:36:06,102 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /home/hudson/hudson_workspace/workspace/early-testing-cli-embedded-manual/4b767fc2/wildfly/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> [0m[0m01:36:06,185 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [0m[0m01:36:06,196 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [0m[0m01:36:06,204 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [0m[0m01:36:06,217 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [0m[0m01:36:06,287 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 12.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Alpha9) (Host Controller) started in 266ms - Started 54 of 59 services (18 services are lazy, passive or on-demand)
> ...
> {noformat}
> *Expected results:*
> No errors in logs
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-2235) Intermittent module loading failure in InterdependentDeploymentTestCase
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2235?page=com.atlassian.jira.plugi... ]
Jason Greene updated WFCORE-2235:
---------------------------------
Fix Version/s: 5.0.0.Alpha1
(was: 4.0.0.Final)
> Intermittent module loading failure in InterdependentDeploymentTestCase
> -----------------------------------------------------------------------
>
> Key: WFCORE-2235
> URL: https://issues.jboss.org/browse/WFCORE-2235
> Project: WildFly Core
> Issue Type: Bug
> Components: Modules, Server
> Affects Versions: 4.0.0.Alpha6
> Reporter: Brian Stansberry
> Assignee: Richard Opalka
> Fix For: 5.0.0.Alpha1
>
> Attachments: WFCORE-2235svcdump.txt
>
>
> InterdependentDeploymentTestCase tests deployment handling of a set of interdependent deployments, where some of the dependencies are optional.
> The test intermittently fails due to a ModuleLoadException while deploying one of the modules:
> https://ci.wildfly.org/viewLog.html?buildId=42957&buildTypeId=WildFlyCore...
> The most notable bit of info in the log is:
> {code}
> 17:32:08,639 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.module.service."deployment.interrelated-c.jar".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.interrelated-c.jar".main: WFLYSRV0179: Failed to load module: deployment.interrelated-c.jar
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at org.jboss.msc.service.MSCExecutor$1.run(MSCExecutor.java:77)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.modules.ModuleNotFoundException: deployment.interrelated-c.jar
> at org.jboss.modules.ModuleLoader$FutureModule.getModule(ModuleLoader.java:834)
> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:472)
> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:457)
> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:370)
> at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloadModule(ServiceModuleLoader.java:147)
> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:387)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:282)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:270)
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68)
> ... 6 more
> {code}
> The interrelated-c.jar deployment depends (*not optionally*) on interrelated-a.jar.The failure occurs during execution of a management op that redeploys interrelated-a.jar. FWIW, another deployment in the set, interrelated-f.jar, does depend optionally on interrelated-c.jar.
> The full stdout output for the failed test in the above linked CI run also includes a dump of all MSC services following the failure. Note though that the failure does not result in MSC not obtaining stability. Inability to reach stability was the initial problem that led to the introduction of this test (see https://github.com/wildfly/wildfly-core/pull/2099.)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-1598) Out of the box SSL - or shortly after.
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-1598?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-1598:
-------------------------------
Fix Version/s: 13.0.0.Beta1
(was: 12.0.0.Final)
> Out of the box SSL - or shortly after.
> --------------------------------------
>
> Key: WFLY-1598
> URL: https://issues.jboss.org/browse/WFLY-1598
> Project: WildFly
> Issue Type: Sub-task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Priority: Critical
> Labels: management_security,, management_sso
> Fix For: 13.0.0.Beta1
>
>
> There are various reasons that we do not support SSL/TLS out of the box e.g.
> - If we ship a default keystore then everyone has access to the private key.
> - Generating one on first boot we do not have sufficient information to generate it correctly, also the performance overhead.
> This issue is to explorer other options to encourage their use and make it easier to configure.
> As an example could the admin console detect a non encrypted connection and have an box that encourages the config along with a wizard like workflow to get it set up?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-466) Detect JBossWS Configuration for @PermitAll endpoints within Undertow subsystem.
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-466?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-466:
------------------------------
Fix Version/s: 13.0.0.Beta1
(was: 12.0.0.Final)
> Detect JBossWS Configuration for @PermitAll endpoints within Undertow subsystem.
> --------------------------------------------------------------------------------
>
> Key: WFLY-466
> URL: https://issues.jboss.org/browse/WFLY-466
> Project: WildFly
> Issue Type: Task
> Components: Web (Undertow)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 13.0.0.Beta1
>
>
> UNDERTOW-38 has added the possibility of deploying web applications where authentication is mandated but no authorization checks are performed - this is required for integration use cases such as EJB endpoints where authorization checks are being left to the EJB container.
> This task is to update the Undertow susbsystem to detect this scenario and enable the new mode for UNDERTOW-38.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months