[JBoss JIRA] Created: (SOAG-100) When latest Overlord snapshot installed in JBossAS4.2.3, with JBossESB4.4
by Gary Brown (JIRA)
When latest Overlord snapshot installed in JBossAS4.2.3, with JBossESB4.4
-------------------------------------------------------------------------
Key: SOAG-100
URL: https://jira.jboss.org/jira/browse/SOAG-100
Project: SOA Governance
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Conversation Runtime
Affects Versions: 1.0 MR2
Reporter: Gary Brown
Assignee: Jeff Yu
Fix For: 1.0 MR2
When deploying the latest Overlord-cdl snapshot, the following error occurs in the JBossAS console - although it deploys without any problems in jbossesb-server-4.5:
13:33:17,686 INFO [JBoss4ESBDeployer] create esb service, overlord-cdl-runtime.
esb
13:33:17,736 INFO [H2Database] jdbc:h2:file:/C:/testing/overlord/jboss-4.2.3.GA
/server/default/data/h2/cdlDB;MVCC=TRUE;DB_CLOSE_ON_EXIT=FALSE
13:33:18,116 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=DataSourceBinding,name=cdlDS' to JNDI name 'java:cdlDS'
13:33:18,177 INFO [DatabaseInitializer] java:/cdlDS datasource is already initi
alized
13:33:18,817 WARN [ServiceController] Problem starting service jboss.esb:deploy
ment=overlord-cdl-runtime.esb
java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: Unable to
create Scheduler instance.
at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration
.java:132)
at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(J
Boss4ESBDeployment.java:82)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy43.start(Unknown Source)
at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.soa.esb.ConfigurationException: Unable to create Scheduler
instance.
at org.jboss.soa.esb.schedule.ScheduleProvider.<init>(ScheduleProvider.j
ava:75)
at org.jboss.soa.esb.listeners.config.ScheduleProviderFactory.createInst
ance(ScheduleProviderFactory.java:56)
at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration
.java:116)
... 114 more
Caused by: org.quartz.SchedulerConfigException: Thread count must be > 0
at org.quartz.simpl.SimpleThreadPool.initialize(SimpleThreadPool.java:22
5)
at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.j
ava:965)
at org.quartz.impl.StdSchedulerFactory.getScheduler(StdSchedulerFactory.
java:1152)
at org.jboss.soa.esb.schedule.ScheduleProvider.<init>(ScheduleProvider.j
ava:69)
... 116 more
13:33:19,298 INFO [JBoss4ESBDeployer] create esb service, overlord-cdl-validato
r.esb
13:33:19,799 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
13:33:19,949 INFO [JBoss4ESBDeployer] create esb service, pmiexample.esb
13:33:19,989 INFO [pmi-trading-system] Bound to JNDI name: queue/pmi-trading-sy
stem
13:33:19,989 INFO [pmi-validation-service] Bound to JNDI name: queue/pmi-valida
tion-service
13:33:19,999 INFO [pmi-exception-manager] Bound to JNDI name: queue/pmi-excepti
on-manager
13:33:20,009 INFO [pmi-trade-store] Bound to JNDI name: queue/pmi-trade-store
13:33:20,019 INFO [pmi-trade-store_reply] Bound to JNDI name: queue/pmi-trade-s
tore_reply
13:33:20,019 INFO [pmi-document-generation] Bound to JNDI name: queue/pmi-docum
ent-generation
13:33:20,029 INFO [pmi-books-and-records] Bound to JNDI name: queue/pmi-books-a
nd-records
13:33:20,380 INFO [JDBCDataStore] Generated token 'authToken:817B3E80-1941-11DE
-BE80-FD99FF59B2A2' for user: 'jbossesb/JBoss ESB User'
13:33:20,440 INFO [JDBCDataStore] Generated token 'authToken:81877380-1941-11DE
-B380-EA5C5E600D39' for user: 'jbossesb/JBoss ESB User'
13:33:20,480 INFO [JDBCDataStore] Generated token 'authToken:818D8E00-1941-11DE
-8E00-E647257703F3' for user: 'jbossesb/JBoss ESB User'
13:33:20,510 INFO [JDBCDataStore] Generated token 'authToken:819221E0-1941-11DE
-A1E0-9BDAD8C5A125' for user: 'jbossesb/JBoss ESB User'
13:33:20,580 INFO [JDBCDataStore] Generated token 'authToken:819CD040-1941-11DE
-9040-EB57FD77FD40' for user: 'jbossesb/JBoss ESB User'
13:33:20,630 INFO [JDBCDataStore] Generated token 'authToken:81A2EAC0-1941-11DE
-AAC0-BE8B08EE07B9' for user: 'jbossesb/JBoss ESB User'
13:33:20,650 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
13:33:20,730 INFO [JBoss4ESBDeployer] create esb service, slsb.esb
13:33:20,890 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
13:33:27,370 INFO [JBoss4ESBDeployer] create esb service, smooks.esb
13:33:27,400 INFO [Update] Bound to JNDI name: topic/org.jboss.soa.esb.transfor
mation.Update
13:33:27,480 INFO [SmooksService] Centralized Smooks Instance (Console Based) i
nstance not started. See the 'console.url' property in '/smooks.esb.properties'
13:33:27,520 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
13:33:33,509 INFO [JBoss4ESBDeployer] create esb service, soap.esb
13:33:33,639 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
13:33:35,762 INFO [JBoss4ESBDeployer] create esb service, spring.esb
13:33:35,812 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
13:33:35,812 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.esb:deployment=overlord-cdl-runtime.esb
State: FAILED
Reason: java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException:
Unable to create Scheduler instance.
I Depend On:
jboss.esb:deployment=jbossesb.esb
jboss.esb:service=CDLDatabaseInitializer
jboss.jca:service=DataSourceBinding,name=cdlDS
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.esb:deployment=overlord-cdl-runtime.esb
State: FAILED
Reason: java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException:
Unable to create Scheduler instance.
I Depend On:
jboss.esb:deployment=jbossesb.esb
jboss.esb:service=CDLDatabaseInitializer
jboss.jca:service=DataSourceBinding,name=cdlDS
13:33:35,902 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
080
13:33:35,992 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
13:33:36,052 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBos
s_4_2_3_GA date=200807181417)] Started in 2m:21s:794ms
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Created: (SOAG-82) Move filter, used for service validator, from pi4soa into Overlord code base
by Gary Brown (JIRA)
Move filter, used for service validator, from pi4soa into Overlord code base
----------------------------------------------------------------------------
Key: SOAG-82
URL: https://jira.jboss.org/jira/browse/SOAG-82
Project: SOA Governance
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Behavioural Monitoring
Affects Versions: 1.0 MR2
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0 MR2
The service validator for jbossesb was originally developed before Project Overlord was established. However the models and configuration files that the service validators use are stored in the ESB bundle: overlord-cdl-validator.esb
When Overlord is installed, the ant script sets up the global filter currently using the class: org.pi4soa.jbossesb.validator.ValidatorFilter
As part of a separate task, to enable the service validators to use a "hot deployment" mechanism to update the configuration being monitored, I propose to move the Overlord specific aspects of the service validator into the Overlord code base.
The impact of this change will be the configuration of the global filter. This can be updated in the M2 release, so that when it is next installed, it will configure the Overlord version of the filter - however if the ant script is not used to do the upgrade to M2, it is possible that a user will experience a problem.
I believe we just need to document this in the release note, to ensure deployment of M2 is done using the ant scripts.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months