WE
Hi All,
We are trying to install Business Publisher, but it keeps on giving us errors.
The log file:
2016-05-19 14:50:03,934|WARN |qtp1888442711-21| com.aris.prov.agent.config.DefaultAgentConfig - Properties loaded from the file agent.user.cfg.bak for verification differ from those that were written. Expected: {autostart.mode=off, local.repository.only=FALSE, remote.repository.url=http://PVBJHBNHSVSTZ1.COMPANY.CORP:13131} vs actual: {autostart.mode=off, local.repository.only=FALSE, remote.repository.url=http://PVBJHBNHSVSTZ1.COMPANY.CORP:13131}
2016-05-19 14:50:03,934|INFO |qtp1888442711-21| com.aris.prov.agent.config.DefaultAgentConfig - Verification of agent configuration written to file agent.user.cfg.bak successful.
2016-05-19 14:50:03,969|ERROR|qtp1888442711-26| com.aris.prov.agent.rest.resources.RunnableLifecycleResource - InstanceIdDoesNotExistA runnable with ID businesspublisher_l is not configured
RunnableLifecycleException [status=InstanceIdDoesNotExist, getMessage()=A runnable with ID businesspublisher_l is not configured]
at com.aris.prov.agent.lifecycle.AbstractRunnableLifecycleManager.getRunnableInfoWithValidation(AbstractRunnableLifecycleManager.java:415)
at com.aris.prov.agent.lifecycle.AbstractRunnableLifecycleManager.enhanceRunnableWithReturnValue(AbstractRunnableLifecycleManager.java:353)
at com.aris.prov.agent.lifecycle.AbstractRunnableLifecycleManager.enhanceRunnable(AbstractRunnableLifecycleManager.java:334)
at com.aris.prov.agent.rest.resources.RunnableLifecycleResource.enhanceRunnableInstance(RunnableLifecycleResource.java:204)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:708)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:598)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:486)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:413)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:999)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:486)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
at org.eclipse.jetty.server.Server.handle(Server.java:350)
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454)
at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:900)
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:954)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:851)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:606)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:46)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538)
at java.lang.Thread.run(Thread.java:745)
As shown in the highlighted text, "RunnableLifecycleResource - InstanceIdDoesNotExistA runnable with ID businesspublisher_l is not configured" comes from the log file, any ideas on why we get this error ?
Thanks,
Willem
Hi Willem,
just a guess: maybe the url used remote.repository.url is not complete.
The url in the logfile points to a server-adress, but this is maybe not the place where the repository is located on the server.
In the installation-administration-guide I found some examples for the use of remote.repository.url and all of them have the format: set remote.repository.url="http\://something.com/repo and on our publisher-Server I found a similar entry in the mentioned file agent.user.cfg.bak: remote.repository.url=http\://ARI-1234.LVRINTERN.LVR.DE\:13131/repo
BG Gerald
Hi Gerald,
Thanks for your reply, we will check this and I will give feedback to the community. Another thing that might be an issue, and is something that we will be testing within the next week, is the Firewall. The computer that we want to install publisher from is not on the same network as the server, the IT team only gave us a link to the server for install purposes, NOT full access. But again, it will be something that we will be testing within the next week.
WE
