How to check with JBossTS is deployed on JBossAS

[skajotde]

Hi all!

How to check with JBossTS is deployed on JBossAS ? I checked MANIFEST.MF in jbossts-common.jar but there is only JBoss AS version like "Implementation-Version: 5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=20

0812041714)"

And when I start JBoss 4.2.3 there in only

21:08:27,485 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
21:08:27,485 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
21:08:27,779 INFO [TransactionManagerService] Starting recovery manager
21:08:27,935 INFO [TransactionManagerService] Recovery manager started
21:08:27,935 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference

without version number. I also checked jmx console with TransactionManager but I didn't find version deployed JBossTS.

[adinn]

If you look at the build subdirectory in any JBoss AS source tree there is an ant script called build-thirdparty.xml. This script downloads all the components included in JBossAS release. Search for JBossTS and you will see the release version your AS release uses.

[jhalliday]

A side note for users of more recent AS versions: for AS 5.0 the build process has changed from that used in 4.2.x component-matrix/pom.xml is the new place to look.

[skajotde]

"adinn" wrote:
If you look at the build subdirectory in any JBoss AS source tree there is an ant script called build-thirdparty.xml. This script downloads all the components included in JBossAS release. Search for JBossTS and you will see the release version your AS release uses.

Thanks.

Unfortunately I have packed binary vesion of JBossAS, prepared for project. It has diference , eg other version of JBossWS. In JbossWS a can simply check which version is runnging (in three ways).

One of I would like to check is if my jboss has standard JBossTS distributed with JbossAS 4.2.3.GA (according build-thirdypart.xml it is 4.2.3.SP7) or other, packed.

I think MANIFEST.MF should containt information about version or during start should be info like this:

21:08:27,485 INFO [TransactionManagerService] JBossTS Transaction Service (JTA 4.2.3.SP1 version) - JBoss Inc.

You know, when you know version you can attach exact sources to expected version and look at exactly documentation what you means (to exact version).

[adinn]

Unfortunately I have packed binary vesion of JBossAS, prepared for project.

Hmm, yes, very unfortunate. I know we provide _fantastic_ support on this forum (well, ok, it's _free_ and it _doesn't suck_ :-) but don't believe the hype. We are not actually able to read minds and we cannot look back through time and space to see what other people might have done. I think you probably need to ask the person who packed your release how they built it.

[skajotde]

"adinn" wrote:

Unfortunately I have packed binary vesion of JBossAS, prepared for project.

Hmm, yes, very unfortunate. I know we provide _fantastic_ support on this forum (well, ok, it's _free_ and it _doesn't suck_ :-) but don't believe the hype. We are not actually able to read minds and we cannot look back through time and space to see what other people might have done. I think you probably need to ask the person who packed your release how they built it.

I asked this question because I think is it case of component versioning. Maybe it is hidden option and I had asked (in JBossWS there are three non hidden options to check this and support wasn't need because it was intuitive - you wrote it is matter of support).

I believe that JBossTS is great product but I think it is lack of feature. JBossTS jars should be versioned (my collegue didnt extract jar and replace classes, he replace jar, so if jar would be versioned there would be no problem).

It is funny that, on EJB3 forum I asked on opposite feature http://www.jboss.org/index.html?module=bb&op=viewtopic&t=149276 - download sources in one archive (EJB3 version each component separately in maven2).