[aeternitas]

jaikiran pai wrote:

It's the xsd in the ejb-jar.xml (if you have one) of your application which decides which EJB version is being used (that effectively decides the timerservice).

I don't use that file, it is optional, so I thought by default EJB3.0 was used (or know JBoss AS 6 uses EJB3.1 by default); shouldn't be so?

jaikiran pai wrote:

What kind of a "service" is that class?

It is @Singleton and @Startup service, which executes one method after construction and then each N minutes updates some data (well, just sort of chache service)

[jaikiran]

Maxym Pendyshchuk wrote:

jaikiran pai wrote:

It's the xsd in the ejb-jar.xml (if you have one) of your application which decides which EJB version is being used (that effectively decides the timerservice).

I don't use that file, it is optional, so I thought by default EJB3.0 was used (or know JBoss AS 6 uses EJB3.1 by default); shouldn't be so?

Yes, JBoss AS6 defaults to EJB3.1 in the absence of the ejb-jar.xml descriptor. So yeah, the timerservice-mk2 will be used and is required if you deploy any EJB3 beans.

Maxym Pendyshchuk wrote:

jaikiran pai wrote:

What kind of a "service" is that class?

It is @Singleton and @Startup service, which executes one method after construction and then each N minutes updates some data (well, just sort of chache service)

Okay, so you use EJB3 beans. Don't remove the timerservice-mk2.jar then. It's required for the EJB3 service to function.

P.S: I'll answer your rest of the questions too - just getting some other work done in the meantime.

[aeternitas]

jaikiran pai wrote:

Letting those common/lib jars remain, should be fine. They wouldn't really add to any additional class processing since they aren't picked up for any of the annotation scanning or any similar stuff. So I don't think removing those jars is necessary.

Just performed a little test, I leave hornetq-xyz jars in common/lib folder, boot server and see appropriate empty folders in tmp/automount2776603a7b8e9bd8 folder (like hornetq-xyz/contents). As I told they are empty, but it looks like Jboss spends at least some minimal time to analyze those jars, creates folders in tmp folder as for any other jar from common/lib folder. What's the reason to create those empty folders for them?

[aeternitas]

P.S: I'll answer your rest of the questions too - just getting some other work done in the meantime.

thank you, very appreciate your help and time spent for it

[richard.clayton]

Thank you so much for your guide.  For JMS, I found out you also had to remove:

${JBOSS_HOME}/common/lib/jboss-as-hornetq-int.jar

Richard

[jaikiran]

Maxym Pendyshchuk wrote:

jaikiran pai wrote:

Letting those common/lib jars remain, should be fine. They wouldn't really add to any additional class processing since they aren't picked up for any of the annotation scanning or any similar stuff. So I don't think removing those jars is necessary.

Just performed a little test, I leave hornetq-xyz jars in common/lib folder, boot server and see appropriate empty folders in tmp/automount2776603a7b8e9bd8 folder (like hornetq-xyz/contents). As I told they are empty, but it looks like Jboss spends at least some minimal time to analyze those jars, creates folders in tmp folder as for any other jar from common/lib folder. What's the reason to create those empty folders for them?

That looks like something related to VFS3 (mounting?). I am not an expert on that one. Let's see if someone with VFS3 knowledge can comment on whether the implementation unjars/reads all the jars from JBOSS_HOME/common/lib. If it does, then yes, removing those unnecessary jars will help.

[richard.clayton]

Jaikiran,

I tested this about an hour ago; if you don't remove those jars in the common/lib folder, VFS will produce a dependency error as it attempts to instantiate the EJB's locked in those JARs.

Richard

[aeternitas]

Richard, can you show an example of it? At the beginning I cleaned only deploy and deployers folder, so I left dependent jars in common/lib folder, and as I remember I didn't have any errors while JBoss booting

[jaikiran]

Yes, an exception stacktrace would help. It would be surprising if there are any EJBs being bundled in jars in common/lib folder.

[richard.clayton]

Hey Guys,

Can't give you a stack trace because I'm developing on an intranet.  I can, however, give you the source code:

http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.jbossas/jboss-as-hornetq-int/6.0.0.20100429-M3/org/jboss/as/integration/hornetq/management/jms/JMSServerMO.java?av=f

I think this is a management bean under the hood.  Until I deleted the jboss-as-hornetq-int.jar out of the common/lib directory, I kept getting errors with VFS.

Richard

[saifeldeen]

The following link provides some tips to slimming a JAS6 server:

https://community.jboss.org/wiki/JBoss6xTuningSlimming