1 2 Previous Next 23 Replies Latest reply on Nov 25, 2010 4:15 AM by jaikiran Go to original post
      • 15. Re: Failed to resolve schema nsURI= location=JBoss
        jaikiran

        I meant the code in com.globalsight.cxe.adaptermdb.adobe.AdobeSourceAdapterMDB class Is that MDB annotated? Does it implement javax.jms.MessageListener?

        • 16. Re: Failed to resolve schema nsURI= location=JBoss
          ohmygod

          It does not directly implement the MessageListener but extends a class (BaseAdapterMDB) which implements the MessageListener.

           

          It is simple itself. Here is AdobeSourceAdapterMDB code.

           

          public class AdobeSourceAdapterMDB extends BaseAdapterMDB
          {
              private static String ADAPTER_NAME = "AdobeSourceAdapter";

              protected String getAdapterName()
              {
                  return ADAPTER_NAME;
              }

              protected BaseAdapter loadAdapter() throws Exception
              {
                  return new AdobeAdapter(ADAPTER_NAME);
              }
          }

           

          Head of BaseAdapterMDB:

          public abstract class BaseAdapterMDB
              implements MessageDrivenBean, MessageListener {

          ...

           

           

          If this is the problem, then my question is why other MDB classes do not have this problem. They also behave like AdobeSourceAdapterMDB. Don't tell me JBoss reads AdobeSourceAdapterMDB before others.. But others are written before AdobeSourceAdapterMDB in ejb-jar.xml and jboss.xml.

           

          And if annotation is needed, tell me how to do this. (I've never annotated such thing before)

           

          Looking forward.

          • 17. Re: Failed to resolve schema nsURI= location=JBoss
            jaikiran

            MDB with a base class and no explicit MessageListener in the implements clause is known to throw this exception (see this http://community.jboss.org/message/7464). You can either add that interface in the implements clause of the MDB or add the messaging-type element within the message-driven section of your ejb-jar.xml:

             

            <messaging-type>javax.jms.MessageListener</messaging-type>

            • 18. Re: Failed to resolve schema nsURI= location=JBoss
              ohmygod

              Thank you so much, jaikiran. I hope this is the last question.

               

              Is there a way to add this parameter below to ejb-jar.xml? Because I do not want to make changes to the MDB classes as there are too many of them.

              <subscription-durability>
                   Durable
                  </subscription-durability>

              • 19. Re: Failed to resolve schema nsURI= location=JBoss
                ohmygod

                I hope you are well. Now I got a bunch of errors which are almost saying:

                (one of them)

                10:01:48,011 WARN  [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.J
                msActivationSpec@75012d(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@1e03412 destination=que
                ue/com.globalsight.everest.jms.AddSourceFile destinationType=javax.jms.Queue tx=true durable=false s
                ubscription=AddSourceFileMDB reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1
                minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inf
                low.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
                javax.naming.NameNotFoundException: com.globalsight.everest.jms.AddSourceFile not bound
                        at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
                        at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
                        at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
                        at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
                        at org.jnp.server.NamingServer.lookup(NamingServer.java:399)
                        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)
                        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
                        at javax.naming.InitialContext.lookup(InitialContext.java:392)
                        at org.jboss.util.naming.Util.lookup(Util.java:222)
                        at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:4
                64)
                        at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352)
                        at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.jav
                a:729)
                        at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
                        at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
                        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
                        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                        at java.lang.Thread.run(Thread.java:619)

                 

                Piece of content in jboss.xml:

                <message-driven>
                   <ejb-name>AddSourceFileMDB</ejb-name><!--javax.jms.Queue-->
                   <destination-jndi-name>
                    queue/com.globalsight.everest.jms.AddSourceFile
                   </destination-jndi-name>
                   <mdb-subscription-id>AddSourceFileMDB</mdb-subscription-id>
                  </message-driven>

                 

                Piece of content in ejb-jar.xml:

                <message-driven>
                   <ejb-name>AddSourceFileMDB</ejb-name>
                   <ejb-class>com.globalsight.cxe.adaptermdb.filesystem.AddSourceFileMDB</ejb-class>
                   <messaging-type>javax.jms.MessageListener</messaging-type>
                   <transaction-type>Bean</transaction-type>
                   <message-destination-type>javax.jms.Queue</message-destination-type>
                  </message-driven>

                 

                Do you have any suggestions?

                • 20. Re: Failed to resolve schema nsURI= location=JBoss
                  jaikiran

                  How do you create and deploy this queue/com.globalsight.everest.jms.AddSourceFile queue?

                  • 21. Re: Failed to resolve schema nsURI= location=JBoss
                    ohmygod

                    I added the missing mdb in the xxx-JMS-service.xml in default\deploy folder and this problem resolved.

                    • 22. Re: Failed to resolve schema nsURI= location=JBoss
                      ohmygod

                      Hi jaikiran, I'm wondering if it is ok to post all the problems in one thread. Here is another error happening. It seems some jar files missing? Could you please suggest?

                       

                      16:42:04,703 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminCaptureRootCA
                      16:42:04,703 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminClients
                      16:42:04,703 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminConnections
                      16:42:04,718 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminEvents
                      16:42:04,718 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminJDBC
                      16:42:04,718 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminLicense
                      16:42:04,750 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminMain
                      16:42:04,765 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminProps
                      16:42:04,765 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminRealm
                      16:42:04,765 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminThreads
                      16:42:04,781 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminVersion
                      16:42:04,796 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: com.globalsight.everest.serv
                      let.L10nRequesterServlet
                      16:42:04,828 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: com.globalsight.dotNet.L10nS
                      erviceServlet
                      16:42:04,843 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: admin.AdminMain
                      16:42:04,921 WARN  [JAXWSDeployerHookPreJSE] Cannot load servlet class: xdeSpellApplet
                      16:42:05,156 INFO  [TomcatDeployment] deploy, ctxPath=/globalsight
                      16:42:05,671 ERROR [[/globalsight]] Error configuring application listener of class org.apache.axis.
                      transport.http.AxisHTTPSessionListener
                      java.lang.NoClassDefFoundError: org/apache/commons/discovery/tools/DiscoverSingleton
                              at org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java:45)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at org.apache.axis.components.logger.LogFactory.getLogFactory(LogFactory.java:41)
                              at org.apache.axis.components.logger.LogFactory.<clinit>(LogFactory.java:33)
                              at org.apache.axis.transport.http.AxisHTTPSessionListener.<clinit>(AxisHTTPSessionListener.j
                      ava:33)

                       

                      ...

                       

                      at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
                              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
                              at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(
                      AbstractProfileService.java:306)
                              at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootst
                      rap.java:271)
                              at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
                              at org.jboss.Main.boot(Main.java:221)
                              at org.jboss.Main$1.run(Main.java:556)
                              at java.lang.Thread.run(Thread.java:619)
                      Caused by: java.lang.ClassNotFoundException: org.apache.commons.discovery.tools.DiscoverSingleton fr
                      om BaseClassLoader@80d069{VFSClassLoaderPolicy@f2d004{name=vfsfile:/C:/tmp/GlobalSight_7.1/jboss/jbo
                      ss_server/server/default/deploy/globalsight.ear/ domain=ClassLoaderDomain@15a0316{name=org.w3c:loade
                      r=globalsight.ear parentPolicy=AFTER_BUT_JAVA_BEFORE parent=ClassLoaderDomain@4b82d2{DefaultDomain}}

                       

                       

                      I'm thinking the root cause is some jar files have confict with those in JBoss itself. But need further suggestions on how to get rid of this.

                      • 23. Re: Failed to resolve schema nsURI= location=JBoss
                        jaikiran

                        mike just wrote:

                         

                        Hi jaikiran, I'm wondering if it is ok to post all the problems in one thread.

                        New threads for different issues, please.

                        1 2 Previous Next