Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [glassfish-dev] Question about Jakarta EE 6 Build
Now revoke the local Grizzly but now grizzly packages tries to find javax.servlet and they are not founding this.

Caused by: org.osgi.framework.BundleException: Unable to resolve org.glassfish.main.grizzly.glassfish-grizzly-extra-all [99](R 99.0): missing requirement [org.glassfish.main.grizzly.glassfish-grizzly-extra-all [99](R 99.0)] osgi.wiring.package; (osgi.wiring.package=javax.servlet) Unresolved requirements: [[org.glassfish.main.grizzly.glassfish-grizzly-extra-all [99](R 99.0)] osgi.wiring.package; (osgi.wiring.package=javax.servlet)]

On Mon, May 25, 2020 at 8:58 PM Gurkan Erdogdu <cgurkanerdogdu@xxxxxxxxx> wrote:
Hi Arjan
Thanks for the pointer.
Actually I tried to use the latest local Grizzly built instead of using 2.x. I think this was the problem.
Where is the location of JAR files' OSGI export definitions?
Regards.
Gurkan

On Mon, May 25, 2020 at 8:23 PM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
Hi,

The org.glassfish.main.web.naming bundle can't find the package org.glassfish.grizzly.utils with a version lower than 3.0.0. 

The exception becomes a little more descriptive when you enable OSGi debug, by setting felix.log.level to 4 in glassfish/config/osgi.properties.

# log level 1: error, 2: warning, 3: info, 4: debug
felix.log.level=1

In this case, the package is likely exported, but in the wrong version. So that typically means updating the bundle that imports the package. Here the bundle is "276", which you can lookup in glassfish/domains/domain1/osgi-cache/felix/bubdle276.

Kind regards,
Arjan




On Mon, May 25, 2020 at 6:45 PM Gurkan Erdogdu <cgurkanerdogdu@xxxxxxxxx> wrote:
This is the exception I debug:

org.osgi.framework.BundleException: Unable to resolve org.glassfish.main.webservices.connector [276](R 276.0): missing requirement [org.glassfish.main.webservices.connector [276](R 276.0)] osgi.wiring.package; (&(osgi.wiring.package=org.glassfish.web.deployment.descriptor)(version>=6.0.0)(!(version>=7.0.0))) [caused by: Unable to resolve org.glassfish.main.web.glue [269](R 269.0): missing requirement [org.glassfish.main.web.glue [269](R 269.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.catalina)(version>=6.0.0)(!(version>=7.0.0))) [caused by: Unable to resolve org.glassfish.main.web.core [267](R 267.0): missing requirement [org.glassfish.main.web.core [267](R 267.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.naming.factory)(version>=6.0.0)(!(version>=7.0.0))) [caused by: Unable to resolve org.glassfish.main.web.naming [272](R 272.0): missing requirement [org.glassfish.main.web.naming [272](R 272.0)] osgi.wiring.package; (&(osgi.wiring.package=org.glassfish.grizzly.utils)(version>=2.4.0)(!(version>=3.0.0)))]]] Unresolved requirements: [[org.glassfish.main.webservices.connector [276](R 276.0)] osgi.wiring.package; (&(osgi.wiring.package=org.glassfish.web.deployment.descriptor)(version>=6.0.0)(!(version>=7.0.0)))]

in OSGIModuleImpl#startBundle

On Mon, May 25, 2020 at 5:12 PM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
P.s.

When debugging OSGi failures, org.apache.felix.framework.BundleWiringImpl.BundleClassLoader.loadClass(String, boolean) is a good place to put an initial break point.




On Mon, May 25, 2020 at 3:23 PM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
Hi,

The best course of action at this point is to watch the various PRs, which are each waiting on their own blockers upstream. To fix the OSGi errors, look at what the error message says, or in case the error is swallowed, add break points in the class loader (the API class loader specifically) to see what error Felix is throwing. 

Then try to solve that error locally, and do PRs to the associated projects and to the GlassFish project.

But again, do watch the existing PRs, as there's an amount of work already done but just waiting to be merged.

Kind regards,
Arjan Tijms



On Mon, May 25, 2020 at 2:52 PM Gurkan Erdogdu <cgurkanerdogdu@xxxxxxxxx> wrote:

Hi folks
After building the master, Glassfish instance is not started. As I see from previous messages, it is related with OSGI modules. Is there any way to start the instance? Any hint, pointer?

In the meantime, do we have any IRC channel? I looked into Slack channel but seems that it is not actively used.

Regards.
Gurkan
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev


--
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev


--


--
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com

Back to the top