Bug 1040883

Summary:	Jbosseap crash at boot
Product:	OpenShift Online	Reporter:	web.dev
Component:	Image	Assignee:	Dan Mace <dmace>
Status:	CLOSED NOTABUG	QA Contact:	libra bugs <libra-bugs>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	2.x
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://fapp-esmart.rhcloud.com/
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-16 16:50:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description web.dev 2013-12-12 09:29:05 UTC

Description of problem:
When I try to restart the platform it stop

Version-Release number of selected component (if applicable):
JBoss Enterprise Application Platform 6

How reproducible:
Just try to restart the app. Server crash with the following error

04:23:03,811 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration

Steps to Reproduce:
1.
2.
3.

Actual results:

All my webapp are stopped!

Expected results:


Additional info:

Comment 1 web.dev 2013-12-12 15:42:51 UTC

Dear

We've solved the bug!
The environment variable env.OPENSHIFT_INTERNAL_IP has been replaced by env.OPENSHIFT_JBOSSEAP_IP

Could we please be inform next time something like this happen??

We lost quite a lot of data that would be avoided if we've know this issue.

Regards

Fabrizio

Comment 2 Dan Mace 2013-12-16 16:50:35 UTC

Fabrizio,

I'm happy to hear the problem was resolved. The environment variable change was made many months back, and was intended to (and tested to be) compatible from a standalone.xml perspective. However, that doesn't account for any application code or configuration which may refer to the old variable.

Sorry for the confusion.