Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-14676

[GSS](7.2.z) In EAP 7.x when you deploy a simple Jar file , EAP 7.x treats the jar as the EJB and starts the "ejb" cache container.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 7.1.0.GA
    • Clustering, EJB
    • None
    • Compatibility/Configuration, User Experience
    • +
    • Workaround Exists
    • Hide

      Remove remoting configuration from ejb3 subsystem. This configuration is what requires the "ejb" cache container to start.

      Show
      Remove remoting configuration from ejb3 subsystem. This configuration is what requires the "ejb" cache container to start.
    • Hide

      1> From management console deploy a JAR file (the Jar file is any simple jar and not an EJB jar)
      2> Check the console and we will see the ejb cache container getting activated for that container and the container joining the cluster.

      Show
      1> From management console deploy a JAR file (the Jar file is any simple jar and not an EJB jar) 2> Check the console and we will see the ejb cache container getting activated for that container and the container joining the cluster.

    Description

      Deployment(from management console) of a simple Jar file in EAP 7.1.x causes the ejb cache container to start , which should not be the case .

      From EAP 7.1.x onwards @clustered annotation has been depricated and EJB application is required to start clustering , but in contradiction to this even if we deploy ant jar file (let's say ojdbc6.jar ) the container treats it as an EJB application and starts the EJB cache container as seen in the logs below :

      ~~~~
      1,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000078: Starting JGroups channel ejb
      22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000078: Starting JGroups channel ejb
      22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000078: Starting JGroups channel ejb
      22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000078: Starting JGroups channel ejb
      22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia]
      22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia]
      22:14:21,676 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200]
      22:14:21,678 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200]
      ~~~~

      Attachments

        Issue Links

          Activity

            People

              chaowan@redhat.com Chao Wang
              rhn-support-plohia Pranab Lohia (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: