From: SourceForge.net <no...@so...> - 2009-10-01 10:21:26
|
Bugs item #2869885, was opened at 2009-09-29 18:03 Message generated for change (Comment added) made by gabrielke You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=879332&aid=2869885&group_id=176962 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: AVA (vmware images) Group: None Status: Open Resolution: None Priority: 9 Private: No Submitted By: Akos Gabriel (gabrielke) Assigned to: Paul Aviles (avilespa) Summary: initial client setup impossible - showstopper Initial Comment: With the AVA of today initial client setup is impossible. After I do the setup, the new client isn't there, moreover GardenWorld is gone... :( ---------------------------------------------------------------------- >Comment By: Akos Gabriel (gabrielke) Date: 2009-10-01 12:20 Message: I've extracted the newest AVA and run install. It is 353a now, and it does not need adempieretrunk.com. Now I'll check the upgrade. ---------------------------------------------------------------------- Comment By: Paul Aviles (avilespa) Date: 2009-09-30 16:27 Message: I just found that /vmware/share/htdocs/service/core/view-deploy.xml contains http://adempieretrunk.com:8080, which should only be a message in the management console, but not really used. will fix that. Paul Aviles ---------------------------------------------------------------------- Comment By: Paul Aviles (avilespa) Date: 2009-09-30 16:19 Message: Akos, that is my point. I don't use adempieretrunk for host names, it should only be adempierehost.com. That is set using /vmware/share/vami/vami_dns which gets executed every time you change the dns or networking settings. Can you try downloading the .l7 file from SF again? Regards, Paul Aviles ---------------------------------------------------------------------- Comment By: Akos Gabriel (gabrielke) Date: 2009-09-30 15:00 Message: I did ava_agent install today so I guess it is today's AVA. I think the problem is somewhere around the Java RPC config (port 1099). Quite easy to test: remove adempieretrunk.com from the client's hosts file Try to access the application server via host adempierehost.com 1099 It will fail. Add adempieretrunk.com again. Try to access adempieretrunk.com 1099 It will work. I guess the server side checks by which hostname it is accessed and if the hostname does not match, refuses connection. Rgds, Akos ---------------------------------------------------------------------- Comment By: Paul Aviles (avilespa) Date: 2009-09-30 14:29 Message: Akos, which AVA version is that? I initially did adempieretrunk but changed that to adempierehost as that is the same used in the ava 342, but for what I remember I never released one with adempieretrunk to the public so makes me wonder where did I left that name on. Regards, Paul Aviles ---------------------------------------------------------------------- Comment By: Akos Gabriel (gabrielke) Date: 2009-09-30 14:16 Message: I've further researched the problem. The problem occurs when the webstart client is not configured fully (see the other problem related to hostnames) and the webstart client can't access the appserver and can't start the process at the end of the initial client setup process. I guess it is doing something on the database which is not finished yet. After a clean install and correct hostname setup (adempieretrunk.com and adempierehost.com both in hosts file) the client setup just works fine. I guess this bug is not related to AVA any more, it is a general bug again. I think such processes must not be started if (at the end) they can't be finished successfully and they cause massive data corruption. Regards, Akos ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=879332&aid=2869885&group_id=176962 |