Jonathan Lalou's Blog

Archive for the ‘en-US’ Category

I wrote the following notice on Karim CHORFI‘s profile on LinkedIn:

Working with Karim is a pleasure: always available, smiling, with a sense of humor. This is for the human profile ; concerning his professionnal abilities, let’s mention his double skills -finance and IT- make him able to handle various problems, as complex technically as functionnaly.

I recommand Karim warmly.

I wrote the following notice on David CHAU‘s profile on LinkedIn:

David gathers two main qualities: first, he is an actual developer, I mean: a guy with a passion for technologies, Java, frameworks, able to deal of Android on his iPhone, to argue pros and cons on the JARs his depends on, or advise on complex technical points. Besides, he is a nice, sociable, and open-minded boy, working with whom is a pleasure.

Case and Topology

RMI services are deployed on UAT, exposed via a F5, at the following address: t3://my-f5-frontal.my.domain.extension:7090
The actual servers are my-first-node.my.domain.extension and my-second-node.my.domain.extension.

The client application is deployed in a remote location, on a QA server.
The ports are open between QA and UAT, and we can ping and use telnet with no issue on QA.

Anyway, when I launch the client application from QA, I get the following error:

[java]2011-10-31 06:41:03,277 INFO support.DefaultListableBeanFactory – Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@79e304: defining beans [jonathanServiceClient]; root of factory hierarchy
Exception in thread "main" org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘smartServiceClient’ defined in class path resource [com/lalou/jonathan/rmi-client-spring.xml]: Invocation of init method failed; nested exception is org.springframework.remoting.RemoteLookupFailureException: JNDI lookup for RMI service [rmiServices] failed; nested exception is javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://my-f5-frontal.my.domain.extension:7090: Bootstrap to my-f5-frontal.my.domain.extension/111.222.012.123:7090 failed. It is likely that the remote side declared peer gone on this JVM][/java]

Explanation and Fix

Owing to my understanding, here is the point: when the client tries to connect to F5, it presents itself with its name, and the F5 returns the name of the actual server. If both client and server are not on the same domain (“domain” as network domain, no link with Weblogic domain), then the DNS resolution may fail.

To fix this issue, you have to follow one or both of the following points: everything depends on your local topology.

WebLogic: “Listen Address”

Modify the “Listen Address” in WebLogic administration console, from home:  Servers > MyFirstNode/MySecondNode > Configuration > General > Listen Address > update it

By “update” the “Listen Address”, I mean providing the complete name of the machines, including the domain extension.
eg: my-first-node.my.domain.extension and my-second-node.my.domain.extension, rather than my-first-node and my-second-node (or, even worse, localhost).
You can also provide an IP, cf. WebLogic documentation on Oracle’s website.

Of course, you can decide to set it directly in WebLogic’s config.xml.

Caution! This option may also be set via the command line running WebLogic, using the flag -Dweblogic.ListenAddress=... Therefore, take care to be consistent between the content of console/config.xml and the command line option.

Hosts

On client side, check the content of hosts file. Usually, you can found it at /etc/hosts (or C:\WINDOWS\system32\drivers\etc\hosts on Windows XP).
Assuming your machine is myClientMachine with an IP 123.123.123.123 and a domain extension remote.domain, then your hosts file should look like:

[java]127.0.0.1 localhost
123.123.123.123 myClientMachine[/java]

Update it to:

[java]127.0.0.1 localhost
123.123.123.123 myClientMachine myClientMachine.remote.domain[/java]

Lamine SIDIBE honored me in writing the following notice on my profile on LinkedIn:

“I was working at BNP Paribas when Jonatthan joined the Prime Brokerage team. His skills allowed him to work in a very demanding environment. It was very pleasant to work with him for his human and profesional qualities. Jonathan is able to find efficient technical solutions for complex functional business requirements.” October 25, 2011

1st Lamine SIDIBE, J2EE Consultant, BNP PARIBAS
worked directly with Jonathan at BNPParibas

Jacky LALOU honored me in writing the following notice on my profile on LinkedIn:

“Jonathan is a detail-oriented manager who watches the balance sheet like a hawk without ever losing sight of the strategic objective.” October 5, 2011

1st Jacky Lalou, Actuarial analyst, BNP Paribas Assurance
was with another company when working with Jonathan at BNPParibas

Kim Quoc TRAN honored me in writing the following recommendation on my profile on LinkedIn:

“I had worked with Jonathan for more than 2 years at Bnp Paribas. He has a very good technical knowledge (Java/J2EE, Weblogic, Mule, …) and i was impressed by his ability to learn and to adapt to new things very quickly. The project has improved in quality with him.
I highly recommend him.” September 21, 2011

Kim Quoc Tran, J2EE Consultant, BNP PARIBAS
worked directly with Jonathan at BNPParibas

I wrote the following notice on Nicolas GRISO‘s profile on LinkedIn:

Nicolas has a wide knowledge of Java technologies and agile methods. He delivers high quality code, does not hesitate to start big refactorings and keeps his focus on general improvement of the project.

I wrote the following notice on Andre CAPLAIN‘s profile on LinkedIn:

I have worked directly with Andre for three years. As member, and later head, of support team, Andre is committed to his job and tasks, with seriousness and efficiency. I strongly recommend Andre for his open mind and the professionalism he demonstrated.

I wrote the following notice on Dr. Karl TOMBRE‘s profile on LinkedIn:

Many students and former students who followed Karl’s lessons will tell he is a brillant teacher. Their statement is right, but incomplete: for all a generation of Engineers of the Ecole des Mines who discovered Java and C++ through Karl, Dr Tombre is more than a teacher: he is a master.

I wrote the following notice on Francois LECOINTRE‘s profile on LinkedIn:

Francois is a very good analyst, who always investigates and gives a the right response when a problem occurs. Besides, he is pleasant colleague to work with, because of his open-mindness.

I highly recommand Francois.