StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POUsing application's Log4J configuration under JBoss 7.1.1
primarykey
Id
14182257
data
AcceptedAnswerId
14337990
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-06T12:46:31.923
FavoriteCount
6
LastActivityDate
2015-05-01T21:29:16.817
LastEditDate
2013-01-14T21:54:34.673
LastEditorUserId
50776
OwnerUserId
575458
ParentId
0
PostTypeId
1
Score
8
ViewCount
14777
LastEditorDisplayName
text
Body
I'm am having trouble logging using my appenders defined on my XML log4j configuration file. I created the jboss-deployment-structure.xml on my EAR's META-INF folder with no sucess. The jboss-deployment-structure.xml structure is: <pre><code><jboss-deployment-structure> <ear-subdeployments-isolated>false</ear-subdeployments-isolated> <deployment> <exclusions> <module name="org.apache.log4j" slot="main"/> </exclusions> </deployment> </jboss-deployment-structure> </code></pre> I have even tried to edit my standalone.conf.bat file adding the following line: <pre><code>set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" </code></pre> My application deployment is like this: <pre><code>-> MyAppEAR.ear -> META-INF -> MANIFEST.MF -> MyAoo.war -> META-INF -> MANIFEST.MF -> jboss-deployment-structure.xml -> WEB-INF -> web.xml -> lib -> log4j-1.2.17.jar -> --- -> classes -> log4j.xml -> ... </code></pre> I've noticed the following error: <ul> <li>jboss-deployment-structure.xml in subdeployment ignored. jboss-deployment-structure.xml is only parsed for top level deployments.</li> </ul> I even tried migrating from JBOSS 7.1.0 to 7.1.1 Some help please! Thanks <hr> Thanks for the repply James. I did what you said and moved the jboss-deployment-structure.xml file to MyAppEAR.ear/META-INF. I've noticed that this way the exception: <pre><code>jboss-deployment-structure.xml in subdeployment ignored. jboss-deployment-structure.xml is only parsed for top level deployments. </code></pre> ... doesn't occur. I don't know if that means that the file was parsed... how can I tell? Despite of this new behaviour my log4j.xml configuration file still isn't loaded and the logger used still is Log4J's. I know this becaused I wrote to the console: <pre><code>System.out.println(Logger.getRootLogger().getClass().toString()) </code></pre> ...and got: <pre><code>class org.jboss.logmanager.log4j.BridgeLogger </code></pre> I've also tried: <ul> <li>moving my log4j.xml to MyAppEAR.ear/META-INF.</li> <li>removing the unecessary -Dorg.jboss.as.logging.per-deployment=false from standalone.conf.bat</li> <li>removing slot from my jboss-deployment-structure.xml</li> </ul> Any more ideas? Thanks
Tags
<java><logging><jboss><log4j><jboss7.x>
Title
Using application's Log4J configuration under JBoss 7.1.1
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. UScasperOne
UserOwnerUserId
1. USRedEagle
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POUsing application's Log4J configuration under JBoss 7.1.1
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POUsing application's Log4J configuration under JBoss 7.1.1
 UserUserId
 USRedEagle
 VoteTypeVoteTypeId
 VTBountyStart
3. VO
 singulars
 PostPostId
 POUsing application's Log4J configuration under JBoss 7.1.1
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.