Bug 779986 (SOA-2346) - error in server log - 5.1
Summary: error in server log - 5.1
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-2346
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EAP
Version: 5.1.0.ER2,5.1.0.ER5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-25 19:36 UTC by Aleksandar Kostadinov
Modified: 2011-12-06 22:01 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
RHEL4/5 and windows, Sun java 16, server default/production/all
Last Closed: 2011-12-06 22:01:38 UTC
Type: Bug

Attachments (Terms of Use)
server_default.log (168.84 KB, text/x-log)
2010-12-16 11:48 UTC, Aleksandar Kostadinov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2346 0 Major Closed error in server log - 5.1 2014-04-25 10:58:07 UTC

Description Aleksandar Kostadinov 2010-09-25 19:36:27 UTC 
Steps to Reproduce: just start server all
project_key: SOA

I see the following in server log when starting SOA-P for the first time. It happens almost always with server all and production.

Exception detected by:`15:22:27,707 WARN  [loggerI18N] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR
Comment 1 Aleksandar Kostadinov 2010-12-16 11:48:07 UTC 
Attachment: Added: server_default.log
Comment 2 Aleksandar Kostadinov 2010-12-16 11:53:40 UTC 
Link: Added: This issue Cloned to SOA-2689
Comment 3 Aleksandar Kostadinov 2010-12-16 11:57:51 UTC 
separating the new error in SOA-2689
Comment 4 Aleksandar Kostadinov 2010-12-16 11:58:54 UTC 
Link: Removed: This issue Cloned to SOA-2689
Note You need to log in before you can comment on or make changes to this bug.