11 Replies Latest reply on Aug 26, 2010 7:06 PM by oconnor0

    JBossAS 5.1.0, OSGi integration, PAX and WAR issue

      I wish to deploy an OSGi-fied WAR under JBossAS 5.1.0 with OSGi. looking at documentation and examples this should be very easy: just add some attributes to the manifest, and so I did. My web application is a very simple one, just one "hello world" servlet and I builded my manifest like the one following:

       

      Manifest-Version: 1.0

      Bundle-ManifestVersion: 2

      Bundle-Name: example

      Bundle-Category: educational

      Bundle-Version: 1.0.0

      Bundle-Description: A very simple example

      Bundle-Vendor: Me

      Bundle-ContactAddress: N/A

      Blundle-Copyright: none

      Bundle-SymbolicName: edu.mine.example

      Bundle-ClassPath: .,WEB-INF/classes

      Webapp-Context: example

      Import-Package: org.osgi.service.http,org.ops4j.pax.web.service,javax.servlet,javax.servlet.http

       

      Deploying the WAR file I can see the installation and starting message notifications for my web application bundle but I'm not able to access my servlet (it should be mapped as "/hello" according to the web.xml file); I tried http://localhost:8090/example/hello, http://localhost:8090/hello, http://localhost:8090/edu.mine.example/hello but nothing else a 404 appeared... What's wrong? Maybe there is some kind of configuration matter?

       

      Thank you

        • 1. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue
          thomas.diesler
          Can you show me a log output that shows how you webapp bundle gets installed and started?
          • 2. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue

            The JBossAS console and server.log file just says:

             

            2010-01-26 13:38:29,778 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (HDScanner) Installed: edu.mine.example [17]
            2010-01-26 13:38:29,794 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (HDScanner) Started: edu.mine.example [17]

            • 3. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue
              thomas.diesler
              What jboss-osgi version is this? What framework? Is there really no more debug level logging?
              • 4. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue

                My configuration is JBoss 5.1.0.GA + JBoss OSGi 1.0.0 Beta5 with Apache Felix.

                To install it I simply downloaded the installation jar and followed all steps. Deploying a "standard" bundle, like ones in Apache Felix tutorials (a simple activator class and a service interface to export), everything seems to work. I've chenged the console log level to "DEBUG" and it didn't says nothing more. This is my first time with OSGi so I don't know any other way to increase the log verbosity or to check what's wrong; in you and search engines I trust

                Thank you for your patience.

                 

                --

                PS: Here is the full JBossAS console log:

                 

                2010-01-26 18:23:33,657 INFO  [org.jboss.web.WebService] (main) Using RMI server codebase: http://127.0.0.1:8083/
                2010-01-26 18:23:44,532 INFO  [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) JBoss Web Services - Stack Native Core
                2010-01-26 18:23:44,548 INFO  [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) 3.1.2.GA
                2010-01-26 18:23:45,470 INFO  [org.jboss.osgi.felix.FelixIntegration] (main) JBossOSGi Felix - 2.0.2
                2010-01-26 18:23:46,720 INFO  [org.jboss.osgi.spi.framework.FrameworkIntegrationBean] (main) Installed bundle [1]: osgi.cmpn
                2010-01-26 18:23:46,829 INFO  [org.jboss.osgi.spi.framework.FrameworkIntegrationBean] (main) Installed bundle [2]: org.apache.felix.log
                2010-01-26 18:23:47,063 INFO  [org.jboss.osgi.spi.framework.FrameworkIntegrationBean] (main) Installed bundle [3]: jboss-osgi-common
                2010-01-26 18:23:47,079 INFO  [org.jboss.osgi.spi.framework.FrameworkIntegrationBean] (main) Started bundle: org.apache.felix.log
                2010-01-26 18:23:47,329 INFO  [org.jboss.osgi.spi.framework.FrameworkIntegrationBean] (main) Started bundle: jboss-osgi-common
                2010-01-26 18:23:48,095 INFO  [org.jboss.dependency.plugins.AttributeCallbackItem] (main) Owner callback not implemented.
                2010-01-26 18:23:49,923 INFO  [org.jboss.logbridge.LogNotificationListener] (main) Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@d0f59e[ defaultDomain='jboss' ]
                2010-01-26 18:24:10,141 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: jboss-osgi-apache-xerces [4]
                2010-01-26 18:24:10,500 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: jboss-osgi-blueprint [5]
                2010-01-26 18:24:10,875 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: jboss-osgi-common-core [6]
                2010-01-26 18:24:11,188 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: jboss-osgi-husky [7]
                2010-01-26 18:24:11,516 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: jboss-osgi-jaxb [8]
                2010-01-26 18:24:11,672 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: jboss-osgi-jmx [9]
                2010-01-26 18:24:11,907 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: jboss-osgi-jndi [10]
                2010-01-26 18:24:12,360 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: jboss-osgi-reflect [11]
                2010-01-26 18:24:12,750 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: jboss-osgi-webconsole [12]
                2010-01-26 18:24:13,078 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: jboss-osgi-xml-binding [13]
                2010-01-26 18:24:13,282 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: org.apache.felix.configadmin [14]
                2010-01-26 18:24:13,453 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: org.apache.felix.metatype [15]
                2010-01-26 18:24:13,938 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: org.ops4j.pax.web.pax-web-jetty-bundle [16]
                2010-01-26 18:24:14,016 INFO  [org.jboss.osgi.deployer.BundleRealDeployer] (main) Installed: edu.mine.example [17]
                2010-01-26 18:24:24,656 INFO  [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered deployment AbstractVFSDeploymentContext@15403056{vfsfile:/C:/Programmi/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
                2010-01-26 18:24:24,656 INFO  [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered deployment AbstractVFSDeploymentContext@15403056{vfsfile:/C:/Programmi/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
                2010-01-26 18:24:24,656 INFO  [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered deployment AbstractVFSDeploymentContext@15403056{vfsfile:/C:/Programmi/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
                2010-01-26 18:24:24,656 INFO  [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (main) Encountered deployment AbstractVFSDeploymentContext@15403056{vfsfile:/C:/Programmi/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
                2010-01-26 18:24:29,156 INFO  [org.jboss.mx.remoting.service.JMXConnectorServerService] (main) JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
                2010-01-26 18:24:29,516 INFO  [org.jboss.mail.MailService] (main) Mail Service bound to java:/Mail
                2010-01-26 18:24:32,844 WARN  [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (main) WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
                2010-01-26 18:24:32,891 WARN  [org.jboss.annotation.factory.AnnotationCreator] (main) No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
                2010-01-26 18:24:33,031 WARN  [org.jboss.annotation.factory.AnnotationCreator] (main) No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
                2010-01-26 18:24:33,141 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
                2010-01-26 18:24:33,141 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Setting up property manager MBean and JMX layer
                2010-01-26 18:24:33,562 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Initializing recovery manager
                2010-01-26 18:24:33,812 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Recovery manager configured
                2010-01-26 18:24:33,812 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Binding TransactionManager JNDI Reference
                2010-01-26 18:24:33,859 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Starting transaction recovery manager
                2010-01-26 18:24:34,656 INFO  [org.apache.catalina.core.AprLifecycleListener] (main) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Programmi\Java\jdk1.6.0_18\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programmi\Intel\Wireless\Bin\;C:\Programmi\Microsoft SQL Server\90\Tools\binn\;C:\Programmi\Java\jdk1.6.0_18\bin;C:\Programmi\jboss-5.1.0.GA\bin
                2010-01-26 18:24:34,844 INFO  [org.apache.coyote.http11.Http11Protocol] (main) Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
                2010-01-26 18:24:34,859 INFO  [org.apache.coyote.ajp.AjpProtocol] (main) Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
                2010-01-26 18:24:34,906 INFO  [org.apache.catalina.core.StandardService] (main) Starting service jboss.web
                2010-01-26 18:24:34,922 INFO  [org.apache.catalina.core.StandardEngine] (main) Starting Servlet Engine: JBoss Web/2.1.3.GA
                2010-01-26 18:24:35,015 INFO  [org.apache.catalina.startup.Catalina] (main) Server startup in 153 ms
                2010-01-26 18:24:35,094 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/invoker
                2010-01-26 18:24:36,203 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/jbossws
                2010-01-26 18:24:36,297 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/web-console
                2010-01-26 18:24:37,203 INFO  [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfszip:/C:/Programmi/jboss-5.1.0.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
                2010-01-26 18:24:37,234 INFO  [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfszip:/C:/Programmi/jboss-5.1.0.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
                2010-01-26 18:24:37,281 INFO  [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfszip:/C:/Programmi/jboss-5.1.0.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
                2010-01-26 18:24:37,328 INFO  [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfszip:/C:/Programmi/jboss-5.1.0.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
                2010-01-26 18:24:37,359 INFO  [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfszip:/C:/Programmi/jboss-5.1.0.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
                2010-01-26 18:24:37,594 INFO  [org.quartz.simpl.SimpleThreadPool] (main) Job execution threads will use class loader of thread: main
                2010-01-26 18:24:37,640 INFO  [org.quartz.core.QuartzScheduler] (main) Quartz Scheduler v.1.5.2 created.
                2010-01-26 18:24:37,640 INFO  [org.quartz.simpl.RAMJobStore] (main) RAMJobStore initialized.
                2010-01-26 18:24:37,640 INFO  [org.quartz.impl.StdSchedulerFactory] (main) Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
                2010-01-26 18:24:37,656 INFO  [org.quartz.impl.StdSchedulerFactory] (main) Quartz scheduler version: 1.5.2
                2010-01-26 18:24:37,750 INFO  [org.quartz.core.QuartzScheduler] (main) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
                2010-01-26 18:24:38,640 INFO  [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (main) Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
                2010-01-26 18:24:39,437 INFO  [org.jboss.jms.server.ServerPeer] (main) JBoss Messaging 1.4.3.GA server [0] started
                2010-01-26 18:24:39,578 INFO  [org.jboss.jms.server.destination.QueueService] (main) Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                2010-01-26 18:24:39,640 INFO  [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                2010-01-26 18:24:39,640 INFO  [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) org.jboss.jms.server.connectionfactory.ConnectionFactory@531f75 started
                2010-01-26 18:24:39,656 INFO  [org.jboss.jms.server.destination.QueueService] (main) Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                2010-01-26 18:24:39,656 INFO  [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                2010-01-26 18:24:39,656 INFO  [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) org.jboss.jms.server.connectionfactory.ConnectionFactory@1b6c2e6 started
                2010-01-26 18:24:39,656 INFO  [org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper] (main) supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
                2010-01-26 18:24:39,672 INFO  [org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper] (main) supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancin
                2010-01-26 18:24:39,672 INFO  [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                2010-01-26 18:24:39,672 INFO  [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) org.jboss.jms.server.connectionfactory.ConnectionFactory@1c591f5 started
                2010-01-26 18:24:39,828 INFO  [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (main) Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
                2010-01-26 18:24:40,797 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: jboss-osgi-apache-xerces [4]
                2010-01-26 18:24:41,093 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: jboss-osgi-blueprint [5]
                2010-01-26 18:24:41,203 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: jboss-osgi-common-core [6]
                2010-01-26 18:24:41,578 WARN  [org.jboss.osgi.husky.runtime.osgi.JMXConnector] (main) Multiple MBeanServer instances: [org.jboss.mx.server.MBeanServerImpl@d0f59e[ defaultDomain='jboss' ], org.jboss.mx.server.MBeanServerImpl@a39620[ defaultDomain='null' ]]
                2010-01-26 18:24:41,578 INFO  [org.jboss.osgi.husky.runtime.osgi.JMXConnector] (main) JMXConnector registered: jboss.osgi.husky:service=jmx-connector
                2010-01-26 18:24:41,593 INFO  [org.jboss.osgi.husky.runtime.osgi.SocketConnector] (main) SocketConnector registered: {port=5401, host=127.0.0.1, transport=socket}
                2010-01-26 18:24:41,593 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: jboss-osgi-husky [7]
                2010-01-26 18:24:42,875 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: jboss-osgi-jaxb [8]
                2010-01-26 18:24:42,922 WARN  [org.jboss.osgi.jmx.internal.MBeanServerService] (main) Multiple MBeanServer instances: [org.jboss.mx.server.MBeanServerImpl@d0f59e[ defaultDomain='jboss' ], org.jboss.mx.server.MBeanServerImpl@a39620[ defaultDomain='null' ]]
                2010-01-26 18:24:42,968 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: jboss-osgi-jmx [9]
                2010-01-26 18:24:43,640 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: jboss-osgi-jndi [10]
                2010-01-26 18:24:44,140 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: jboss-osgi-reflect [11]
                2010-01-26 18:24:45,250 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: jboss-osgi-webconsole [12]
                2010-01-26 18:24:45,750 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: jboss-osgi-xml-binding [13]
                2010-01-26 18:24:45,828 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: org.apache.felix.configadmin [14]
                2010-01-26 18:24:45,906 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: org.apache.felix.metatype [15]
                2010-01-26 18:24:46,437 INFO  [org.ops4j.pax.web.service.internal.Activator] (main) Pax Web started
                2010-01-26 18:24:46,437 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: org.ops4j.pax.web.pax-web-jetty-bundle [16]
                2010-01-26 18:24:46,547 INFO  [org.ops4j.pax.web.service.jetty.internal.JettyServerImpl] (Configuration Updater) Pax Web available at [0.0.0.0]:[8090]
                2010-01-26 18:24:46,640 INFO  [org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl] (Thread-18) Binding bundle: [jboss-osgi-webconsole [12]] to http service
                2010-01-26 18:24:47,453 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main) Created KernelDeployment for: profileservice-secured.jar
                2010-01-26 18:24:47,468 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main) installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
                2010-01-26 18:24:47,468 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)   with dependencies:
                2010-01-26 18:24:47,468 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)   and demands:
                2010-01-26 18:24:47,484 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
                2010-01-26 18:24:47,484 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     jboss.ejb:service=EJBTimerService
                2010-01-26 18:24:47,484 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)   and supplies:
                2010-01-26 18:24:47,484 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     Class:org.jboss.profileservice.spi.ProfileService
                2010-01-26 18:24:47,484 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     jndi:SecureProfileService/remote
                2010-01-26 18:24:47,484 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     jndi:SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService
                2010-01-26 18:24:47,500 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main) Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3) to KernelDeployment of: profileservice-secured.jar
                2010-01-26 18:24:47,500 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main) installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
                2010-01-26 18:24:47,500 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)   with dependencies:
                2010-01-26 18:24:47,500 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)   and demands:
                2010-01-26 18:24:47,500 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     jboss.ejb:service=EJBTimerService
                2010-01-26 18:24:47,500 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)   and supplies:
                2010-01-26 18:24:47,500 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     jndi:SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager
                2010-01-26 18:24:47,500 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     Class:org.jboss.deployers.spi.management.deploy.DeploymentManager
                2010-01-26 18:24:47,500 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     jndi:SecureDeploymentManager/remote
                2010-01-26 18:24:47,500 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main) Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3) to KernelDeployment of: profileservice-secured.jar
                2010-01-26 18:24:47,515 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main) installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
                2010-01-26 18:24:47,515 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)   with dependencies:
                2010-01-26 18:24:47,515 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)   and demands:
                2010-01-26 18:24:47,515 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     jboss.ejb:service=EJBTimerService
                2010-01-26 18:24:47,531 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)   and supplies:
                2010-01-26 18:24:47,546 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
                2010-01-26 18:24:47,546 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     Class:org.jboss.deployers.spi.management.ManagementView
                2010-01-26 18:24:47,546 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main)     jndi:SecureManagementView/remote
                2010-01-26 18:24:47,546 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (main) Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3) to KernelDeployment of: profileservice-secured.jar
                2010-01-26 18:24:47,593 INFO  [org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy AbstractBeanMetaData@4e88e7{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
                2010-01-26 18:24:47,593 INFO  [org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy AbstractBeanMetaData@1eefa77{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
                2010-01-26 18:24:47,593 INFO  [org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer] (main) Deploy AbstractBeanMetaData@1301c58{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
                2010-01-26 18:24:47,968 INFO  [org.jboss.ejb3.session.SessionSpecContainer] (main) Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
                2010-01-26 18:24:48,000 INFO  [org.jboss.ejb3.EJBContainer] (main) STARTED EJB: org.jboss.profileservice.ejb.SecureDeploymentManager ejbName: SecureDeploymentManager
                2010-01-26 18:24:48,125 INFO  [org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase] (main) Binding the following Entries in Global JNDI:
                    SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface
                    SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface
                2010-01-26 18:24:48,359 INFO  [org.jboss.ejb3.session.SessionSpecContainer] (main) Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
                2010-01-26 18:24:48,359 INFO  [org.jboss.ejb3.EJBContainer] (main) STARTED EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName: SecureManagementView
                2010-01-26 18:24:48,375 INFO  [org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase] (main) Binding the following Entries in Global JNDI:
                    SecureManagementView/remote - EJB3.x Default Remote Business Interface
                    SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView - EJB3.x Remote Business Interface
                2010-01-26 18:24:48,578 INFO  [org.jboss.ejb3.session.SessionSpecContainer] (main) Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
                2010-01-26 18:24:48,578 INFO  [org.jboss.ejb3.EJBContainer] (main) STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService
                2010-01-26 18:24:48,593 INFO  [org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase] (main) Binding the following Entries in Global JNDI:
                    SecureProfileService/remote - EJB3.x Default Remote Business Interface
                    SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface
                2010-01-26 18:24:49,031 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/admin-console
                2010-01-26 18:24:49,578 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (main) Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console'
                2010-01-26 18:24:54,249 INFO  [org.jboss.osgi.deployer.BundleStartStopDeployer] (main) Started: edu.mine.example [17]
                2010-01-26 18:24:54,453 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/
                2010-01-26 18:24:54,671 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/jmx-console
                2010-01-26 18:24:54,906 INFO  [org.apache.coyote.http11.Http11Protocol] (main) Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
                2010-01-26 18:24:54,937 INFO  [org.apache.coyote.ajp.AjpProtocol] (main) Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
                2010-01-26 18:24:54,937 INFO  [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 1m:33s:61ms

                • 5. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue
                  thomas.diesler

                  Yes, this is a bug. Please apply the workaround that is described in the associated JIRA issue.

                   

                  https://jira.jboss.org/jira/browse/JBOSGI-283

                  • 6. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue

                    Thank you, it solved the problem and servlet works; I can not say the same for JSPs.

                    It seems that another jar is missing from distribution, the Pax Web Extender JSP, as the log message says:

                     

                    WARN  [RegisterWebAppVisitorWC] Jsp support is not enabled. Is org.ops4j.pax.web.jsp bundle installed?

                     

                    Obviously not! So I downloaded the latest version (0.7.1) of Pax Web Extender JSP and successfully deployed it:

                     

                    INFO  [BundleStartStopDeployer] Started: org.ops4j.pax.web.pax-web-extender-war [16]
                    INFO  [Activator] Pax Web started
                    INFO  [BundleStartStopDeployer] Started: org.ops4j.pax.web.pax-web-jetty-bundle [17]
                    INFO  [JettyServerImpl] Pax Web available at [0.0.0.0]:[8090]
                    INFO  [HttpServiceFactoryImpl] Binding bundle: [jboss-osgi-webconsole [12]] to http service
                    INFO  [BundleStartStopDeployer] Started: org.ops4j.pax.web.pax-web-jsp [18]

                     

                    But it doesn't seems to work because I always get the same WARN message above... suggestions?

                    • 7. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue
                      Ok, JBoss OSGi seems to use the 0.7.2 snapshot of Pax Web Components, I will try to build it by maven and then use it...
                      • 8. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue

                        Done... everythings works fine by now.

                        Thank you

                        • 9. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue
                          thomas.diesler
                          • 10. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue
                            bmcardoso

                            Gaetano,

                             

                            Where did you get the jar ?

                             

                            I tried several versions from here: http://repository.ops4j.org/mvn-snapshots/org/ops4j/pax/web/pax-web-jsp/0.7.2-SNAPSHOT/

                             

                            but none of them worked for me.

                            • 11. Re: JBossAS 5.1.0, OSGi integration, PAX and WAR issue
                              oconnor0

                              Has there been discussion of applying that workaround for JBossAS 6? I downloaded JBossAS 6M4 today & the Pax Web Extender wasn't anywhere in the distribution.