Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Multiple embedded Yaws instances
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dean Song  
View profile  
 More options May 8 2012, 10:50 pm
From: Dean Song <dean_yanq...@yahoo.com.cn>
Date: Wed, 9 May 2012 10:50:17 +0800 (CST)
Local: Tues, May 8 2012 10:50 pm
Subject: Re: [erlang-questions] Multiple embedded Yaws instances

Hi Arijan
    If want to start two Yaws, it could work start them in separate VM rather than one VM ( one in dog@node, the other in cat@node).

I guess it could be an option to start the SUT in its own Erlang VM, but how would I start and stop this VM from the Common Test one (from init_per_suite/end_per_suite)? 

  You can start SUT through os:cmd function, and I suggest you start SUT outside Common Test and make it running,at least before CT execute TC.  Stat/stop SUT frequently useless.

________________________________
 From: Arjan Hakkesteegt <ar...@hakwerk.com>
To: erlang-questi...@erlang.org
Sent: Wednesday, May 9, 2012 2:49 AM
Subject: [erlang-questions] Multiple embedded Yaws instances

Hi,

I am trying to setup a Common Test mock layer around my SUT (System Under Test). Both the SUT and CT should start an embedded Yaws instance because both should both act as client and as server for SOAP.
Client(SUT) -> Server(CT)
Server(SUT) <- Client(CT)

However, it appears that it is not possible to run more than 1 embedded Yaws within a VM? When starting the second instance I get already_started errors from the supervisor. I tried to modify the ChildSpecs returned by yaws_api:embedded_start_conf/4 to append the Yaws instance Id to the supervisor child Ids, but still get the already_started errors. I tried it like this:
   [{yaws_log_myid,
    {yaws_log,start_link,[]},
    permanent,5000,worker,
    [yaws_log]},
    {yaws_server_myid,
    ...}]

I've used multiple SConfs within a single embedded Yaws instance before, but I don't think that this is an option here as my SUT and the CT suite are completely separate applications and the SUT should be seen as a blackbox.

I guess it could be an option to start the SUT in its own Erlang VM, but how would I start and stop this VM from the Common Test one (from init_per_suite/end_per_suite)?

Any solutions to this problem? Or am I missing something obvious?

Thanks,
Arjan

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.