[wildfly-dev] ejb-client invocation broken (upstream yesterday/today)

[Wolf-Dieter Fink]

The reason of the question is that from my tests with AS7 I need to open 
the firewall as there is no possibility to invoke ejb's remote across 
different machines
I did not investigate further what is the exact reason behind (I think 
remoting will open it but not sure) but if I only open the 'visible' 
ports shown in the configuration the ejb-invocation failed.
After allow the communication for all ports it worked.

Wolf

On 07/17/2013 01:23 PM, Jaikiran Pai wrote:
> Hi Wolf,
>
> Sorry, I am not getting the context of that question. Which additional 
> temporary ports were being used?
>
> -Jaikiran
> On Wednesday 17 July 2013 04:51 PM, Wolf-Dieter Fink wrote:
>> Yes Jaikiran,
>> I understood that but does that mean also that there are no 
>> additional temporary ports used (for ejb invocation) as this was in 
>> former versions?
>>
>> - Wolf
>>
>> On 07/17/2013 12:58 PM, Jaikiran Pai wrote:
>>> This isn't just a ejb-client specific thing. One of the goals of 
>>> WildFly 8 has been to allow communication over a single port (http). 
>>> So ports like 4447 are no longer opened by default. This affects all 
>>> applications communicating with WildFly and isn't specific to 
>>> ejb-client. For example, even remote naming need to use the new port.
>>>
>>> -Jaikiran
>>> On Wednesday 17 July 2013 04:18 PM, Wolf-Dieter Fink wrote:
>>>> works so far,
>>>>
>>>> but yet another change to the ejb-client.
>>>>
>>>> Does this mean the whole communication will use the 8080 port and 
>>>> there is no other temporary port opened (for firewall configuration)?
>>>>
>>>> - Wolf
>>>>
>>>>
>>>> On 07/17/2013 12:12 PM, Jaikiran Pai wrote:
>>>>> WildFly upstream no longer uses 4447 port for remote 
>>>>> communication. Undertow now supports http-upgrade which means that 
>>>>> the communication happens on the http port which by default is 8080.
>>>>>
>>>>> -Jaikiran
>>>>> On Wednesday 17 July 2013 03:31 PM, Wolf-Dieter Fink wrote:
>>>>>> I try to run my quickstart (ejb-multi-server) with WildFly.
>>>>>> Configuration and deployment work.
>>>>>>
>>>>>> But the (remote) EJB invocation failed. Neither standalone nor 
>>>>>> client inside the server works.
>>>>>> If I use an older WildFly pulled at the 07/11 (don't know the 
>>>>>> exact commit) everything works fine.
>>>>>>
>>>>>> I retest with the ejb-remote QS, here the same issue.
>>>>>>
>>>>>> To avoid any maven issue I've used plain java command and include 
>>>>>> the correct jboss-client.jar
>>>>>>
>>>>>> I've attached the logfiles from a working and non-working attempt.
>>>>>> The only difference I see is that the ejb-client library is new 
>>>>>> (moved from 1.x => 2.x.Beta), remoting is unkown and XNIO 3.1.0.CR3.
>>>>>>
>>>>>> - Wolf
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> wildfly-dev mailing list
>>>>>> wildfly-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>
>>>>
>>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20130717/af05c014/attachment.html