-
1. Re: jgroups deployment issue
brian.stansberry Jan 10, 2006 12:25 PM (in response to alesj)jgroups.jar isn't a deployment unit, it's a library. Don't put jgroups.jar in /server/default/deploy; put it in /server/default/lib or inside the deployment unit (e.g. war, ear, sar) that uses jgroups.
-
2. Re: jgroups deployment issue
alesj Jan 10, 2006 12:40 PM (in response to alesj)The only place that I have jgroups.jar is exactly '/server/default/lib'.
I did a a full JBossAS search on just 'jg' string. All it found was the above mentioned file (in that directory). -
3. Re: jgroups deployment issue
brian.stansberry Jan 10, 2006 1:02 PM (in response to alesj)Hmm. Well at some point some deployer took the jgroups.jar and expanded it in the tmp directory. If you delete the tmp directory before starting jboss, does the problem go away?
-
4. Re: jgroups deployment issue
alesj Jan 10, 2006 1:05 PM (in response to alesj)Yep, I think so.
But who could have taken it to the tmp? -
5. Re: jgroups deployment issue
alesj Jan 10, 2006 1:07 PM (in response to alesj)And why is it then threated as 'deploy material' (the actual 'default-minimalthreads.xml')?
-
6. Re: jgroups deployment issue
starksm64 Jan 11, 2006 5:37 PM (in response to alesj)The only reason this would be is if the default-minimalthreads.xml referenced the jgroups.jar via a classpath. This is something that should not be done for the server lib jars.