You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "sapthagiri (JIRA)" <ji...@apache.org> on 2016/11/30 09:50:58 UTC

[jira] [Created] (SM-3173) upgrading servicemix from 5.1.4 to 6.1.2

sapthagiri created SM-3173:
------------------------------

             Summary: upgrading servicemix from 5.1.4 to 6.1.2
                 Key: SM-3173
                 URL: https://issues.apache.org/jira/browse/SM-3173
             Project: ServiceMix
          Issue Type: Bug
            Reporter: sapthagiri


Hi,

We are currently running application on  Apache service mix 5.1.4.
We want to upgrade to 6.1.2. We are facing some dependency issues.

Environment details

Windows 7/Linux
JDK 7.X

Stack traces

2016-11-30 15:07:22,656 | WARN  | mix-6.1.2/deploy | container                        | 143 - org.apache.aries.jpa.container - 1.0.2 | There are no providers available.
2016-11-30 15:07:22,656 | WARN  | mix-6.1.2/deploy | container                        | 143 - org.apache.aries.jpa.container - 1.0.2 | There are no providers available.
2016-11-30 15:07:22,657 | ERROR | mix-6.1.2/deploy | aries                            | 142 - org.apache.aries.jpa.blueprint.aries - 1.0.4 | No org.apache.aries.jpa.container.sync.Synchronization service registered.
2016-11-30 15:07:22,658 | ERROR | mix-6.1.2/deploy | aries                            | 142 - org.apache.aries.jpa.blueprint.aries - 1.0.4 | No org.apache.aries.jpa.container.sync.Synchronization service registered.
2016-11-30 15:07:22,660 | INFO  | mix-6.1.2/deploy | BlueprintContainerImpl           | 15 - org.apache.aries.blueprint.core - 1.6.1 | Bundle thor-company-persist-jpa-cm/3.18.2.SNAPSHOT is waiting for dependencies [(&(&(org.apache.aries.jpa.proxy.factory=true)(osgi.unit.name=company-jpa-cm))(objectClass=javax.persistence.EntityManagerFactory)), (&(&(org.apache.aries.jpa.proxy.factory=true)(osgi.unit.name=company-jpa-cm))(objectClass=javax.persistence.EntityManagerFactory))]


Please help us to resolve this issue.







--
This message was sent by Atlassian JIRA
(v6.3.4#6332)