Bug 793837 (JBEPP-911) - EPP5.1.1.dev01 failed to start in cluster profile
Summary: EPP5.1.1.dev01 failed to start in cluster profile
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-911
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: 5.1.1.DEV01
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.1.DEV02
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-02 13:13 UTC by mposolda
Modified: 2012-02-28 16:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
JBoss EPP 5.1.1.Dev01 started with cluster profile ( -Dexo.profiles=cluster )
Last Closed: 2011-05-02 14:46:03 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-911 0 None Closed EPP5.1.1.dev01 failed to start in cluster profile 2012-03-28 15:32:59 UTC

Description mposolda 2011-05-02 13:13:40 UTC
project_key: JBEPP

Start OOTB EPP 5.1.1.DEV01 with command:

./run.sh -c all -Dexo.profiles=cluster

Then there is exception in server log (Seems like bad jboss cache configuration for picketlink). And there is also exception in browser when I am trying to access http://localhost:8080/portal

09:02:55,829 INFO  [SchemaUpdate] schema update complete
09:02:55,856 ERROR [RootElementBuilder] Configuration warning: The markup in the document following the root element must be well-formed.
09:02:55,867 ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file.
09:02:55,867 ERROR [XmlConfigHelper] Configurator SAXParse error
org.xml.sax.SAXParseException: Premature end of file.
	at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
	at org.jboss.cache.config.parsing.XmlConfigHelper.getDocumentRoot(XmlConfigHelper.java:454)
	at org.jboss.cache.config.parsing.XmlConfigurationParser2x.parseStream(XmlConfigurationParser2x.java:103)
	at org.jboss.cache.DefaultCacheFactory.createCache(DefaultCacheFactory.java:179)
	at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.<init>(PicketLinkIDMServiceImpl.java:141)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at org.exoplatform.container.ExoContainer.createComponent(ExoContainer.java:321)
	at org.exoplatform.container.jmx.MX4JComponentAdapter.getComponentInstance(MX4JComponentAdapter.java:94)
	at org.exoplatform.container.management.ManageableComponentAdapter.getComponentInstance(ManageableComponentAdapter.java:68)
	at org.exoplatform.container.ConcurrentPicoContainer.getInstance(ConcurrentPicoContainer.java:400)
	at org.exoplatform.container.ConcurrentPicoContainer.getComponentInstancesOfType(ConcurrentPicoContainer.java:350)
	at org.exoplatform.container.CachingContainer.getComponentInstancesOfType(CachingContainer.java:111)
	at org.picocontainer.defaults.LifecycleVisitor.visitContainer(LifecycleVisitor.java:97)
	at org.exoplatform.container.ConcurrentPicoContainer.accept(ConcurrentPicoContainer.java:517)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.picocontainer.defaults.AbstractPicoVisitor.traverse(AbstractPicoVisitor.java:32)
	at org.picocontainer.defaults.LifecycleVisitor.traverse(LifecycleVisitor.java:63)
	at org.picocontainer.defaults.LifecycleVisitor.start(LifecycleVisitor.java:113)

Comment 1 mposolda 2011-05-02 13:36:08 UTC
There is workaround. It seems that there is some mistake in files http://anonsvn.jboss.org/repos/gatein/epp/portal/tags/EPP_5_1_1_Dev01/web/portal/src/main/webapp/WEB-INF/conf/organization/picketlink-idm/jboss-cache-api-cluster.xml and jboss-cache-store-cluster.xml in same directory. 

There are two "jbosscache" elements. After deleting of one of these elements from both files, I am not seeing error anymore.

Comment 2 Scott Mumford 2011-08-09 01:43:46 UTC
Release Notes Docs Status: Added: Not Required



Note You need to log in before you can comment on or make changes to this bug.