#65 Portal ignores hostname parameter in servENT 0.3.9

[fsolana]

In servENT 0.3.9

Using the portal to execute a service with an OpenLazslo UI tries to load it in localhost, ignoring the hostname parameter in the config files, then if I'm on another host an http error 404 page not fount is displayed.

I have the hostname uncommented and defined with my IP in the following files:
servent/deployment.props
servent/fada/fada.rc
servent/deploy/core-webapps/deployment.props

[Andy Edmonds]

Logged In: YES
user_id=1312564
Originator: NO

Hi,
Could you please send on your configuration files and if possible the
service and UI so I can reproduce the problem?

Thanks

Andy

[fsolana]

configuration files

[fsolana]

Logged In: YES
user_id=1642072
Originator: YES

These are the configuration files.

It happens with all the services we try to execute with.

In version 0.3.8 we haven't this problem.
File Added: configFiles.zip

[Andy Edmonds]

Logged In: YES
user_id=1312564
Originator: NO

Thanks! :-)
Is there any exceptions thrown on the console?

[Andy Edmonds]

Logged In: YES
user_id=1312564
Originator: NO

Hey - I've just had a look over your configuration files again and you have 2 different IP addresses only differing by their first octet - 192.xxx.xxx.xxx and 193.xxx.xxx.xxx
Is this intentional? If not that's most likely your problem.

Andy

[Nobody/Anonymous]

Logged In: NO

Thanks! :-)
Is there any exceptions thrown on the console?

[Nobody/Anonymous]

Logged In: NO

I was making some changes, the good files are all with 193.xxx.xxx.xxx

There are no exceptions in the console. The Portal http://xxx.xxx.xxx.xxx/portal/ tries to display the UI in the direction http://localhost/portal/uicache/SM-...../xxx.lzx

[Andy Edmonds]

Logged In: YES
user_id=1312564
Originator: NO

Until a proper fix can be issued is it possible for you to work with the 0.3.8 servent?

[Andy Edmonds]

Logged In: YES
user_id=1312564
Originator: NO

Seems this reply got lost...
I've looked further into the problem and there seems to be a problem with a call to a servent method.
At the moment I use:

ServentInfo.getInstance().getIP()

to discover the servent's IP - however when a IP/hostname is configured within the servent.props file, it is not picked up by the servent.
I'll post this off as a bug here.

Andy

[Nobody/Anonymous]

Logged In: NO

Yes we will use 0.3.8.

[Andy Edmonds]

Logged In: YES
user_id=1312564
Originator: NO

Just a quick update - we're still working with sun/techideas to resolve this issue with getIP()

Andy

[Andy Edmonds]

Logged In: YES
user_id=1312564
Originator: NO

I've created a work around in the portal that will read the ip/hostname from the servent configuration file. The fix is now in the mainline on CVS. If you would like the updated jar, rather than waiting on a new servent release please contact me through my sourceforge mail address.

Andy