Dear Javier,
this was our first issue regarding the initial loading of CEP.
We have tried the last image of CEP on a new instance with Docker with all
possible browsers.
The UI Administration although is still slow, we have overcome it by having
a continuous open session on a VPS so regarding the question you could close
it as ticket as it escalated.

We had,and still have, a number of other issues since that, and we sent
another email from 24th of September on which we still have no answer
and all the problems that come with that in our development.

Below is the email from 24th of September, to let you aware of.

Regards,
Marios Protogiros

---------- Forwarded message ----------
> From: zahos pap <zacpapac04@gmail.com>
> Date: Thu, Sep 24, 2015 at 12:33 PM
> Subject: BeeZon Issues using FIWARE-LAB and GE enablers
> To: tech@fractals-fp7.com, dsoukaras@di.uoa.gr, gkraggel@di.uoa.gr
>
>
>
> Dear All,
>
>
> We are experiencing a number of issues with the cloud administrator Web UI
> that except the delay they cause to development , they resulted even to
> lose an instance of CEP and the effort we made to have it up and running.
>
> Issues
> 1)2 members of beezon cloud, while connected from different locations were
> seeing different number of instances in the cloud. One was seeing one
> instance, and another 2. The correct was one instance as the other was
> deleted, but despite refreshes and log out log in at cloud.filab did not
> help.
>
> 2)Also the name and attributes of the key pair selected was also viewed
> differently.
>
> 3) A member logged in with its username, and uses the cloud tab. Then logs
> out, and another member logs in with other credentials. When clicking the
> cloud tab, the web ui shows the previous user`s name.
>
> 4) One of our instances containing the CEP enabler, was deleted without
> knowing how it was triggered. This caused a lot of working hours lost. Is
> there any way to recover a deleted instance?
>
> 5) Our members used IE , and others Chrome. The most of problems were with
> IE. Our guess that the web application uses history and caching on the
> browser in not the best way, so this is why all these issues came up? Is
> there a recommended browser that we should use? If yes, why it is not
> documented?
>
> 6) Before the instance of CEP got deleted, a list of issues were there as
> well.
> a) The delete context menu does not work,
> b) Importing a project from a previous saved definition does not render
> well to the UI.
> c) The save button also does not update the definition.
> d) There is not a complete tutorial of using the WebUI in a new CEP.
> There are some video tutorials, showing glimpses of defining an event, EPA,
> etc, but not an end to end scenario, and how to update the server of using
> the new definition.
> e)The only way, it was finally possible to use a new project was this,
> create a new project, add the events, consumers,context, EPAs.
> export definition to a file for back up.
> Export definition to server.
> Updating with the REST Api the definition to use.
> Success in posting a new event and getting a callback to another rest
> consumer.
> And all that worked for the deleted instance after a lot of hours spent on
> trying and retrying.
>
> 7) When we launch then iot application we get the foollowing errors from
> log4cplus
> log4cplus: ERROR No appenders cound be found for logger (main)
> log4cplus: ERROR Please initialize the log4plus system properly.
> Is there any configuration file to properly set the log4plus? Any
> sample/example?
>
>
>
> Best Regards,
>

On Tue, Oct 27, 2015 at 5:03 PM, Romero, Javier <javier.romero@atos.net>
wrote:

> Dear Marios
>
>
>
> Can we consider this issue resolved?
>
>
>
> BR
>
>
>
> From: Romero, Javier
> Sent: Monday, September 07, 2015 10:12 AM
> To: 'Marios Protogiros'; tech@fractals-fp7.com
> Cc: zahos; John Sokianos; Mhtsos Karantonis
> Subject: RE: CEP instance problem
>
>
>
> Dear Marios
>
>
>
> Following you have the answer we have received from FIWARE related to your
> issue:
>
>
>
>
> *My suggestion would be to install the CEP from the open source and get
> the latest version. *
> *The installation guide is here:
> https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/CEP_GE_-_IBM_Proactive_Technology_Online_Installation_and_Administration_Guide
> <https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/CEP_GE_-_IBM_Proactive_Technology_Online_Installation_and_Administration_Guide>
> **The open source is here:
> https://github.com/ishkin/Proton/tree/master/mvn-repo/com/ibm/hrl/proton
> <https://github.com/ishkin/Proton/tree/master/mvn-repo/com/ibm/hrl/proton> *
>
>
>
> Hope it helps.
>
>
>
> Best Regards.
>
>
>
> From: Marios Protogiros [mailto:mariosprotos@gmail.com
> <mariosprotos@gmail.com>]
> Sent: Friday, September 04, 2015 10:14 AM
> To: tech@fractals-fp7.com
> Cc: zahos; John Sokianos; Mhtsos Karantonis
> Subject: CEP instance problem
>
>
>
> Hello,
>
> A CEP image was installed in our cloud, but we are having some strange
> problems that are blockers to our development.
>
> The problem is that the UI of the AuthoringTool is very unstable at
> loading. In other words many times takes a lot of time to
>
> load, and most of the times never loads.
>
>
> The public CEP instance for comparison, provided for everyone as a test
> server has no problems and we can make tests on that but it is not a safe
> environment as anyone can delete our project.
>
> Our instance was tested through all the major browsers, IE, Chrome,
> Firefox.
>
> the URL of the instance is
> http://185.23.171.114:8080/AuthoringTool/Main.html
>
> The instance is dual CPU, with 2048MB RAM.
>
>
>
> That unstable behavior blocks us on experimenting and proceed with the
> development of our tasks related to CEP.
>
> Could you give us some instructions of what can be done to make the
> responsiveness of the CEP server more stable?
>
> Kind Regards,
>
>
> Marios Protogiros
>
> Beezon IoT Solutions
>
>
>
>
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive this
> e-mail in error, please notify the sender immediately and destroy it.
> As its integrity cannot be secured on the Internet, the Atos group
> liability cannot be triggered for the message content. Although the sender
> endeavors to maintain a computer virus-free network, the sender does not
> warrant that this transmission is virus-free and will not be liable for any
> damages resulting from any virus transmitted.
>
> Este mensaje y los ficheros adjuntos pueden contener información
> confidencial destinada solamente a la(s) persona(s) mencionadas
> anteriormente y pueden estar protegidos por secreto profesional.
> Si usted recibe este correo electrónico por error, gracias por informar
> inmediatamente al remitente y destruir el mensaje.
> Al no estar asegurada la integridad de este mensaje sobre la red, Atos no
> se hace responsable por su contenido. Su contenido no constituye ningún
> compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
> Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor
> no puede garantizar nada al respecto y no será responsable de cualesquiera
> daños que puedan resultar de una transmisión de virus.
>

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Marios Protogiros <mariosprotos@gmail.com>]