Hide Forgot
project_key: SOA When starting the admin console, the following error is logged by the server: 17:45:04,745 ERROR [modeshape] Exception invoking getConnectors java.lang.reflect.UndeclaredThrowableException: Failed to invoke method 'getConnectors' on component 'ModeShapeEngine' with parameters []. at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:201) See attached log file.
Attachment: Added: server.log.gz
Link: Added: This issue is a dependency of MODE-955
The following directories/files are created under the users' home directory (i.e. not the server directory), when the admin console is started: jboss-as jboss-as/server jboss-as/server/default jboss-as/server/default/data jboss-as/server/default/data/modeshape jboss-as/server/default/data/modeshape/repositories jboss-as/server/default/data/modeshape/repositories/repository jboss-as/server/default/data/modeshape/repositories/repository/indexes jboss-as/server/default/data/modeshape/repositories/repository/indexes/eds jboss-as/server/default/data/modeshape/repositories/repository/indexes/eds/content jboss-as/server/default/data/modeshape/repositories/repository/indexes/eds/content/segments_2 jboss-as/server/default/data/modeshape/repositories/repository/indexes/eds/content/segments.gen jboss-as/server/default/data/modeshape/repositories/repository/indexes/eds/content/_0.cfx jboss-as/server/default/data/modeshape/repositories/repository/indexes/eds/content/_0.cfs jboss-as/server/default/data/modeshape/repositories/repository/indexes/system jboss-as/server/default/data/modeshape/repositories/repository/indexes/system/content jboss-as/server/default/data/modeshape/repositories/repository/indexes/system/content/segments_i jboss-as/server/default/data/modeshape/repositories/repository/indexes/system/content/segments.gen jboss-as/server/default/data/modeshape/repositories/repository/indexes/system/content/_w.cfs (The dynamicvdb-ws-weather Teiid example had been deployed before the admin console was started.)
I'm not seeing this same behavior. I've installed the server on a rhel and a mac, and both times the data/modeshape/... directory is being placed within the profile where the server is installed. The modeshape-config.xml file controls this location: soa-p - ../../jboss-as/server/<profile>/data/modeshape/repositories/repository/indexes brms - ../jboss-as-web/server/<profile>/data/modeshape/repositories/repository/indexes standalone - ../jboss-as/server/<profile>/data/modeshape/repositories/repository/indexes
I think I realize what the issue is, it's because of using relative paths that this could happen. I'm changing the modeshape build.xml to insert the full path to the data directory.
The one problem I see doing this is the soa-p install can't just be moved to another location and expect modeshape to work. I don't recall if this a feature of soa-p or not.
ModeShape has applied the fix to 2.2.x branch regarding the admin console, and the modeshape build.xml has been updated to set the full path the modeshape data directory in the profile being used. These should be available for the next build.
Link: Added: This issue is duplicated by SOA-2483
Writer: Added: Darrin
Release Notes Docs Status: Added: Not Yet Documented
Verified fixed in ER9.