[jbosstools-dev] Re: JBoss AS adapter problems

[Denis Golovin]

Rob,

Create seam project in ear deployment configuration,
deploy it to JBoss AS by Deploy button on Servers View,
check that there is exploded ear in deploy directory,
start server,
build is failed,
project-name.war folder and project-name-ejb.jar appear in deploy directory.

I've check it on last build and it has the same behavior under windows..

Thanks
Denis

Rob Stryker wrote:
> Dennis:
>
> exact steps to replicate?
>
> Thanks.
>
> - Rob
>
> Denis Golovin wrote:
>> Rob,
>>
>> I've just noticed that seam-ear projects are not started after 
>> deployment. After deployment exploded EAR folder appears in deploy 
>> directory and its structure looks fine, but after server is being 
>> started ejb jar is added to deploy folder also. It happens all the 
>> time. Sometimes war folder from ear is duplicated right into deploy 
>> folder, so there are two the same wars one in ear folder structure 
>> and another one right in deploy directory. Two ejb: exploded in ear 
>> folder and jar in deploy folder. All these war and ejb's jar files in 
>> deploy folder lead to errors during starting seam ear project.
>>
>> for example, there is a problem with conflicted datasources
>>
>> org.jboss.deployment.DeploymentException: Trying to install an 
>> already registered mbean: 
>> jboss.jca:service=LocalTxCM,name=seam99Datasource
>>    at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103)
>>    at 
>> org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449) 
>>
>>    at 
>> org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171) 
>>
>>    at 
>> org.jboss.system.ServiceController.install(ServiceController.java:226)
>>    at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source)
>>    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>    at java.lang.reflect.Method.invoke(Unknown Source)
>>    at 
>> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) 
>>
>>    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
>>    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
>>    at 
>> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) 
>>
>>    at 
>> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
>>    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
>>    at $Proxy4.install(Unknown Source)
>>    at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
>>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>
>> it happens only when JBoss AS server started form Eclipse if remove 
>> all unnecessary wars and jars and start JBoss from command line it 
>> works.
>>
>> I didn't create a jira issue yet, just want to ask you look at it. 
>> Can you reproduce it locally or that is only my local problem?
>>
>> Thanks
>> Denis
>