Thanks Howard, I was able to download the JBoss Messaging zip file on Windows
platform and this time around it was correctly downloaded.
I upgraded to JBoss Messaging 1.4.5.GA and JBoss Remoting 2_2_3_SP1 however
there is no change in my observations. The Worker Threads still remain in
memory a
Thanks for your suggestions.
The JBoss 4.2.3 GA default Remoting package was upgraded to JBoss Remoting
version to 2.2.2 SP11. After running the test again I saw no change in the
behavior i.e. the worker thread count reaches a high water mark and stays
there. All the Worker threads remain in wa
Hi Howard,
Thankyou for your response. I will post the issue to JBoss Remoting forum.
The JBoss Remoting version is 2.2.2.SP8 the one that came with JBoss AS 4.2.3
GA (haven't upgraded the JBoss Remoting version).
| Contents of Manifest.mf file in jboss-remoting.jar are shown below:
|
|
I will appreciate any insight regarding the behavior observed with JBoss 4.2.3
GA, JBoss Messaging and Worker Threads.
The JBoss 4.2.3 GA is running on Windows XP (SP 3) and uses jdk1.6.0_12.
The server is configured to use JBoss Messaging jboss-messaging-1.4.2.GA-SP1
(instead of JBoss MQ provid
Hi Flavia,
You are right, the "src" tag must point to the class files to be transformed.
Although I had read the docs, I made an error in thinking of the "src" folder
as the actual Java sources.
I had to set the "src" tag as shown below to get the AOPC compiler to pickup
the files correctly,
I recently got introduced to JBOSS AOP and was able to try out the sample code.
Thanks to the development team for all their efforts.
My development environment is Windows XP, JDK build 1.6.0_03-b05 and
JBoss-AOP_1.5.6.GA
I am facing a interesting issue while using the AOPC compiler. The compil
