[JBoss JIRA] (WFCORE-2592) wildfly-service.exe and jbosspass wrong with # inside
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2592?page=com.atlassian.jira.plugi... ]
Tomaz Cerar moved WFLY-7715 to WFCORE-2592:
-------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-2592 (was: WFLY-7715)
Component/s: Scripts
(was: Scripts)
> wildfly-service.exe and jbosspass wrong with # inside
> -----------------------------------------------------
>
> Key: WFCORE-2592
> URL: https://issues.jboss.org/browse/WFCORE-2592
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Seb Dk
> Assignee: Tomaz Cerar
>
> 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.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8458) NPE when MBean does not have no-arg constructor
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8458?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reopened WFLY-8458:
------------------------------------
Hi [~soul2zimate] -- please update this fix to not use EeLogger. Logger interfaces should not be used outside their own module. Thanks!
> NPE when MBean does not have no-arg constructor
> -----------------------------------------------
>
> Key: WFLY-8458
> URL: https://issues.jboss.org/browse/WFLY-8458
> Project: WildFly
> Issue Type: Bug
> Components: JMX, Server
> Affects Versions: 11.0.0.Alpha1
> Reporter: Chao Wang
> Assignee: Chao Wang
> Fix For: 11.0.0.Beta1
>
>
> NPE when MBean does not have no-arg constructor, it should log an error message indicating the issue rather than NPE
> {code}
> 15:05:48,605 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."jboss-helloworld-dynamicmbean-helloworld-mbean-service.sar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jboss-helloworld-dynamicmbean-helloworld-mbean-service.sar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jboss-helloworld-dynamicmbean-helloworld-mbean-service.sar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> 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: java.lang.IllegalArgumentException: WFLYSAR0004: Class not instantiated
> at org.jboss.as.service.ReflectionUtils.newInstance(ReflectionUtils.java:133)
> at org.jboss.as.service.ParsedServiceDeploymentProcessor.newInstance(ParsedServiceDeploymentProcessor.java:283)
> at org.jboss.as.service.ParsedServiceDeploymentProcessor.addServices(ParsedServiceDeploymentProcessor.java:129)
> at org.jboss.as.service.ParsedServiceDeploymentProcessor.deploy(ParsedServiceDeploymentProcessor.java:118)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.jboss.as.service.ReflectionUtils.newInstance(ReflectionUtils.java:131)
> ... 9 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2591) deployment add/add-content alternatives and required issues
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2591?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise updated WFCORE-2591:
-----------------------------------------
Description:
add operation
- content should be required.
- alternatives hash/bytes/url/path/input-stream-index/empty should be required.
add-content operation
- content should be required.
- alternatives input-stream-index/hash/bytes/url should be required.
- alternatives empty/relative-to/path should not be present in alternatives list.
was:
add operation
- content should be required.
- alternatives hash/bytes/url/path/input-stream-index should be required.
add-content operation
- content should be required.
- alternatives input-stream-index/hash/bytes/url should be required.
- alternatives empty/relative-to/path should not be present in alternatives list.
> deployment add/add-content alternatives and required issues
> -----------------------------------------------------------
>
> Key: WFCORE-2591
> URL: https://issues.jboss.org/browse/WFCORE-2591
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Jean-Francois Denise
> Assignee: Brian Stansberry
> Priority: Minor
>
> add operation
> - content should be required.
> - alternatives hash/bytes/url/path/input-stream-index/empty should be required.
> add-content operation
> - content should be required.
> - alternatives input-stream-index/hash/bytes/url should be required.
> - alternatives empty/relative-to/path should not be present in alternatives list.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2591) deployment add/add-content alternatives and required issues
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-2591:
--------------------------------------------
Summary: deployment add/add-content alternatives and required issues
Key: WFCORE-2591
URL: https://issues.jboss.org/browse/WFCORE-2591
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Jean-Francois Denise
Assignee: Brian Stansberry
Priority: Minor
add operation
- content should be required.
- alternatives hash/bytes/url/path/input-stream-index should be required.
add-content operation
- content should be required.
- alternatives input-stream-index/hash/bytes/url should be required.
- alternatives empty/relative-to/path should not be present in alternatives list.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2535) ModuleResourceRootPathsTestCase fails with security manager in WF core
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2535?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet reassigned WFCORE-2535:
-----------------------------------------
Assignee: ehsavoie Hugonnet
> ModuleResourceRootPathsTestCase fails with security manager in WF core
> ----------------------------------------------------------------------
>
> Key: WFCORE-2535
> URL: https://issues.jboss.org/browse/WFCORE-2535
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Test Suite
> Reporter: Jan Tymel
> Assignee: ehsavoie Hugonnet
>
> *org.jboss.as.test.integration.management.cli.modules.ModuleResourceRootPathsTestCase#testModules*
> {{cd testsuite/standalone/}}
> {{mvn test -Dtest=ModuleResourceRootPathsTestCase -Dsecurity.manager -DtestLogToFile=false}}
> {code}
> 13:26:00,583 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."test-archive.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."test-archive.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "test-archive.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.lang.Thread.run(Thread.java:785)
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "jboss.bind.address" "read")" in code source "(vfs:/content/test-archive.war <no signer certificates>)" of "ModuleClassLoader for Module "deployment.test-archive.war" from Service Module Loader")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPropertyAccess(WildFlySecurityManager.java:469)
> at java.lang.System.getProperty(System.java:443)
> at java.lang.System.getProperty(System.java:427)
> at org.jboss.as.test.shared.TestSuiteEnvironment.getSystemProperty(TestSuiteEnvironment.java:50)
> at org.jboss.as.test.shared.TestSuiteEnvironment.getHttpAddress(TestSuiteEnvironment.java:173)
> at org.wildfly.test.undertow.UndertowServiceActivator.getAddress(UndertowServiceActivator.java:100)
> at org.wildfly.test.undertow.UndertowServiceActivator.activate(UndertowServiceActivator.java:66)
> at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:91)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2398) Legacy Kerberos in management, EAP search for HTTPS/localhost ticket
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2398?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFCORE-2398:
-------------------------------------
Fix Version/s: 3.0.0.Beta12
> Legacy Kerberos in management, EAP search for HTTPS/localhost ticket
> --------------------------------------------------------------------
>
> Key: WFCORE-2398
> URL: https://issues.jboss.org/browse/WFCORE-2398
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: regression
> Fix For: 3.0.0.Beta12
>
>
> Accessing management interface secured by Kerberos + TLS causes EAP requests from KDC ticket HTTPS/localhost. Which was not necessary in EAP 7.0 and it worked fine with HTTP/localhost service name
> {code:title=server.log}
> 14:20:19,321 TRACE [org.jboss.as.domain.management.security] (management task-7) No mapping for name 'https/localhost.localdomain' to KeytabService, attempting to use host only match.
> 14:20:19,322 TRACE [org.jboss.as.domain.management.security] (management task-7) Selected KeytabService with principal 'HTTP/localhost.localdomain(a)JBOSS.ORG' for host 'localhost.localdomain'
> 14:20:19,322 INFO [stdout] (management task-7) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap7/target/krb/krb.2269988831769483313.keytab for HTTP/localhost.localdomain(a)JBOSS.ORG
> 14:20:19,323 INFO [stdout] (management task-7) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap7/target/krb/krb.2269988831769483313.keytab for HTTP/localhost.localdomain(a)JBOSS.ORG
> 14:20:19,323 INFO [stdout] (management task-7) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap7/target/krb/krb.2269988831769483313.keytab for HTTP/localhost.localdomain(a)JBOSS.ORG
> 14:20:19,323 INFO [stdout] (management task-7) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap7/target/krb/krb.2269988831769483313.keytab for HTTP/localhost.localdomain(a)JBOSS.ORG
> 14:20:19,524 WARN [org.apache.directory.server.protocol.shared.kerberos.StoreUtils] (NioDatagramAcceptor-3) No server entry found for kerberos principal name HTTPS/localhost.localdomain(a)JBOSS.ORG
> 14:20:19,524 WARN [org.apache.directory.server.KERBEROS_LOG] (NioDatagramAcceptor-3) No server entry found for kerberos principal name HTTPS/localhost.localdomain(a)JBOSS.ORG
> 14:20:19,524 WARN [org.apache.directory.server.kerberos.protocol.KerberosProtocolHandler] (NioDatagramAcceptor-3) Server not found in Kerberos database (7)
> 14:20:19,525 WARN [org.apache.directory.server.KERBEROS_LOG] (NioDatagramAcceptor-3) Server not found in Kerberos database (7)
> 14:20:19,528 WARN [org.apache.http.impl.auth.HttpAuthenticator] (main) NEGOTIATE authentication error: No valid credentials provided (Mechanism level: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7) - Server not found in Kerberos database))
> 14:20:19,532 TRACE [org.jboss.as.domain.management.security] (management task-9) No mapping for name 'https/localhost.localdomain' to KeytabService, attempting to use host only match.
> 14:20:19,532 TRACE [org.jboss.as.domain.management.security] (management task-9) Selected KeytabService with principal 'HTTP/localhost.localdomain(a)JBOSS.ORG' for host 'localhost.localdomain'
> 14:20:19,533 INFO [stdout] (management task-9) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap7/target/krb/krb.2269988831769483313.keytab for HTTP/localhost.localdomain(a)JBOSS.ORG
> 14:20:19,533 INFO [stdout] (management task-9) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap7/target/krb/krb.2269988831769483313.keytab for HTTP/localhost.localdomain(a)JBOSS.ORG
> 14:20:19,533 INFO [stdout] (management task-9) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap7/target/krb/krb.2269988831769483313.keytab for HTTP/localhost.localdomain(a)JBOSS.ORG
> 14:20:19,533 INFO [stdout] (management task-9) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap7/target/krb/krb.2269988831769483313.keytab for HTTP/localhost.localdomain(a)JBOSS.ORG
> [Krb5LoginModule]: Entering logout
> [Krb5LoginModule]: logged out Subject
> {code}
> Also see network dump krb_https_management.pcap in attachement, where TGS-REQ for HTTPS/localhost is captured.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-1515) Improve PersistentResourceDefinition to make it easier to register attribute write handlers
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1515?page=com.atlassian.jira.plugi... ]
Tomaz Cerar reassigned WFCORE-1515:
-----------------------------------
Assignee: (was: Tomaz Cerar)
> Improve PersistentResourceDefinition to make it easier to register attribute write handlers
> -------------------------------------------------------------------------------------------
>
> Key: WFCORE-1515
> URL: https://issues.jboss.org/browse/WFCORE-1515
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Tomaz Cerar
>
> Currently if you want to take register custom write handler you need to override whole registerAttributes methods and do it yourself all the way.
> We could add PersistentResourceDefinition.getAttributeHandlers() method that returns
> a Map<String, OperationStepHandler>.
> And then registerAttributes uses the map instead of hardcoding ReloadRequiredWriteAttributeHandler. Default impl just fills the map values with
> ReloadRequiredWriteAttributeHandler.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month