6 Replies Latest reply on Nov 18, 2004 12:00 AM by letiemble

    JSP compiler and custom TAGs

    andrzejros
    andrzejros Oct 28, 2004 4:18 PM

      Hi!

      Is there any workaround for JSP compiler to use my tag-handler class?
      project structure :
      bin/
      src/
      EAR/
      META-INF/application.xml
      EJB/
      META-INF/ejb-jar.xml
      /rest of files
      WEB/
      WEB-INF/web.xml
      /rest of files
      mypage.jsp

      error is pointed only in pages that are using my TAG with:
      Unable to load tag handler class "web.tag.ShopsTag" for tag "my:myTag"

      are there any solutions for this?

      • 19048 Views
      • Tags:
        • 1. Re: JSP compiler and custom TAGs
          letiemble Oct 29, 2004 6:58 AM (in response to andrzejros)

          Hi,

          The Taglib detection is done through :
          - the analysis of the web.xml file
          - the analysis of jar libraries declared in the project class-path (TLD can be embedded in jar files).

          So, if you want your taglibs to be recognized, you should put your WEB-INF folder in the JSP Folder.

          Laurent.

            • Actions
          • 2. Re: JSP compiler and custom TAGs
            andrzejros
            andrzejros Oct 29, 2004 9:07 AM (in response to andrzejros)

             

            "letiemble" wrote:
            Hi,

            The Taglib detection is done through :
            - the analysis of the web.xml file
            - the analysis of jar libraries declared in the project class-path (TLD can be embedded in jar files).

            So, if you want your taglibs to be recognized, you should put your WEB-INF folder in the JSP Folder.

            Laurent.

            so i have did it this way - WEB/jsps WEB/WEB-INF/, but compiler still can't locate class from bin/ directory, do I have to put my 'bin' classes into web-inf/classes instead of project's bin?

              • Actions
            • 3. Re: JSP compiler and custom TAGs
              rjurkiewicz
              rjurkiewicz Nov 2, 2004 8:35 AM (in response to andrzejros)

              I have the same issue.

              Tried to add jar files to libraries defined in the plugin.xml. It did not help.

              Any ideas how to solve it?

              Thanks,
              Robert

                • Actions
              • 4. Re: JSP compiler and custom TAGs
                pgatt Nov 11, 2004 10:37 PM (in response to andrzejros)

                I'm having the same issue, as well as being unable to get auto-complete to work. Might as well bump this thread up.

                Is auto-complete for custom taglibs even a feature of the IDE?

                  • Actions
                • 5. Re: JSP compiler and custom TAGs
                  pgatt Nov 12, 2004 1:46 AM (in response to andrzejros)

                  Forget that last comment about auto-complete. It all started working when I set the project up to compile JSPs.

                  This brings up another issue though. I was building a EAR with several different webroots. Each webroot represents a different domain. JbossIDE seems to only allow one web-root per project.

                  Anyone got any ideas?

                    • Actions
                  • 6. Delays observed servicing connection requests from pool with
                    letiemble Nov 18, 2004 12:00 AM (in response to andrzejros)

                    Does anyone have any ideas why there appears to be a delay when getting connections from the connection pool in the logs below (it seems to happen at busy times throughout the day)?
                    The pool size is believed to be sufficient to service the maximium load on the system.

                    Any help appreciated.

                    Thanks


                    Normal logging ..... extracted from server-jboss.log on 21/09/04.

                    2004-09-21 09:40:23,281 (PoolThread-23:user1:10.0.0.81) PUT
                    2004-09-21 09:40:23,281 (PoolThread-23:user1:10.0.0.81) RTN [InUse/Available/Max]: [7/45/45]
                    2004-09-21 09:40:23,281 (PoolThread-23:user1:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@ca2f5c
                    2004-09-21 09:40:23,281 (PoolThread-23:user1:10.0.0.0) GET [InUse/Available/Max]: [8/45/45]
                    2004-09-21 09:40:23,359 (PoolThread-23::) PUT
                    2004-09-21 09:40:23,359 (PoolThread-23::) RTN [InUse/Available/Max]: [7/45/45]
                    2004-09-21 09:40:23,359 (PoolThread-23:user1:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@ca2f5c
                    2004-09-21 09:40:23,359 (PoolThread-23:user1:10.0.0.0) GET [InUse/Available/Max]: [8/45/45]
                    2004-09-21 09:40:23,374 (PoolThread-23::) PUT
                    2004-09-21 09:40:23,374 (PoolThread-23::) RTN [InUse/Available/Max]: [7/45/45]

                    Jboss normally logs a "supplying" and "GET" daignostic in quick succession in response to a
                    connection request (from single GetConnection call in the application) as can be seen above.
                    For no apparent reason, the log send out only "supplying" messages for the next 35 seconds.
                    The last log above reports that only 7 out of the possible 45 connections are in use.

                    2004-09-21 09:40:23,546 (PoolThread-40:user2:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@ca2f5c
                    2004-09-21 09:40:23,562 (PoolThread-27:user3:10.0.0.237) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@6fb951
                    2004-09-21 09:40:23,984 (PoolThread-0:user4:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@6d3b6a
                    2004-09-21 09:40:24,374 (PoolThread-22:user5:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@d9155b
                    2004-09-21 09:40:24,671 (PoolThread-32:user6:10.0.0.12) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@e733af
                    2004-09-21 09:40:24,796 (PoolThread-46:user7:10.0.0.205) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@f15e81
                    2004-09-21 09:40:24,796 (PoolThread-29:user8:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1457e63
                    2004-09-21 09:40:24,921 (PoolThread-18:user9:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1b88f01
                    2004-09-21 09:40:24,937 (PoolThread-41:user10:10.0.0.170) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@174db3b
                    2004-09-21 09:40:25,078 (PoolThread-19:user1:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@d01482
                    2004-09-21 09:40:25,124 (PoolThread-20:user3:10.0.0.237) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1473f52
                    2004-09-21 09:40:25,921 (PoolThread-45:user2:10.0.0.224) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1d7183d
                    2004-09-21 09:40:26,015 (PoolThread-39:user11:10.0.0.176) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@cbbd69
                    2004-09-21 09:40:26,109 (PoolThread-21:user12:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@6d9748
                    2004-09-21 09:40:26,140 (PoolThread-34:user13:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@d30a6e
                    2004-09-21 09:40:26,203 (PoolThread-48:user14:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@822d9f
                    2004-09-21 09:40:26,218 (PoolThread-35:user15:10.0.0.121) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@a8efca
                    2004-09-21 09:40:26,312 (PoolThread-37:user16:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@865c34
                    2004-09-21 09:40:26,593 (PoolThread-50:user17:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@db3c46
                    2004-09-21 09:40:27,281 (PoolThread-23:user1:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1a8720f
                    2004-09-21 09:40:28,390 (PoolThread-24:user18:10.0.0.234) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1d57ca9
                    2004-09-21 09:40:30,359 (PoolThread-43:user8:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@166fd33
                    2004-09-21 09:40:30,640 (PoolThread-3:user19:10.0.0.180) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@189c32f
                    2004-09-21 09:40:30,812 (PoolThread-2:user20:10.0.0.10) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@578e9e
                    2004-09-21 09:40:30,859 (PoolThread-44:user15:10.0.0.121) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@e30056
                    2004-09-21 09:40:31,609 (PoolThread-12:user21:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1258b5c
                    2004-09-21 09:40:32,828 (PoolThread-10:user22:10.0.0.78) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@b3b699
                    2004-09-21 09:40:33,031 (PoolThread-28:user1:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@582d3f
                    2004-09-21 09:40:33,328 (PoolThread-31:user16:125.193.50.100) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@a57266
                    2004-09-21 09:40:34,093 (PoolThread-30:user8:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@408c3a
                    2004-09-21 09:40:36,312 (PoolThread-36:user23:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@399990
                    2004-09-21 09:40:36,312 (PoolThread-9:user24:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@dbc8b9
                    2004-09-21 09:40:37,265 (PoolThread-51:user23:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1c52b32
                    2004-09-21 09:40:37,734 (PoolThread-7:user4:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1ca72a8
                    2004-09-21 09:40:37,796 (PoolThread-6:user25:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1d70843
                    2004-09-21 09:40:38,890 (PoolThread-15:user26:10.0.0.186) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@3667f0
                    2004-09-21 09:40:39,203 (PoolThread-17:user16:125.193.50.100) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@cb3b6b
                    2004-09-21 09:40:42,656 (PoolThread-14:user1:10.0.0.81) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@ade52c
                    2004-09-21 09:40:44,015 (PoolThread-52:user17:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@3f4fc
                    2004-09-21 09:40:44,468 (PoolThread-53:user27:10.0.0.123) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1b81c27
                    2004-09-21 09:40:49,187 (PoolThread-54:user21:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@a67ad3
                    2004-09-21 09:40:52,749 (PoolThread-11:user17:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@abc422
                    2004-09-21 09:41:00,515 (PoolThread-38:user26:10.0.0.186) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@a0d722
                    2004-09-21 09:41:01,406 (PoolThread-49:user28:10.0.0.0) supplying ManagedConnection from pool: org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1157f48

                    GET diagnostics corresponding to the "supplying" ones above start being logged next.
                    During the 'freeze' period (up to 35 seconds in this instance) users will have had no feedback
                    from the application as responses to their requests are not received.
                    Now that application has a lot of unserviced 'queued' requests, the pool subsequentlty
                    get exhausted (and a "No Managed Connections" error is ultimately reported in the application).

                    2004-09-21 09:41:02,546 (PoolThread-27:user3:10.0.0.237) GET [InUse/Available/Max]: [8/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-0:user4:10.0.0.0) GET [InUse/Available/Max]: [9/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-40:user2:10.0.0.0) GET [InUse/Available/Max]: [10/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-19:user1:10.0.0.0) GET [InUse/Available/Max]: [17/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-45:user2:10.0.0.224) GET [InUse/Available/Max]: [19/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-18:user9:10.0.0.0) GET [InUse/Available/Max]: [15/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-21:user12:10.0.0.0) GET [InUse/Available/Max]: [20/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-34:user13:10.0.0.0) GET [InUse/Available/Max]: [21/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-3:user19:10.0.0.180) GET [InUse/Available/Max]: [29/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-10:user22:10.0.0.78) GET [InUse/Available/Max]: [33/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-32:user6:10.0.0.12) GET [InUse/Available/Max]: [12/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-30:user8:10.0.0.0) GET [InUse/Available/Max]: [36/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-7:user4:10.0.0.0) GET [InUse/Available/Max]: [40/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-17:user16:125.193.50.100) GET [InUse/Available/Max]: [43/45/45]
                    2004-09-21 09:41:02,546 (PoolThread-9:user24:10.0.0.0) GET [InUse/Available/Max]: [38/45/45]

                      • Actions