[JBoss JIRA] (WFLY-9450) NPE on jaxrs subsystem of FAILED deployment
by Bartosz Baranowski (Jira)
[ https://issues.redhat.com/browse/WFLY-9450?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski edited comment on WFLY-9450 at 1/29/20 4:21 AM:
-------------------------------------------------------------------
[~emiliocuberos] - this seem to be different issue. Please open new JIRA and attach reproducer.
was (Author: baranowb):
@Emilio Cuberos - this seem to be different issue. Please open new JIRA and attach reproducer.
> NPE on jaxrs subsystem of FAILED deployment
> --------------------------------------------
>
> Key: WFLY-9450
> URL: https://issues.redhat.com/browse/WFLY-9450
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 15.0.1.Final
> Reporter: Claudio Miranda
> Assignee: Bartosz Baranowski
> Priority: Major
> Fix For: 19.0.0.Beta1
>
>
> read deployment resources of a server, where one deployment is in failed status, throws a NPE and doesn't return the list of deployed applications.
> To reproduce, get the kitchensink from quickstarts, change the persistence.xml to point to ExampleDS datasource, deploy and assign to main-server-group. Then disable ExampleDS, restart server-one.
> Run the following command:
> {code}
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> {code}
> deploy ~/redhat/git/quickstart/kitchensink/target/kitchensink.war --server-groups=main-server-group
> /profile=default/subsystem=datasources/data-source=ExampleDS:write-attribute(name=enabled,value=false)
> /profile=full/subsystem=datasources/data-source=ExampleDS:write-attribute(name=enabled,value=false)
> /profile=full-ha/subsystem=datasources/data-source=ExampleDS:write-attribute(name=enabled,value=false)
> /host=master/server=server-one:reload
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> The exception in server.log
> {code}
> 2017-10-17 17:08:02,778 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "jaxrs"),
> ("rest-resource" => "org.jboss.as.quickstarts.kitchensink.rest.MemberResourceRESTService")
> ]): java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.getDeployment(UndertowDeploymentService.java:170)
> at org.jboss.as.jaxrs.DeploymentRestResourcesDefintion$AbstractRestResReadHandler.execute(DeploymentRestResourcesDefintion.java:183)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:172)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:135)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:231)
> {code}
> The CLI results doesn't display the error message
> {code}
> [domain@localhost:9990 /] /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => undefined,
> "failure-description" => undefined
> }
> {code}
> There is a similar problem while reading a specific deployment,
> {code}
> /host=master/server=server-one/deployment=kitchensink.war:read-children-resources(child-type=subsystem,recursive)
> {code}
> results in the following error in server.log
> {code}
> 2017-10-17 17:16:09,857 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "ejb3"),
> ("stateless-session-bean" => "MemberRegistration")
> ]) - failure description: "WFLYEJB0370: EJB component for address [
> (\"deployment\" => \"kitchensink.war\"),
> (\"subsystem\" => \"ejb3\"),
> (\"stateless-session-bean\" => \"MemberRegistration\")
> ] is in
> state DOWN, must be in state UP"
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-9450) NPE on jaxrs subsystem of FAILED deployment
by Bartosz Baranowski (Jira)
[ https://issues.redhat.com/browse/WFLY-9450?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski commented on WFLY-9450:
------------------------------------------
@Emilio Cuberos - this seem to be different issue. Please open new JIRA and attach reproducer.
> NPE on jaxrs subsystem of FAILED deployment
> --------------------------------------------
>
> Key: WFLY-9450
> URL: https://issues.redhat.com/browse/WFLY-9450
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 15.0.1.Final
> Reporter: Claudio Miranda
> Assignee: Bartosz Baranowski
> Priority: Major
> Fix For: 19.0.0.Beta1
>
>
> read deployment resources of a server, where one deployment is in failed status, throws a NPE and doesn't return the list of deployed applications.
> To reproduce, get the kitchensink from quickstarts, change the persistence.xml to point to ExampleDS datasource, deploy and assign to main-server-group. Then disable ExampleDS, restart server-one.
> Run the following command:
> {code}
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> {code}
> deploy ~/redhat/git/quickstart/kitchensink/target/kitchensink.war --server-groups=main-server-group
> /profile=default/subsystem=datasources/data-source=ExampleDS:write-attribute(name=enabled,value=false)
> /profile=full/subsystem=datasources/data-source=ExampleDS:write-attribute(name=enabled,value=false)
> /profile=full-ha/subsystem=datasources/data-source=ExampleDS:write-attribute(name=enabled,value=false)
> /host=master/server=server-one:reload
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> The exception in server.log
> {code}
> 2017-10-17 17:08:02,778 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "jaxrs"),
> ("rest-resource" => "org.jboss.as.quickstarts.kitchensink.rest.MemberResourceRESTService")
> ]): java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.getDeployment(UndertowDeploymentService.java:170)
> at org.jboss.as.jaxrs.DeploymentRestResourcesDefintion$AbstractRestResReadHandler.execute(DeploymentRestResourcesDefintion.java:183)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:172)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:135)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:231)
> {code}
> The CLI results doesn't display the error message
> {code}
> [domain@localhost:9990 /] /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => undefined,
> "failure-description" => undefined
> }
> {code}
> There is a similar problem while reading a specific deployment,
> {code}
> /host=master/server=server-one/deployment=kitchensink.war:read-children-resources(child-type=subsystem,recursive)
> {code}
> results in the following error in server.log
> {code}
> 2017-10-17 17:16:09,857 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "ejb3"),
> ("stateless-session-bean" => "MemberRegistration")
> ]) - failure description: "WFLYEJB0370: EJB component for address [
> (\"deployment\" => \"kitchensink.war\"),
> (\"subsystem\" => \"ejb3\"),
> (\"stateless-session-bean\" => \"MemberRegistration\")
> ] is in
> state DOWN, must be in state UP"
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4820) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ]
Darran Lofthouse reassigned WFCORE-4820:
----------------------------------------
Assignee: (was: Darran Lofthouse)
> Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4820
> URL: https://issues.redhat.com/browse/WFCORE-4820
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Affects Versions: 10.0.3.Final
> Reporter: Mark Sanchez
> Priority: Major
>
> error:
> WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> We get an error with the following ldap configuration. This works for version 17.
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <engine enabled-protocols="TLSv1.2"/>
> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> </security-realms>
> <outbound-connections>
> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
> </outbound-connections>
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4820) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ]
Darran Lofthouse commented on WFCORE-4820:
------------------------------------------
Can you please post the full error including any associated stack trace.
> Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4820
> URL: https://issues.redhat.com/browse/WFCORE-4820
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Affects Versions: 10.0.3.Final
> Reporter: Mark Sanchez
> Priority: Major
>
> error:
> WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> We get an error with the following ldap configuration. This works for version 17.
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <engine enabled-protocols="TLSv1.2"/>
> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> </security-realms>
> <outbound-connections>
> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
> </outbound-connections>
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-13031) EAP quickstart 'messaging-clustering-singleton' shows errors after import
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFLY-13031?page=com.atlassian.jira.plugi... ]
Parul Sharma moved JBEAP-17131 to WFLY-13031:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-13031 (was: JBEAP-17131)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Quickstarts
(was: JMS)
(was: Quickstarts)
Environment: (was: OS X 10.14.5)
Target Release: (was: 7.backlog.GA)
Affects Version/s: (was: 7.2.0.GA)
> EAP quickstart 'messaging-clustering-singleton' shows errors after import
> -------------------------------------------------------------------------
>
> Key: WFLY-13031
> URL: https://issues.redhat.com/browse/WFLY-13031
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Zbyněk Červinka
> Assignee: Parul Sharma
> Priority: Major
> Attachments: Problems view.png, Project Explorer.png, jboss-ejb3.xml file.png
>
>
> h1. EAP quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import:
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4967) decision table rules are not loaded into kiebase
by Volodymyr Shymkiv (Jira)
[ https://issues.redhat.com/browse/DROOLS-4967?page=com.atlassian.jira.plug... ]
Volodymyr Shymkiv commented on DROOLS-4967:
-------------------------------------------
Attached your file updated. It won't be working but it is completely the same as yours. Just edited in excel in different order...
> decision table rules are not loaded into kiebase
> ------------------------------------------------
>
> Key: DROOLS-4967
> URL: https://issues.redhat.com/browse/DROOLS-4967
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 7.21.0.Final, 7.22.0.Final, 7.23.0.Final, 7.24.0.Final, 7.25.0.Final, 7.26.0.Final, 7.27.0.Final, 7.28.0.Final, 7.29.0.Final, 7.30.0.Final, 7.31.0.Final
> Reporter: Volodymyr Shymkiv
> Assignee: Mario Fusco
> Priority: Blocker
> Attachments: CanDrink2.xls, CanNotDrink2.xls
>
>
> When compiling xls decision table, wrong ruleset name is parsed from the xls file. This can lead to multiple issues, like rules being filtered out by kmodule.xml configuration.
> According to documentation, decision table begins with a cell at second or third column, having value RuleSet. The cell on the right of this one contains the name of the rule set, which we want to use as a package name.
> The problem lies in naive approach to parsing the package name from the xls file. As you can see in project drools-compiler, class org.drools.compiler.kie.builder.impl.KieBuilderImpl method packageNameFromDtable, it execute as follows:
> # find "RuleSet" string in the binary data
> # find and return the nearest string which can act as a valid java package name
> The problem is, the string returned from packageNameFromDtable is NOT the value of the cell next to the RuleSet. It is actually a value of a random cell.
> To understand the problem, we need to understand the binary content of the actual xls file. Every cell is presented as a few bytes, containing cell's value, position, and other information. The "problematic" thing here is, the _order_ of the cells in the binary data is NOT constant. BUT the code really just reads the cell _binary_ next to the "RuleSet" cell.
> Problem is present since version 7.21 as it is caused by a fix for DROOLS-3888 - commit 9a179b6e6b955889200b0258ccd18cd1a5f14b46
> In our case, this results in rules not being loaded, as they are filtered out by kmodule.xml configuration. We have a lot of decision tables we want to migrate from an older drools version, and most of them are now ignored due to this bug.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4967) decision table rules are not loaded into kiebase
by Volodymyr Shymkiv (Jira)
[ https://issues.redhat.com/browse/DROOLS-4967?page=com.atlassian.jira.plug... ]
Volodymyr Shymkiv updated DROOLS-4967:
--------------------------------------
Attachment: CanNotDrink2.xls
> decision table rules are not loaded into kiebase
> ------------------------------------------------
>
> Key: DROOLS-4967
> URL: https://issues.redhat.com/browse/DROOLS-4967
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 7.21.0.Final, 7.22.0.Final, 7.23.0.Final, 7.24.0.Final, 7.25.0.Final, 7.26.0.Final, 7.27.0.Final, 7.28.0.Final, 7.29.0.Final, 7.30.0.Final, 7.31.0.Final
> Reporter: Volodymyr Shymkiv
> Assignee: Mario Fusco
> Priority: Blocker
> Attachments: CanDrink2.xls, CanNotDrink2.xls
>
>
> When compiling xls decision table, wrong ruleset name is parsed from the xls file. This can lead to multiple issues, like rules being filtered out by kmodule.xml configuration.
> According to documentation, decision table begins with a cell at second or third column, having value RuleSet. The cell on the right of this one contains the name of the rule set, which we want to use as a package name.
> The problem lies in naive approach to parsing the package name from the xls file. As you can see in project drools-compiler, class org.drools.compiler.kie.builder.impl.KieBuilderImpl method packageNameFromDtable, it execute as follows:
> # find "RuleSet" string in the binary data
> # find and return the nearest string which can act as a valid java package name
> The problem is, the string returned from packageNameFromDtable is NOT the value of the cell next to the RuleSet. It is actually a value of a random cell.
> To understand the problem, we need to understand the binary content of the actual xls file. Every cell is presented as a few bytes, containing cell's value, position, and other information. The "problematic" thing here is, the _order_ of the cells in the binary data is NOT constant. BUT the code really just reads the cell _binary_ next to the "RuleSet" cell.
> Problem is present since version 7.21 as it is caused by a fix for DROOLS-3888 - commit 9a179b6e6b955889200b0258ccd18cd1a5f14b46
> In our case, this results in rules not being loaded, as they are filtered out by kmodule.xml configuration. We have a lot of decision tables we want to migrate from an older drools version, and most of them are now ignored due to this bug.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JGRP-2436) Diagnostics: enable TCP by default
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2436?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2436:
--------------------------------
I had to revert this: the testsuite created way too many ports, some members failed to start because they failed to allocate a port in range {{7500..7550}} (port_range=50).
Need to rethink this...
> Diagnostics: enable TCP by default
> ----------------------------------
>
> Key: JGRP-2436
> URL: https://issues.redhat.com/browse/JGRP-2436
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 5.0, 4.2.0
>
>
> Set {{diag_enable_tcp}} to true by default; a lot of deployments happen in the cloud today, and if we don't enable this, {{probe -addr ADDR}} will only return a response from the local member.
> This will open a UDP *and* TCP diagnostics socket, but if {{enable_diagnostics}} is false, then no socket will be opened
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months