[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] [error] encoded string too long

Please open a bug as Pascal suggests.  What configuration property are you
using to configure in the system packages?  There are two available:

org.osgi.framework.system.packages - This is intended to be filled in
automatically by the framework according the the VM class library the
framework is running on (e.g JavaSE 5 vs JavaSE 6).  I would not touch this
configuration property and just let the framework calculate it.

org.osgi.framework.system.packages.extra - This is intended to append
additional packages which your embedded environment may be providing to the
framework.  This is where I would recommend you place your extra packages.

Perhaps if you split your extra packages out to the
org.osgi.framework.system.packages.extra property it would make the string
small enough.  Another option is to install a system bundle fragment which
is just an empty fragment to the system.bundle, all it contains is a bundle
manifest that declares the extra packages the system bundle should export
in your embedded environment.

HTH

Tom




|------------>
| From:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Pascal Rapicault <pascal@xxxxxxxxxxxxx>                                                                                                           |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Equinox development mailing list <equinox-dev@xxxxxxxxxxx>,                                                                                       |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |04/05/2012 05:36 PM                                                                                                                               |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject:   |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Re: [equinox-dev] [error] encoded string too long                                                                                                 |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|





I would recommend opening a bug report with a real test case or a just a
some fake data exhibiting the problem. In this case we may be able to
produce a patch that you could apply back on this particular version of the
fwk.

HTH

Pascal

On 2012-04-05, at 6:32 PM, Raymond Auge wrote:

      Hello everyone,

      My name is Raymond Augé, I'm a senior architect at Liferay, Inc.

      We're bundling equinox (3.7.2.v20120110-1415) and recently I've
      started seeing the following error when the Framework tried to save
      it's state:

      18:04:28,630 INFO  [org_eclipse_osgi:84] FrameworkEvent STARTLEVEL
      CHANGED
      18:04:38,142 ERROR [org_eclipse_osgi:81]
      java.io.UTFDataFormatException: encoded string too long: 72142 bytes
      at java.io.DataOutputStream.writeUTF(DataOutputStream.java:364)
      at java.io.DataOutputStream.writeUTF(DataOutputStream.java:323)
      at org.eclipse.osgi.internal.resolver.StateWriter.writeStringOrNull
      (StateWriter.java:686)
      at org.eclipse.osgi.internal.resolver.StateWriter.writePlatformProp
      (StateWriter.java:181)
      at org.eclipse.osgi.internal.resolver.StateWriter.saveState
      (StateWriter.java:130)
      at
      org.eclipse.osgi.internal.resolver.StateObjectFactoryImpl.writeState
      (StateObjectFactoryImpl.java:439)
      at org.eclipse.osgi.internal.baseadaptor.StateManager.writeState
      (StateManager.java:178)
      at org.eclipse.osgi.internal.baseadaptor.StateManager.update
      (StateManager.java:116)
      at org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveStateData
      (BaseStorage.java:661)
      at org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveAllData
      (BaseStorage.java:458)
      at org.eclipse.osgi.internal.baseadaptor.BaseStorage$StateSaver.run
      (BaseStorage.java:1304)
      at java.lang.Thread.run(Thread.java:679)

      It appears to be due to a very large number of package exports on the
      system bundle (the Framework is embedded).

      Has anyone encountered this? I search bugs.eclipse.org/bugs with no
      results that seem to match.

      It appears I may have to create an Storage hook to get around the
      issue short term.

      Thoughts?

      Sincerely,
      --
      Raymond Augé  | Senior Software Architect | Liferay, Inc.


      ---


      25 Apr 2012 | Liferay Nordic Symposium | liferay.com/nordic2012  NEW!
      17 May 2012 | Liferay Budapest Symposium | liferay.com/budapest2012
      23 May 2012 | Liferay France Symposium | liferay.com/france2012



      _______________________________________________
      equinox-dev mailing list
      equinox-dev@xxxxxxxxxxx
      https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev