[JBoss JIRA] (DROOLS-702) Rule Inheritance fired the sub rule even the condition doen't match
by Yacine Jaber (JIRA)
[ https://issues.jboss.org/browse/DROOLS-702?page=com.atlassian.jira.plugin... ]
Yacine Jaber closed DROOLS-702.
-------------------------------
> Rule Inheritance fired the sub rule even the condition doen't match
> -------------------------------------------------------------------
>
> Key: DROOLS-702
> URL: https://issues.jboss.org/browse/DROOLS-702
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.Final
> Environment: Windows, Java6.0.29
> Reporter: Yacine Jaber
> Assignee: Davide Sottara
> Priority: Critical
> Attachments: wod-drools-test.7z
>
>
> You can find the attached a simple maven project that shows this error.
> You can run ExampleDrools class as main java application.
> The sub rules are fired even if the condition is not matched.
> There are a work arround by using <from $fact> into a sub rule to avoid firing this one.
> This simple project shows the failed and work arround test.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFLY-4305) Script rumbles on after error
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/WFLY-4305?page=com.atlassian.jira.plugin.... ]
Carlo de Wolf updated WFLY-4305:
--------------------------------
Issue Type: Bug (was: Feature Request)
> Script rumbles on after error
> -----------------------------
>
> Key: WFLY-4305
> URL: https://issues.jboss.org/browse/WFLY-4305
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Carlo de Wolf
> Assignee: Carlo de Wolf
>
> After a failure in the script it rumbles on.
> {noformat}
> (master) carlo@devel01:~/work/wildfly$ ./build.sh clean
> ./tools/download-maven.sh: 20: ./tools/download-maven.sh: curl: not found
> Archive: maven.zip
> End-of-central-directory signature not found. Either this file is not
> a zipfile, or it constitutes one disk of a multi-part archive. In the
> latter case the central directory and zipfile comment will be found on
> the last disk(s) of this archive.
> unzip: cannot find zipfile directory in one of maven.zip or
> maven.zip.zip, and cannot find maven.zip.ZIP, period.
> mv: cannot stat ‘apache-maven*’: No such file or directory
> build.sh: Could not locate Maven; check $MVN or $MAVEN_HOME.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFLY-4305) Script rumbles on after error
by Carlo de Wolf (JIRA)
Carlo de Wolf created WFLY-4305:
-----------------------------------
Summary: Script rumbles on after error
Key: WFLY-4305
URL: https://issues.jboss.org/browse/WFLY-4305
Project: WildFly
Issue Type: Feature Request
Components: Build System
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
After a failure in the script it rumbles on.
{noformat}
(master) carlo@devel01:~/work/wildfly$ ./build.sh clean
./tools/download-maven.sh: 20: ./tools/download-maven.sh: curl: not found
Archive: maven.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of maven.zip or
maven.zip.zip, and cannot find maven.zip.ZIP, period.
mv: cannot stat ‘apache-maven*’: No such file or directory
build.sh: Could not locate Maven; check $MVN or $MAVEN_HOME.
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFLY-2422) Simplify the remote-outbound connections
by Wolf-Dieter Fink (JIRA)
[ https://issues.jboss.org/browse/WFLY-2422?page=com.atlassian.jira.plugin.... ]
Wolf-Dieter Fink commented on WFLY-2422:
----------------------------------------
>From my point of view there are further issues to consider.
It is not common to have a bunch of remote-outbound-connection with different user and property setting, this will make the configuration complicated and will not work if clustering is used.
The current configuration does not take this into account each r-o-c need to have the parameters AND if the cluster will be implemented in the same way the properties need to be repeated here as well.
This seems unnecessary and the profile should have user and properties to override the r-o-c and a simple flag cluster=true/false to configure the cluster.
Another issue is that it is only one <profile> allowed in the jboss-ejb-client.xml.
A reason to have more profiles is that huge environments have different applications and one application might need more than one foreign ejb application, other might use a different combination. This approach is application oriented and each app need to have a unique profile to be flexible.
Let say app-main use appOne and appTwo; app-web use appOne and app-web2 use appTwo.
In this case each application need it's own profile and the configuration of remote-profile is repeated.
>From my point of view there are two possible approaches:
application oriented:
one profile in jboss-ejb-client.xml
the profile element allow to reference other profiles
target oriented:
jboss-ejb-client.xml allow multiple profile
A profile is target oriented and contains 'only' a bunch of outbound definitions which point to servers which have the same app-deployment or are within the same cluster
> Simplify the remote-outbound connections
> ----------------------------------------
>
> Key: WFLY-2422
> URL: https://issues.jboss.org/browse/WFLY-2422
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB, Remoting
> Affects Versions: 8.0.0.Beta1
> Reporter: Wolf-Dieter Fink
> Assignee: Tomasz Adamski
> Fix For: 9.0.0.Beta1
>
>
> At the moment the application need to reference each outbound connection with a remote-ejb-receiver element in the jboss-ejb-client.xml.
> But from an application perspective it is not relevant whether the server environment provide one or many receivers or whether the ejb-receiver is a cluster.
> It should be possible to add many outbound-socket-binding-ref elements and related properties to the remote-outbound-connection element of the server configuration.
> In this case it is possible to keep the application deployment independent from the server environment.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFLY-2422) Simplify the remote-outbound connections
by Wolf-Dieter Fink (JIRA)
[ https://issues.jboss.org/browse/WFLY-2422?page=com.atlassian.jira.plugin.... ]
Wolf-Dieter Fink reopened WFLY-2422:
------------------------------------
At the moment the remoting-profil only work if the target is not a cluster.
If the client-context (jboss-ejb-client.xml) switch from the former configuration to <profile> it will not possible to add clusters element (TBH this is not wanted)
But the server side configuration does not allow to add a cluster configuration.
As a result the RemotingConnectionClusterNodeManager will not be able to install the cluster view.
An example can be found here
https://github.com/wfink/quickstart/compare/ejb-multi-server-remote-profiles
> Simplify the remote-outbound connections
> ----------------------------------------
>
> Key: WFLY-2422
> URL: https://issues.jboss.org/browse/WFLY-2422
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB, Remoting
> Affects Versions: 8.0.0.Beta1
> Reporter: Wolf-Dieter Fink
> Assignee: Tomasz Adamski
> Fix For: 9.0.0.Beta1
>
>
> At the moment the application need to reference each outbound connection with a remote-ejb-receiver element in the jboss-ejb-client.xml.
> But from an application perspective it is not relevant whether the server environment provide one or many receivers or whether the ejb-receiver is a cluster.
> It should be possible to add many outbound-socket-binding-ref elements and related properties to the remote-outbound-connection element of the server configuration.
> In this case it is possible to keep the application deployment independent from the server environment.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFLY-4295) warn about _ds.xml deplyments are deprecated
by Frank Langelage (JIRA)
[ https://issues.jboss.org/browse/WFLY-4295?page=com.atlassian.jira.plugin.... ]
Frank Langelage commented on WFLY-4295:
---------------------------------------
I only have 2 -ds.xml files
/mbi/tools/jboss/9.0/standalone/deployments/DefaultDS-ds.xml
/mbi/tools/jboss/9.0/standalone/deployments/maj2e-langfr-dev-ora-ds.xml
for defining 2 datasources in total
but get 33 times the warning message now like
03.02. 01:21:59,611 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
It seams this message is created for every deployment and subdeployment, not only for deployment of -ds.xml file.
egrep "(WFLYJCA0091|WFLYSRV0027|WFLYSRV0207)" server.log
03.02. 01:21:54,521 INFO [org.jboss.as.server.deployment#start] WFLYSRV0027: Starting deployment of "ifxjdbc_all.jar" (runtime-name: "ifxjdbc_all.jar")
03.02. 01:21:54,530 INFO [org.jboss.as.server.deployment#start] WFLYSRV0027: Starting deployment of "sqljdbc41.jar" (runtime-name: "sqljdbc41.jar")
03.02. 01:21:54,935 INFO [org.jboss.as.server.deployment#start] WFLYSRV0027: Starting deployment of "camunda-webapp-jboss-7.3.0-SNAPSHOT.war" (runtime-name: "camunda-webapp-jboss-7.3.0-SNAPSHOT.war")
03.02. 01:21:54,940 INFO [org.jboss.as.server.deployment#start] WFLYSRV0027: Starting deployment of "ojdbc7.jar" (runtime-name: "ojdbc7.jar")
03.02. 01:21:54,944 INFO [org.jboss.as.server.deployment#start] WFLYSRV0027: Starting deployment of "DefaultDS-ds.xml" (runtime-name: "DefaultDS-ds.xml")
03.02. 01:21:59,611 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:21:59,611 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:21:59,818 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:22:04,405 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:22:06,043 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:22:48,579 INFO [org.jboss.as.server.deployment#start] WFLYSRV0027: Starting deployment of "XADisk.rar" (runtime-name: "XADisk.rar")
03.02. 01:22:48,959 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:22:55,116 INFO [org.jboss.as.server.deployment#start] WFLYSRV0027: Starting deployment of "controller.rar" (runtime-name: "controller.rar")
03.02. 01:22:55,174 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:52:31,885 INFO [org.jboss.as.server.deployment#start] WFLYSRV0027: Starting deployment of "maj2e-langfr-dev-ora-ds.xml" (runtime-name: "maj2e-langfr-dev-ora-ds.xml")
03.02. 01:52:31,894 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:04,155 INFO [org.jboss.as.server.deployment#start] WFLYSRV0027: Starting deployment of "maj2e-langfr-dev.ear" (runtime-name: "maj2e-langfr-dev.ear")
03.02. 01:53:15,647 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-camunda.jar")
03.02. 01:53:15,659 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-production.jar")
03.02. 01:53:15,664 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-distribution.jar")
03.02. 01:53:15,664 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ws-purchase.war")
03.02. 01:53:15,665 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-common.jar")
03.02. 01:53:15,666 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ws-production.war")
03.02. 01:53:15,667 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-costing.jar")
03.02. 01:53:15,668 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-inventory.jar")
03.02. 01:53:15,669 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-core.jar")
03.02. 01:53:15,731 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ws-common.war")
03.02. 01:53:15,775 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-sales.jar")
03.02. 01:53:15,816 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ws-external.war")
03.02. 01:53:15,818 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ws-planning.war")
03.02. 01:53:15,820 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ws-sales.war")
03.02. 01:53:15,821 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "web.war")
03.02. 01:53:15,823 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-purchase.jar")
03.02. 01:53:15,824 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ws-inventory.war")
03.02. 01:53:15,826 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-entity.jar")
03.02. 01:53:15,828 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-planning.jar")
03.02. 01:53:15,829 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ws-core.war")
03.02. 01:53:15,831 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ws-costing.war")
03.02. 01:53:15,832 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ws-distribution.war")
03.02. 01:53:15,834 INFO [org.jboss.as.server.deployment#start] WFLYSRV0207: Starting subdeployment (runtime-name: "ejb-session-param.jar")
03.02. 01:53:16,002 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,081 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,101 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,119 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,145 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,155 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,225 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,235 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,285 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,299 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,305 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,308 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,315 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,317 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,336 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,350 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,408 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,450 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,454 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,498 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,538 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,554 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,564 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:53:16,572 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
03.02. 01:55:03,552 INFO [org.jboss.as.server.deployment#start] WFLYSRV0027: Starting deployment of "web-maj2e-langfr-dev.war" (runtime-name: "web-maj2e-langfr-dev.war")
03.02. 01:55:09,094 WARN [org.jboss.as.connector#deploy] WFLYJCA0091: -ds.xml file deployment is deprecated. Support will be removed in next versions
> warn about _ds.xml deplyments are deprecated
> --------------------------------------------
>
> Key: WFLY-4295
> URL: https://issues.jboss.org/browse/WFLY-4295
> Project: WildFly
> Issue Type: Feature Request
> Components: JCA
> Reporter: Stefano Maestri
> Assignee: Stefano Maestri
>
> _ds.xml deployement will no more supported in next vesions of WF. log a warning during deployment to warn users about that.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFLY-4188) Client Mapping expressions are allowed but are not resolved if used
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-4188?page=com.atlassian.jira.plugin.... ]
Chao Wang updated WFLY-4188:
----------------------------
Affects Version/s: 9.0.0.Alpha1
> Client Mapping expressions are allowed but are not resolved if used
> -------------------------------------------------------------------
>
> Key: WFLY-4188
> URL: https://issues.jboss.org/browse/WFLY-4188
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, ConfigAdmin
> Affects Versions: 8.2.0.Final, 9.0.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Assignee: Paul Ferraro
>
> If socket binding with client-mapping is used to provide a valid client address for EJB invocation to the client the expressions are not resolved.
> Depend on the attribute the parsing failed direct during startup (port# is not numeric) or the expression is send to the client where the Exception is thrown at runtime.
> Notice for EJB invocation the problem is only visible if the application is clustered, otherwise the cluster view (where the client-mapping take effect) is not send to the client.
> Dec 17, 2014 2:53:43 PM org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager getEJBReceiver
> INFO: Could not create a connection for cluster node ClusterNode{clusterName='ejb', nodeName='redhat', clientMappings=[ClientMapping{sourceNetworkAddress=/0:0:0:0:0:0:0:0, sourceNetworkMaskBits=0, destinationAddress='${jboss.node.name}', destinationPort=8080}], resolvedDestination=[Destination address=${jboss.node.name}, destination port=8080]} in cluster ejb
> java.lang.RuntimeException: java.io.IOException: java.net.URISyntaxException: Illegal character in authority at index 7: http://@${jboss.node.name}:8080/?#
> at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:92)
> at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:77)
> at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)
> at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:79)
> at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:405)
> at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:379)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.io.IOException: java.net.URISyntaxException: Illegal character in authority at index 7: http://@${jboss.node.name}:8080/?#
> at org.jboss.remoting3.remote.HttpUpgradeConnectionProvider.createConnection(HttpUpgradeConnectionProvider.java:102)
> at org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:215)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:298)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:388)
> at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:153)
> at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:133)
> at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:75)
> at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)
> at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:79)
> at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:405)
> at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:379)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:388)
> at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:153)
> at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:133)
> at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:75)
> ... 8 more
> Caused by: java.net.URISyntaxException: Illegal character in authority at index 7: http://@${jboss.node.name}:8080/?#
> at java.net.URI$Parser.fail(URI.java:2829)
> at java.net.URI$Parser.parseAuthority(URI.java:3167)
> at java.net.URI$Parser.parseHierarchical(URI.java:3078)
> at java.net.URI$Parser.parse(URI.java:3034)
> at java.net.URI.<init>(URI.java:680)
> at org.jboss.remoting3.remote.HttpUpgradeConnectionProvider.createConnection(HttpUpgradeConnectionProvider.java:100)
> at org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:215)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:298)
> ... 12 more
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months