[JBoss JIRA] (WFLY-11127) Can not get activemq and undertow subsystem data from HTTP management api
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11127?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11127:
-----------------------------------------
The first one looks to be invalid JSON, the leading {"address": is missing.
> Can not get activemq and undertow subsystem data from HTTP management api
> -------------------------------------------------------------------------
>
> Key: WFLY-11127
> URL: https://issues.jboss.org/browse/WFLY-11127
> Project: WildFly
> Issue Type: Bug
> Components: Management, Web (Undertow)
> Affects Versions: 12.0.0.Final
> Reporter: Toni Moreno
> Assignee: Jeff Mesnil
> Priority: Critical
>
> As described in https://github.com/wildfly/wildfly/issues/11309
> I can not get some subsystems info data with the HTTP management API working with
>
> ======================================
> "product-version" => "12.0.0.Final",
> "product-community-identifier" => "Product",
> "product-home" => "/usr/local/wildfly-12.0.0.Final",
> "standalone-or-domain-identifier" => "HOST_CONTROLLER",
> "host-operating-system" => "Debian GNU/Linux 8 (jessie)}}
> ===============
> This the a activemq POST request with curl and its error
> ---------8<------------------------------------------8<-----------------------
> root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"host":"master","server":"server-two","subsystem":"messaging-activemq","server":"default"},"operation":"read-children-resources","child-type":"jms-queue","include-runtime":"true","json.pretty":1,"recursive-depth":2}' -u admin
> Enter host password for user 'admin':
> HTTP/1.1 401 Unauthorized
> Connection: keep-alive
> WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABCwnAAANoo77ka2vPx9H1LY0IuT5cmkcn5HWBS88gigGzT786K6qnnpMAk=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
> X-Frame-Options: SAMEORIGIN
> Content-Length: 77
> Content-Type: text/html
> Date: Sat, 02 Jun 2018 08:05:53 GMT
> HTTP/1.1 500 Internal Server Error
> Connection: keep-alive
> X-Frame-Options: SAMEORIGIN
> Content-Type: application/json; charset=utf-8
> Content-Length: 103
> Date: Sat, 02 Jun 2018 08:05:53 GMT
> "java.io.IOException: org.jboss.dmr.stream.ModelException: Unexpected content following the DMR
> --------->8------------------------------------------>8-----------------------
> And this the query with the GUI client
> [jboss_jms_queue_gui_query|https://user-images.githubusercontent.com/58834...]
> Also with undertow subsystem
> ---------8<------------------------------------------8<-----------------------
> root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"address":{"host":"master","server":"server-two","subsystem":"undertow","server":"default-server","http-listener":"default"},"include-runtime":"true","json.pretty":1,"operation":"read-resource","recursive-depth":0}' -u admin
> Enter host password for user 'admin':
> HTTP/1.1 401 Unauthorized
> Connection: keep-alive
> WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABC0jwAAN04NaeQD9tlEeeNzizRu5PGuUY9Adi18uuLUzOM1RZNHWkCqnc4=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
> X-Frame-Options: SAMEORIGIN
> Content-Length: 77
> Content-Type: text/html
> Date: Sat, 02 Jun 2018 08:19:54 GMT
> HTTP/1.1 500 Internal Server Error
> Connection: keep-alive
> X-Frame-Options: SAMEORIGIN
> Content-Type: application/json; charset=utf-8
> Content-Length: 302
> Date: Sat, 02 Jun 2018 08:19:54 GMT
> {
> "outcome" : "failed",
> "failure-description" : "WFLYCTL0030: No resource definition is registered for address [\n (\"host\" => \"master\"),\n (\"server\" => \"default-server\"),\n (\"subsystem\" => \"undertow\"),\n (\"http-listener\" => \"default\")\n]",
> "rolled-back" : true
> }
> --------->8------------------------------------------>8-----------------------
> Here Image of the GUI management query.
> [jboss_undertow_listener_gui_query|https://user-images.githubusercontent.c...]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11129) Temporary files not cleaned up after build
by Frank Langelage (Jira)
[ https://issues.jboss.org/browse/WFLY-11129?page=com.atlassian.jira.plugin... ]
Frank Langelage commented on WFLY-11129:
----------------------------------------
Approved.
Upgrading Galleon and Galleon-plugins from 2.0.0.Final to 2.0.1.Final like done in https://github.com/wildfly/wildfly-core/pull/3545 and https://github.com/wildfly/wildfly/commit/f8d4f64e1a6da1c585329ac63844878... solved this problem.
> Temporary files not cleaned up after build
> ------------------------------------------
>
> Key: WFLY-11129
> URL: https://issues.jboss.org/browse/WFLY-11129
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 14.0.1.Final
> Environment: Solaris SPARC 10, Oracle JDK 1.80,0_181
> Reporter: Frank Langelage
> Assignee: Yeray Borges
> Priority: Major
> Labels: maven
> Fix For: 15.0.0.Alpha1
>
>
> After building WildFly 14 from sources I have a lot of files in /var/tmp folder under a unique folder.
> {{sb2000.[neu2l]/mbi/mbi2e_all. ls -l /var/tmp
> total 5356
> drwxr-xr-x 3 jboss informix 512 Oct 6 14:47 1397ea75-a91c-490a-9860-0041c101ef3a
> drwxr-xr-x 3 jboss informix 512 Oct 6 13:47 23d28bb9-0bdd-4991-aa9b-8805d613e720
> drwxr-xr-x 3 jboss informix 512 Oct 5 23:34 2c3bd18e-8b83-46d3-b06f-18378e1cb12d
> drwxr-xr-x 3 jboss informix 512 Oct 6 14:56 396f75f7-45b0-4b50-9607-9060cabf018b
> drwxr-xr-x 3 jboss informix 512 Oct 6 13:48 521e2a76-764c-4f5a-8a6e-282dd5978991
> drwxr-xr-x 3 jboss informix 512 Oct 5 23:35 5430e295-1afa-4257-a2e0-e08b980b7e35
> drwxr-xr-x 3 jboss informix 512 Oct 6 14:53 5a265551-8f04-48c9-8945-abf830e54852
> drwxr-xr-x 3 jboss informix 512 Oct 6 13:46 70a1f863-7e84-40df-9206-23690bcf3ef6
> drwxr-xr-x 3 jboss informix 512 Oct 5 22:02 7186627a-5a89-4334-bdc2-8bfb944e3841
> drwxr-xr-x 3 jboss informix 512 Oct 6 14:52 85663b19-7e4e-48e9-8988-bd24c11fe4d4
> drwxr-xr-x 3 jboss informix 512 Oct 5 23:39 8842f374-85b7-4018-a1fc-6274cb704785
> drwxr-xr-x 3 jboss informix 512 Oct 5 22:05 973d7e32-efe5-4ffa-8f02-079cb7f29e71
> drwxr-x--- 3 oracle dba 2560 Aug 30 00:00 CVU_18.0.0.0.0_oracle
> drwxr-xr-x 3 jboss informix 512 Oct 5 22:06 b8975817-9381-41a3-a512-e8fc6596fa7a
> drwxr-xr-x 3 jboss informix 512 Oct 6 13:40 bd0c1dd7-e8c6-413d-b658-f3c5236bba34
> drwxr-xr-x 3 jboss informix 512 Oct 6 14:54 c3aa3f01-66df-4066-bb35-fed4bd0ad559
> drwxr-xr-x 3 jboss informix 512 Oct 5 23:32 c66c2972-ad28-49e9-a7ff-a7ceed5b7ea3
> drwxr-xr-x 3 jboss informix 512 Oct 5 23:24 ca8816d8-ad10-4860-a18b-0c09b37ed88b
> drwxr-xr-x 3 jboss informix 512 Oct 6 13:50 cc799f82-ed02-4dc4-b56e-ffe0d8eeab75
> drwx------ 2 langfr staff 512 Nov 15 2006 orbit-lafr
> -rw-rw-rw- 1 langfr staff 2383862 Oct 5 03:17 patchdiag.xref
> -rw------- 1 root root 314461 Oct 6 15:32 wscon-:0-5saqic}}
> {{sb2000.[neu2l]/var/tmp. ls -l 396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/*/current
> 396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/wildfly-core/current:
> total 2
> drwxr-xr-x 7 jboss informix 512 Oct 6 14:55 6.0.2.Final
> 396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/wildfly-servlet/current:
> total 2
> drwxr-xr-x 6 jboss informix 512 Oct 6 14:55 14.0.1.Final
> 396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/wildfly/current:
> total 2
> drwxr-xr-x 6 jboss informix 512 Oct 6 14:55 14.0.1.Final}}
> Created by galleon feature pack build (galleon-pack/wildfly-feature-pack-build.xml).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11128) wsconsume failure on wildfly14 + JDK 11
by R Searls (Jira)
[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ]
R Searls commented on WFLY-11128:
---------------------------------
wsconsume needs a wsdl. Your zip file is just the java files. Do you have the wsdl for this?
> wsconsume failure on wildfly14 + JDK 11
> ---------------------------------------
>
> Key: WFLY-11128
> URL: https://issues.jboss.org/browse/WFLY-11128
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 14.0.0.Final
> Environment: Windows 7 64bits
> JDK 11
> Wildfly 14
> Reporter: mazen mahmoud
> Assignee: R Searls
> Priority: Major
> Attachments: demo-service-code.zip, log.txt, logs.zip
>
>
> running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
> the service is very simple.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (JBLOGGING-111) LoggerProvider configured with new ServiceLoader crash
by Steven Sharp (Jira)
[ https://issues.jboss.org/browse/JBLOGGING-111?page=com.atlassian.jira.plu... ]
Steven Sharp commented on JBLOGGING-111:
----------------------------------------
Thank you, [~dmlloyd]. You are correct that we are looking for another means of logger configuration. I have created an enhancement request ([JBLOGGING-133|https://issues.jboss.org/browse/JBLOGGING-133]) for this discussion.
> LoggerProvider configured with new ServiceLoader crash
> ------------------------------------------------------
>
> Key: JBLOGGING-111
> URL: https://issues.jboss.org/browse/JBLOGGING-111
> Project: JBoss Logging
> Issue Type: Bug
> Affects Versions: 3.2.0.Beta1
> Environment: Weblogic 10.3.2.0
> Configured in ejb jar, deployed by an ear file
> Reporter: Frederic Allard
> Assignee: James Perkins
> Priority: Major
> Fix For: 3.2.0.Final
>
>
> There is a new feature in the beta which uses the ServiceLoader to specify a LoggerProvider to be used by JBoss Logging.
> org.jboss.logging.LoggerProviders snippet :
> {code}
> // Next try for a service provider
> try {
> final ServiceLoader<LoggerProvider> loader = ServiceLoader.load(LoggerProvider.class, cl);
> if (loader.iterator().hasNext()) {
> return loader.iterator().next();
> }
> } catch (Throwable ignore) {
> // TODO consider printing the stack trace as it should only happen once
> }
> {code}
> When you try to configure a provider (ex. org.jboss.logging.Slf4jLoggerProvider), the ServiceLoader crash silently and ignore the provider.
> {code}
> java.util.ServiceConfigurationError: org.jboss.logging.LoggerProvider: Provider org.jboss.logging.Slf4jLoggerProvider could not be instantiated: java.lang.IllegalAccessException: Class java.util.ServiceLoader$LazyIterator can not access a member of class org.jboss.logging.Slf4jLoggerProvider with modifiers ""
> at java.util.ServiceLoader.fail(ServiceLoader.java:207)
> at java.util.ServiceLoader.access$100(ServiceLoader.java:164)
> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:353)
> at java.util.ServiceLoader$1.next(ServiceLoader.java:421)
> at org.jboss.logging.LoggerProviders.findProvider(LoggerProviders.java:70)
> at org.jboss.logging.LoggerProviders.find(LoggerProviders.java:32)
> at org.jboss.logging.LoggerProviders.<clinit>(LoggerProviders.java:29)
> at org.jboss.logging.Logger.getLogger(Logger.java:2177)
> at org.jboss.logging.Logger$1.run(Logger.java:2277)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.logging.Logger.getMessageLogger(Logger.java:2241)
> at org.jboss.logging.Logger.getMessageLogger(Logger.java:2228)
> at org.hibernate.cfg.Configuration.<clinit>(Configuration.java:176)
> ...
> {code}
> This is caused by the fact that all JBoss providers are not public classes and are instead package classes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (JBLOGGING-133) Support specification of existing logging provider other than by system property.
by Steven Sharp (Jira)
Steven Sharp created JBLOGGING-133:
--------------------------------------
Summary: Support specification of existing logging provider other than by system property.
Key: JBLOGGING-133
URL: https://issues.jboss.org/browse/JBLOGGING-133
Project: JBoss Logging
Issue Type: Feature Request
Components: jboss-logging-spi
Reporter: Steven Sharp
Assignee: James Perkins
The only way to choose a logging provider other than jboss is by using the {{org.jboss.logging.provider}} system property. There are cases where this is not feasible or even possible. Since using the service loader method is not a supported solution, there needs to be an alternative to the system property for selecting a different logging provider.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11139) Exception from getRunningExecutions method causes undeployment to hang
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-11139?page=com.atlassian.jira.plugin... ]
Cheng Fang updated WFLY-11139:
------------------------------
Description:
When undeploying a batch application, or stopping the server with active batch application deployment, the batch subsystem tries to get all running batch job executionsm, and to stop them before undeploying the application or shutting down the server.
When exceptions occurs from calling {{batchJobReposiotory.getRunningExecutions}}, the undeployment operation hangs. This happens to both in-memory and jdbc batch job repository. These exceptions may be caused by database server down, or connection timeout, for instance.
was:
When undeploying a batch application, or stopping the server with active batch application deployment, the batch subsystem tries to get all running batch job executionsm, and to stop them before undeploying the application or shutting down the server.
When exceptions occurs from calling {{batchJobReposiotory.getRunningExecutions}}, the undeployment operation hangs. This happens to both in-memory and jdbc batch job repository.
> Exception from getRunningExecutions method causes undeployment to hang
> ----------------------------------------------------------------------
>
> Key: WFLY-11139
> URL: https://issues.jboss.org/browse/WFLY-11139
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Affects Versions: 14.0.0.Final
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
>
> When undeploying a batch application, or stopping the server with active batch application deployment, the batch subsystem tries to get all running batch job executionsm, and to stop them before undeploying the application or shutting down the server.
> When exceptions occurs from calling {{batchJobReposiotory.getRunningExecutions}}, the undeployment operation hangs. This happens to both in-memory and jdbc batch job repository. These exceptions may be caused by database server down, or connection timeout, for instance.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11139) Exception from getRunningExecutions method causes undeployment to hang
by Cheng Fang (Jira)
Cheng Fang created WFLY-11139:
---------------------------------
Summary: Exception from getRunningExecutions method causes undeployment to hang
Key: WFLY-11139
URL: https://issues.jboss.org/browse/WFLY-11139
Project: WildFly
Issue Type: Bug
Components: Batch
Affects Versions: 14.0.0.Final
Reporter: Cheng Fang
Assignee: Cheng Fang
When undeploying a batch application, or stopping the server with active batch application deployment, the batch subsystem tries to get all running batch job executionsm, and to stop them before undeploying the application or shutting down the server.
When exceptions occurs from calling {{batchJobReposiotory.getRunningExecutions}}, the undeployment operation hangs. This happens to both in-memory and jdbc batch job repository.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11138) [GSS](7.1.z) NPE when trying to remove an EJB subsystem channel-creation-options resource
by Brad Maxwell (Jira)
Brad Maxwell created WFLY-11138:
-----------------------------------
Summary: [GSS](7.1.z) NPE when trying to remove an EJB subsystem channel-creation-options resource
Key: WFLY-11138
URL: https://issues.jboss.org/browse/WFLY-11138
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 11.0.0.CR1
Reporter: Brad Maxwell
Assignee: Brian Stansberry
Fix For: 12.0.0.Beta1, 12.0.0.Final
This fails:
{code}
[standalone@localhost:9990 /] /subsystem=ejb3:remove
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException",
"rolled-back" => true
}
{code}
with this in the server log:
{code}
15:53:42,572 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("remove") failed - address: ([
("subsystem" => "ejb3"),
("service" => "remote"),
("channel-creation-options" => "MAX_OUTBOUND_MESSAGES")
]): java.lang.NullPointerException
at org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:894)
at org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:884)
at org.jboss.as.controller.RestartParentResourceHandlerBase.getModel(RestartParentResourceHandlerBase.java:216)
at org.jboss.as.controller.RestartParentResourceHandlerBase.access$000(RestartParentResourceHandlerBase.java:39)
at org.jboss.as.controller.RestartParentResourceHandlerBase$1.execute(RestartParentResourceHandlerBase.java:66)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:980)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418)
...
{code}
I believe a post-boot add of this resource would fail as well.
Problem is ChannelCreationOptionRemove and ChannelCreationOptionAdd in RemoteConnectorChannelCreationOptionResource use an incorrect parentKeyName. These handlers extend RestartParentResourceHandlerBase but are passing the *value* of the parent element as "parentKeyName" instead of its *key*; i.e. "remote" instead of "service".
Even though this code has been like this since 2012, this is somewhat a regression since before the current version our standard configs did not include resources of this type. So users could hit this in previous releases but now they are more likely to.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
