[jboss-jira] [JBoss JIRA] (WFLY-10654) In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container.

[Chao Wang (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chao Wang moved JBEAP-14963 to WFLY-10654:
------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-10654  (was: JBEAP-14963)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Clustering
                       EJB
                           (was: Clustering)
                           (was: EJB)
    Affects Version/s: 13.0.0.Final
                           (was: 7.1.0.GA)


> In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container.
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-10654
>                 URL: https://issues.jboss.org/browse/WFLY-10654
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 13.0.0.Final
>            Reporter: Chao Wang
>            Assignee: Chao Wang
>
> 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]
> ~~~~



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)