Bug 1020302 - EAP started with JTS transaction starting with WARN message in the log
Summary: EAP started with JTS transaction starting with WARN message in the log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER7
: EAP 6.2.0
Assignee: tom.jenkinson
QA Contact: Ondrej Chaloupka
URL:
Whiteboard:
Depends On: 1022054
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-17 12:15 UTC by Ondrej Chaloupka
Modified: 2017-10-10 00:08 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:15:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Ondrej Chaloupka 2013-10-17 12:15:48 UTC 
When you start EAP (in my case EAP 6.2.0.ER6 but it happens for previous versions as well) and you configure the jts transactions:
 - jacorb subsystem - transactions="on"
 - transactions subsystem - addding tag <jts/>

and start the EAP like
./bin/standalone.sh -c standalone-full.xml

you can see WARN message in the log
WARN  [com.arjuna.ats.jts] (MSC service thread 1-1) ARJUNA022251: The ORBManager is already associated with an ORB/OA.

The start of the EAP server should be clean without warnings.
Comment 1 tom.jenkinson 2013-10-17 12:43:29 UTC 
Hi Ondra,

Would info level be OK?

Tom
Comment 2 Ondrej Chaloupka 2013-10-17 13:11:14 UTC 
Hi Tom,

yes, the info level is ok. The log of the starting EAP will be clean from the warning messages and the user will be able to see the information form the narayana processing.

Thanks
Ondra
Comment 3 Ondrej Chaloupka 2013-10-17 15:37:27 UTC 
Just to be clear one more point - this warning does not influence the EAP functionality. It's purpose is just informative and for this reason is better to be under INFO log level.
Comment 4 Ondrej Chaloupka 2013-10-31 12:43:40 UTC 
Verified for 6.2.0.ER7
Note You need to log in before you can comment on or make changes to this bug.