• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Error while deploying Maven generated war.

 
Raghu Sha
Ranch Hand
Posts: 122
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In weblogic 12c, while deploying maven generated war give below exception.
Newly created domain also giving same exception.

Unable to access the selected application
Exception in AppMerge flow's progression
HTTP:101380 More than one web fragments with the same name:"spring_web"

But exported as war from eclipse no deployment issue.
 
anandraj tadkal
Ranch Hand
Posts: 98
Oracle Redhat
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Below is description from Oracle website:

BEA-101380: More than one web fragments with the same name: "{0}".
Cause: More than one web fragments with the same name.
Action: Change one or more web fragment names to avoid the conflict.

Level: 1

Type: ERROR

Impact: HTTP

There could be a conflict in the web fragment name.

Regards,
Anandraj
 
Raghu Sha
Ranch Hand
Posts: 122
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks.

How to change & set web fragment name?
 
Dmytro Lastname
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
anandraj tadkal wrote:Below is description from Oracle website:

BEA-101380: More than one web fragments with the same name: "{0}"
....
There could be a conflict in the web fragment name.

Regards,
Anandraj


Quite useless reply, heh.
I have found it happens to me if I build war with 1.7 JDK. Return to 1.6 helps. You may have to rebuild/re/install maven if you have 1.7 binary distribution.

Hope it helps,
Dmytro
 
Raghu Sha
Ranch Hand
Posts: 122
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
@Dmytro,

No luck. I did all the way you specified and deleted all the domains and created new one. Using 1.6 only for comiplation and same 1.6 also configured in eclipse & weblogic domain



Any other possbile solutions?
 
Dmytro Lastname
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Raghu Sha wrote:@Dmytro,

No luck. I did all the way you specified and deleted all the domains and created new one. Using 1.6 only for comiplation and same 1.6 also configured in eclipse & weblogic domain



Any other possbile solutions?


Does it mean you did rebuild with the same JDK? BTW, compilation phase is not important in this case.
What does your `mvn -version` return?
 
Raghu Sha
Ranch Hand
Posts: 122
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Rebuild using same JDK only.

 
Dmytro Lastname
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm using:

and

for deployment.
 
Raghu Sha
Ranch Hand
Posts: 122
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using
Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-28 07:45:3
2+0530)

changed
To

As usual deleted tmp & cache in server and clean & rebuild.

Still same issue persists.
 
Raghu Sha
Ranch Hand
Posts: 122
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is there is any other way to deploy the war to eliminate the above issue.? I used admin console for deployment.
need to change anything in settings.xml of maven?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic