instrumented .ear file contains zero ejb?

[Stephen Gaudet]

Some parts of this message have been removed. Learn more about Nabble's security policy.

I have used cobertura (v 1.9.3)to instrument an .ear file, and then try to deploy the ear in glassfish, however I get the following error when I try to deploy it:

 

[#|2009-10-08T19:59:27.753-0700|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=16;_ThreadName=Timer-11;Error loading deployment descriptors for module [SODAServer] -- Invalid ejb jar [SODAServer-ejb.jar]: it contains zero ejb.

Note:

1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.

2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.

3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.

;_RequestID=9ae70c9d-ff12-4670-9ae9-c9308e5d5d7a;|"DPL8011: autodeployment failure while deploying the application : Error loading deployment descriptors for module [SODAServer] -- Invalid ejb jar [SODAServer-ejb.jar]: it contains zero ejb.

Note:

1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.

2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.

3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.

"|#]

 

[#|2009-10-08T19:59:27.753-0700|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=16;_ThreadName=Timer-11;|[AutoDeploy] Autodeploy failed : C:\Program Files\glassfish-v2ur2\domains\domain1\autodeploy\SODAServer.ear.|#]

 

Can someone suggest how to debug this problem?   To me it looks like cobertura’s instrumentation has corrupted my .ear file, but I’m not sure what to do next to solve the problem.

The instrumented version is 49140KB while the original version is 48,895KB so it looks like some tracing must have been added to my classes.

 

(The non-instrumented ear deploys fine)

 

 

Stephen Gaudet | Quality Assurance | Techneos Systems Inc. | O: +1.604.435.6007 x113 | www.techneos.com

Survey software for a mobile world.

 

Read our blog on mobile research!

 

 

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Cobertura-devel mailing list
Cobertura-devel@...
https://lists.sourceforge.net/lists/listinfo/cobertura-devel

[John W. Lewis]

Some parts of this message have been removed. Learn more about Nabble's security policy.

 

I have not seen that kind of a problem before.   The instrumentation will add tracing to you classes.   Before every original line there is a “touch” call added so the line count is incremented.   The instrumented class will also implement HasBeenInstrumented.

 

I would try using <includeClasses> and <excludeClasses> to instrument a subset of the classes in the ear.    For instance, I would try instrumenting only one class.   If that passes I would instrument another one until I got an idea of which one causes a problem.

 

John

 

From: Stephen Gaudet [mailto:sgaudet@...]
Sent: Tuesday, October 20, 2009 2:10 PM
To: cobertura-devel@...
Subject: [Cobertura-devel] instrumented .ear file contains zero ejb?

 

I have used cobertura (v 1.9.3)to instrument an .ear file, and then try to deploy the ear in glassfish, however I get the following error when I try to deploy it:

 

[#|2009-10-08T19:59:27.753-0700|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=16;_ThreadName=Timer-11;Error loading deployment descriptors for module [SODAServer] -- Invalid ejb jar [SODAServer-ejb.jar]: it contains zero ejb.

Note:

1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.

2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.

3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.

;_RequestID=9ae70c9d-ff12-4670-9ae9-c9308e5d5d7a;|"DPL8011: autodeployment failure while deploying the application : Error loading deployment descriptors for module [SODAServer] -- Invalid ejb jar [SODAServer-ejb.jar]: it contains zero ejb.

Note:

1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.

2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.

3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.

"|#]

 

[#|2009-10-08T19:59:27.753-0700|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=16;_ThreadName=Timer-11;|[AutoDeploy] Autodeploy failed : C:\Program Files\glassfish-v2ur2\domains\domain1\autodeploy\SODAServer.ear.|#]

 

Can someone suggest how to debug this problem?   To me it looks like cobertura’s instrumentation has corrupted my .ear file, but I’m not sure what to do next to solve the problem.

The instrumented version is 49140KB while the original version is 48,895KB so it looks like some tracing must have been added to my classes.

 

(The non-instrumented ear deploys fine)

 

 

Stephen Gaudet | Quality Assurance | Techneos Systems Inc. | O: +1.604.435.6007 x113 | www.techneos.com

Survey software for a mobile world.

 

Read our blog on mobile research!

 

 

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Cobertura-devel mailing list
Cobertura-devel@...
https://lists.sourceforge.net/lists/listinfo/cobertura-devel

[Stephen Gaudet]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Doh!

 

This error is what you should expect from glassfish server when you have not put the cobertura.jar file in the proper places within your glassfish installation.

 

Solved my own problem, but thank you to John W. Lewis for helping me along.

 

 

From: Stephen Gaudet [mailto:sgaudet@...]
Sent: Tuesday, October 20, 2009 11:10 AM
To: cobertura-devel@...
Subject: [Cobertura-devel] instrumented .ear file contains zero ejb?

 

I have used cobertura (v 1.9.3)to instrument an .ear file, and then try to deploy the ear in glassfish, however I get the following error when I try to deploy it:

 

[#|2009-10-08T19:59:27.753-0700|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=16;_ThreadName=Timer-11;Error loading deployment descriptors for module [SODAServer] -- Invalid ejb jar [SODAServer-ejb.jar]: it contains zero ejb.

Note:

1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.

2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.

3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.

;_RequestID=9ae70c9d-ff12-4670-9ae9-c9308e5d5d7a;|"DPL8011: autodeployment failure while deploying the application : Error loading deployment descriptors for module [SODAServer] -- Invalid ejb jar [SODAServer-ejb.jar]: it contains zero ejb.

Note:

1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.

2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.

3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.

"|#]

 

[#|2009-10-08T19:59:27.753-0700|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=16;_ThreadName=Timer-11;|[AutoDeploy] Autodeploy failed : C:\Program Files\glassfish-v2ur2\domains\domain1\autodeploy\SODAServer.ear.|#]

 

Can someone suggest how to debug this problem?   To me it looks like cobertura’s instrumentation has corrupted my .ear file, but I’m not sure what to do next to solve the problem.

The instrumented version is 49140KB while the original version is 48,895KB so it looks like some tracing must have been added to my classes.

 

(The non-instrumented ear deploys fine)

 

 

Stephen Gaudet | Quality Assurance | Techneos Systems Inc. | O: +1.604.435.6007 x113 | www.techneos.com

Survey software for a mobile world.

 

Read our blog on mobile research!

 

 

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Cobertura-devel mailing list
Cobertura-devel@...
https://lists.sourceforge.net/lists/listinfo/cobertura-devel