[xwiki-users] XWiki 5.4.6 standalone: Failed to extract Entity Resource from URL
Hello everybody, I just started to check out XWiki 5.4.6 in the standalone package (Win7, 32bit). It installed fine and I can play with it locally (http://localhost:8080). If I put http://hostname.domain:8080/ in a browser on a _remote_ machine, I get a HTTP error 500 telling me: Error number 11007 in 0: Failed to extract Entity Resource from URL [http://ricardo_tubbs.eboek.local:8080/xwiki/bin/view/Main/]; Is the standalone version meant to work just locally and that's it? If not: what should I check or fix in any way? Thanks, Holger ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] XWiki 5.4.6 standalone: Failed to extract Entity Resource from URL
Hi Holger, On 31 Oct 2014 at 14:53:05, Holger Zimmermann (holger.zimmerm...@eboek.de(mailto:holger.zimmerm...@eboek.de)) wrote: Hello everybody, I just started to check out XWiki 5.4.6 in the standalone package (Win7, 32bit). It installed fine and I can play with it locally (http://localhost:8080). If I put http://.:8080/; in a browser on a _remote_ machine, I get a HTTP error 500 telling me: Error number 11007 in 0: Failed to extract Entity Resource from URL [http://ricardo_tubbs.eboek.local:8080/xwiki/bin/view/Main/]; Is the standalone version meant to work just locally and that's it? If not: what should I check or fix in any way? Could you paste the full stack trace you get? Thanks -Vincent Thanks, Holger ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] XWiki 5.4.6 standalone: Failed to extract Entity Resource from URL
Hi Vincent, Thanks for picking this up… The whole stacktrace: Caused by: com.xpn.xwiki.XWikiException: Error number 11007 in 0: Failed to extract Entity Resource from URL [http://ricardo_tubbs.eboek.local:8080/xwiki/bin/view/Main/] at com.xpn.xwiki.XWiki.initializeResourceFromURL(XWiki.java:546) at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:496) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:153) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:129) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449) at javax.servlet.http.HttpServlet.service(HttpServlet.java:735) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:669) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1448) at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:121) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:66) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:208) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:111) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:368) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:488) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:932) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:994) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:640) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException: Null keys are not supported! at org.infinispan.CacheImpl.assertKeyNotNull(CacheImpl.java:194) at org.infinispan.CacheImpl.get(CacheImpl.java:388) at org.infinispan.CacheImpl.get(CacheImpl.java:383) at org.xwiki.cache.infinispan.internal.InfinispanCache.get(InfinispanCache.java:95) at org.xwiki.wiki.internal.manager.DefaultWikiDescriptorCache.getFromAlias(DefaultWikiDescriptorCache.java:112) at
Re: [xwiki-users] XWiki 5.4.6 standalone: Failed to extract Entity Resource from URL
Hi Vincent, thanks for the quick answer... I can't ask companies admin to change the host name just for testing xwiki. I will install a serious XWiki-instance using MySQL on a machine without the _ character in name. May be this should go into installation notes or something. Thank you very much! Holger -Ursprüngliche Nachricht- Von: Vincent Massol [mailto:vmas...@gmail.com] Im Auftrag von vinc...@massol.net Gesendet: Freitag, 31. Oktober 2014 15:38 An: XWiki Users; Holger Zimmermann Betreff: Re: AW: [xwiki-users] XWiki 5.4.6 standalone: Failed to extract Entity Resource from URL Hi again, The issue is that we convert a URL to a URI (since the URL class has so many problems) and calling URI.getHost() returns null in your case and that’s because your host name contains the “_” character which is invalid for a URI (see http://docs.oracle.com/javase/7/docs/api/java/net/URI.html#getHost()), only “-“ (hyphen) is allowed. However URL.getHost() works fine for your case… But it’s probably wrong and shouldn’t since it’s not following the RFC 2396 (see http://www.ietf.org/rfc/rfc2396.txt). In any case, to fix your issue, you need to use a valid domain label ;) (remove the “_” or replace with “-“). I’m still hesitating about whether to call this a bug or a feature ;) Thanks -Vincent On 31 Oct 2014 at 15:01:57, Holger Zimmermann (holger.zimmerm...@eboek.de(mailto:holger.zimmerm...@eboek.de)) wrote: Hi Vincent, Thanks for picking this up… The whole stacktrace: Caused by: com.xpn.xwiki.XWikiException: Error number 11007 in 0: Failed to extract Entity Resource from URL [http://ricardo_tubbs.eboek.local:8080/xwiki/bin/view/Main/] at com.xpn.xwiki.XWiki.initializeResourceFromURL(XWiki.java:546) at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:496) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:153) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:129) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449) at javax.servlet.http.HttpServlet.service(HttpServlet.java:735) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:669) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1448) at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:121) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:66) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:208) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:111) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:368) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:488) at
[xwiki-users] XWiki 6, Java 7 and Red-Hat
Dear community, I tried to migrate a test xwiki instance to 6.x on my red-hat linux server, and encountered a (fatal) issue: as it requires java 7, in turn, it requires RHEL = 5.5 (and I'm on an old RHEL 4.6) due to glibc (thank you, java...). Upgrading red-hat on this server is not an option for now, even if it's way too old I agree, so I hope I'll be able to do this upgrade one day ... :/ But my point is, do you think interesting to add this information in installation guide somewhere ? [1] Maybe there's a better place, or maybe it's not needed at all I don't know... There's already info about java 7 obviously, I'm talking about specific impact for red-hat. WDYT ? Best regards, Jeremie [1] - http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Monitoring an Xwiki stack
Having made my XWiki site available to other users, I was concerned to find that the site became unusable at one point with client connections eventually timing out. I had no way to diagnose the problem, but eventually I managed to make a (slow) SSH connection to the server and restarted Tomcat, and things seemed to settle back to normal. The problem is I have no real sense of what happened and how to prevent it happening again. To that end, I'd appreciate any suggestions for monitoring the server and diagnosing poor performance. What do others typically use? I have an Apache2 server passing wiki page requests to Tomcat7 via an ajp connector, and a PostgreSQL database. My guess is that Tomcat is doing most of the work here so that's probably what I need to monitor the most. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Monitoring an Xwiki stack
I's also find any suggestions very helpful, I've had that happen a few times and outside of monitoring CPU and RAM, I've found logging to be difficult to use and configure, and even when I get it configured it's not very helpful. On Oct 31, 2014, at 1:57 PM, Bryn Jeffries bryn.jeffr...@sydney.edu.au wrote: Having made my XWiki site available to other users, I was concerned to find that the site became unusable at one point with client connections eventually timing out. I had no way to diagnose the problem, but eventually I managed to make a (slow) SSH connection to the server and restarted Tomcat, and things seemed to settle back to normal. The problem is I have no real sense of what happened and how to prevent it happening again. To that end, I'd appreciate any suggestions for monitoring the server and diagnosing poor performance. What do others typically use? I have an Apache2 server passing wiki page requests to Tomcat7 via an ajp connector, and a PostgreSQL database. My guess is that Tomcat is doing most of the work here so that's probably what I need to monitor the most. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Monitoring an Xwiki stack
Hello all, Here's my experience at monitoring XWikis. With i2geo.net and with my private XWiki, I use a zabbix server. This php-based monitoring tool is quite easy to configure for http monitoring and with a few more steps you get a mail notification when, e.g., a timeout occurs in connections. I've been using HypericHQ for a while, a java based monitoring, which was rather nice to manipulate but a machine-name-change broke everything, so I looked for something a tick more modern. At curriki.org, a site with lots of visitors, there's quite a few tools used to monitor. - First, for the safety and honesty of a system outside, alertsite.com is used. It is very effective at detecting breakges, including potential internet backbones'. We use monitoring from three locations. - Second, because, indeed, the XWiki servers sometimes need a push, there used to be a regular script that checks a basic page and, if failed, auto-restarts the app-server. For us, this is a bit unsafe because we like to control things after a restart. - Third, for a while, we have been running a combined monitoring which allowed to combine a small graphical view synced with logs of apache, the app-server, thread-dumps, and mysql. This allowed to catch bad actions which sometimes happen when power users perform actions which trigger too big queries which locked others (group-deletions were such an action). - Finally, we also added a zabbix which collects http monitoring as well as other classical values (disks, memory, apache-stats, …). The rhythm at curriki is about a week… after a week, one of the two cluster nodes (there's two currently) needs a restart because some memory gets exhausted and the GC starts to fail. We generally get alertsite errors then. The interest of running a monitoring infrastructure such as zabbix, is that you can analyze the behaviors of multiple variables and see if there is a way to predict if things are getting wrong. It remains a guts' feeling story but still gives you quite some confidence. It would be really nice if we could converge on a set of JMX analysis items for zabbix so that we could be analyzing more concretely the xwiki-relevant information (in particular the cache behaviors) and start adjusting to less fall out of memory. paul On 31 oct. 2014, at 22:29, Jason Clemons jason.clem...@live.com wrote: I's also find any suggestions very helpful, I've had that happen a few times and outside of monitoring CPU and RAM, I've found logging to be difficult to use and configure, and even when I get it configured it's not very helpful. On Oct 31, 2014, at 1:57 PM, Bryn Jeffries bryn.jeffr...@sydney.edu.au wrote: Having made my XWiki site available to other users, I was concerned to find that the site became unusable at one point with client connections eventually timing out. I had no way to diagnose the problem, but eventually I managed to make a (slow) SSH connection to the server and restarted Tomcat, and things seemed to settle back to normal. The problem is I have no real sense of what happened and how to prevent it happening again. To that end, I'd appreciate any suggestions for monitoring the server and diagnosing poor performance. What do others typically use? I have an Apache2 server passing wiki page requests to Tomcat7 via an ajp connector, and a PostgreSQL database. My guess is that Tomcat is doing most of the work here so that's probably what I need to monitor the most. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
