4 Replies Latest reply on Apr 15, 2015 4:08 AM by jaikiran

deployment (jdbc driver) installed using maven plugin is removed after deploying a war file that fails to deploy

baspet Apr 14, 2015 1:08 PM

hi,

i really stuck trying to find a proper title, but here's my problem:

1) successfully deployed my oracle jdbc driver using deploy-artifact (there's an entry in standalone-full-ha.xml as well a content file under standalone/data/content/a2)

2) stop server

3) start server (jdbcdriver is still there)

4) tried to deploy using standard procedure (putting in standalone\deployments) a war file with no dependencies on driver but having errors by mistake (web.xml not well formed)

5) wildfly correctly undeploys war but also undeploys jdbc driver!

regards

1. Re: deployment (jdbc driver) installed using maven plugin is removed after deploying a war file that fails to deploy

jaikiran Apr 15, 2015 2:02 AM (in response to baspet)

Known issue https://issues.jboss.org/browse/AS7-783
Actions
2. Re: deployment (jdbc driver) installed using maven plugin is removed after deploying a war file that fails to deploy

ehugonnet Apr 15, 2015 3:22 AM (in response to jaikiran)

Which version of WildFly do you use ? there have been some work around this kind of issue.
Also I'm not sure AS7-783 applies here Jaikiran as the driver is already deployed so the rollback from the scanner shouldn't include the driver deployment.
Actions
3. Re: deployment (jdbc driver) installed using maven plugin is removed after deploying a war file that fails to deploy

baspet Apr 15, 2015 4:06 AM (in response to ehugonnet)

8.2.0.Final
maybe, it's a side effect of AS7-783. if not, should i file an issue?

Regards
V.
Actions
4. Re: deployment (jdbc driver) installed using maven plugin is removed after deploying a war file that fails to deploy

jaikiran Apr 15, 2015 4:08 AM (in response to ehugonnet)

Hi Emmanuel,

ehsavoie Hugonnet wrote:

Also I'm not sure AS7-783 applies here Jaikiran as the driver is already deployed so the rollback from the scanner shouldn't include the driver deployment.

I think you are right. I misread the steps noted by Vassilis and thought that both the driver and the .war have been placed in the deployments folder and then the server started.
Actions

Go to original post