T3 Communication error on Oracle SOA Suite
I was able to install Oracle SOA Suite 11gR1, a product having a slightly complicated structure, to my computer following instructions carefully. Once the installation is complete, I checked that there were two servers named as AdminServer and SOAServer. In addition, there is no cluster defined but there is a machine definition named as LocalMachine, where SOAServer is contained. The port assignment was like that 7001 and 8001 are reserved for AdminServer and SOAServer respectively. I developed a simple composite application and tried to deploy it as a SOA Composite Application to the SOA server. Deployment was failed with an exception shown in Figure 1 and the generated log outputs below. As you see, the message is “Unable to register service…”
Failed to retrieve policy oracle.wsm.policyaccess.PolicyAccessException: WSM-06132 : Error creating a connection to Oracle WSM Policy Manager. at oracle.wsm.policyaccess.impl.PMPolicyResolverBase.init(PMPolicyResolverBase.java:113) at oracle.wsm.policyaccess.impl.remote.RemotePolicyResolver.init(RemotePolicyResolver.java:116) at oracle.wsm.policyaccess.impl.PolicyAccessResolver.getResolver(PolicyAccessResolver.java:169) at oracle.wsm.policyaccess.impl.PolicyAccessResolver.getResolver(PolicyAccessResolver.java:98) ... at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused By: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://mymachine:8001: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination] at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40) at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:367) at weblogic.jndi.Environment.getContext(Environment.java:315)..
Once I analyzed the generated log, I found out that the error was about T3 Protocol used by WebLogic server internally. Briefly, T3 protocol is WebLogic’s Object Serialization and RMI implementation with the idea of effective communication behind it. Going a step further, I used weblogic.Admin utility (illustration on Linux shown in Figure 2) and found that although pinging URL including IP address returns successfull response; usage of computer name in the URL causes failure of pinging the same URL with T3 protocol as shown Figure 2. By the way, no matter particular URL includes computer name or IP address, HTTP communication works fine (at least you can test it by openning administration tool). It means that there is something wrong with the host name conversion once T3 protocol is used. At that point, I have to say that I am using Ubuntu, and most of discussion forums and blogs say that the same problem does not occur at Microsoft Windows.
First of all, I tried to enter IP adress as 127.0.0.1 to “Listen Address” of SOA Server configuration (which is blank as a default, no installation instruction is provided to enter the proper value!) as shown Figure 3, restart both servers WebLogic and SOA Server then deployment was completed successfully. But, there is still an error with JDeveloper that deployment via JDeveloper was fine but generated URL’s does not work properly. For example, generated URL for testing a Web Service via JDeveloper does not work as shown in Figure 4. So, it means that the first solution was not a proper one and I still needed an effective way to figure it out.
Finally, the solution is as follows:
- Provide a new host entry into Host file by referring local IP address (e.g. 127.0.0.1 oraclehost)
- Reinstall the product by using new hostname entry (shown in Figure 5,6,7)
- Define a new application server connection in JDeveloper regarding the same hostname
The worst part of this experience was the lack of public information over discussion forums and blogs. I guess with each new level added to software technology, products’ complexity increases. However, I would like to believe that there has to be more public information, FAQs, etc. to provide fast and effective solutions.
good post. For similar and related posts on SOA and weblogic check this http://onlineappsdba.com/index.php/2009/07/08/oracle-fusion-middleware-soa-suite-11g-r1-installation/
Like or Dislike:
0 
0
Hello mr. Acikgoz,
thanks for the post, I’m having the same problem and I’m glad someone took the time to make the solution public. I’m just having some trouble figuring out what do you mean with
“Provide a new host entry into Host file by referring local IP address (e.g. 127.0.0.1 oraclehost)”
As I’ve seen within the pictures it means I have to create a new domain, but I don’t see where do you enter the 127.0.0.1 address, only oraclehost. I’m I understending it wrong?
Thanks!
Like or Dislike:
0 
0
Hi,
Host entry helps avoiding to use IP values in the configuration. Instead of IP value, hostname (i.e. oraclehost) is used in my configuration.
Anyway, oraclehost is not a domain; it is just locally provided a hostname by referring IP 127.0.0.1. So, you may enter localhost 127.0.0.1 IP value everywhere that oraclehost is entered. I think it may help.
Like or Dislike:
0 
0