Help coderanch get a
new server
by contributing to the fundraiser

Sibi Joseph

Greenhorn
+ Follow
since Jan 31, 2007
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
1
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Sibi Joseph

Hi sandeep

Thanks Sandeep for the info , it worked for me by setting the property sonar.findbugs.timeout. I have set the property within my sonar-project.properties file present in the root of the prioject being analysed by sonar runner tool.

sonar.findbugs.timeout=1200000

Thanks and Regards
Sibi


sandeep mathur wrote:Hi Peter,

Thanks for your reply.

Yes when mentioning sonar I mean http://www.sonarsource.org/? .

I got the solution for this issue. This was caused because the module on which I was running the sonar was big and the build machine was very slow. I have increased the timeout value in Findbug and it worked.


Thanks,
Sandeep

11 years ago

Devaka Cooray wrote:Are you using WebSphere?



Hi Devaka

I am facing the same problem on Websphere Application Server 7.0.0.7. I would be greatful if you could post the solution.

Regards
Sibi
Hi Askar

Thank you for the reply.. I have the issue resolved. It was indeed the problem of client not able to look-up the server by name. First my WAS server did not have a fully qualified domain name. I gave the linux box a fully qualified domain name. http://www-01.ibm.com/support/docview.wss?uid=swg21315802

Apart from this i have added the port and host name to the sas.client.props file (not actually necessary).

Additional Info i have gathered.


A good way to debug IIOP issues is to add the following arguments to java when you start the client

-Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true -Dcom.ibm.CORBA.Debug.Output= client.log

IIOP data gets logged into client.log file.

it is also seen that at times the sas.client.props file is not being read properly. Set the values in the file problematically and try its seen to work.

Thanks and Regards
sibi


Askar Akhmerov wrote:try to check port number.
as long as I understand 2810 is a port number of some node(on my installation it's the port number of the app server which was created along with installation). Make sure you have deployed your EjB on that node.
2809 - default port
2811, 2812, and so on are the port numbers of the AppSrv's that you have created on your own.

You should look for the correct port number in you admin console.

14 years ago
Hi Just to update.. that did not work either..

please help if any of you have an answer


sibi

Sibi Joseph wrote:hi Saw the following post
http://www.ecmplace.com/viewtopic.php?f=39&t=9906&start=0

I was experiencing this problem, and after running an ethernet trace found that my WebSphere server was responding with a redirect to itself using it's host name, which was not resolvable from the client.

Once I added the hostname into the <windows>\system32\drivers\etc\hosts file, it worked just fine.

So check to make sure the name ( not ip) that your host thinks it is can be resolved by anybody trying to lookup jndi resources on it.





Sibi Joseph wrote:hi

DID anyine get a solution. i am facing the same problem with WAS 7.0.0.7 running on a redhat enterprise linux 5.5

please share

thanks and Regards
sibi

Andr�s Irmer wrote:Same problem here... Any solution?

14 years ago
hi Saw the following post
http://www.ecmplace.com/viewtopic.php?f=39&t=9906&start=0

I was experiencing this problem, and after running an ethernet trace found that my WebSphere server was responding with a redirect to itself using it's host name, which was not resolvable from the client.

Once I added the hostname into the <windows>\system32\drivers\etc\hosts file, it worked just fine.

So check to make sure the name ( not ip) that your host thinks it is can be resolved by anybody trying to lookup jndi resources on it.





Sibi Joseph wrote:hi

DID anyine get a solution. i am facing the same problem with WAS 7.0.0.7 running on a redhat enterprise linux 5.5

please share

thanks and Regards
sibi

Andr�s Irmer wrote:Same problem here... Any solution?

14 years ago
hi

DID anyine get a solution. i am facing the same problem with WAS 7.0.0.7 running on a redhat enterprise linux 5.5

please share

thanks and Regards
sibi

Andr�s Irmer wrote:Same problem here... Any solution?

14 years ago
Hi Dhirendra

I am also facing a similar issue now. I need to authenticate an application using siteminder. Could you help me out with some pointers/sample code?

thanks in advance
sibi
15 years ago