Re: [xwiki-users] Diagnosing empty start page

[Bryn Jeffries]

Hi Vincent,

> From: Vincent Massol [mailto:vinc...@massol.net]
> Sent: Monday, 22 August 2016 8:48 PM
>
> You should try to stop tomcat fully and start it again. It seems you’re only
> stopping the webapp and there are issues with xwiki cleanup when doing so.
> 
> Let us know if there are still errors.

I've stopped and started as you suggest, but I get the same result. The 
catalina.out log gives more data than the one I included before. Below are some 
selected lines. I recall that my previous installation generated a lot of 
warnings relating to Solr, but it's worrying that there are so many. Also, 
could the ClassLoader messages be part of the issue?

Sorry to appear naïve. I've no idea which errors are tolerated in a typical 
installation and which are not.

Bryn


Aug 22, 2016 9:07:10 PM 
org.apache.catalina.core.JreMemoryLeakPreventionListener lifecycleEvent
SEVERE: Failed to trigger creation of the GC Daemon thread during Tomcat start 
to prevent possible memory leaks. This is expected on non-Sun JVMs.
java.lang.ClassNotFoundException: sun.misc.GC
[...]
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:484)

[...]
Aug 22, 2016 9:07:14 PM org.apache.catalina.loader.WebappLoader buildClassPath
INFO: Unknown loader jdk.internal.loader.ClassLoaders$AppClassLoader@5f150435 
class jdk.internal.loader.ClassLoaders$AppClassLoader
Aug 22, 2016 9:08:04 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug 
logging for this logger for a complete list of JARs that were scanned but no 
TLDs were found in them. Skipping unneeded JARs during scanning can improve 
startup time and JSP compilation time.
2016-08-22 21:08:32,827 [localhost-startStop-1] INFO  
o.x.s.s.i.EmbeddedSolrInstance - Starting embedded Solr server...
2016-08-22 21:08:32,888 [localhost-startStop-1] INFO  
o.x.s.s.i.EmbeddedSolrInstance - Using Solr home directory: 
[/var/lib/xwiki/data/solr]
2016-08-22 21:08:39,654 [coreLoadExecutor-6-thread-1] WARN  
o.i.j.ResourceDMBean   - ISPN42: Did not find queried attribute 
with name coreHashCode
[many more lines line this]
2016-08-22 21:08:39,726 [coreLoadExecutor-6-thread-1] ERROR 
o.a.s.c.CoreContainer  - Error creating core [xwiki]: Error opening new 
searcher
org.apache.solr.common.SolrException: Error opening new searcher
at org.apache.solr.core.SolrCore.(SolrCore.java:820)
[...]
at java.lang.Thread.run(java.base@9-internal/Thread.java:804)
Caused by: org.apache.solr.common.SolrException: Error opening new searcher
at org.apache.solr.core.SolrCore.openNewSearcher(SolrCore.java:1662)
[...]
at org.apache.solr.core.SolrCore.(SolrCore.java:793)
... 9 common frames omitted
Caused by: java.io.IOException: Unable to unmap the mapped buffer: 
MMapIndexInput(path="/var/lib/xwiki/data/solr/xwiki/data/index/segments_1")
at 
org.apache.lucene.store.MMapDirectory$2.freeBuffer(MMapDirectory.java:329)
[...]
at org.apache.solr.core.SolrCore.openNewSearcher(SolrCore.java:1631)
... 12 common frames omitted
Caused by: java.lang.IllegalAccessException: class 
org.apache.lucene.store.MMapDirectory$2$1 cannot access class 
jdk.internal.ref.Cleaner (in module java.base) because module java.base does 
not export jdk.internal.ref to unnamed module @
65abf25c
at 
sun.reflect.Reflection.throwIllegalAccessException(java.base@9-internal/Reflection.java:411)
[...]
at 
org.apache.lucene.store.MMapDirectory$2.freeBuffer(MMapDirectory.java:314)
... 22 common frames omitted
2016-08-22 21:08:39,729 [localhost-startStop-1] ERROR 
.o.i.DefaultObservationManager - Failed to lookup listeners
org.xwiki.component.manager.ComponentLookupException: Failed to lookup 
component [role = [interface org.xwiki.observation.EventListener] hint = 
[solr.availablelocales]]
at 
org.xwiki.component.embed.EmbeddableComponentManager.getInstanceMap(EmbeddableComponentManager.java:216)
[...]
at java.lang.Thread.run(java.base@9-internal/Thread.java:804)
Caused by: org.xwiki.component.manager.ComponentLookupException: Failed to 
lookup component [org.xwiki.search.solr.internal.SolrInstanceProvider] 
identified by [role = 
[javax.inject.Provider] hint = 
[default]]
at 
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:394)
[...]at 
org.xwiki.component.embed.EmbeddableComponentManager.getInstanceMap(EmbeddableComponentManager.java:214)
... 19 common frames omitted
Caused by: org.xwiki.component.phase.InitializationException: Failed to lookup 
configured Solr instance type [embedded]
at 
org.xwiki.search.solr.internal.SolrInstanceProvider.initialize(SolrInstanceProvider.java:73)
[...]at 
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392)
... 24 common frames omitted
Caused by: org.xwi

Re: [xwiki-users] A problem with xwiki macros

[Edward Knyshov]

Hi, Vincent.
It's a requirement, that xwiki is fully configured after it's bootstrapped.
So our clients get working system right after deploy. That's why why setup
permissions in code.
Edward.

2016年8月22日(月) 14:51 Vincent Massol :

> Hi,
>
> > On 19 Aug 2016, at 05:21, Edward Knyshov  wrote:
> >
> > Hi. I'm trying to customize permissions in xwiki
> > using ApplicationReadyEventListener.
> > I override some permission in XWikiPreferences XWikiGlobalRights page to
> > get page deletion work by default for all users.
> >
> > https://gist.github.com/edvorg/4e2771ac02c4c64b705127964bc53c64
> >
> > I set up permissions in these functions.
> >
> > https://gist.github.com/edvorg/da7f8e64a46b7bbbf16f953e3fcc0e30
>
> I’m curious to know why you need to write code to set permissions for all
> users? Why don’t you use the UI?
>
> Thanks
> -Vincent
>
> >
> > This solutions works fine. But I got a problem with fresh xwiki
> bootstrap.
> > Sometimes I get fully broken xwiki - all macros shows error. And I have
> > something about admin user not having permission to edit some page:
> >
> > https://gist.github.com/edvorg/1bdec91e5483307696bc68841d2cb1d8
> >
> > I tried to debug all this code but it doesn't make much sense to me. I
> only
> > found that this CacheChecker thing somehow affects the issue. Could
> someone
> > point me to possible issues in my solution and maybe describe how this
> > CacheChecker should be used? I would appreciate any help, as we can not
> get
> > rid of xwiki integration bugs for a long time. Thank you!
>
> ___
> 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

[xwiki-users] Debian installation failed

[Eugen Colesnicov]

I am trying to install xwiki on Debian 8.5 using Debian packages.

I made commands (according to instruction):
1) wget -q "http://maven.xwiki.org/public.gpg"; -O- | apt-key add -
2) wget "http://maven.xwiki.org/stable/xwiki-stable.list"; -P
/etc/apt/sources.list.d/
3) sudo apt-get update
4) apt-cache search xwiki - all ok, I see xwiki packages

When I trying to install - 
5) apt-get install xwiki-enterprise-tomcat8-mysql
but result is:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xwiki-enterprise-tomcat8-mysql : Depends: xwiki-enterprise-mysql-common (=
8.2.1) but it is not going to be installed
  Depends: xwiki-enterprise-tomcat8-common (= 8.2.1) but it is not going to
be installed
E: Unable to correct problems, you have held broken packages.

What is the problem and how I can correct it?




--
View this message in context: 
http://xwiki.475771.n2.nabble.com/Debian-installation-failed-tp7600759.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users

Re: [xwiki-users] Special characters in titles

[Paul Libbrecht]

Wolfgang,

is there Apache in the loop?
Is it using ProxyPass or RewriteRule ?
I've been more successful if I used the nocanon rewrite-rule option in
these kind of attempts.

Paul

> wolfgang.theis...@online.de 
> 22 August 2016 at 13:09
> Hi,
>  
>  
> We have a problem with special characters like ÖÄÜ in page titles
> since some time.
>  
> I’ll try to explain our problem:
>  
> The browser address line is if you want to create a new page
> (Übeltäter is the title):
>  
> “…/xwiki/bin/edit/MBS/MBS-Members/MKL/Übeltäter/WebHome?template=&parent=MBS.MBS-Members.MKL.WebHome&title=Übeltäter”
>  
> This results in a document with the following title: �beltäter (the
> browser shows a more weired title...)
>  
> The xwiki address of the document is still correct:
>  
> “…/xwiki/bin/view/MBS/MBS-Members/MKL/Übeltäter/”
>  
> if you now create a document like this:
>  
> “…/xwiki/bin/view/MBS/MBS-Members/MKL/Übeltäter/Übung/” (which gets
> the title: Ã?bung)
>  
> The document is not shown as a child of the above but you can show the
> document if you enter the address in the browser directly and you are
> also able to find  it via search..
>  
> No other problems so far when using these characters within the documents.
> We didn’t had this problems in beginning. I had checked a backup of
> the system which is a few months old (Version 7.4.2) – no problems here
>  
> We are running Xwiki Version 7.4.4., OS is Ubuntu Linux 14.04.5 LTS,
> with UTF-8 support..
> The Xwiki parameters have not been changed between the backup and the
> current system except for installation of the JIRA API and patches for
> the OS. .
>  
> I hope I was able to explain our problem precisely enough.
>  
> Any help is appreciated
>  
> Regards, Wolfgang
>  
>
> ___
> 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] Special characters in titles

[Vincent Massol]

Hi Wolfgang,

> On 22 Aug 2016, at 13:09, wolfgang.theis...@online.de wrote:
> 
> Hi,
>  
>  
> We have a problem with special characters like ÖÄÜ in page titles since some 
> time.
>  
> I’ll try to explain our problem:
>  
> The browser address line is if you want to create a new page (Übeltäter is 
> the title):
>  
> “…/xwiki/bin/edit/MBS/MBS-Members/MKL/Übeltäter/WebHome?template=&parent=MBS.MBS-Members.MKL.WebHome&title=Übeltäter”
>  
> This results in a document with the following title: �beltäter (the browser 
> shows a more weired title...)
>  
> The xwiki address of the document is still correct: 
>  
> “…/xwiki/bin/view/MBS/MBS-Members/MKL/Übeltäter/”
>  
> if you now create a document like this:
>  
> “…/xwiki/bin/view/MBS/MBS-Members/MKL/Übeltäter/Übung/” (which gets the 
> title: Ã?bung)
>  
> The document is not shown as a child of the above but you can show the 
> document if you enter the address in the browser directly and you are also 
> able to find  it via search..
>  
> No other problems so far when using these characters within the documents.
> We didn’t had this problems in beginning. I had checked a backup of the 
> system which is a few months old (Version 7.4.2) – no problems here 
>  
> We are running Xwiki Version 7.4.4., OS is Ubuntu Linux 14.04.5 LTS, with 
> UTF-8 support.. 
> The Xwiki parameters have not been changed between the backup and the current 
> system except for installation of the JIRA API and patches for the OS. .
>  
> I hope I was able to explain our problem precisely enough.
>  
> Any help is appreciated

Could you make sure that you have all encodings configured correctly, see:
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Encoding

Thanks
-Vincent

>  
> Regards, Wolfgang
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users

[xwiki-users] Special characters in titles

[wolfgang.theissen]

Hi,
 
 
We have a problem with special characters like ÖÄÜ in page titles since some 
time.
 
I’ll try to explain our problem:
 
The browser address line is if you want to create a new page (Übeltäter is the 
title):
 
“…/xwiki/bin/edit/MBS/MBS-Members/MKL/Übeltäter/WebHome?template=&parent=MBS.MBS-Members.MKL.WebHome&title=Übeltäter”
 
This results in a document with the following title: �beltäter (the browser 
shows a more weired title...)
 
The xwiki address of the document is still correct: 
 
“…/xwiki/bin/view/MBS/MBS-Members/MKL/Übeltäter/”
 
if you now create a document like this:
 
“…/xwiki/bin/view/MBS/MBS-Members/MKL/Übeltäter/Übung/” (which gets the title: 
Ã?bung)
 
The document is not shown as a child of the above but you can show the document 
if you enter the address in the browser directly and you are also able to find  
it via search..
 
No other problems so far when using these characters within the documents.
We didn’t had this problems in beginning. I had checked a backup of the system 
which is a few months old (Version 7.4.2) – no problems here 
 
We are running Xwiki Version 7.4.4., OS is Ubuntu Linux 14.04.5 LTS, with UTF-8 
support.. 
The Xwiki parameters have not been changed between the backup and the current 
system except for installation of the JIRA API and patches for the OS. .
 
I hope I was able to explain our problem precisely enough.
 
Any help is appreciated
 
Regards, Wolfgang
 

___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users

Re: [xwiki-users] Diagnosing empty start page

[Vincent Massol]

Hi Bryn,

> On 22 Aug 2016, at 12:37, Bryn Jeffries  wrote:
> 
> Hi,
> 
> It's been a while since I've installed XWiki from scratch, and last time it 
> was for Ubuntu 14 with 7.1.1. It looks like enough things have changed since 
> then that I'm doing something wrong. I'd appreciate any help in diagnosing 
> the problem.
> 
> This time I'm using Ubuntu 16.04.1 and Tomcat 8. I'm installing from the 
> debian/Ubuntu xwiki-enterprise-tomcat8-pgsql package version 8.2.1, with 
> Tomcat8 package 8.0.32-1ubuntu1.1. It's running (as before) via an AJP 
> connector behind Apache2.
> 
> https://mysite/xwiki correctly redirects to 
> https://mysite/xwiki/bin/view/Main/ so it looks like something is happening, 
> but I'm getting an empty page. The following are the Catalina log entries 
> (please excuse the length) from restarting tomcat onwards. My experience has 
> been that one always gets some warnings, but my guess is that one or more of 
> the following are resulting in pages failing to load.
> 
> 22-Aug-2016 10:11:46.465 INFO [Thread-11] 
> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler 
> ["ajp-nio-8009"]
> 22-Aug-2016 10:11:46.471 INFO [Thread-11] 
> org.apache.catalina.core.StandardService.stopInternal Stopping service 
> Catalina
> 22-Aug-2016 10:11:46.536 SEVERE [Catalina-startStop-2] 
> org.apache.catalina.core.ContainerBase.stopInternal A child container failed 
> during stop
> java.util.concurrent.ExecutionException: 
> org.apache.catalina.LifecycleException: Failed to stop component 

[snip]

You should try to stop tomcat fully and start it again. It seems you’re only 
stopping the webapp and there are issues with xwiki cleanup when doing so.

Let us know if there are still errors.

Thanks
-Vincent

> 
> Visiting the page in my browser then gets a blank page, and there are no 
> further entries in the log. Can anyone advise what might be the next step in 
> resolving things?
> 
> Thanks,
> 
> Bryn
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users

[xwiki-users] Diagnosing empty start page

[Bryn Jeffries]

Hi,

It's been a while since I've installed XWiki from scratch, and last time it was 
for Ubuntu 14 with 7.1.1. It looks like enough things have changed since then 
that I'm doing something wrong. I'd appreciate any help in diagnosing the 
problem.

This time I'm using Ubuntu 16.04.1 and Tomcat 8. I'm installing from the 
debian/Ubuntu xwiki-enterprise-tomcat8-pgsql package version 8.2.1, with 
Tomcat8 package 8.0.32-1ubuntu1.1. It's running (as before) via an AJP 
connector behind Apache2.

https://mysite/xwiki correctly redirects to https://mysite/xwiki/bin/view/Main/ 
so it looks like something is happening, but I'm getting an empty page. The 
following are the Catalina log entries (please excuse the length) from 
restarting tomcat onwards. My experience has been that one always gets some 
warnings, but my guess is that one or more of the following are resulting in 
pages failing to load.

22-Aug-2016 10:11:46.465 INFO [Thread-11] 
org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler 
["ajp-nio-8009"]
22-Aug-2016 10:11:46.471 INFO [Thread-11] 
org.apache.catalina.core.StandardService.stopInternal Stopping service Catalina
22-Aug-2016 10:11:46.536 SEVERE [Catalina-startStop-2] 
org.apache.catalina.core.ContainerBase.stopInternal A child container failed 
during stop
 java.util.concurrent.ExecutionException: 
org.apache.catalina.LifecycleException: Failed to stop component 
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]
at 
java.util.concurrent.FutureTask.report(java.base@9-internal/FutureTask.java:123)
at 
java.util.concurrent.FutureTask.get(java.base@9-internal/FutureTask.java:193)
at 
org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:972)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:224)
at 
org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1424)
at 
org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1413)
at 
java.util.concurrent.FutureTask.run(java.base@9-internal/FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@9-internal/ThreadPoolExecutor.java:1158)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@9-internal/ThreadPoolExecutor.java:632)
at java.lang.Thread.run(java.base@9-internal/Thread.java:804)
Caused by: org.apache.catalina.LifecycleException: Failed to stop component 
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:228)
... 6 more
Caused by: org.apache.catalina.LifecycleException: Failed to stop component 
[WebappLoader[]]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:228)
at 
org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5517)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:224)
... 6 more
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make member 
of class sun.rmi.transport.Target accessible:  module java.rmi does not export 
sun.rmi.transport to unnamed module @4abdb505
at 
sun.reflect.Reflection.throwInaccessibleObjectException(java.base@9-internal/Reflection.java:420)
at 
java.lang.reflect.AccessibleObject.checkCanSetAccessible(java.base@9-internal/AccessibleObject.java:174)
at 
java.lang.reflect.Field.checkCanSetAccessible(java.base@9-internal/Field.java:170)
at 
java.lang.reflect.Field.setAccessible(java.base@9-internal/Field.java:164)
at 
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesRmiTargets(WebappClassLoaderBase.java:2234)
at 
org.apache.catalina.loader.WebappClassLoaderBase.clearReferences(WebappClassLoaderBase.java:1553)
at 
org.apache.catalina.loader.WebappClassLoaderBase.stop(WebappClassLoaderBase.java:1496)
at 
org.apache.catalina.loader.WebappLoader.stopInternal(WebappLoader.java:446)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:224)
... 8 more
22-Aug-2016 10:12:07.202 WARNING [main] 
org.apache.catalina.startup.ClassLoaderFactory.validateFile Problem with 
directory [/usr/share/tomcat8/common/classes], exists: [false], isDirectory: 
[false], canRead: [false]
22-Aug-2016 10:12:07.262 WARNING [main] 
org.apache.catalina.startup.ClassLoaderFactory.validateFile Problem with 
directory [/usr/share/tomcat8/common], exists: [false], isDirectory: [false], 
canRead: [false]
22-Aug-2016 10:12:07.271 WARNING [main] 
org.apache.catalina.startup.ClassLoaderFactory.validateFile Problem with 
directory [/usr/share/tomcat8/server/classes], exists: [false], isDirectory: 
[false], canRead: [false]
22-Aug-2016 10:12:07.277 WARNING [main] 
org.apache.catalina.startup.ClassLoaderFactory.validateFile Problem with 
directory [/usr/share/tomcat8/server], exists: [false], isDirectory: [false], 
canRead: [false]
22-

Re: [xwiki-users] A problem with xwiki macros

[Vincent Massol]

Hi,

> On 19 Aug 2016, at 05:21, Edward Knyshov  wrote:
> 
> Hi. I'm trying to customize permissions in xwiki
> using ApplicationReadyEventListener.
> I override some permission in XWikiPreferences XWikiGlobalRights page to
> get page deletion work by default for all users.
> 
> https://gist.github.com/edvorg/4e2771ac02c4c64b705127964bc53c64
> 
> I set up permissions in these functions.
> 
> https://gist.github.com/edvorg/da7f8e64a46b7bbbf16f953e3fcc0e30

I’m curious to know why you need to write code to set permissions for all 
users? Why don’t you use the UI?

Thanks
-Vincent

> 
> This solutions works fine. But I got a problem with fresh xwiki bootstrap.
> Sometimes I get fully broken xwiki - all macros shows error. And I have
> something about admin user not having permission to edit some page:
> 
> https://gist.github.com/edvorg/1bdec91e5483307696bc68841d2cb1d8
> 
> I tried to debug all this code but it doesn't make much sense to me. I only
> found that this CacheChecker thing somehow affects the issue. Could someone
> point me to possible issues in my solution and maybe describe how this
> CacheChecker should be used? I would appreciate any help, as we can not get
> rid of xwiki integration bugs for a long time. Thank you!

___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users