[JBoss JIRA] (WFCORE-2592) wildfly-service.exe and jbosspass wrong with # inside
by Lukas Vydra (Jira)
[ https://issues.redhat.com/browse/WFCORE-2592?page=com.atlassian.jira.plug... ]
Lukas Vydra reassigned WFCORE-2592:
-----------------------------------
Assignee: Lukas Vydra
> wildfly-service.exe and jbosspass wrong with # inside
> -----------------------------------------------------
>
> Key: WFCORE-2592
> URL: https://issues.redhat.com/browse/WFCORE-2592
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 8.0.0.Beta5
> Reporter: Seb Dk
> Assignee: Lukas Vydra
> Priority: Major
>
> Hi there,
>
> I am installing wildfy 10.1.0 as service on a win 20012 server.
> It is working but I cannot stop the service.
> I figured out where the problem is coming from.
>
> When I installe Wildly as a service, I run the following command:
> E:\Products\wildfly-10.1.0.Final\bin\service>service.bat install /serviceuser .\JBoss /servicepass my#pass /controller localhost:9991 /jbossuser myuser /jbosspass *my#pass*
>
> But I can see whe I am trying to stop the service, the command running is:
> E:\Products\wildfly-10.1.0.Final\bin\jboss-cli.bat --controller=localhost:9991 --connect --user=myuser --password=*my" "pass* --command=:shutdown
>
> Any workaround?
>
> Thanks,
>
> S.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFLY-13828) remote+tls is not supported by EJBClient and remote-outbound-connection
by Ranabir Chakraborty (Jira)
[ https://issues.redhat.com/browse/WFLY-13828?page=com.atlassian.jira.plugi... ]
Ranabir Chakraborty edited comment on WFLY-13828 at 9/29/20 2:36 AM:
---------------------------------------------------------------------
Hello, [~mgrossmann] can you please describe this bug in a more detailed way and also what are the steps you are following to reproduce it?
was (Author: rchakrab):
Hello, [~mgrossmann] can you please describe this issue in a more detailed way and what is the bug you are facing?
> remote+tls is not supported by EJBClient and remote-outbound-connection
> -----------------------------------------------------------------------
>
> Key: WFLY-13828
> URL: https://issues.redhat.com/browse/WFLY-13828
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 20.0.1.Final
> Reporter: Matthias Großmann
> Assignee: Ranabir Chakraborty
> Priority: Major
>
> Hi,
> in our company we would like to use the newest Wildfly together with legacy servers like JBoss AS 7 over SSL.
> This is possible with the Uri scheme "remote+tls" provided by jboss-remoting
> https://github.com/jboss-remoting/jboss-remoting/blob/master/src/main/jav...
> {code:java}
> final RemoteConnectionProviderFactory remoteConnectionProviderFactory = new RemoteConnectionProviderFactory();
> ...
> endpoint.addConnectionProvider("remote+tls", remoteConnectionProviderFactory, OptionMap.create(Options.SECURE, Boolean.TRUE));
> {code}
> But that uri scheme is not supported by the jboss-ejb-client in current version
> https://github.com/wildfly/jboss-ejb-client/blob/master/src/main/java/org...
> {code}
> public boolean supportsProtocol(final String uriScheme) {
> switch (uriScheme) {
> case "remote":
> case "remote+http":
> case "remote+https":
> // compatibility
> case "remoting":
> case "http-remoting":
> case "https-remoting": {
> return true;
> }
> default: {
> return false;
> }
> }
> }
> {code}
> and also the remote-outbound-connection does not allow that protocol:
> https://github.com/wildfly/wildfly-core/blob/master/remoting/subsystem/sr...
> {code}
> public enum Protocol {
> REMOTE("remote"),
> REMOTE_HTTP("remote+http"),
> HTTP_REMOTING("http-remoting"),
> HTTPS_REMOTING("https-remoting"),
> REMOTE_HTTPS("remote+https");
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFLY-13828) remote+tls is not supported by EJBClient and remote-outbound-connection
by Ranabir Chakraborty (Jira)
[ https://issues.redhat.com/browse/WFLY-13828?page=com.atlassian.jira.plugi... ]
Ranabir Chakraborty commented on WFLY-13828:
--------------------------------------------
Hello, [~mgrossmann] can you please describe this issue in a more detailed way and what is the bug you are facing?
> remote+tls is not supported by EJBClient and remote-outbound-connection
> -----------------------------------------------------------------------
>
> Key: WFLY-13828
> URL: https://issues.redhat.com/browse/WFLY-13828
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 20.0.1.Final
> Reporter: Matthias Großmann
> Assignee: Ranabir Chakraborty
> Priority: Major
>
> Hi,
> in our company we would like to use the newest Wildfly together with legacy servers like JBoss AS 7 over SSL.
> This is possible with the Uri scheme "remote+tls" provided by jboss-remoting
> https://github.com/jboss-remoting/jboss-remoting/blob/master/src/main/jav...
> {code:java}
> final RemoteConnectionProviderFactory remoteConnectionProviderFactory = new RemoteConnectionProviderFactory();
> ...
> endpoint.addConnectionProvider("remote+tls", remoteConnectionProviderFactory, OptionMap.create(Options.SECURE, Boolean.TRUE));
> {code}
> But that uri scheme is not supported by the jboss-ejb-client in current version
> https://github.com/wildfly/jboss-ejb-client/blob/master/src/main/java/org...
> {code}
> public boolean supportsProtocol(final String uriScheme) {
> switch (uriScheme) {
> case "remote":
> case "remote+http":
> case "remote+https":
> // compatibility
> case "remoting":
> case "http-remoting":
> case "https-remoting": {
> return true;
> }
> default: {
> return false;
> }
> }
> }
> {code}
> and also the remote-outbound-connection does not allow that protocol:
> https://github.com/wildfly/wildfly-core/blob/master/remoting/subsystem/sr...
> {code}
> public enum Protocol {
> REMOTE("remote"),
> REMOTE_HTTP("remote+http"),
> HTTP_REMOTING("http-remoting"),
> HTTPS_REMOTING("https-remoting"),
> REMOTE_HTTPS("remote+https");
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-5680) STANDARD_DRL property reactivity doesn't recognize multiple properties in an expression
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-5680:
------------------------------------
Summary: STANDARD_DRL property reactivity doesn't recognize multiple properties in an expression
Key: DROOLS-5680
URL: https://issues.redhat.com/browse/DROOLS-5680
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.43.1.Final
Reporter: Hiroko Miura
Assignee: Mario Fusco
When a constraint expression has multiple properties, standard drl (MvelConstraint.calculateMaskFromExpression()) enlists only the first property for property reactivity (e.g. 'age' in the below case) while executable model can react on both.
{noformat}
$p : Person( age > salary )
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFLY-13910) Class visibility problem with SimpleWebserviceEndpointTestCase with -Dts.layers
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13910?page=com.atlassian.jira.plugi... ]
Paul Ferraro commented on WFLY-13910:
-------------------------------------
[~brian.stansberry] This should hopefully resolve itself following https://github.com/wildfly/wildfly/pull/13609
> Class visibility problem with SimpleWebserviceEndpointTestCase with -Dts.layers
> -------------------------------------------------------------------------------
>
> Key: WFLY-13910
> URL: https://issues.redhat.com/browse/WFLY-13910
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 21.0.0.Final
>
>
> In recent days we've had nightly CI jobs failing with a bunch of WS failures with the first failure in SimpleWebserviceEndpointTestCase
> https://ci.wildfly.org/project.html?projectId=WF&testNameId=-828936378136...
> The failed tests in jobs that run with -Dts.layers, so the slimmed server tests.
> {code}
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy ws-endpoint-example.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ws-endpoint-example.war\".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"ws-endpoint-example.war\"
> Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.jboss.as.test.integration.ws.SimpleWebserviceEndpointImpl with ClassLoader ModuleClassLoader for Module \"deployment.ws-endpoint-example.war\" from Service Module Loader
> Caused by: java.lang.NoClassDefFoundError: Ljavax/xml/ws/WebServiceContext;
> Caused by: java.lang.ClassNotFoundException: javax.xml.ws.WebServiceContext from [Module \"deployment.ws-endpoint-example.war\" from Service Module Loader]"}}}}
> org.jboss.arquillian.container.spi.client.container.DeploymentException:
> Cannot deploy ws-endpoint-example.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ws-endpoint-example.war\".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"ws-endpoint-example.war\"
> Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.jboss.as.test.integration.ws.SimpleWebserviceEndpointImpl with ClassLoader ModuleClassLoader for Module \"deployment.ws-endpoint-example.war\" from Service Module Loader
> Caused by: java.lang.NoClassDefFoundError: Ljavax/xml/ws/WebServiceContext;
> Caused by: java.lang.ClassNotFoundException: javax.xml.ws.WebServiceContext from [Module \"deployment.ws-endpoint-example.war\" from Service Module Loader]"}}}}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFLY-13910) Class visibility problem with SimpleWebserviceEndpointTestCase with -Dts.layers
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13910?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13910:
------------------------------------
Component/s: Clustering
Test Suite
(was: Web Services)
> Class visibility problem with SimpleWebserviceEndpointTestCase with -Dts.layers
> -------------------------------------------------------------------------------
>
> Key: WFLY-13910
> URL: https://issues.redhat.com/browse/WFLY-13910
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 21.0.0.Final
>
>
> In recent days we've had nightly CI jobs failing with a bunch of WS failures with the first failure in SimpleWebserviceEndpointTestCase
> https://ci.wildfly.org/project.html?projectId=WF&testNameId=-828936378136...
> The failed tests in jobs that run with -Dts.layers, so the slimmed server tests.
> {code}
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy ws-endpoint-example.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ws-endpoint-example.war\".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"ws-endpoint-example.war\"
> Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.jboss.as.test.integration.ws.SimpleWebserviceEndpointImpl with ClassLoader ModuleClassLoader for Module \"deployment.ws-endpoint-example.war\" from Service Module Loader
> Caused by: java.lang.NoClassDefFoundError: Ljavax/xml/ws/WebServiceContext;
> Caused by: java.lang.ClassNotFoundException: javax.xml.ws.WebServiceContext from [Module \"deployment.ws-endpoint-example.war\" from Service Module Loader]"}}}}
> org.jboss.arquillian.container.spi.client.container.DeploymentException:
> Cannot deploy ws-endpoint-example.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ws-endpoint-example.war\".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"ws-endpoint-example.war\"
> Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.jboss.as.test.integration.ws.SimpleWebserviceEndpointImpl with ClassLoader ModuleClassLoader for Module \"deployment.ws-endpoint-example.war\" from Service Module Loader
> Caused by: java.lang.NoClassDefFoundError: Ljavax/xml/ws/WebServiceContext;
> Caused by: java.lang.ClassNotFoundException: javax.xml.ws.WebServiceContext from [Module \"deployment.ws-endpoint-example.war\" from Service Module Loader]"}}}}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFLY-13910) Class visibility problem with SimpleWebserviceEndpointTestCase with -Dts.layers
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13910?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFLY-13910:
---------------------------------------
Assignee: Brian Stansberry (was: Jim Ma)
[~jim.ma] [~jfdenise]
I'm going to assume this has nothing to do with webservices or galleon.
Looking at https://ci.wildfly.org/viewLog.html?buildId=224572&buildTypeId=WF_PullReq... I see that the final execution in the preceding testsuite/integration/clustering did not complete normally:
{code}
[09:52:44][org.wildfly:wildfly-ts-integ-clustering] [INFO] Running org.jboss.as.test.clustering.cluster.ejb.remote.TwoConnectorsEJBFailoverTestCase
[11:19:53][org.wildfly:wildfly-ts-integ-clustering] [INFO]
[11:19:53][org.wildfly:wildfly-ts-integ-clustering] [INFO] Results:
[11:19:53][org.wildfly:wildfly-ts-integ-clustering] [INFO]
[11:19:53][org.wildfly:wildfly-ts-integ-clustering] [WARNING] Tests run: 17, Failures: 0, Errors: 0, Skipped: 1
[11:19:53][org.wildfly:wildfly-ts-integ-clustering] [INFO]
[11:19:53][org.wildfly:wildfly-ts-integ-clustering] [ERROR] There was a timeout or other error in the fork
{code}
This may be testsuite or CI job configuration issue. [~pferraro] FYI.
> Class visibility problem with SimpleWebserviceEndpointTestCase with -Dts.layers
> -------------------------------------------------------------------------------
>
> Key: WFLY-13910
> URL: https://issues.redhat.com/browse/WFLY-13910
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 21.0.0.Final
>
>
> In recent days we've had nightly CI jobs failing with a bunch of WS failures with the first failure in SimpleWebserviceEndpointTestCase
> https://ci.wildfly.org/project.html?projectId=WF&testNameId=-828936378136...
> The failed tests in jobs that run with -Dts.layers, so the slimmed server tests.
> {code}
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy ws-endpoint-example.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ws-endpoint-example.war\".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"ws-endpoint-example.war\"
> Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.jboss.as.test.integration.ws.SimpleWebserviceEndpointImpl with ClassLoader ModuleClassLoader for Module \"deployment.ws-endpoint-example.war\" from Service Module Loader
> Caused by: java.lang.NoClassDefFoundError: Ljavax/xml/ws/WebServiceContext;
> Caused by: java.lang.ClassNotFoundException: javax.xml.ws.WebServiceContext from [Module \"deployment.ws-endpoint-example.war\" from Service Module Loader]"}}}}
> org.jboss.arquillian.container.spi.client.container.DeploymentException:
> Cannot deploy ws-endpoint-example.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ws-endpoint-example.war\".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"ws-endpoint-example.war\"
> Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.jboss.as.test.integration.ws.SimpleWebserviceEndpointImpl with ClassLoader ModuleClassLoader for Module \"deployment.ws-endpoint-example.war\" from Service Module Loader
> Caused by: java.lang.NoClassDefFoundError: Ljavax/xml/ws/WebServiceContext;
> Caused by: java.lang.ClassNotFoundException: javax.xml.ws.WebServiceContext from [Module \"deployment.ws-endpoint-example.war\" from Service Module Loader]"}}}}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFCORE-5143) Bouncycastle - Failing tests in RESTEasy TS
by Alessio Soldano (Jira)
[ https://issues.redhat.com/browse/WFCORE-5143?page=com.atlassian.jira.plug... ]
Alessio Soldano commented on WFCORE-5143:
-----------------------------------------
Page refreshed... Emanuel found that already :)
> Bouncycastle - Failing tests in RESTEasy TS
> -------------------------------------------
>
> Key: WFCORE-5143
> URL: https://issues.redhat.com/browse/WFCORE-5143
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 13.0.0.Beta6
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Blocker
>
> [~ehugonnet] please set the component. I cannot find anything suitable.
> I noticed it in the context of a bootable JAR execution but [~jfdenise] confirmed this happens with WF 21 Beta1.
> This is about some tests in the RESTEasy TS which has been adapted to execute against bootable JARs through a specific profile [1].
> The tests are running successfully with WildFly 20.0.1.Final (the {{ejb}} layer needs to be removed for this experiment to be run [2]) but fail against 21.0.0.Beta1, so it is a regression.
> There are 108 tests failing but this JIRA is reporting just one as a reference, see "Steps to reproduce" in order to have a full list:
> {code}
> org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest.org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest
> Error Details
> Cannot deploy BlacklistedMediaTypeTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.BlacklistedMediaTypeTest.war\".main" => "WFLYSRV0179: Failed to load module: deployment.BlacklistedMediaTypeTest.war
> Caused by: org.jboss.modules.ModuleNotFoundException: org.bouncycastle"}}}}
> {code}
> *Steps to reproduce*:
> 1. clone https://github.com/fabiobrz/Resteasy/tree/bootable-jar-support
> 2. build RESTEasy:
> {code}
> $ mvn install -Dmaven.test.skip=true -Dmaven.repo.local=/home/my-local-repo
> {code}
> 3. cd to testsuite directory:
> {code}
> cd testsuite
> {code}
> 4. run the test against WF 21.0.0.Beta1 with bootable JAR:
> {code}
> mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable
> {code}
> The test should *fail*
> 5. run the test against WF 20.0.1.Final with bootable JAR:
> {code}
> mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=20.0.1.Final -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable
> {code}
> The test should *pass*
> [1]
> https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46...
> [2]
> https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years