August 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5226) [Migration operation] [Web to Undertow] Web subsystem attribute "password" should be migrated as "keystore-password" for both

by Radim Hatlapatka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5226?page=com.atlassian.jira.plugin.... ] Radim Hatlapatka updated WFLY-5226: ----------------------------------- Affects Version/s: 10.0.0.Beta2 > [Migration operation] [Web to Undertow] Web subsystem attribute "password" should be migrated as "keystore-password" for both > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-5226 > URL: https://issues.jboss.org/browse/WFLY-5226 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Priority: Blocker > > When calling migrate on web with defined https connector as > {code:xml} > <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true"> > <ssl key-alias="javaserver" password="tomcat" certificate-key-file="${jboss.server.config.dir}/server-cert-key-rsa.jks" > certificate-file="${jboss.server.config.dir}/server-cert-key-rsa.jks" > ca-certificate-file="${jboss.server.config.dir}/ca-cert.jks" > keystore-type="JKS" truststore-type="JKS"/> > {code} > it fails on migrating Web subystem ssl config password attribute to keystore-password in security realms, see > {noformat} > "migration-error" => {"operation" => {"operation" => "add","address" => [("core-service" => "management"),("security-realm" => "jbossweb-migration-security-realm1"),("authentication" => "truststore")],"keystore-path" => expression "${jboss.server.config.dir}/ca-cert.jks","keystore-password" => undefined,"keystore-provider" => "JKS","operation-headers" => {"caller-type" => "user","access-mechanism" => "NATIVE"}},"result" => {"outcome" => "failed","failure-description" => "WFLYCTL0155: keystore-password may not be null","rolled-back" => true}}},"failure-description" => "WFLYWEB0005: Migration failed, see results for more details.","rolled-back" => true} > {noformat} > Marking as blocker as this operation fails for migrating of critical part of Web subsystem configuration as is HTTPS ssl configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5226) [Migration operation] [Web to Undertow] Web subsystem attribute "password" should be migrated as "keystore-password" for both

by Radim Hatlapatka (JIRA)

Radim Hatlapatka created WFLY-5226: -------------------------------------- Summary: [Migration operation] [Web to Undertow] Web subsystem attribute "password" should be migrated as "keystore-password" for both Key: WFLY-5226 URL: https://issues.jboss.org/browse/WFLY-5226 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Radim Hatlapatka Assignee: Stuart Douglas Priority: Blocker When calling migrate on web with defined https connector as {code:xml} <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true"> <ssl key-alias="javaserver" password="tomcat" certificate-key-file="${jboss.server.config.dir}/server-cert-key-rsa.jks" certificate-file="${jboss.server.config.dir}/server-cert-key-rsa.jks" ca-certificate-file="${jboss.server.config.dir}/ca-cert.jks" keystore-type="JKS" truststore-type="JKS"/> {code} it fails on migrating Web subystem ssl config password attribute to keystore-password in security realms, see {noformat} "migration-error" => {"operation" => {"operation" => "add","address" => [("core-service" => "management"),("security-realm" => "jbossweb-migration-security-realm1"),("authentication" => "truststore")],"keystore-path" => expression "${jboss.server.config.dir}/ca-cert.jks","keystore-password" => undefined,"keystore-provider" => "JKS","operation-headers" => {"caller-type" => "user","access-mechanism" => "NATIVE"}},"result" => {"outcome" => "failed","failure-description" => "WFLYCTL0155: keystore-password may not be null","rolled-back" => true}}},"failure-description" => "WFLYWEB0005: Migration failed, see results for more details.","rolled-back" => true} {noformat} Marking as blocker as this operation fails for migrating of critical part of Web subsystem configuration as is HTTPS ssl configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4260) Schema validation errors against jboss-service_7_0.xsd

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-4260?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-4260: -------------------------------- Description: When you import a quickstart containing a jboss-service.xml file, you get the following XML: cvc-complex-type.2.3: Element 'attribute' cannot have character [children], because the type's content type is element-only. The quickstart source is located here: https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x/hello... I searched the https://github.com/jbossas/jboss-eap/ source code for other jboss-service.xml examples, and found a few with syntax similar to what the quickstarts use: * sar/src/test/resources/test/serviceXmlDeployment.jar/META-INF/jboss-service.xml * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/sar/injection/jboss-service.xml * testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/sar/jboss-service.xml * arquillian/container-managed/src/test/resources/sar-example.sar/META-INF/jboss-service.xml * arquillian/container-remote/src/test/resources/sar-example.sar/META-INF/jboss-service.xml There seems to be an error in the schema: http://www.jboss.org/schema/jbossas/jboss-service_7_0.xsd The quickstart bug is located here: https://bugzilla.redhat.com/show_bug.cgi?id=1178782 was: When you import a quickstart containing a jboss-service.xml file, you get the following XML: cvc-complex-type.2.3: Element 'attribute' cannot have character [children], because the type's content type is element-only. The quickstart source is located here: https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x-devel... I searched the https://github.com/jbossas/jboss-eap/ source code for other jboss-service.xml examples, and found a few with syntax similar to what the quickstarts use: * sar/src/test/resources/test/serviceXmlDeployment.jar/META-INF/jboss-service.xml * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/sar/injection/jboss-service.xml * testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/sar/jboss-service.xml * arquillian/container-managed/src/test/resources/sar-example.sar/META-INF/jboss-service.xml * arquillian/container-remote/src/test/resources/sar-example.sar/META-INF/jboss-service.xml There seems to be an error in the schema: http://www.jboss.org/schema/jbossas/jboss-service_7_0.xsd The quickstart bug is located here: https://bugzilla.redhat.com/show_bug.cgi?id=1178782 > Schema validation errors against jboss-service_7_0.xsd > ------------------------------------------------------- > > Key: WFLY-4260 > URL: https://issues.jboss.org/browse/WFLY-4260 > Project: WildFly > Issue Type: Bug > Reporter: Sande Gilda > Assignee: Tomas Hofman > > When you import a quickstart containing a jboss-service.xml file, you get the following XML: > cvc-complex-type.2.3: Element 'attribute' cannot have character [children], because the type's content type is element-only. > The quickstart source is located here: > https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x/hello... > I searched the https://github.com/jbossas/jboss-eap/ source code for other jboss-service.xml examples, and found a few with syntax similar to what the quickstarts use: > * sar/src/test/resources/test/serviceXmlDeployment.jar/META-INF/jboss-service.xml > * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/sar/injection/jboss-service.xml > * testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/sar/jboss-service.xml > * arquillian/container-managed/src/test/resources/sar-example.sar/META-INF/jboss-service.xml > * arquillian/container-remote/src/test/resources/sar-example.sar/META-INF/jboss-service.xml > There seems to be an error in the schema: > http://www.jboss.org/schema/jbossas/jboss-service_7_0.xsd > The quickstart bug is located here: https://bugzilla.redhat.com/show_bug.cgi?id=1178782 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-880) Return a success response but the rule seems to be not running.

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-880?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-880: ---------------------------------- Assignee: Edson Tirelli (was: Mario Fusco) > Return a success response but the rule seems to be not running. > --------------------------------------------------------------- > > Key: DROOLS-880 > URL: https://issues.jboss.org/browse/DROOLS-880 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.3.0.CR1 > Environment: CPU : Intel(R) Xeon(R) CPU E5-2650 > RAM : 128Gb > Linux Kernel : 2.6.32-431.el6.x86_64 > Drools : 6.3.0.CR1 > Rest Client : Soap UI > Reporter: 재우 이 > Assignee: Edson Tirelli > Attachments: 2015_08_20_11_27_43_987.mp4, window-1.1.4.jar > > > Kie_server returns a success rest response status code, but nothing show up in my log file. > It seems to be not running only in "6.3.0.CR1". (The rules work "6.2.0.Final") -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5219) Datasource transformer for EAP6.2

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-5219?page=com.atlassian.jira.plugin.... ] Hynek Švábek commented on WFLY-5219: ------------------------------------ Thanks for explanation. It is ok now. > Datasource transformer for EAP6.2 > ---------------------------------- > > Key: WFLY-5219 > URL: https://issues.jboss.org/browse/WFLY-5219 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 10.0.0.Beta2 > Reporter: Hynek Švábek > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 10.0.0.CR1 > > > Datasource transformer for EAP6.2 work with wrong model version. > EAP 6.2 doesn't contain datasource model version 1.2, right version is 1.1 (jboss-as-datasources_1_1.xsd) > https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... > I execute this command over CLI > DomainController - EAP7 DR8 > Slave - EAP 6.2 > {code} > data-source add --profile=full-ha --jndi-name=java:jboss/datasources/TestDS --name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1 > {code} > and get this output > {code} > Failed to execute line 'data-source add --profile=full-ha --jndi-name=java:jboss/datasources/TestDS --name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1': org.jboss.as.cli.CommandLineException: {"host-failure-descriptions" => {"slave" => "WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"profile\" => \"full-ha\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"java:jboss/datasources/TestDS\") > ], > \"operation\" => \"add\", > \"jndi-name\" => \"java:jboss/datasources/TestDS\", > \"driver-name\" => \"h2\", > \"connection-url\" => \"jdbc:h2:mem:test;DB_CLOSE_DELAY=-1\", > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"1dc420b4-d16f-4d0b-9cc5-3709939cff7d\", > \"execute-for-coordinator\" => true, > \"domain-controller-lock-id\" => 131382573 > } > } at resource [ > (\"profile\" => \"full-ha\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"java:jboss/datasources/TestDS\") > ] to subsystem 'datasources' model version '1.2.0' -- attributes [statistics-enabled] WFLYJCA0088: Attributes [statistics-enabled] rejected. Must be true"}} > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-845) @KSession throws exception when using kmodule in separate jar

by lucio piccoli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-845?page=com.atlassian.jira.plugin... ] lucio piccoli commented on DROOLS-845: -------------------------------------- hi mario i add a full test case that shows same issue in junit and war. > @KSession throws exception when using kmodule in separate jar > ------------------------------------------------------------- > > Key: DROOLS-845 > URL: https://issues.jboss.org/browse/DROOLS-845 > Project: Drools > Issue Type: Bug > Components: core engine, decision tables, kie server > Affects Versions: 6.2.0.Final > Environment: windows 7 > Reporter: lucio piccoli > Assignee: Mario Fusco > Attachments: drools-bug.zip > > > i am using drools with a kmodules.xml and decisiontable inside a separate jar file. when i attempt to bind the @KSession to the spring application context it throws an nullpointer exception deep inside the annotation. > org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'oft.onlineservice.business.FeeRulesEngineTest': Injection of kie dependencies failed; nested exception is java.lang.NullPointerException > at org.kie.spring.annotations.AnnotationsPostProcessor.postProcessPropertyValues(AnnotationsPostProcessor.java:109) > using a simple junittest shows the problem. > public class FeeRulesEngineTest { > @KSession( "ksession1") > private StatelessKieSession ksession; > @KBase("feeDecisionTable") > private KieBase kbase; > the kmodule.xml > <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule"> > <kbase name="feeDecisionTable" packages="oft.rulesengine" default="true"> > <ksession name="ksession1" type="stateless" default="true" > > </ksession> > </kbase> > </kmodule> > the spring config is using the annonation postprocessor. > <kie:import /> > <bean id="kiePostProcessor" > class="org.kie.spring.annotations.KModuleAnnotationPostProcessor"/> > > my curent work around to is to use @Autowire for the KSession and KBase. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-845) @KSession throws exception when using kmodule in separate jar

by lucio piccoli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-845?page=com.atlassian.jira.plugin... ] lucio piccoli updated DROOLS-845: --------------------------------- Attachment: drools-bug.zip > @KSession throws exception when using kmodule in separate jar > ------------------------------------------------------------- > > Key: DROOLS-845 > URL: https://issues.jboss.org/browse/DROOLS-845 > Project: Drools > Issue Type: Bug > Components: core engine, decision tables, kie server > Affects Versions: 6.2.0.Final > Environment: windows 7 > Reporter: lucio piccoli > Assignee: Mario Fusco > Attachments: drools-bug.zip > > > i am using drools with a kmodules.xml and decisiontable inside a separate jar file. when i attempt to bind the @KSession to the spring application context it throws an nullpointer exception deep inside the annotation. > org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'oft.onlineservice.business.FeeRulesEngineTest': Injection of kie dependencies failed; nested exception is java.lang.NullPointerException > at org.kie.spring.annotations.AnnotationsPostProcessor.postProcessPropertyValues(AnnotationsPostProcessor.java:109) > using a simple junittest shows the problem. > public class FeeRulesEngineTest { > @KSession( "ksession1") > private StatelessKieSession ksession; > @KBase("feeDecisionTable") > private KieBase kbase; > the kmodule.xml > <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule"> > <kbase name="feeDecisionTable" packages="oft.rulesengine" default="true"> > <ksession name="ksession1" type="stateless" default="true" > > </ksession> > </kbase> > </kmodule> > the spring config is using the annonation postprocessor. > <kie:import /> > <bean id="kiePostProcessor" > class="org.kie.spring.annotations.KModuleAnnotationPostProcessor"/> > > my curent work around to is to use @Autowire for the KSession and KBase. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5222) Unable to grant custom permission from a WildFly module

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-5222?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-5222: -------------------------------------- This appears to be user error: 1) You must specify the module to load the permission from in the minimum set 2) Your permission must have a constructor of the form (String, String) 3) When loading from a deployment using permissions.xml the deployment must have a module dependency on the module that contains the permission. With that said though Wildfly/Jboss modules should not be silently swallowing these exceptions, they should be logged at ERROR level. > Unable to grant custom permission from a WildFly module > ------------------------------------------------------- > > Key: WFLY-5222 > URL: https://issues.jboss.org/browse/WFLY-5222 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 10.0.0.Beta2 > Reporter: Josef Cacek > Assignee: Stefan Guilhen > Priority: Blocker > > When a custom permission is defined in a WildFly module (e.g. {{org.jboss.remoting3.security.RemotingPermission}}) then it's not possible to grant it to deployments. > Neither defining permissions in {{security-manager}} subsystem nor requesting them in {{META-INF/permissions.xml}} works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5222) Unable to grant custom permission from a WildFly module

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-5222?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-5222: -------------------------------------- Have you added a dependency on the module that contains the permission to the deployment? > Unable to grant custom permission from a WildFly module > ------------------------------------------------------- > > Key: WFLY-5222 > URL: https://issues.jboss.org/browse/WFLY-5222 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 10.0.0.Beta2 > Reporter: Josef Cacek > Assignee: Stefan Guilhen > Priority: Blocker > > When a custom permission is defined in a WildFly module (e.g. {{org.jboss.remoting3.security.RemotingPermission}}) then it's not possible to grant it to deployments. > Neither defining permissions in {{security-manager}} subsystem nor requesting them in {{META-INF/permissions.xml}} works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5221) TimerServiceTimerService.getTimers() returns not only the associated timer entries for the current Bean

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-5221?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-5221: ------------------------------------ Assignee: Stuart Douglas (was: Wolf-Dieter Fink) > TimerServiceTimerService.getTimers() returns not only the associated timer entries for the current Bean > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-5221 > URL: https://issues.jboss.org/browse/WFLY-5221 > Project: WildFly > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > Priority: Blocker > > According to the spec [1] the getTimers() method must only return timers associated to the current EJB. > This is a huge issue if timers are cancled by this collection as it will remove all timers! > [1] https://docs.oracle.com/javaee/6/api/javax/ejb/TimerService.html#getTimer... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2015