Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » [CDO] Package exception
[CDO] Package exception [message #1699057] Fri, 19 June 2015 22:10 Go to next message
Stephane  Fournier is currently offline Stephane FournierFriend
Messages: 299
Registered: July 2009
Senior Member
Hi,

I have to clients A & B in separated JVM connected to a CDO server.

Client A deals with a resource one.res in the server according to Company.ecore.

Client B also deals with the resource one.res in the server but also create and / deals with a resource other.res according to the OtherModel.ecore in the same repository.

Client A does not know about the OtherModel and the bundles of OtherModel.ecore are not deployed in the client A OSGi JVM due to the fact they are useless for client A JVM.

The issue I faced is a Package Exception on client A JVM when client B creates the other.res resource in the server complaining about an unknown package.

Is there a solution to fix that without deploying the OtherModel bundles in client A JVM ?

With this exception what are the impacts in client A JVM ? Will it corrupt the client A transaction ?

Thanks in advance,
Stéphane





Re: [CDO] Package exception [message #1699064 is a reply to message #1699057] Sat, 20 June 2015 05:21 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6446
Registered: July 2009
Senior Member
Hi Stephane,

Please show the the stack trace and tell us the version of CDO you're using? Is that a new effect?

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Re: [CDO] Package exception [message #1699067 is a reply to message #1699064] Sat, 20 June 2015 07:47 Go to previous messageGo to next message
Stephane  Fournier is currently offline Stephane FournierFriend
Messages: 299
Registered: July 2009
Senior Member
Hi Eike,
Thanks for you quick answer.

I'm using CDO shipped with Luna 4.4.1 (the one from last september) thus a CDO 4.3.1 version.

Il will providing you the exception on Monday.

Stéphane.
Re: [CDO] Package exception [message #1699185 is a reply to message #1699064] Mon, 22 June 2015 11:42 Go to previous messageGo to next message
Stephane  Fournier is currently offline Stephane FournierFriend
Messages: 299
Registered: July 2009
Senior Member
Hi Eike,

I'm a not sure it is a new effect ?
I'm still using CDO version 4.3.1 shipped with Luna Modeling SR1 distribution.


The exception :
[ERROR] Generated packages locally not available: CDOPackageUnit[id=http://bit/1.0.0, state=PROXY, type=UNKNOWN, originalType=NATIVE, timeStamp=2015-06-22 13:37:15.564]
[ERROR] Invalid signalID 0
org.eclipse.emf.cdo.common.util.CDOException: Generated packages locally not available: CDOPackageUnit[id=http://bit/1.0.0, state=PROXY, type=UNKNOWN, originalType=NATIVE, timeStamp=2015-06-22 13:37:15.564]
at org.eclipse.emf.internal.cdo.session.CDOSessionImpl.loadPackages(CDOSessionImpl.java:566)
at org.eclipse.emf.cdo.internal.common.model.CDOPackageUnitImpl.load(CDOPackageUnitImpl.java:239)
at org.eclipse.emf.cdo.internal.common.model.CDOPackageUnitImpl.load(CDOPackageUnitImpl.java:228)
at org.eclipse.emf.cdo.internal.common.model.CDOPackageInfoImpl.getEPackage(CDOPackageInfoImpl.java:116)
at org.eclipse.emf.cdo.internal.common.model.CDOPackageInfoImpl.getEPackage(CDOPackageInfoImpl.java:109)
at org.eclipse.emf.ecore.impl.EPackageRegistryImpl.getEPackage(EPackageRegistryImpl.java:127)
at org.eclipse.emf.cdo.common.model.CDOClassifierRef.resolve(CDOClassifierRef.java:113)
at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOClassifierRefAndResolve(CDODataInputImpl.java:170)
at org.eclipse.emf.cdo.spi.common.revision.BaseCDORevision.readSystemValues(BaseCDORevision.java:210)
at org.eclipse.emf.cdo.spi.common.revision.BaseCDORevision.read(BaseCDORevision.java:163)
at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDORevision(CDODataInputImpl.java:427)
at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDORevision(CDODataInputImpl.java:418)
at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOChangeSetData(CDODataInputImpl.java:212)
at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOCommitData(CDODataInputImpl.java:264)
at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOCommitInfo(CDODataInputImpl.java:279)
at org.eclipse.emf.cdo.common.protocol.CDOProtocol$CommitNotificationInfo.<init>(CDOProtocol.java:75)
at org.eclipse.emf.cdo.internal.net4j.protocol.CommitNotificationIndication.indicating(CommitNotificationIndication.java:36)
at org.eclipse.emf.cdo.internal.net4j.protocol.CDOClientIndication.indicating(CDOClientIndication.java:74)
at org.eclipse.net4j.signal.Indication.doExtendedInput(Indication.java:57)
at org.eclipse.net4j.signal.Signal.doInput(Signal.java:331)
at org.eclipse.net4j.signal.Indication.execute(Indication.java:51)
at org.eclipse.net4j.signal.Signal.runSync(Signal.java:256)
at org.eclipse.net4j.signal.Signal.run(Signal.java:149)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
java.lang.IllegalArgumentException: Invalid signalID 0
at org.eclipse.net4j.signal.SignalProtocol.provideSignalReactor(SignalProtocol.java:343)
at org.eclipse.net4j.signal.SignalProtocol.handleBuffer(SignalProtocol.java:211)
at org.eclipse.spi.net4j.Channel$ReceiverWork.run(Channel.java:366)
at org.eclipse.net4j.util.concurrent.QueueRunner.work(QueueRunner.java:26)
at org.eclipse.net4j.util.concurrent.QueueRunner.work(QueueRunner.java:1)
at org.eclipse.net4j.util.concurrent.QueueWorker.doWork(QueueWorker.java:78)
at org.eclipse.net4j.util.concurrent.QueueWorker.work(QueueWorker.java:70)
at org.eclipse.net4j.util.concurrent.Worker$WorkerThread.run(Worker.java:209)



Eike Stepper wrote on Sat, 20 June 2015 01:21
Hi Stephane,

Please show the the stack trace and tell us the version of CDO you're using? Is that a new effect?

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Re: [CDO] Package exception [message #1700086 is a reply to message #1699185] Tue, 30 June 2015 05:29 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6446
Registered: July 2009
Senior Member
Am 22.06.2015 um 13:42 schrieb Stephane Fournier:
> Hi Eike,
>
> I'm a not sure it is a new effect ? I'm still using CDO version 4.3.1 shipped with Luna Modeling SR1 distribution.
If this problem is new (for you) and you didn't update the CDO version, then you may have changed something in your
application. Or you execute new scenarios now. I'm trying to understand why that happens NOW.

>
>
> The exception :
> [ERROR] Generated packages locally not available: CDOPackageUnit[id=http://bit/1.0.0, state=PROXY, type=UNKNOWN,
> originalType=NATIVE, timeStamp=2015-06-22 13:37:15.564]
Is this package empty? Or doesn't it have at least one concrete EClass?

You can set CDOSession.Options.setGeneratedPackageEmulationEnabled(true) to allow the use of dynamic packages even in
cases where the original package was generated.

> [ERROR] Invalid signalID 0
What is this?
Are there other stack traces in the log (related to protocol version mismatches or so)?
What protocols are you using?

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper




> org.eclipse.emf.cdo.common.util.CDOException: Generated packages locally not available:
> CDOPackageUnit[id=http://bit/1.0.0, state=PROXY, type=UNKNOWN, originalType=NATIVE, timeStamp=2015-06-22 13:37:15.564]
> at org.eclipse.emf.internal.cdo.session.CDOSessionImpl.loadPackages(CDOSessionImpl.java:566)
> at org.eclipse.emf.cdo.internal.common.model.CDOPackageUnitImpl.load(CDOPackageUnitImpl.java:239)
> at org.eclipse.emf.cdo.internal.common.model.CDOPackageUnitImpl.load(CDOPackageUnitImpl.java:228)
> at org.eclipse.emf.cdo.internal.common.model.CDOPackageInfoImpl.getEPackage(CDOPackageInfoImpl.java:116)
> at org.eclipse.emf.cdo.internal.common.model.CDOPackageInfoImpl.getEPackage(CDOPackageInfoImpl.java:109)
> at org.eclipse.emf.ecore.impl.EPackageRegistryImpl.getEPackage(EPackageRegistryImpl.java:127)
> at org.eclipse.emf.cdo.common.model.CDOClassifierRef.resolve(CDOClassifierRef.java:113)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOClassifierRefAndResolve(CDODataInputImpl.java:170)
> at org.eclipse.emf.cdo.spi.common.revision.BaseCDORevision.readSystemValues(BaseCDORevision.java:210)
> at org.eclipse.emf.cdo.spi.common.revision.BaseCDORevision.read(BaseCDORevision.java:163)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDORevision(CDODataInputImpl.java:427)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDORevision(CDODataInputImpl.java:418)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOChangeSetData(CDODataInputImpl.java:212)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOCommitData(CDODataInputImpl.java:264)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOCommitInfo(CDODataInputImpl.java:279)
> at org.eclipse.emf.cdo.common.protocol.CDOProtocol$CommitNotificationInfo.<init>(CDOProtocol.java:75)
> at
> org.eclipse.emf.cdo.internal.net4j.protocol.CommitNotificationIndication.indicating(CommitNotificationIndication.java:36)
> at org.eclipse.emf.cdo.internal.net4j.protocol.CDOClientIndication.indicating(CDOClientIndication.java:74)
> at org.eclipse.net4j.signal.Indication.doExtendedInput(Indication.java:57)
> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:331)
> at org.eclipse.net4j.signal.Indication.execute(Indication.java:51)
> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:256)
> at org.eclipse.net4j.signal.Signal.run(Signal.java:149)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> java.lang.IllegalArgumentException: Invalid signalID 0
> at org.eclipse.net4j.signal.SignalProtocol.provideSignalReactor(SignalProtocol.java:343)
> at org.eclipse.net4j.signal.SignalProtocol.handleBuffer(SignalProtocol.java:211)
> at org.eclipse.spi.net4j.Channel$ReceiverWork.run(Channel.java:366)
> at org.eclipse.net4j.util.concurrent.QueueRunner.work(QueueRunner.java:26)
> at org.eclipse.net4j.util.concurrent.QueueRunner.work(QueueRunner.java:1)
> at org.eclipse.net4j.util.concurrent.QueueWorker.doWork(QueueWorker.java:78)
> at org.eclipse.net4j.util.concurrent.QueueWorker.work(QueueWorker.java:70)
> at org.eclipse.net4j.util.concurrent.Worker$WorkerThread.run(Worker.java:209)
>
>
>
> Eike Stepper wrote on Sat, 20 June 2015 01:21
>> Hi Stephane,
>>
>> Please show the the stack trace and tell us the version of CDO you're using? Is that a new effect?
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://www.esc-net.de
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>
>


Re: [CDO] Package exception [message #1700212 is a reply to message #1700086] Tue, 30 June 2015 20:02 Go to previous message
Stephane  Fournier is currently offline Stephane FournierFriend
Messages: 299
Registered: July 2009
Senior Member
Eike Stepper wrote on Tue, 30 June 2015 01:29
Am 22.06.2015 um 13:42 schrieb Stephane Fournier:
> Hi Eike,
>
> I'm a not sure it is a new effect ? I'm still using CDO version 4.3.1 shipped with Luna Modeling SR1 distribution.
If this problem is new (for you) and you didn't update the CDO version, then you may have changed something in your
application. Or you execute new scenarios now. I'm trying to understand why that happens NOW.

>
>
> The exception :
> [ERROR] Generated packages locally not available: CDOPackageUnit[id=http://bit/1.0.0, state=PROXY, type=UNKNOWN,
> originalType=NATIVE, timeStamp=2015-06-22 13:37:15.564]
Is this package empty? Or doesn't it have at least one concrete EClass?

I have multiple applications (each one has its own JVM) connected to same repository ( a mem store one).
I have 3 CDO resources in the repository.
One of the resource is using an EMF model that the other 2 resources do not know. No link between the 2 first resources and the 3rd one.
Thus, one application is connected to all resources and knows every EMF packages
==> no issue.

But another application named "AppFooBar" (for instance) has only to deal with 2 first CDO resources, no need to load the 3rd one.
==> The EMF plug-in for the EMF model that is not used by AppFooBar is not deployed at all in this Equinox app.

This is why I get this exception, if I deploy the bundle in the AppFooBar app without using it, I do not have the error. But deploying a useless EMF model bundle is a bit strange in a component-based application approach Smile

The CDO server is notifying my AppFooBar (as CDO client) about the 3rd resource creation with a content that this application is not supposed to deal with.
I never try to load this 3rd resource in the transaction of the AppFooBar app.

Is this use case managed by CDO ?


You can set CDOSession.Options.setGeneratedPackageEmulationEnabled(true) to allow the use of dynamic packages even in
cases where the original package was generated.

Ok I will test this setting.

> [ERROR] Invalid signalID 0
What is this?
Are there other stack traces in the log (related to protocol version mismatches or so)?
What protocols are you using?

I'am using TCP/IP protocol between clients and the MemStore CDO server. All CDO & EMF bundles are the ones from Luna Modeling SR1 (4.3.1)

Thanks for your help and your time to help me.



Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper




> org.eclipse.emf.cdo.common.util.CDOException: Generated packages locally not available:
> CDOPackageUnit[id=http://bit/1.0.0, state=PROXY, type=UNKNOWN, originalType=NATIVE, timeStamp=2015-06-22 13:37:15.564]
> at org.eclipse.emf.internal.cdo.session.CDOSessionImpl.loadPackages(CDOSessionImpl.java:566)
> at org.eclipse.emf.cdo.internal.common.model.CDOPackageUnitImpl.load(CDOPackageUnitImpl.java:239)
> at org.eclipse.emf.cdo.internal.common.model.CDOPackageUnitImpl.load(CDOPackageUnitImpl.java:228)
> at org.eclipse.emf.cdo.internal.common.model.CDOPackageInfoImpl.getEPackage(CDOPackageInfoImpl.java:116)
> at org.eclipse.emf.cdo.internal.common.model.CDOPackageInfoImpl.getEPackage(CDOPackageInfoImpl.java:109)
> at org.eclipse.emf.ecore.impl.EPackageRegistryImpl.getEPackage(EPackageRegistryImpl.java:127)
> at org.eclipse.emf.cdo.common.model.CDOClassifierRef.resolve(CDOClassifierRef.java:113)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOClassifierRefAndResolve(CDODataInputImpl.java:170)
> at org.eclipse.emf.cdo.spi.common.revision.BaseCDORevision.readSystemValues(BaseCDORevision.java:210)
> at org.eclipse.emf.cdo.spi.common.revision.BaseCDORevision.read(BaseCDORevision.java:163)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDORevision(CDODataInputImpl.java:427)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDORevision(CDODataInputImpl.java:418)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOChangeSetData(CDODataInputImpl.java:212)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOCommitData(CDODataInputImpl.java:264)
> at org.eclipse.emf.cdo.spi.common.protocol.CDODataInputImpl.readCDOCommitInfo(CDODataInputImpl.java:279)
> at org.eclipse.emf.cdo.common.protocol.CDOProtocol$CommitNotificationInfo.<init>(CDOProtocol.java:75)
> at
> org.eclipse.emf.cdo.internal.net4j.protocol.CommitNotificationIndication.indicating(CommitNotificationIndication.java:36)
> at org.eclipse.emf.cdo.internal.net4j.protocol.CDOClientIndication.indicating(CDOClientIndication.java:74)
> at org.eclipse.net4j.signal.Indication.doExtendedInput(Indication.java:57)
> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:331)
> at org.eclipse.net4j.signal.Indication.execute(Indication.java:51)
> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:256)
> at org.eclipse.net4j.signal.Signal.run(Signal.java:149)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> java.lang.IllegalArgumentException: Invalid signalID 0
> at org.eclipse.net4j.signal.SignalProtocol.provideSignalReactor(SignalProtocol.java:343)
> at org.eclipse.net4j.signal.SignalProtocol.handleBuffer(SignalProtocol.java:211)
> at org.eclipse.spi.net4j.Channel$ReceiverWork.run(Channel.java:366)
> at org.eclipse.net4j.util.concurrent.QueueRunner.work(QueueRunner.java:26)
> at org.eclipse.net4j.util.concurrent.QueueRunner.work(QueueRunner.java:1)
> at org.eclipse.net4j.util.concurrent.QueueWorker.doWork(QueueWorker.java:78)
> at org.eclipse.net4j.util.concurrent.QueueWorker.work(QueueWorker.java:70)
> at org.eclipse.net4j.util.concurrent.Worker$WorkerThread.run(Worker.java:209)
>
>
>
> Eike Stepper wrote on Sat, 20 June 2015 01:21
>> Hi Stephane,
>>
>> Please show the the stack trace and tell us the version of CDO you're using? Is that a new effect?
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://www.esc-net.de
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>
>
Previous Topic:[CDO] ERROR Generated packages locally not available
Next Topic:[CDO ] Web GUI
Goto Forum:
  


Current Time: Tue Oct 15 11:43:47 GMT 2019

Powered by FUDForum. Page generated in 0.01970 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top