I'm trying to add microprofile opentracing subsystem to Wildfly23 using thins guide: https://github.com/wildfly/wildfly/blob/main/docs/src/main/asciidoc/_admin-guide/subsystem-configuration/MicroProfile_OpenTracing_SmallRye.adoc
However, the second step fails:
[standalone#localhost:9990 /] /subsystem=microprofile-opentracing-smallrye:add
ERROR [org.jboss.as.cli.CommandContext] {
"outcome" => "failed",
"failure-description" => "WFLYCTL0369: Required capabilities are not available:
org.wildfly.microprofile.config; There are no known registration points which can provide this capability.",
"rolled-back" => true
}
I tried adding microprofile config using this model as a reference: https://docs.wildfly.org/23/wildscribe/subsystem/microprofile-config-smallrye/index.html however i get this error
[standalone#localhost:9990 /] /subsystem=microprofile-config-smallrye:add
ERROR [org.jboss.as.cli.CommandContext] {
"outcome" => "failed",
"failure-description" => "WFLYCTL0030: No resource definition is registered for address [(\"subsystem\" => \"microprofile-config-smallrye\")]",
"rolled-back" => true
}
What am i missing? The doc seems fresh enough, last updated in March on 2021...
You also need to install the extensions "org.wildfly.extension.microprofile.config-smallrye" and "org.wildfly.extension.microprofile.opentracing-smallrye" before adding the subsystems.
Also wildfly provides a standalone-microprofile.xml that can server as example.
Related
I am trying to migrate WildFly 21 to 24 .
I have these errors in the console. Server can not running it is stopped.
14:11:19,550 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available:
org.wildfly.extension.health.http-context; There are no known registration points which can provide this capability.
org.wildfly.extension.health.server-probes; There are no known registration points which can provide this capability. 14:11:19,550 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-metrics-smallrye' are not available:
org.wildfly.extension.metrics.http-context; There are no known registration points which can provide this capability.
I have added metrics and health extensions to standalone xmls
<extension module="org.wildfly.extension.microprofile.health-smallrye"/>
<extension module="org.wildfly.extension.microprofile.metrics-smallrye"/>
<subsystem xmlns="urn:wildfly:microprofile-health-smallrye:2.0" security-enabled="false" empty-liveness-checks-status="${env.MP_HEALTH_EMPTY_LIVENESS_CHECKS_STATUS:UP}" empty-readiness-checks-status="${env.MP_HEALTH_EMPTY_READINESS_CHECKS_STATUS:UP}"/>
<subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>
but for main configuration file I am using a different xml.
I saw in another questions using jboss.cli to add these extensions but jboss cli is not connecting because server can not running currently.
Do you have any suggestions or advices ?
Thanks.
You can still use CLI in "offline" mode to add the extension. First simply enter a CLI session with:
$JBOSS_HOME/bin/jboss-cli.sh
Then you can start the embedded server to make your changes.
embed-server
You should end up seeing something like this:
[disconnected /] embed-server
[standalone#embedded /]
From here you can enter CLI commands like:
/extension=org.wildfly.extension.microprofile.health-smallrye:add
/extension=org.wildfly.extension.microprofile.metrics-smallrye:add
/subsystem=microprofile-health-smallrye:add(security-enabled=false, empty-liveness-checks-status="${env.MP_HEALTH_EMPTY_LIVENESS_CHECKS_STATUS:UP}", empty-readiness-checks-status="${env.MP_HEALTH_EMPTY_READINESS_CHECKS_STATUS:UP}")
The output should look something like:
[standalone#embedded /] /extension=org.wildfly.extension.microprofile.health-smallrye:add
{"outcome" => "success"}
[standalone#embedded /] /extension=org.wildfly.extension.microprofile.metrics-smallrye:add
{"outcome" => "success"}
[standalone#embedded /] /subsystem=microprofile-health-smallrye:add(security-enabled=false, empty-liveness-checks-status="${env.MP_HEALTH_EMPTY_LIVENESS_CHECKS_STATUS:UP}", empty-readiness-checks-status="${env.MP_HEALTH_EMPTY_READINESS_CHECKS_STATUS:UP}")
{"outcome" => "success"}
Then you can just exit CLI.
I found out microprofile.health-smallrye and microprofile.metrics-smallrye are not supported in WildFly 24. You should use subsystem=metrics,subsystem=health.
If you look into this in detail check here.
So, my question is in theme.
Firstly, I added into EAP 6 my vault with command
/core-service=vault:add(vault-options=[("KEYSTORE_URL" => "PATH_TO_KEYSTORE"), ("KEYSTORE_PASSWORD" => "MASKED_PASSWORD"), ("KEYSTORE_ALIAS" => "ALIAS"), ("SALT" => "SALT"),("ITERATION_COUNT" => "ITERATION_COUNT"), ("ENC_FILE_DIR" => "ENC_FILE_DIR")])
But I got mistake and try do the same command with correct fields, but get exception
{"outcome" => "failed",
"failure-description" => "JBAS014803: Duplicate resource [(\"core-service\" => \"vault\")]",
"rolled-back" => true
}
In standalone.xml I deleted any vault but still got that error.
How to fix it?
Or How can I find that in my web-console?
The problem was because I had to stop JBoss and after that remove
<vault>...</vault>
elements from standalone.xml.
After that start JBoss and again do action from management cli. There is noone error happen
I started wildfly 24 server with standalone-full.xml profile, when i run following command in jboss-cli to create jms-queue i get following error
[standalone#localhost:9990 /] jms-queue --profile=full add --queue-address=foo --entries=["java:/jms/queue/foo"]
WFLYCTL0175: Resource [
("subsystem" => "messaging-activemq"),
("server" => "default")
] does not exist; a resource at address [
("subsystem" => "messaging-activemq"),
("server" => "default"),
("jms-queue" => "foo")
] cannot be created until all ancestor resources have been added
What am i missing here? Any reference docs to create the jms server, queues?
Update:
I tried to create the server using web console first
And it filed with the required capabilities are not available, any documentation refernece that indicates what are the required capabilities i need to added prior configuring JMS
Yes don't use the profile parameter which is used in domain mode.
jms-queue add --queue-address=foo --entries=["java:/jms/queue/foo"]
works properly.
The issue is i was using wildfly "WildFly Preview EE 9.1 Distribution" the correct verirsion is "Jakarta EE 8 Full & Web Distribution"
I am adding a new security realm and https-listener with CLI:
/core-service=management/security-realm=HTTPSRealm/:add
/core-service=management/security-realm=HTTPSRealm/server-identity=ssl:add(alias=ssl,keystore-path="/path/to/configuration/testCA.jks", keystore-password="12345678")
reload
/subsystem=undertow/server=default-server/https-listener=https:add(socket-binding="proxy-https", security-realm="HTTPSRealm")
At the last step I only get this:
{
"outcome" => "failed",
"failure-description" => undefined,
"rolled-back" => true
}
I already tried every solution I could find here. (running as batch etc)
Edit:
The listener config is added like this:
/socket-binding-group=standard-sockets/socket-binding=proxy-http:add(port=9080)
/socket-binding-group=standard-sockets/socket-binding=proxy-https:add(port=9443)
Have you created socket bindings for proxy-https ? The default binding is https. Try with it
/subsystem=undertow/server=default-server/https-listener=https:add(socket-binding=https, security-realm=HTTPSRealm)
In JBossAS4, the MBean jboss.jca.ManagedConnectionPool allows to access, e.g., the number of used and the number of available connections of a data source. This MBean is no longer available in JBossAS7.
How can these values be accessed in JBossAS7? There seems to be a way: the JBoss Adminstration Console offers the values.
OK on windows or Linux you can can use Jboss cli (client interface).
This is on JBOSS AS 7.1.3
On my windows box this is what I did (My jboss home is C:\jboss-eap-6.0)
Execute the following batch file
C:\jboss-eap-6.0\bin\jboss-cli.bat
It will take you to a prompt
[disconnected /]
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands
.
Now type connect. for all other command try help. This will allow you to browse the JMX tree (May be my terminology may be wrong).
[disconnected /]connect
[standalone#rama-local:9999]
Lets say my data pool name is "OracleSampleDS"
Then you can query the stats by using below command
/subsystem=datasources/data-source=OracleSampleDS/statistics=pool:read-resource(include-runtime=true)
Here is the output I got
{
"outcome" => "success",
"result" => {
"ActiveCount" => "0",
"AvailableCount" => "20",
"AverageBlockingTime" => "0",
"AverageCreationTime" => "0",
"CreatedCount" => "0",
"DestroyedCount" => "0",
"MaxCreationTime" => "0",
"MaxUsedCount" => "0",
"MaxWaitTime" => "0",
"TimedOut" => "0",
"TotalBlockingTime" => "0",
"TotalCreationTime" => "0"
}
}
In case you changed the hostname during jboss installation to anything other than localhost you can edit jboss-cli.xml
I tried the same command on linux by using jboss-cl.sh
In case you have separate profile (mostly if you use domain mode) then specify the profile name as below.
/profile=full-ha/subsystem=datasources/data-source=OracleSampleDS/statistics=jdbc:read-resource(include-runtime=true)
Here the profile I was using in domain mode was "full-ha"
Once you are connected to the Jboss command line tool you can use few commands like
ls
pwn
connect
quit
(Try it out)
Also there is
http://loclahost:9990/management/subsystem/datasources/data-source/OracleSampleDS/statistics/pool?include-runtime=true
The ports my differ please see your hosts.xml (in case you are using domain mode)
or standalone.xml to see which management ports you have exposed by checking
Look at the section that says http-interface security-realm="ManagementRealm"
There is a MBean jboss.as:subsystem=datasources,xa-data-source=DATASOURCENAME_Pool which has all of the configuration attributes, but it does not feature statistics. According to this thread, the statistics are only exposed to the management API (http access with JSON export).