[ 
https://issues.apache.org/jira/browse/FELIX-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845222#action_12845222
 ] 

Felix Meschberger commented on FELIX-2184:
------------------------------------------

Looking at the attached org_apache_felix_cm_impl_DynamicBindings.config file it 
looks like there are a number of illegal keys in it:

   ...
   File Log 
Appender="file:/home/martin/gofer/cluster/node1/bundles/gofer-logging.jar"

   SMTP Log 
Appender="file:/home/martin/gofer/cluster/node1/bundles/gofer-logging.jar"

   ...
   Socket Log 
Appender="file:/home/martin/gofer/cluster/node1/bundles/gofer-logging.jar"

   Telnet Log 
Appender="file:/home/martin/gofer/cluster/node1/bundles/gofer-logging.jar"

   Jabber 
Service="file:/home/martin/gofer/cluster/node1/bundles/gofer-jabber.jar"

   ...
   Socket Hub Log 
Appender="file:/home/martin/gofer/cluster/node1/bundles/gofer-logging.jar"

   ...
   Syslog Log 
Appender="file:/home/martin/gofer/cluster/node1/bundles/gofer-logging.jar"

   ...
   NT Event Log 
Appender="file:/home/martin/gofer/cluster/node1/bundles/gofer-logging.jar"

   ...


These properties are illegal since according to the spec a property name must 
not contain blanks:

    property-name ::= public | private
    public ::= symbolic-name // See 1.3.2
    private ::= '.' symbolic-name

Apache Felix Configuration Admin 2.0.4 does not allow you to set such 
properties.

Has this .config file been prepared manually ? [ It looks so, because there are 
a few properies missing, which are written by the Felix Configuration Admin 
implementation ]

> PID with space causes ERROR log, but otherwise works
> ----------------------------------------------------
>
>                 Key: FELIX-2184
>                 URL: https://issues.apache.org/jira/browse/FELIX-2184
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin
>    Affects Versions:  configadmin-1.2.4
>         Environment: Linux bono 2.6.32-16-generic #24-Ubuntu SMP Sat Mar 6 
> 12:33:21 UTC 2010 i686 GNU/Linux
> java version "1.6.0_18"
> Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
> Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode, sharing)
>            Reporter: Martin Zdila
>            Assignee: Felix Meschberger
>         Attachments: org_apache_felix_cm_impl_DynamicBindings.config
>
>
> Reading the specification I am not sure what characters are really allowed 
> for PIDs. We are using PIDs with spaces. All works fine, just the exception 
> is logged upon startup. I will attach the 
> org_apache_felix_cm_impl_DynamicBindings.config file that causes the parsing 
> error.
> *ERROR* Failure setting up dynamic configuration bindings
> java.io.IOException: Unexpected token 78; expected: 61 (line=2, pos=10)
>       at 
> org.apache.felix.cm.file.ConfigurationHandler.readFailure(ConfigurationHandler.java:652)
>       at 
> org.apache.felix.cm.file.ConfigurationHandler.readInternal(ConfigurationHandler.java:273)
>       at 
> org.apache.felix.cm.file.ConfigurationHandler.read(ConfigurationHandler.java:236)
>       at 
> org.apache.felix.cm.file.FilePersistenceManager._load(FilePersistenceManager.java:542)
>       at 
> org.apache.felix.cm.file.FilePersistenceManager.load(FilePersistenceManager.java:487)
>       at 
> org.apache.felix.cm.impl.DynamicBindings.<init>(DynamicBindings.java:51)
>       at 
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:211)
>       at 
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:661)
>       at org.apache.felix.framework.Felix.activateBundle(Felix.java:1756)
>       at org.apache.felix.framework.Felix.startBundle(Felix.java:1678)
>       at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1124)
>       at 
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
>       at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to