gmane.comp.cms.magnolia.devel

JIRA (on behalf of Tom Wespi | 16 Jul 11:36

[magnolia-dev] [JIRA] Created: (MAGNOLIA-2266) Activating a page throws an error

Activating a page throws an error
---------------------------------

                 Key: MAGNOLIA-2266
                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2266
             Project: Magnolia
          Issue Type: Bug
    Affects Versions: 3.6 RC1
         Environment: Mac OSX 10.5.4, magnolia 3.6-RC2
            Reporter: Tom Wespi
            Assignee: Gregory Joseph

Those steps directly after the installation, no restart.

Delete  /config/modules/adminInterface/commands/website to remove the workflow
Create a new page
Activate the page
No Activation Comment

After a restart activation is working

Transporter Transporter.java(transport:137) 16.07.2008 11:30:33  Simple exchange transport failed:
Error writing request body to server
java.io.IOException: Error writing request body to server
	at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:2265)
	at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:2248)
	at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1026)
	at org.apache.commons.io.IOUtils.copy(IOUtils.java:999)
	at info.magnolia.module.exchangesimple.Transporter.transport(Transporter.java:133)
	at info.magnolia.module.exchangetransactional.TransactionalSyndicator.activate(TransactionalSyndicator.java:278)

(Continue reading)

headers

JIRA (on behalf of Gregory Joseph | 16 Jul 12:57

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2266) Activating a page throws an error


    [
http://jira.magnolia.info/browse/MAGNOLIA-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139#action_17139
] 

Gregory Joseph commented on MAGNOLIA-2266:
------------------------------------------

- isn't this the same issue you reported yesterday ?
- is it any different if you leave the workflow commands in ? how is it behaving if you don't change the
commands ?
- you're saying "After a restart activation is working" : does that mean this exception only happens if you
try to activate a page after changing the commands config but before restarting and that all works as
expected after a restart ?
- could you put your stacktraces in attachments, would help readability ? :)
- this is happening with EE (info.magnolia.module.exchangetransactional) - please report in
appropriate project and/or mention it clearly in the report :)

> Activating a page throws an error
> ---------------------------------
>
>                 Key: MAGNOLIA-2266
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2266
>             Project: Magnolia
>          Issue Type: Bug
>    Affects Versions: 3.6 RC1
>         Environment: Mac OSX 10.5.4, magnolia 3.6-RC2
>            Reporter: Tom Wespi
>            Assignee: Gregory Joseph
>

(Continue reading)

headers

JIRA (on behalf of Gregory Joseph | 16 Jul 13:05

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-1959) Leopard (osx 10.5) issues


    [
http://jira.magnolia.info/browse/MAGNOLIA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140#action_17140
] 

Gregory Joseph commented on MAGNOLIA-1959:
------------------------------------------

{{/var/log/appfirewall.log}} is where issues with this could be logged.

> Leopard (osx 10.5) issues
> -------------------------
>
>                 Key: MAGNOLIA-1959
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1959
>             Project: Magnolia
>          Issue Type: Bug
>    Affects Versions: 3.5
>            Reporter: Gregory Joseph
>            Assignee: Gregory Joseph
>
> There seems to have been a couple of reports from people having trouble running Magnolia 3.5 rc4 (bundled
or with installer) on Leopard.
> Some tracks at the moment:
>  - there might be some ports/security settings which are different from Tiger(10.4), and Magnolia will
not run from the /Applications directory, while it will run perfectly from a user's home directory. (no
errors on startup, everything seems to be fine, but one can't access localhost:8080)
>  - there might be some "max.files opened" issues, with settings which are different from Tiger(10.4).
> When you encounter such issue, please try to tail /var/log/system.log while starting up, it might have
interesting hints.

(Continue reading)

headers

JIRA (on behalf of Philippe Marschall | 16 Jul 13:18

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-1876) Use JSP 2.0/2.1 instead of out-dated JSP 1.2 templates


    [
http://jira.magnolia.info/browse/MAGNOLIA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141#action_17141
] 

Philippe Marschall commented on MAGNOLIA-1876:
----------------------------------------------

J2EE 1.4 includes: [JSR 152|http://jcp.org/en/jsr/detail?id=152] (JSP 2.0)
[http://jcp.org/en/jsr/detail?id=151]

JEE 3 includes [JSR 245|http://jcp.org/en/jsr/detail?id=245] (JSP 2.1)
[http://jcp.org/en/jsr/detail?id=244]

JSP 2.0 requirest Tomcat 5.5. JSP 2.1 requires Tomcat 6.0:
[http://tomcat.apache.org/]

JSP 2.1 reqires servlet spec 2.5 AFAIK

> Use JSP 2.0/2.1 instead of out-dated JSP 1.2 templates
> ------------------------------------------------------
>
>                 Key: MAGNOLIA-1876
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1876
>             Project: Magnolia
>          Issue Type: Sub-task
>          Components: samples
>            Reporter: Vivian Steller
>            Assignee: Vivian Steller
>             Fix For: Green

(Continue reading)

headers

JIRA (on behalf of Philippe Marschall | 16 Jul 13:18

[magnolia-dev] [JIRA] Issue Comment Edited: (MAGNOLIA-1876) Use JSP 2.0/2.1 instead of out-dated JSP 1.2 templates


    [
http://jira.magnolia.info/browse/MAGNOLIA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141#action_17141
] 

pmm edited comment on MAGNOLIA-1876 at 7/16/08 1:19 PM:
-----------------------------------------------------------------------

J2EE 1.4 includes: [JSR 152|http://jcp.org/en/jsr/detail?id=152] (JSP 2.0)
[http://jcp.org/en/jsr/detail?id=151]

JEE 5 includes [JSR 245|http://jcp.org/en/jsr/detail?id=245] (JSP 2.1)
[http://jcp.org/en/jsr/detail?id=244]

JSP 2.0 requirest Tomcat 5.5. JSP 2.1 requires Tomcat 6.0:
[http://tomcat.apache.org/]

JSP 2.1 reqires servlet spec 2.5 AFAIK

      was (Author: pmm):
    J2EE 1.4 includes: [JSR 152|http://jcp.org/en/jsr/detail?id=152] (JSP 2.0)
[http://jcp.org/en/jsr/detail?id=151]

JEE 3 includes [JSR 245|http://jcp.org/en/jsr/detail?id=245] (JSP 2.1)
[http://jcp.org/en/jsr/detail?id=244]

JSP 2.0 requirest Tomcat 5.5. JSP 2.1 requires Tomcat 6.0:
[http://tomcat.apache.org/]

JSP 2.1 reqires servlet spec 2.5 AFAIK

(Continue reading)

headers

JIRA (on behalf of Gregory Joseph | 16 Jul 13:22

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-1959) Leopard (osx 10.5) issues


    [
http://jira.magnolia.info/browse/MAGNOLIA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142#action_17142
] 

Gregory Joseph commented on MAGNOLIA-1959:
------------------------------------------

My first comment in the issue description seems to be false - maybe this has changed since one of the point
releases of OSX10.5? - running under /Applications seems to work fine on my machine, while in my home it
doesn't, even with the firewall supposedly set to "allow all incoming connections"

> Leopard (osx 10.5) issues
> -------------------------
>
>                 Key: MAGNOLIA-1959
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1959
>             Project: Magnolia
>          Issue Type: Bug
>    Affects Versions: 3.5
>            Reporter: Gregory Joseph
>            Assignee: Gregory Joseph
>
> There seems to have been a couple of reports from people having trouble running Magnolia 3.5 rc4 (bundled
or with installer) on Leopard.
> Some tracks at the moment:
>  - there might be some ports/security settings which are different from Tiger(10.4), and Magnolia will
not run from the /Applications directory, while it will run perfectly from a user's home directory. (no
errors on startup, everything seems to be fine, but one can't access localhost:8080)
>  - there might be some "max.files opened" issues, with settings which are different from Tiger(10.4).

(Continue reading)

headers

JIRA (on behalf of Philippe Marschall | 16 Jul 13:31

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2152) QueryManager and JCR browser seem to have different view on repository


    [
http://jira.magnolia.info/browse/MAGNOLIA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143#action_17143
] 

Philippe Marschall commented on MAGNOLIA-2152:
----------------------------------------------

We use Oracle 9 and the bundle persistence manager.

h2.jackrabbit-oracle-search.xml
{code}
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Repository PUBLIC "-//The Apache Software Foundation//DTD Jackrabbit 1.2//EN" "http://jackrabbit.apache.org/dtd/repository-1.2.dtd">
<Repository>
  <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
    <param name="path" value="${rep.home}/repository" />
  </FileSystem>
  <Security appName="Jackrabbit">
    <AccessManager class="org.apache.jackrabbit.core.security.SimpleAccessManager"></AccessManager>
    <LoginModule class="org.apache.jackrabbit.core.security.SimpleLoginModule">
      <param name="anonymousId" value="anonymous" />
    </LoginModule>
  </Security>
  <Workspaces rootPath="${rep.home}/workspaces" defaultWorkspace="default" />
  <Workspace name="default">
    <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
      <param name="path" value="${wsp.home}/default" />
    </FileSystem>
    <PersistenceManager class="org.apache.jackrabbit.core.persistence.bundle.Oracle9PersistenceManager">

(Continue reading)

headers

JIRA (on behalf of Gregory Joseph | 16 Jul 13:35

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-1959) Leopard (osx 10.5) issues


    [
http://jira.magnolia.info/browse/MAGNOLIA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144#action_17144
] 

Gregory Joseph commented on MAGNOLIA-1959:
------------------------------------------

http://securosis.com/2007/11/01/investigating-the-leopard-firewall/

> Leopard (osx 10.5) issues
> -------------------------
>
>                 Key: MAGNOLIA-1959
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1959
>             Project: Magnolia
>          Issue Type: Bug
>    Affects Versions: 3.5
>            Reporter: Gregory Joseph
>            Assignee: Gregory Joseph
>
> There seems to have been a couple of reports from people having trouble running Magnolia 3.5 rc4 (bundled
or with installer) on Leopard.
> Some tracks at the moment:
>  - there might be some ports/security settings which are different from Tiger(10.4), and Magnolia will
not run from the /Applications directory, while it will run perfectly from a user's home directory. (no
errors on startup, everything seems to be fine, but one can't access localhost:8080)
>  - there might be some "max.files opened" issues, with settings which are different from Tiger(10.4).
> When you encounter such issue, please try to tail /var/log/system.log while starting up, it might have
interesting hints.

(Continue reading)

headers

JIRA (on behalf of Jan Haderka | 16 Jul 14:22

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2152) QueryManager and JCR browser seem to have different view on repository


    [
http://jira.magnolia.info/browse/MAGNOLIA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146#action_17146
] 

Jan Haderka commented on MAGNOLIA-2152:
---------------------------------------

{quote}
To bring them in synch again we have worked out the following procedure:

    * export the nodes
    * delete then nodes
    * restart the server
    * import the nodes

Simply exporting, deleting and then importing did not fix the issue.
{quote}
Seems to me like something kills the indexer. In your configuration
{code}
<param name="extractorPoolSize" value="3" />
<param name="extractorTimeout" value="100" />
<param name="extractorBackLogSize" value="100" />
{code}
you are using 3 indexers running on the background asynchronously. If the issue was simple failing to index
the data, you should see the exception in the logs. If the indexing slows down it will be cancelled after the
timeout (value is in miliseconds).
You could try two things at this point:
* increase the timeout, so the indexer has more time to index the content. It won't fix the issue, just
decrease probability of it to manifest itself.

(Continue reading)

headers

JIRA (on behalf of Jan Haderka | 16 Jul 14:52

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2152) QueryManager and JCR browser seem to have different view on repository


    [
http://jira.magnolia.info/browse/MAGNOLIA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148#action_17148
] 

Jan Haderka commented on MAGNOLIA-2152:
---------------------------------------

Actually if the timeout is the issue setting logging level to {{INFO}} for
{{org.apache.jackrabbit.core.query.lucene.TextExtractorJob}} should make dump messages about
timeouts to the log file.

> QueryManager and JCR browser seem to have different view on repository
> ----------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2152
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2152
>             Project: Magnolia
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.8
>            Reporter: Philippe Marschall
>            Assignee: Philipp Bracher
>
> We have a very strange issue with querying custom page attributes. We have a custom page dialog that sets
some custom page properties. These attributes are ad hoc and not defined in some sort of schema. We then
have observation code that queries the JCR for pages with these attributes and certain values. Our
queries look like this:
> {code}
> //element(*, mgnl:content) [@someLongAttribute and @someLongAttribute != 0]

(Continue reading)

headers

JIRA (on behalf of Philippe Marschall | 16 Jul 15:22

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2152) QueryManager and JCR browser seem to have different view on repository


    [
http://jira.magnolia.info/browse/MAGNOLIA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149#action_17149
] 

Philippe Marschall commented on MAGNOLIA-2152:
----------------------------------------------

Or log level for rg.apache.jackrabbit.core.query.lucene.TextExtractorJob was WARN :(
I'll adjust the log level and check the next time we observe the behavior. Thanks for all the prompt help.

> QueryManager and JCR browser seem to have different view on repository
> ----------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2152
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2152
>             Project: Magnolia
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.8
>            Reporter: Philippe Marschall
>            Assignee: Philipp Bracher
>
> We have a very strange issue with querying custom page attributes. We have a custom page dialog that sets
some custom page properties. These attributes are ad hoc and not defined in some sort of schema. We then
have observation code that queries the JCR for pages with these attributes and certain values. Our
queries look like this:
> {code}
> //element(*, mgnl:content) [@someLongAttribute and @someLongAttribute != 0]
> {code}

(Continue reading)

headers

JIRA (on behalf of Gregory Joseph | 16 Jul 16:26

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-1959) Leopard (osx 10.5) issues


    [
http://jira.magnolia.info/browse/MAGNOLIA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150#action_17150
] 

Gregory Joseph commented on MAGNOLIA-1959:
------------------------------------------

Still haven't found a reliable way of controlling this but
 sudo launchctl remove com.apple.alf
completely stops the "application-level firewall". This helps but is no good long term solution :D

And somehow, despite having the setting of the fw on "allow all", I had to remove the specific setting for
java binary for it to work at all.

> Leopard (osx 10.5) issues
> -------------------------
>
>                 Key: MAGNOLIA-1959
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1959
>             Project: Magnolia
>          Issue Type: Bug
>    Affects Versions: 3.5
>            Reporter: Gregory Joseph
>            Assignee: Gregory Joseph
>
> There seems to have been a couple of reports from people having trouble running Magnolia 3.5 rc4 (bundled
or with installer) on Leopard.
> Some tracks at the moment:
>  - there might be some ports/security settings which are different from Tiger(10.4), and Magnolia will

(Continue reading)