Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Process Manager (Stardust) » Deployment error: JDBC URL must not be empty
Deployment error: JDBC URL must not be empty [message #1100677] Tue, 03 September 2013 08:37 Go to next message
Tim Summers is currently offline Tim Summers
Messages: 3
Registered: September 2013
Junior Member
I followed all steps in the Support Case tutorial, but on deployment I receive this error:

- Starting ...
- Deploying model from file [C:\Users\hds973\Documents\eclipse_workspace\Support-Case\ACMEWorkflowModel.xpdl]
- CARNOT version: 1.0.0.71
- Loading properties via provider factory org.eclipse.stardust.common.config.DefaultPropertiesProvider$Factory (priority 1).
- Property bundle 'carnot.properties' not found. Current classloader = sun.misc.Launcher$AppClassLoader@7ced01
- Loading properties via provider factory org.eclipse.stardust.engine.spring.web.SpringAppContextPropertiesProviderFactory (priority 4).
- org.eclipse.stardust.engine.api.spring.cachedApplicationContext = null
- Initializing static extensions resolver
- Initializing Service Provider extensions resolver
- Using extensions manager: org.eclipse.stardust.engine.core.runtime.beans.PartitionAwareExtensionsManager@12437a4
- Bootstrapping engine
- --> login
- Failed bootstrapping runtime properties from audit trail.
java.lang.IllegalArgumentException: JDBC URL must not be empty.
at org.eclipse.stardust.engine.core.persistence.jdbc.LocalDataSource.getConnection(LocalDataSource.java:92)
at org.eclipse.stardust.engine.core.persistence.jdbc.Session.getConnection(Session.java:2252)
at org.eclipse.stardust.engine.core.persistence.jdbc.Session.executeQuery(Session.java:2636)
at org.eclipse.stardust.engine.core.persistence.jdbc.Session.executePersistentQuery(Session.java:2864)
at org.eclipse.stardust.engine.core.persistence.jdbc.Session.getIterator(Session.java:1469)
at org.eclipse.stardust.engine.core.persistence.jdbc.Session.getIterator(Session.java:1443)
at org.eclipse.stardust.engine.core.runtime.beans.PropertyPersistor.findAll(PropertyPersistor.java:80)
at org.eclipse.stardust.engine.core.runtime.beans.PropertyPersistor.findAll(PropertyPersistor.java:64)
at org.eclipse.stardust.engine.core.runtime.interceptor.AuditTrailPropertiesInterceptor.bootstrapAuditTrailProperties(AuditTrailPropertiesInterceptor.java:74)
at org.eclipse.stardust.engine.core.runtime.interceptor.AuditTrailPropertiesInterceptor.getAuditTrailProperties(AuditTrailPropertiesInterceptor.java:50)
at org.eclipse.stardust.engine.core.runtime.beans.interceptors.POJOSessionInterceptor.invoke(POJOSessionInterceptor.java:85)
at org.eclipse.stardust.engine.core.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:130)
at org.eclipse.stardust.engine.core.runtime.beans.interceptors.POJOForkingInterceptor.invoke(POJOForkingInterceptor.java:52)
at org.eclipse.stardust.engine.core.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:130)
at org.eclipse.stardust.engine.api.ejb2.beans.interceptors.ContainerConfigurationInterceptor.invoke(ContainerConfigurationInterceptor.java:78)
at org.eclipse.stardust.engine.core.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:130)
at org.eclipse.stardust.engine.core.runtime.beans.interceptors.PropertyLayerProviderInterceptor.invoke(PropertyLayerProviderInterceptor.java:129)
at org.eclipse.stardust.engine.core.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:130)
at org.eclipse.stardust.engine.core.runtime.beans.interceptors.DebugInterceptor.invoke(DebugInterceptor.java:55)
at org.eclipse.stardust.engine.core.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:130)
at org.eclipse.stardust.engine.core.runtime.interceptor.MethodInvocationImpl.execute(MethodInvocationImpl.java:68)
at org.eclipse.stardust.engine.core.runtime.beans.InvocationManager.invoke(InvocationManager.java:53)
at com.sun.proxy.$Proxy9.login(Unknown Source)
at org.eclipse.stardust.engine.core.runtime.beans.POJOServiceFactory.getNewServiceInstance(POJOServiceFactory.java:44)
at org.eclipse.stardust.engine.core.runtime.beans.AbstractSessionAwareServiceFactory.getOrCreateService(AbstractSessionAwareServiceFactory.java:65)
at org.eclipse.stardust.engine.core.runtime.beans.AbstractSessionAwareServiceFactory.startSession(AbstractSessionAwareServiceFactory.java:120)
at org.eclipse.stardust.engine.core.runtime.beans.AbstractSessionAwareServiceFactory.getService(AbstractSessionAwareServiceFactory.java:53)
at org.eclipse.stardust.engine.core.runtime.beans.DefaultServiceFactory.getQueryService(DefaultServiceFactory.java:63)
at org.eclipse.stardust.modeling.deploy.DeployModelDialog.<init>(DeployModelDialog.java:73)
at org.eclipse.stardust.modeling.deploy.DeployModelDialog.showDialog(DeployModelDialog.java:240)
at org.eclipse.stardust.modeling.deploy.ModelDeploymentTool.deployModel(ModelDeploymentTool.java:298)
at org.eclipse.stardust.modeling.deploy.ModelDeploymentTool.<init>(ModelDeploymentTool.java:206)
at org.eclipse.stardust.modeling.deploy.ModelDeploymentTool.main(ModelDeploymentTool.java:137)
- <-- login
Re: Deployment error: JDBC URL must not be empty [message #1101200 is a reply to message #1100677] Wed, 04 September 2013 02:07 Go to previous messageGo to next message
Robert Emsbach is currently offline Robert Emsbach
Messages: 115
Registered: October 2011
Location: Singapore
Senior Member

Tim,

it looks like the client environment to deploy the model to the server has not bootstrapped correctly. The carnot.properties file was not in the classpath.
This can have several reasons. Is the project that the model resides is a dynamic web project with the stardust project facets?
Does it contain a carnot.properties file in the folder ipp-resources ?

Is the option Project - Build automatically enabled?
Please also try a "Project - Clean..." then try again.

Best regards

Rob








Re: Deployment error: JDBC URL must not be empty [message #1101298 is a reply to message #1101200] Wed, 04 September 2013 05:16 Go to previous message
Tim Summers is currently offline Tim Summers
Messages: 3
Registered: September 2013
Junior Member
Thanks Rob,

a simple "clean" did the trick.
Previous Topic:ConcurrentModificationException when DB is not empty
Next Topic:Roadmap
Goto Forum:
  


Current Time: Tue Jul 22 03:40:12 EDT 2014

Powered by FUDForum. Page generated in 0.02562 seconds