[jboss-user] [EJB 3.0] - Re: @EJB injection after redeploy

2009-05-21 Thread jaikiran 
Are you sure this is happening? I haven't heard of similar caching issues. Is 
there any caching involved within your application for objects returned from 
lookup? 

Also, can you try this on JBossAS-5.1.0 CR1?

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232401#4232401

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232401
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [EJB 3.0] - Re: @EJB injection after redeploy

2009-05-20 Thread jaikiran 
vlotarev wrote : but fails after re-deployment (the first access to injected 
EJB)

How do you redeploy? Do those beans belong to the same application (jar)? Can 
you post the console logs from the point you do a redeploy? Do you access these 
beans from a standalone client?


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232141#4232141

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232141
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [EJB 3.0] - Re: @EJB injection after redeploy

2009-05-20 Thread jaikiran 
Which version of JBoss AS do you use?

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232142#4232142

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232142
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [EJB 3.0] - Re: @EJB injection after redeploy

2009-05-20 Thread vlotarev 
JBoss version is 4.2.3GA

I am making hot-deploy just copying corresponding EAR file in the server/deploy 
folder. Deployment itself went well except several warnings (I removed log 
entries related to entity beans deployment since as far as I guess the are out 
of interest).

INFO  [EARDeployer] Init J2EE application: 
file:/C:/jboss-4.2.3.GA/server/default/deploy/SV2Interface.ear
  | 
  | WARN  [EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface 
only com.foo.service.SwService in ejb-jar.xml of SV2Servicenot used by any EJBs
  | WARN  [EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface 
only com.foo.aaa.service.serviceRejet.IServiceRejetEnterprisein ejb-jar.xml of 
SV2Servicenot used by any EJBs
  | WARN  [EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface 
only com.bar.bbb.service.SessionService in ejb-jar.xml ofSwServicenot used by 
any EJBs
  | WARN  [EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface 
only com.bar.bbb.service.DbSearchService in ejb-jar.xml of SwServicenot used by 
any EJBs
  | INFO  [JmxKernelAbstraction] creating wrapper delegate for: 
org.jboss.ejb3.stateless.StatelessContainer
  | INFO  [JmxKernelAbstraction] installing MBean: 
jboss.j2ee:ear=SV2Interface.ear,jar=SV2InterfaceEJBModule.jar,name=ShipService,service=EJB3
 with dependencies:
  | INFO  [JmxKernelAbstraction]   
persistence.units:ear=SV2Interface.ear,jar=SV2InterfaceEJBModule.jar,unitName=SV2_Ship_Casa
  | INFO  [JmxKernelAbstraction]   
persistence.units:ear=SV2Interface.ear,jar=SV2InterfaceEJBModule.jar,unitName=SV2_Reference
  | INFO  [JmxKernelAbstraction]   
persistence.units:ear=SV2Interface.ear,jar=SV2InterfaceEJBModule.jar,unitName=SV2_Ship_Moro
  | INFO  [EJBContainer] STARTED EJB: com.foo.service.ShipServiceBean ejbName: 
ShipService
  | INFO  [JmxKernelAbstraction] creating wrapper delegate for: 
org.jboss.ejb3.stateless.StatelessContainer
  | INFO  [JmxKernelAbstraction] installing MBean: 
jboss.j2ee:ear=SV2Interface.ear,jar=SV2InterfaceEJBModule.jar,name=SV2Service,service=EJB3
 with dependencies:
  | INFO  [JmxKernelAbstraction]   
jboss.j2ee:ear=SV2Interface.ear,jar=SV2InterfaceEJBModule.jar,name=ShipService,service=EJB3
  | INFO  [EJBContainer] STARTED EJB: com.foo.service.SV2ServiceBean ejbName: 
SV2Service
  | INFO  [JmxKernelAbstraction] creating wrapper delegate for: 
org.jboss.ejb3.stateless.StatelessContainer
  | INFO  [JmxKernelAbstraction] installing MBean: 
jboss.j2ee:ear=SV2Interface.ear,jar=SV2InterfaceEJBModule.jar,name=SwService,service=EJB3
 with dependencies:
  | INFO  [EJBContainer] STARTED EJB: com.foo.service.SwServiceBean ejbName: 
SwService
  | INFO  [EJB3Deployer] Deployed: 
file:/C:/jboss-4.2.3.GA/server/default/tmp/deploy/tmp5596106466848300323SV2Interface.ear-contents/SV2InterfaceEJBModule.jar
  | INFO  [EARDeployer] Started J2EE application: 
file:/C:/jboss-4.2.3.GA/server/default/deploy/SV2Interface.ear
  | 

As I mentioned in my first post all EJB's are located in the same jar (ejb 
module) that, in turn, is packaged in EAR application. I am accesing one EJB 
from another EJB (both of them are located in the same JAR).

Thanks,
Vadim

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232149#4232149

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232149
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [EJB 3.0] - Re: @EJB injection after redeploy

2009-05-20 Thread vlotarev 
I did some testing: replaced @EJB dependency injection by direct JNDI lookup 
but this didn't solve the problem. I noticed that the same $Proxy object is 
returned in response to JNDI lookup after several application re-deployments. 
Though JNDIView MBean shows different $Proxy objects after each re-deployment.
I think that this is a reason - JNDI lookup invoked from application returns an 
old $Proxy object that was created during the first deployment. Looks like a 
bug ... Does anybody can suggest any workaround?

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232286#4232286

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232286
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [EJB 3.0] - Re: @EJB injection after redeploy

2009-05-20 Thread vlotarev 
It's interesting that

new InitialContext().list()

returns right bound proxy classes but direct lookup invoked on the same context

new InitialContext().lookup(name)

returns old proxy class ...

It looks like InitialContext implementation caches bound objects somewhere (in 
static variable?) and this cache is not cleared during re-deployment.

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232308#4232308

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232308
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user