[JBoss JIRA] (WFLY-5244) bean-validation quickstart fails to validate due to non-compliant arquillian.xml
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5244?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5244.
----------------------------
> bean-validation quickstart fails to validate due to non-compliant arquillian.xml
> --------------------------------------------------------------------------------
>
> Key: WFLY-5244
> URL: https://issues.jboss.org/browse/WFLY-5244
> Project: WildFly
> Issue Type: Bug
> Reporter: Rob Stryker
> Assignee: Jason Greene
> Fix For: 10.0.0.CR1
>
>
> bean-validation quickstart fails to validate in arquillian.xml.
> The arquillian_1_0.xsd file includes the following:
> {code}
> <element name="container">
> <complexType>
> <choice minOccurs="1" maxOccurs="unbounded">
> <element ref="tns:configuration" minOccurs="0" maxOccurs="1" />
> <!--
> <element ref="tns:dependencies" minOccurs="0" maxOccurs="1" />
> -->
> <element ref="tns:protocol" minOccurs="0" maxOccurs="unbounded" />
> </choice>
> <attribute name="qualifier" type="string" use="required" />
> <attribute name="default" type="boolean" use="optional" default="false" />
> <attribute name="mode" use="optional" default="suite">
> <simpleType>
> <restriction base="string">
> <enumeration value="suite" />
> <enumeration value="class" />
> <enumeration value="manual" />
> <enumeration value="custom" />
> </restriction>
> </simpleType>
> </attribute>
> </complexType>
> <unique name="unique-protocol-within-container">
> <annotation>
> <documentation>
> @type must be unique between all
> protocols in a container.
> </documentation>
> </annotation>
> <selector xpath="tns:protocol" />
> <field xpath="@type" />
> </unique>
> </element>
> {code}
> The arquillian.xml included in the example includes the following:
> {code}
> <container qualifier="jboss" default="true">
> <!-- By default, arquillian will use the JBOSS_HOME environment variable. Alternatively, the configuration below can be uncommented. -->
> <!--<configuration> -->
> <property name="jbossHome">C:/tools/wildfly-9.0.0.Final</property>
> <!--</configuration> -->
> </container>
> {code}
> Validation error is that "property" is not a valid sub-element, which is true based on the xsd file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-5337) NPE when restarting Infinispan transport
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5337?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5337.
----------------------------
> NPE when restarting Infinispan transport
> ----------------------------------------
>
> Key: WFLY-5337
> URL: https://issues.jboss.org/browse/WFLY-5337
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Beta2
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 10.0.0.CR1
>
>
> This is actually due to a bug in Infinispan. Infinispan's JGroupsTransport inappropriately sets its channel to null during stop(), even if a channel was provided to the constructor.
> {noformat}
> 10:10:34,923 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 71) MSC000001: Failed to start service jboss.infinispan.server.default: org.jboss.msc.service.StartException in service jboss.infinispan.server.default: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.remoting.transport.jgroups.JGroupsTransport.start() on object of type ChannelTransport
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:107)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.remoting.transport.jgroups.JGroupsTransport.start() on object of type ChannelTransport
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:248)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:618)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:580)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:445)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:464)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:455)
> at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:120)
> at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:111)
> at org.wildfly.clustering.infinispan.spi.service.CacheBuilder.start(CacheBuilder.java:80)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:102)
> ... 4 more
> Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.remoting.transport.jgroups.JGroupsTransport.start() on object of type ChannelTransport
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:226)
> ... 13 more
> Caused by: java.lang.NullPointerException
> at org.jboss.as.clustering.infinispan.ChannelTransport.initChannel(ChannelTransport.java:84)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannelAndRPCDispatcher(JGroupsTransport.java:350)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:188)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
> ... 18 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-5231) [Migration operation] [Web to Undertow] Web - access-log and its directory attributes are not migrated
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5231?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5231.
----------------------------
> [Migration operation] [Web to Undertow] Web - access-log and its directory attributes are not migrated
> ------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5231
> URL: https://issues.jboss.org/browse/WFLY-5231
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Beta2
> Reporter: Radim Hatlapatka
> Assignee: Stuart Douglas
> Priority: Critical
> Fix For: 10.0.0.CR1
>
>
> When migrating access-log via {{:migrate}} and access-log contains directory definition, the properties {{relative-to}} and {{path}} are not migrated.
> Web subsystem snippet:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:web:2.2" default-virtual-server="default" native="false">
> <virtual-server name="default" enable-welcome-root="true">
> <alias name="localhost"/>
> <alias name="example.com"/>
> <access-log resolve-hosts="true" prefix="test" rotate="false">
> <directory relative-to="jboss.server.log.dir" path="testvs/vs"/>
> </access-log>
> </virtual-server>
> </subsystem>
> {code}
> access log part expected to be migrated as
> {code:xml}
> <access-log rotate="false" prefix="test" directory="testvs/vs" relative-to="jboss.server.log.dir" />
> {code}
> instead it is migrated without the {{directory}} and {{relative-to}} attributes:
> <access-log rotate="false" prefix="test"/>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month