Broadleaf Commerce Discussion Forums

Hi All,

I am getting the following error when running the admin server.

[artifact:mvn] [ WARN] 22:00:52 RuntimeEnvironmentPropertiesConfigurer - Unable to determine runtime environment, using default environment 'development'
[artifact:mvn] [ WARN] 22:00:53 RuntimeEnvironmentPropertiesConfigurer - Unable to determine runtime environment, using default environment 'development'
[artifact:mvn] [ WARN] 22:00:53 RuntimeEnvironmentPropertiesConfigurer - Unable to determine runtime environment, using default environment 'development'
[artifact:mvn] [ WARN] 22:00:53 RuntimeEnvironmentPropertiesConfigurer - Unable to determine runtime environment, using default environment 'development
[artifact:mvn] 2013-02-11 22:00:22.997:WARN:oeji.nio:javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?'

Also following are few error lines I can see in the console what this are for.

[artifact:mvn] [ERROR] 21:58:44 Ejb3Configuration - Container is providing a null PersistenceUnitRootUrl: discovery impossible'

Thanks
MS

These are not errors in the sense that they block you from doing anything. The first one you can get rid of by sending the JVM a -D argument for the runtime environment (-Druntime.environment=development, -Druntime.environment=production, etc). The runtime.environment property is used to select the properties file in your project (development.properties, production.properties, etc). The second part about the SSLException is unique to Jetty; probably has to do with the fact that you don't run with 'real' certificates on localhost.

For the second part (ejb3Configuration) I'm not really sure about but again this doesn't cause anything detrimental.

Hi,

Where to set these values, I mean in which file. Also I am getting blank screen when admin page is loaded.

Thanks
MS

Sorry I don't really understand your question. If you mean "where do you pass the -D argument" you would do this for CATALINA_OPTS if you are running on Tomcat, but for local development you would do it in build.xml (you can see in that file where other -D arguments are passed). However this is not required for local development because the only thing you would set is -Druntime.environment=development which is the default.

What is the URL that gives you a blank screen? You should be hitting https://localhost:8444/admin.

Hi All,
Same thing happen in my case please suggest me

log
***************************************************************************
[INFO] Started Jetty Server
[artifact:mvn] 2013-02-27 11:03:08.546:INFO:oejs.AbstractConnector:Started SslSelectChannelConnector@0.0.0.0:8444
[artifact:mvn] [ WARN] 11:25:24 RuntimeEnvironmentPropertiesConfigurer - Unable to determine runtime environment, using default environment 'development'
[artifact:mvn] [ WARN] 11:25:25 RuntimeEnvironmentPropertiesConfigurer - Unable to determine runtime environment, using default environment 'development'
[artifact:mvn] 2013-02-27 11:25:25.093:WARN:oeji.nio:javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
[artifact:mvn] 2013-02-27 11:25:25.093:WARN:oeji.nio:javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
[artifact:mvn] [ WARN] 11:25:25 RuntimeEnvironmentPropertiesConfigurer - Unable to determine runtime environment, using default environment 'development'
[artifact:mvn] [ WARN] 11:25:25 RuntimeEnvironmentPropertiesConfigurer - Unable to determine runtime environment, using default environment 'development'
[artifact:mvn] 2013-02-27 11:38:20.828:WARN:oeji.nio:javax.net.ssl.SSLException: Received fatal alert: bad_certificate