mguimard
commented
6 years ago Hello there,
Sorry for the late reply. It seems that there's a bug that prevent to create a workspace in 2.0 if no Indexer (elasticsearch) is running. Please can you try the latest version from docdoku-plm-docker/dev ? (it has been improved, and you'll also find the answer to the second question in the README)
magnarok49
So I have downloaded "docdoku-server-ear.ear" (v 2.0) and "eplmp-server-ear.ear" from this link : "https://www.docdokuplm.com/docdoku-plm/" , and tried both of them in Docker, using following the guide given here: "https://github.com/docdoku/docdoku-plm-docker".
After I create an account, I enter the menu to create a new workspace, fill in name and description. Regardless of what I enter, I always get an error bar saying "the workspace 'some-workspace-name' already exists". I checked the database, and the workspace table is completely empty.
Some context: Running a separate docker with mySQL 5.7, and the EAR is deployed on a docker with payara 4.181. (had to change the tag of the image it fetched, as the newest payara was 5.some_version, and that messed things up) It is filling user info into the database, so it seems to be connected and have the necessary rights.
I have not configured a mail server, so the java mail session is filled with dummy values, I don't know if that would affect anything.
I had a look at the requests flying around, and it seems the GET on "~/api/workspaces" is rightly saying I have no associated workspaces: raw response: "{"administratedWorkspaces":[],"allWorkspaces":[]}".
Payara logs also reveal that there is a singleton indexer that failed to initialize, I don't know if that might have anything to do with it, these are the generated raw logs right after I click the button to add a workspace:
`[2018-07-04T14:25:42.074+0000] [Payara 4.1] [WARNING] [AS-EJB-00056] [javax.enterprise.ejb.container] [tid: _ThreadID=28 _ThreadName=http-thread-pool::http-listener-1(3)] [timeMillis: 1530714342074] [levelValue: 900] [[
A system exception occurred during an invocation on EJB IndexerClientProducer, method: public io.searchbox.client.JestClient org.polarsys.eplmp.server.indexer.IndexerClientProducer.produce()]]
[2018-07-04T14:25:42.075+0000] [Payara 4.1] [WARNING] [] [javax.enterprise.ejb.container] [tid: _ThreadID=28 _ThreadName=http-thread-pool::http-listener-1(3)] [timeMillis: 1530714342075] [levelValue: 900] [[
javax.ejb.NoSuchEJBException: Singleton IndexerClientProducer is unavailable because its original initialization failed.
]]
[2018-07-04T14:25:42.076+0000] [Payara 4.1] [WARNING] [AS-EJB-00056] [javax.enterprise.ejb.container] [tid: _ThreadID=28 _ThreadName=http-thread-pool::http-listener-1(3)] [timeMillis: 1530714342076] [levelValue: 900] [[
A system exception occurred during an invocation on EJB IndexerManagerBean, method: public void org.polarsys.eplmp.server.indexer.IndexerManagerBean.createWorkspaceIndex(java.lang.String)]]
[2018-07-04T14:25:42.076+0000] [Payara 4.1] [WARNING] [] [javax.enterprise.ejb.container] [tid: _ThreadID=28 _ThreadName=http-thread-pool::http-listener-1(3)] [timeMillis: 1530714342076] [levelValue: 900] [[
javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean
Caused by: javax.ejb.NoSuchEJBException: Singleton IndexerClientProducer is unavailable because its original initialization failed.
]]
[2018-07-04T14:25:42.349+0000] [Payara 4.1] [WARNING] [] [org.polarsys.eplmp.server.rest.exceptions.mapper.AlreadyExistsExceptionMapper] [tid: _ThreadID=28 _ThreadName=http-thread-pool::http-listener-1(3)] [timeMillis: 1530714342349] [levelValue: 900] [[
The workspace "fdsdfs" already exists]]`
My apologies for the faulty markdown syntax.
A second, much easier question: is there a default admin user that already exists upon launching the server? I tried setting the admin field to true when manually creating a user, but it seems the field was ignored.