Bug 779324 (SOA-1712) - Warnings during jUDDI 3 startup
Summary: Warnings during jUDDI 3 startup
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1712
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation, jUDDI - within SOA
Version: 5.0.0 ER5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.0.0 ER8
Assignee: Kurt Stam
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-14 09:52 UTC by Jiri Pechanec
Modified: 2010-02-04 07:26 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Embedde, PostgreSQL, Sun JDK 6, Fedora 10
Last Closed: 2010-02-04 07:26:15 UTC
Type: Bug

Attachments (Terms of Use)
server.log.gz (18.23 KB, application/x-gzip)
2009-12-14 09:53 UTC, Jiri Pechanec 		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-1712 0 None None None Never

Description Jiri Pechanec 2009-12-14 09:52:29 UTC 
Affects: Release Notes
Date of First Response: 2009-12-14 06:08:35
project_key: SOA

When server is starting up two warnings related to jUDDI ar printed during startup. Please verify that these messages are harmless and if so it should be documented as scary messages in the release notes.

2009-12-14 10:41:19,786 WARN  [org.hibernate.ejb.Ejb3Configuration] (main) Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null.
2009-12-14 10:41:22,190 WARN  [org.hibernate.impl.SessionFactoryImpl] (main) JTASessionContext being used with JDBCTransactionFactory; auto-flush will not operate correctly with getCurrentSession()
Comment 1 Jiri Pechanec 2009-12-14 09:53:20 UTC 
Attachment: Added: server.log.gz
Comment 2 trev 2009-12-14 11:08:35 UTC 
Can you comment on this jira please
Comment 3 Kurt Stam 2009-12-16 18:32:04 UTC 
Don't know if this is a problem or not. We will have to investigate. I opened https://issues.apache.org/jira/browse/JUDDI-323. Should be addressed in 3.0.1 due mid January.
Comment 4 David Le Sage 2010-02-02 05:23:29 UTC 
Hello Kurt, 

Is this still an issue?  If so, we will add to the Release Notes.

Thanks,

David
Comment 5 Kurt Stam 2010-02-03 14:41:08 UTC 
Was not able to reproduce with later builds, but it looks like these warnings are not harmful anyway

http://issues.apache.org/jira/browse/JUDDI-323
Comment 6 Jiri Pechanec 2010-02-04 07:26:15 UTC 
Verified in ER8
Note You need to log in before you can comment on or make changes to this bug.