[JBoss JIRA] (ARTIF-714) Error starting Artificer beta 1 - hibernate.search module not found
by Mark Tebong (JIRA)
[ https://issues.jboss.org/browse/ARTIF-714?page=com.atlassian.jira.plugin.... ]
Mark Tebong closed ARTIF-714.
-----------------------------
Resolution: Won't Fix
For EAP 6.3 and before, you would need to manually install hibernate.search. It is recommended to use EAP 6.4+.
> Error starting Artificer beta 1 - hibernate.search module not found
> --------------------------------------------------------------------
>
> Key: ARTIF-714
> URL: https://issues.jboss.org/browse/ARTIF-714
> Project: Artificer
> Issue Type: Bug
> Affects Versions: 1.0.0.Beta1
> Environment: Windows. EAP 6.3
> Reporter: Mark Tebong
> Assignee: Brett Meyer
>
> On start up of EAP, this is the error I get. The server eventually starts, but after log in, Artificer immediately gives error "Error Searching for Artifacts" and "Error Refreshing Ontology List". Thereafter, I can't really do much. It appears artificer-server did not deploy or start, due to the following error.
> 11:22:42,050 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.module.service."deployment.artificer-server.wa
> r".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.artificer-server.war".main: JBAS018759: Failed to load module: deploym
> ent.artificer-server.war:main
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19
> ]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-r
> edhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: org.jboss.modules.ModuleNotFoundException: org.hibernate.search.orm:main
> at org.jboss.modules.Module.addPaths(Module.java:1050) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.Module.link(Module.java:1406) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1434) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:242) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19
> ]
> ... 5 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ARTIF-714) Error starting Artificer beta 1 - hibernate.search module not found
by Mark Tebong (JIRA)
[ https://issues.jboss.org/browse/ARTIF-714?page=com.atlassian.jira.plugin.... ]
Mark Tebong commented on ARTIF-714:
-----------------------------------
It is not a hard requirement. I will download and install 6.4, then artificer beta 1. If it works, I'll close this bug (making the note), and if its stil an issue, I'll update bug.
> Error starting Artificer beta 1 - hibernate.search module not found
> --------------------------------------------------------------------
>
> Key: ARTIF-714
> URL: https://issues.jboss.org/browse/ARTIF-714
> Project: Artificer
> Issue Type: Bug
> Affects Versions: 1.0.0.Beta1
> Environment: Windows. EAP 6.3
> Reporter: Mark Tebong
> Assignee: Brett Meyer
>
> On start up of EAP, this is the error I get. The server eventually starts, but after log in, Artificer immediately gives error "Error Searching for Artifacts" and "Error Refreshing Ontology List". Thereafter, I can't really do much. It appears artificer-server did not deploy or start, due to the following error.
> 11:22:42,050 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.module.service."deployment.artificer-server.wa
> r".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.artificer-server.war".main: JBAS018759: Failed to load module: deploym
> ent.artificer-server.war:main
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19
> ]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-r
> edhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: org.jboss.modules.ModuleNotFoundException: org.hibernate.search.orm:main
> at org.jboss.modules.Module.addPaths(Module.java:1050) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.Module.link(Module.java:1406) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1434) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:242) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19
> ]
> ... 5 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ARTIF-714) Error starting Artificer beta 1 - hibernate.search module not found
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-714?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on ARTIF-714:
-----------------------------------
Hey [~mtebong], is EAP 6.3 a hard requirement? Hibernate Search wasn't introduced into EAP until 6.4. Frankly, we were planning to stop support for EAP 6.0-6.3 entirely. But if there's a reason why users can't use EAP 6.4, I suppose we could temporarily consider providing Search...
> Error starting Artificer beta 1 - hibernate.search module not found
> --------------------------------------------------------------------
>
> Key: ARTIF-714
> URL: https://issues.jboss.org/browse/ARTIF-714
> Project: Artificer
> Issue Type: Bug
> Affects Versions: 1.0.0.Beta1
> Environment: Windows. EAP 6.3
> Reporter: Mark Tebong
> Assignee: Brett Meyer
>
> On start up of EAP, this is the error I get. The server eventually starts, but after log in, Artificer immediately gives error "Error Searching for Artifacts" and "Error Refreshing Ontology List". Thereafter, I can't really do much. It appears artificer-server did not deploy or start, due to the following error.
> 11:22:42,050 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.module.service."deployment.artificer-server.wa
> r".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.artificer-server.war".main: JBAS018759: Failed to load module: deploym
> ent.artificer-server.war:main
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19
> ]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-r
> edhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: org.jboss.modules.ModuleNotFoundException: org.hibernate.search.orm:main
> at org.jboss.modules.Module.addPaths(Module.java:1050) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.Module.link(Module.java:1406) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1434) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:242) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19
> ]
> ... 5 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ARTIF-714) Error starting Artificer beta 1 - hibernate.search module not found
by Mark Tebong (JIRA)
[ https://issues.jboss.org/browse/ARTIF-714?page=com.atlassian.jira.plugin.... ]
Mark Tebong commented on ARTIF-714:
-----------------------------------
When I look at the file system, it does not appear the hibernate.search jar file(s) are installed.
> Error starting Artificer beta 1 - hibernate.search module not found
> --------------------------------------------------------------------
>
> Key: ARTIF-714
> URL: https://issues.jboss.org/browse/ARTIF-714
> Project: Artificer
> Issue Type: Bug
> Affects Versions: 1.0.0.Beta1
> Environment: Windows. EAP 6.3
> Reporter: Mark Tebong
> Assignee: Brett Meyer
>
> On start up of EAP, this is the error I get. The server eventually starts, but after log in, Artificer immediately gives error "Error Searching for Artifacts" and "Error Refreshing Ontology List". Thereafter, I can't really do much. It appears artificer-server did not deploy or start, due to the following error.
> 11:22:42,050 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.module.service."deployment.artificer-server.wa
> r".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.artificer-server.war".main: JBAS018759: Failed to load module: deploym
> ent.artificer-server.war:main
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19
> ]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-r
> edhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: org.jboss.modules.ModuleNotFoundException: org.hibernate.search.orm:main
> at org.jboss.modules.Module.addPaths(Module.java:1050) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.Module.link(Module.java:1406) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1434) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:242) [jboss-modules.jar:1.3.3.Final-redhat-1]
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19
> ]
> ... 5 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ARTIF-714) Error starting Artificer beta 1 - hibernate.search module not found
by Mark Tebong (JIRA)
Mark Tebong created ARTIF-714:
---------------------------------
Summary: Error starting Artificer beta 1 - hibernate.search module not found
Key: ARTIF-714
URL: https://issues.jboss.org/browse/ARTIF-714
Project: Artificer
Issue Type: Bug
Affects Versions: 1.0.0.Beta1
Environment: Windows. EAP 6.3
Reporter: Mark Tebong
Assignee: Brett Meyer
On start up of EAP, this is the error I get. The server eventually starts, but after log in, Artificer immediately gives error "Error Searching for Artifacts" and "Error Refreshing Ontology List". Thereafter, I can't really do much. It appears artificer-server did not deploy or start, due to the following error.
11:22:42,050 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.module.service."deployment.artificer-server.wa
r".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.artificer-server.war".main: JBAS018759: Failed to load module: deploym
ent.artificer-server.war:main
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19
]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-r
edhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
Caused by: org.jboss.modules.ModuleNotFoundException: org.hibernate.search.orm:main
at org.jboss.modules.Module.addPaths(Module.java:1050) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.Module.link(Module.java:1406) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1434) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:242) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19
]
... 5 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ARTIF-713) Persist each batch upload with one single transaction
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-713?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed ARTIF-713.
-----------------------------
Resolution: Won't Fix
For completeness, here's why this should never happen (forgot when I opened it):
Persisting artifact A happens in one transaction, while querying for artifacts to potentially target with a relationship owned by A happens in another transaction. In order to allow items in a batch to be related to *each other*, the transaction needs to be committed after each item is persisted. Otherwise, the latter transaction isn't able to see it.
Being able to support this would be extremely complicated and, ultimately, could require holding quite a bit of info in memory during batch execution.
> Persist each batch upload with one single transaction
> -----------------------------------------------------
>
> Key: ARTIF-713
> URL: https://issues.jboss.org/browse/ARTIF-713
> Project: Artificer
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Currently, each *item* in a batch is handled by a separate JDBC transaction. Instead, it would be far more performant to commit the *entire* batch in a single transaction. Further, from a user perspective, this setup makes more sense anyway...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ARTIF-713) Persist each batch upload with one single transaction
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-713:
---------------------------------
Summary: Persist each batch upload with one single transaction
Key: ARTIF-713
URL: https://issues.jboss.org/browse/ARTIF-713
Project: Artificer
Issue Type: Sub-task
Reporter: Brett Meyer
Assignee: Brett Meyer
Fix For: 1.0.0.Beta2
Currently, each *item* in a batch is handled by a separate JDBC transaction. Instead, it would be far more performant to commit the *entire* batch in a single transaction. Further, from a user perspective, this setup makes more sense anyway...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ARTIF-712) Refactor ArtifactSet, PagedResult, etc.
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-712?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-712:
------------------------------
Description: AbstractSet and its subclasses aren't really needed any more. It would be more performant to solely rely on PagedResult through the architecture and all clients. (was: ArtifactSet#list should never be used server-side unless absolutely necessary (feeds, etc.). Ex: PagedResult is currently handed the list (bad), instead of given an iterator (good). The latter would allow the BaseArtifactTypes to be visited/built on-demand, rather than all up-front.)
> Refactor ArtifactSet, PagedResult, etc.
> ---------------------------------------
>
> Key: ARTIF-712
> URL: https://issues.jboss.org/browse/ARTIF-712
> Project: Artificer
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.0.0.Beta2
>
>
> AbstractSet and its subclasses aren't really needed any more. It would be more performant to solely rely on PagedResult through the architecture and all clients.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years