[JBoss JIRA] Created: (JBESB-843) ftp-listener pollLatencySeconds property ignored
by Kevin Conner (JIRA)
ftp-listener pollLatencySeconds property ignored
------------------------------------------------
Key: JBESB-843
URL: http://jira.jboss.com/jira/browse/JBESB-843
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Tom Fennelly
Fix For: 4.2
The hudson builds have been failing recently because of a race in the QA FtpUnitTest.
The test specifies a pollLatencySeconds property of 5 seconds but this does not appear to be handled in the mapping to the new scheduler code. The consequence of this is that the listener receives a default value of 10 seconds.
The race occurs because the esb containing the test is undeployed after 10 seconds.
On my machine this does not cause a failure, the message processing occurs milliseconds before undeployment, but on the hudson machines it occurs just after. At this point the test has already failed.
We need to add support for mapping pollLatencySeconds.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Created: (JBESB-775) helloworld_hibernate_action - null values for onLoad
by Jaroslaw Kijanowski (JIRA)
helloworld_hibernate_action - null values for onLoad
----------------------------------------------------
Key: JBESB-775
URL: http://jira.jboss.com/jira/browse/JBESB-775
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Jaroslaw Kijanowski
Assigned To: Mark Little
When I add an item and list it (via jsp) I don't see these values in the console, only nulls:
14:44:54,921 INFO [STDOUT] Hibernate: select order0_.unique_id as unique1_0_, order0_.product as product0_, order0_.quantity as quantity0_, order0_.price as price0_ from orders order0_
14:45:05,722 INFO [STDOUT] onSave
14:45:05,903 INFO [STDOUT] Hibernate: insert into orders (product, quantity, price) values (?, ?, ?)
14:45:05,904 INFO [STDOUT]
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
14:45:05,905 INFO [STDOUT] id [0]product [Widgets] quantity [2] price [2.4]
14:45:05,905 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
14:45:05,936 INFO [STDOUT] Hibernate: select order0_.unique_id as unique1_0_, order0_.product as product0_, order0_.quantity as quantity0_, order0_.price as price0_ from orders order0_
14:45:05,956 INFO [STDOUT] onLoad
14:45:05,980 INFO [STDOUT]
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
14:45:05,980 INFO [STDOUT] id [1]product [null] quantity [null] price [null]
14:45:05,980 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Created: (JBESB-827) Scheduled Services: simple-schedule can not be reused by multiple services
by Burr Sutter (JIRA)
Scheduled Services: simple-schedule can not be reused by multiple services
--------------------------------------------------------------------------
Key: JBESB-827
URL: http://jira.jboss.com/jira/browse/JBESB-827
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Burr Sutter
Assigned To: Mark Little
Priority: Minor
Fix For: 5.0 Milestone Release 1
Attachments: jboss-esb.xml
<simple-schedule scheduleid="1-sec-trigger" frequency="1" repeatCount="2" />
can not be reused by 2 services. It causes this error during deployment of the .esb archive
Caused by: org.quartz.ObjectAlreadyExistsException: Unable to store Trigger with
name: '1-sec-trigger' and group: 'DEFAULT', because one already exists with thi
s identification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Created: (JBESB-833) Problems deploying to jboss-4.2.1.GA
by Tom Cunningham (JIRA)
Problems deploying to jboss-4.2.1.GA
------------------------------------
Key: JBESB-833
URL: http://jira.jboss.com/jira/browse/JBESB-833
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Tom Cunningham
Assigned To: Mark Little
Priority: Critical
Fix For: 4.2
Seeing this error on startup on jboss-4.2.1.GA with trunk deployed :
00:23:19,535 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
00:23:20,511 INFO [JBoss4ESBDeployer] create esb service, jbossesb.esb
00:23:20,547 INFO [DeadMessageQueue] Bound to JNDI name: queue/DeadMessageQueue
00:23:21,461 INFO [J2eeConnectionManager] initializing...
00:23:21,495 WARN [ServiceController] Problem starting service jboss.esb:deployment=jbossesb.esb
java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: org.jboss.soa.esb.schedule.SchedulingException: Failed to schedule job.
at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:122)
at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:78)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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(ServiceController.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 sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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:302)
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.GeneratedMethodAccessor18.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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(ServiceController.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(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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:302)
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(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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:613)
Caused by: org.jboss.soa.esb.ConfigurationException: org.jboss.soa.esb.schedule.SchedulingException: Failed to schedule job.
at org.jboss.soa.esb.listeners.config.ScheduleProviderFactory.createInstance(ScheduleProviderFactory.java:72)
at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:106)
... 94 more
Caused by: org.jboss.soa.esb.schedule.SchedulingException: Failed to schedule job.
at org.jboss.soa.esb.schedule.ScheduleProvider.addListener(ScheduleProvider.java:110)
at org.jboss.soa.esb.schedule.ScheduleProvider.addListener(ScheduleProvider.java:90)
at org.jboss.soa.esb.listeners.config.ScheduleProviderFactory.createInstance(ScheduleProviderFactory.java:64)
... 95 more
Caused by: org.quartz.SchedulerException: Based on configured schedule, the given trigger will never fire.
at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:609)
at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:238)
at org.jboss.soa.esb.schedule.ScheduleProvider.addListener(ScheduleProvider.java:108)
... 97 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months