[JBoss JIRA] (WFLY-9379) TUNNEL#gossip_router_hosts does not support capabilities
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-9379:
------------------------------------
Summary: TUNNEL#gossip_router_hosts does not support capabilities
Key: WFLY-9379
URL: https://issues.jboss.org/browse/WFLY-9379
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 11.0.0.CR1
Reporter: Radoslav Husar
Assignee: Radoslav Husar
This requires a custom protocol override to support {{gossip_router_hosts}} as references to {{oubound-socket-binding}}s.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9379) TUNNEL#gossip_router_hosts does not support capabilities
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9379?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-9379:
---------------------------------
Description: This requires a custom protocol override to support {{gossip_router_hosts}} as references to {{outbound-socket-binding}}-s. (was: This requires a custom protocol override to support {{gossip_router_hosts}} as references to {{oubound-socket-binding}}s.)
> TUNNEL#gossip_router_hosts does not support capabilities
> --------------------------------------------------------
>
> Key: WFLY-9379
> URL: https://issues.jboss.org/browse/WFLY-9379
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> This requires a custom protocol override to support {{gossip_router_hosts}} as references to {{outbound-socket-binding}}-s.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-7567) Getting an unexpected token : UNION when running a query
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-7567?page=com.atlassian.jira.plugin.... ]
Scott Marlow closed WFLY-7567.
------------------------------
Resolution: Rejected
Please report this via [Hibernate ORM|http://hibernate.org] project, which is where you can find information about what has changed in different versions of Hibernate ORM, as well as ask questions + report bugs.
Sorry it took me so long to comment.
> Getting an unexpected token : UNION when running a query
> --------------------------------------------------------
>
> Key: WFLY-7567
> URL: https://issues.jboss.org/browse/WFLY-7567
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Environment: Wildfly 10.1.0 Final
> Cent OS 6
> JAVA 1.8.0_40
> Reporter: Prasanth Reddy
> Assignee: Scott Marlow
> Priority: Critical
>
> When running the below EJBQL wildfly 10.1.0 throws an exception. The same works fine in wildfly 9.2.0. I have manually edited the sql below to change the names of tables (so please ignore if there is an error in the sql). The data types of the columns selected are the same.
> SELECT a.pID FROM Arrangement a WHERE a.pID=30947 AND a.effectiveDate = '08/21/2001' UNION SELECT e.yID FROM Event e WHERE e.policyID=30947 AND e.proceedsDate = '08/20/2001'
> Caused by: org.hibernate.hql.internal.ast.QuerySyntaxException: unexpected token: UNION near line 1, column 86 [SELECT a.pID FROM Arrangement a WHERE a.pID=30947 AND a.effectiveDate = '08/21/2001' UNION SELECT e.yID FROM Event e WHERE e.policyID=30947 AND e.proceedsDate = '08/20/2001']
> at org.hibernate.hql.internal.ast.QuerySyntaxException.convert(QuerySyntaxException.java:74)
> at org.hibernate.hql.internal.ast.ErrorCounter.throwQueryException(ErrorCounter.java:91)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.parse(QueryTranslatorImpl.java:288)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:187)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:142)
> at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:115)
> at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:76)
> at org.hibernate.engine.query.spi.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:150)
> at org.hibernate.internal.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:302)
> at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:240)
> at org.hibernate.internal.SessionImpl.createQuery(SessionImpl.java:1894)
> at org.hibernate.jpa.spi.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:291)
> ... 89 more
> Thanks,
> Prasanth
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9378) Attribute TransportResourceDefinition.Attribute#SOCKET_BINDING should be required and with DIAGNOSTICS_SOCKET_BINDING should not allow expressions
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9378?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-9378:
---------------------------------
Summary: Attribute TransportResourceDefinition.Attribute#SOCKET_BINDING should be required and with DIAGNOSTICS_SOCKET_BINDING should not allow expressions (was: Attribute TransportResourceDefinition.Attribute#SOCKET_BINDING should be required)
> Attribute TransportResourceDefinition.Attribute#SOCKET_BINDING should be required and with DIAGNOSTICS_SOCKET_BINDING should not allow expressions
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9378
> URL: https://issues.jboss.org/browse/WFLY-9378
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
>
> {noformat}
> 18:26:26,514 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "jgroups"),
> ("channel" => "ee")
> ]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "org.wildfly.clustering.group.ee",
> "org.wildfly.clustering.jgroups.channel.ee"
> ],
> "Services that may be the cause:" => ["org.wildfly.network.socket-binding.undefined"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9132) Applications won't deploy if their persistence.xml have multiple persistence units
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-9132?page=com.atlassian.jira.plugin.... ]
Scott Marlow closed WFLY-9132.
------------------------------
Resolution: Rejected
This isn't really a bug, the problem is that we are now expect the application to choose the default persistence unit via the "wildfly.jpa.default-unit" persistence unit hint.
> Applications won't deploy if their persistence.xml have multiple persistence units
> ----------------------------------------------------------------------------------
>
> Key: WFLY-9132
> URL: https://issues.jboss.org/browse/WFLY-9132
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Environment: Windows 10 64 bit
> Wildfly 10.1.0
> Reporter: Bobby Bassman
> Assignee: Scott Marlow
>
> Applications won't deploy if their persistence.xml have multiple persistence units. This was not a problem with EAP. Now, Wildfly requires that each @PersistenceContext have a 'unitName' parameter. WIth EAP 6.4, if a @PersistenceContext did not have a 'unitName' parameter, then the default PU was used. By requiring that @PersistenceUnit have 'unitName', developers are forced to unnecessarily bind Java code to configuration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-6137) org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
by Andreas Engvall (JIRA)
[ https://issues.jboss.org/browse/WFLY-6137?page=com.atlassian.jira.plugin.... ]
Andreas Engvall commented on WFLY-6137:
---------------------------------------
I would argue that since dom4j-1.6.1.jar contains no java. or javax. packages it should not have the provided scope, cause any conflicts or ClassCastExceptions. We have the same problem with wildfly-10.x but not with wildfly-9.x or jboss-eap-7 (only the dom4j problem, we are not including hibernate in our app) and it's annoying that we have to treat the different wildfly versions differently.
> org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> ---------------------------------------------------------------------
>
> Key: WFLY-6137
> URL: https://issues.jboss.org/browse/WFLY-6137
> Project: WildFly
> Issue Type: Bug
> Components: Application Client, EE, JPA / Hibernate, Server
> Affects Versions: 10.0.0.Final
> Reporter: Karl Nicholas
> Assignee: Stuart Douglas
>
> Including hibernate-entitymanager (up to version 5.0.7.Final) into a project causes dom4j-1.6.1.jar to be included which causes the application to fail to deploy in Wildfly 10.0.0.Final.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9370) Fix failing SingletonTunnelTestCase(ASYNC-tunnel)#testSingletonService
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9370?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9370:
--------------------------------------
Moreover, opened WFLY-9378 to deal with the fact that not specifying socket-biding on the transport fails.
> Fix failing SingletonTunnelTestCase(ASYNC-tunnel)#testSingletonService
> -----------------------------------------------------------------------
>
> Key: WFLY-9370
> URL: https://issues.jboss.org/browse/WFLY-9370
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> The problem is that this test is not run as part of regular CI execution thus is destined to be broken. The test should be moved to the right location and renamed (i.e. drop tunnel since that has nothing to do with what it is testing).
> {noformat}
> &#27;[0m&#27;[31m04:44:19,235 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "singleton.war")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.clustering.group.default"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.test1.service.default is missing [jboss.clustering.group.default]",
> "jboss.test2.service.default is missing [jboss.clustering.group.default]"
> ],
> "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "jboss.deployment.discovery.\"singleton.war\"",
> "jboss.deployment.unit.\"singleton.war\".CdiValidatorFactoryService",
> "jboss.deployment.unit.\"singleton.war\".WeldStartService",
> "jboss.deployment.unit.\"singleton.war\".component.TopologyChangeListenerBean.JndiBindingsService",
> "jboss.deployment.unit.\"singleton.war\".component.TopologyChangeListenerBean.START",
> "jboss.deployment.unit.\"singleton.war\".component.TopologyChangeListenerBean.VIEW.\"org.jboss.as.test.clustering.TopologyChangeListener\".REMOTE",
> "jboss.deployment.unit.\"singleton.war\".component.TopologyChangeListenerBean.WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.TopologyChangeListenerBean.WeldInterceptorBindingsService",
> "jboss.deployment.unit.\"singleton.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"com.sun.faces.config.ConfigureListener\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.faces.webapp.FacetTag\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.faces.webapp.FacetTag\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.TopologyChangeListenerServlet\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.TopologyChangeListenerServlet\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.cluster.singleton.service.NodeServiceServlet\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.cluster.singleton.service.NodeServiceServlet\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.cluster.singleton.service.ValueServiceServlet\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.cluster.singleton.service.ValueServiceServlet\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.weld.servlet.WeldInitialListener\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.weld.servlet.WeldInitialListener\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.weld.servlet.WeldTerminalListener\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.weld.servlet.WeldTerminalListener\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".deploymentCompleteService",
> "jboss.deployment.unit.\"singleton.war\".ejb3.client-context.registration-service",
> "jboss.deployment.unit.\"singleton.war\".jndiDependencyService",
> "jboss.deployment.unit.\"singleton.war\".moduleDeploymentRuntimeInformation",
> "jboss.deployment.unit.\"singleton.war\".moduleDeploymentRuntimeInformationStart",
> "jboss.naming.context.java.app.singleton.singleton.TopologyChangeListenerBean",
> "jboss.naming.context.java.app.singleton.singleton.\"TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener\"",
> "jboss.naming.context.java.global.singleton.TopologyChangeListenerBean",
> "jboss.naming.context.java.global.singleton.\"TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener\"",
> "jboss.naming.context.java.module.singleton.singleton.TopologyChangeListenerBean",
> "jboss.naming.context.java.module.singleton.singleton.\"TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener\"",
> "jboss.undertow.deployment.default-server.default-host./singleton",
> "jboss.undertow.deployment.default-server.default-host./singleton.UndertowDeploymentInfoService"
> ],
> "Services that may be the cause:" => [
> "jboss.clustering.group.default",
> "org.wildfly.network.socket-binding.undefined"
> ]
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9378) Attribute TransportResourceDefinition.Attribute#SOCKET_BINDING should be required
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9378?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-9378:
---------------------------------
Steps to Reproduce:
{noformat}
[standalone@localhost:9990 /] /subsystem=jgroups/stack=udp/transport=UDP:undefine-attribute(name=socket-binding
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9990 /] :reload
{
"outcome" => "success",
"result" => undefined
}
{noformat}
> Attribute TransportResourceDefinition.Attribute#SOCKET_BINDING should be required
> ---------------------------------------------------------------------------------
>
> Key: WFLY-9378
> URL: https://issues.jboss.org/browse/WFLY-9378
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
>
> {noformat}
> 18:26:26,514 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "jgroups"),
> ("channel" => "ee")
> ]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "org.wildfly.clustering.group.ee",
> "org.wildfly.clustering.jgroups.channel.ee"
> ],
> "Services that may be the cause:" => ["org.wildfly.network.socket-binding.undefined"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9378) Attribute TransportResourceDefinition.Attribute#SOCKET_BINDING should be required
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9378?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-9378:
---------------------------------
Description:
{noformat}
18:26:26,514 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "jgroups"),
("channel" => "ee")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"org.wildfly.clustering.group.ee",
"org.wildfly.clustering.jgroups.channel.ee"
],
"Services that may be the cause:" => ["org.wildfly.network.socket-binding.undefined"]
}}
{noformat}
> Attribute TransportResourceDefinition.Attribute#SOCKET_BINDING should be required
> ---------------------------------------------------------------------------------
>
> Key: WFLY-9378
> URL: https://issues.jboss.org/browse/WFLY-9378
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
>
> {noformat}
> 18:26:26,514 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "jgroups"),
> ("channel" => "ee")
> ]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "org.wildfly.clustering.group.ee",
> "org.wildfly.clustering.jgroups.channel.ee"
> ],
> "Services that may be the cause:" => ["org.wildfly.network.socket-binding.undefined"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months