id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
317 | XD-1339 | 02/20/2014 10:19:43 | Deployment manifest to support directing deployment to run on a group of servers | Need some kind of hint that a given deployment is to be run on a group of servers. That deployment would then be part of a partitioned work flow. Another item on this would be the "group" that the server is running in can be added to removed dynamically. The use case on this would be if the group of servers are running a max CPU capacity we can easily add another compute node. Likewise we can remove a server from the group if the servers are not being fully utilized. This issue is lightly linked to: https://jira.springsource.org/browse/XD-1337 | 8 |
318 | XD-1341 | 02/21/2014 15:24:58 | Support oracle jdbc configuration for XD batch job repository | Currently, hsqldb, postgres and mysql job repositories are supported. We need to add configurable oracle jdbc settings. | 2 |
319 | XD-1342 | 02/21/2014 18:04:42 | Configuration for RabbitMQ message bus concurrent consumers | By having the configuration option for concurrent consumers would help improve the performance of message consumption by the consumer modules when the ordering of the incoming messages don't matter. | 1 |
320 | XD-1343 | 02/24/2014 07:33:08 | Provide a conventional way to extend XD Container configuration | Provide an easy way for users to add beans (e.g., Gemfire cache configuration) or modify default XD configuration such as serializers, and message converters. A simple approach is to add a well known resource selector such as classpath*:META-INF/spring/xd/extensions or include this path in an extensible @Configuration base class. In addition, we should adopt conventional names for beans that are meant to be extended, e.g. use an xd. prefix. | 8 |
321 | XD-1344 | 02/24/2014 11:53:17 | Cannot undeploy stream that was created and deployed with a "." in the name | eserrano-mbp:spring-xd-1.0.0.M5 eserrano$ ./shell/bin/xd-shell _____ __ _______ / ___| (-) \ \ / / _ \ \ `--. _ __ _ __ _ _ __ __ _ \ V /| | | | `--. \ '_ \| '__| | '_ \ / _` | / ^ \| | | | /\__/ / |_) | | | | | | | (_| | / / \ \ |/ / \____/| .__/|_| |_|_| |_|\__, | \/ \/___/ | | __/ | |_| |___/ eXtreme Data 1.0.0.M5 | Admin Server Target: http://localhost:9393 Welcome to the Spring XD shell. For assistance hit TAB or type "help". xd:>stream list Stream Name Stream Definition Status ------------- --------------------------------------------------------- -------- eesstream.log http | transform --expression=payload.toUpperCase() | log deployed httptest http | file tictac time | log xd:>stream stream all stream create stream deploy stream destroy stream list stream undeploy xd:>stream undeploy --name stream undeploy --name required --name: the name of the stream to un-deploy; no default value xd:>stream undeploy --name eesstream.log Command failed org.springframework.xd.rest.client.impl.SpringXDException: The stream named 'eesstream' is not currently deployed xd:> | 1 |
322 | XD-1348 | 02/25/2014 07:38:50 | Allow end users to configure Rabbit MQ properties on the MessageBus (for acks, txs, etc). | This requires exposing properties to the ListenerContainer. Probably cleaner to inject the ListenerContainer into the RabbitMessageBus and expose property placeholders on the LC. Maybe do the same for RabbitAdmin as well. | 1 |
323 | XD-1351 | 02/25/2014 10:29:38 | Replace BeanDefinitionAddingBeanPostProcessor with Ordered Plugins | This will allow us to control the order of plugins and use plugin(s) to manage the common module context, replacing BeanDefinitionAddingBeanPostProcesser | 8 |
324 | XD-1355 | 02/27/2014 11:55:45 | Publish ContainerStoppedEvent when the container shutsdown | When the container shuts down, ContainerStoppedEvent should be published so that appropriate listeners would act on. Please refer to this discussion here: https://github.com/spring-projects/spring-xd/pull/612 | 2 |
325 | XD-1356 | 02/27/2014 11:58:49 | Hadoop distro option hdp20 is broken | Starting the shell with --hadoopDistro hdp20 causes this: Exception in thread "main" org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace [http://www.springframework.org/schema/hadoop] Offending resource: URL [jar:file:/Users/trisberg/Demo/spring-xd-1.0.0.BUILD-SNAPSHOT/shell/lib/spring-xd-shell-1.0.0.BUILD-SNAPSHOT.jar!/META-INF/spring/spring-shell-plugin.xml] Creating a stream "time | hdfs" in xd-singlenode started with --hadoopDistro hdp20 causes this: java.lang.IllegalStateException: Can't find class used for type of option 'codec': org.springframework.data.hadoop.store.codec.Codecs | 3 |
326 | XD-1360 | 02/28/2014 11:06:33 | Json information returned by curl does not reflect deployed status correctly | The Json information returned by curl does not reflect deployed status correctly. To recreate: 1. Start xd-singlenode 2. start xd-shell In the xd-shell (i). stream create --definition "time | log" --name ticktock (ii). stream list Note the status of the ticktock stream is deployed 3. open a new command prompt & type curl http://localhost:9393/streams/ticktock 4. Note the returned json stream: {"name":"ticktock","deployed":null,"definition":"time | log","links":[{"rel":"self","href":"http://localhost:9393/streams/ticktock"}]} 5. I would expect the json attribute "deployed" to be "true", but it is null. | 3 |
327 | XD-1364 | 03/03/2014 08:43:58 | Upgrade to SHDP 2.0 M6 | The YARN support in M6 changes most of the config properties, need to update XD to use new ones. | 5 |
328 | XD-1365 | 03/04/2014 03:16:08 | StreamDeployer.deleteAll() does not handle dependency tracking | create a composed module, use it in a stream, delete ALL streams. Try to delete the composed module => fails thinking that it's still used by the stream | 2 |
329 | XD-1368 | 03/04/2014 14:24:40 | Refactor container to remove shared module context as a separate context | The main container context becomes the shared context for modules. | 8 |
330 | XD-1369 | 03/05/2014 02:28:49 | Using hdfs sink throwing an error | I am trying to use HDFS as sink while creating streams and I am encountering the following error : Please refer attached document : Exception - localhost - 8020.txt The fs.default.name set in hadoop.properties is : fs.default.name=hdfs://localhost:8020 I have also tried the following variation in the hadoop.properties file : fs.default.name=hdfs://127.0.0.2:8020 fs.default.name=hdfs://127.0.0.2:50070 Using these values are also throwing me exceptions as mentioned in the following files attached : Exception - 127.0.0.2 - 8020.txt Exception - 127.0.0.2 - 50070.txt We are using : Pivotal HD 1.0.1 spring-xd-1.0.0.M5-dist Kindly let us know the way around for this issue. | 5 |
331 | XD-1370 | 03/05/2014 05:50:56 | Serialization over data transport fails for classes that are module specific | Given: the counter example from the guide is run with redis enabled: xd-singlenode --transport redis --store redis When: a stream is created stream create --name springtweets --definition "twittersearch --consumerKey=<your_key> --consumerSecret=<your_secret> --query=spring | file --dir=/tweets/" Then: An exception is thrown: Exception in thread "inbound.springtweets.0-redis:queue-inbound-channel-adapter35" org.springframework.integration.MessageHandlingException: error occurred in message handler [springtweets.0.convert.bridge] at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:79) at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:115) at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:102) at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:178) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:149) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:94) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:42) at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:86) at org.springframework.integration.endpoint.MessageProducerSupport.sendMessage(MessageProducerSupport.java:92) at org.springframework.integration.redis.inbound.RedisQueueMessageDrivenEndpoint.popMessageAndSend(RedisQueueMessageDrivenEndpoint.java:207) at org.springframework.integration.redis.inbound.RedisQueueMessageDrivenEndpoint.access$300(RedisQueueMessageDrivenEndpoint.java:51) at org.springframework.integration.redis.inbound.RedisQueueMessageDrivenEndpoint$ListenerTask.run(RedisQueueMessageDrivenEndpoint.java:286) at java.lang.Thread.run(Thread.java:724) Caused by: org.springframework.integration.x.bus.serializer.SerializationException: unable to deserialize [null]. Class not found. at org.springframework.integration.x.bus.MessageBusSupport.deserializeConsumerPayload(MessageBusSupport.java:247) at org.springframework.integration.x.bus.MessageBusSupport.transformPayloadForConsumer(MessageBusSupport.java:191) at org.springframework.integration.x.bus.MessageBusSupport.transformPayloadForConsumerIfNecessary(MessageBusSupport.java:168) at org.springframework.integration.x.redis.RedisMessageBus.access$300(RedisMessageBus.java:57) at org.springframework.integration.x.redis.RedisMessageBus$ReceivingHandler.handleRequestMessage(RedisMessageBus.java:176) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:142) at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:73) ... 13 more Caused by: java.lang.ClassNotFoundException: org.springframework.social.twitter.api.Tweet at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:190) at org.springframework.integration.x.bus.MessageBusSupport.deserializeConsumerPayload(MessageBusSupport.java:241) ... 19 more | 3 |
332 | XD-1371 | 03/05/2014 09:32:22 | Clarify API or syntax for managing deployment parameters | Suppose we have 3 environements of Spring XD : - Dev environment - Test environment - Prod environement ( Suppose whe develop the script bellow: ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// stream1 = http | filter --expression=payload.contains('toto') | file --dir=/tmp/toto stream2 = http | filter --expression=payload.contains('titi') | file --dir=/tmp/titi ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// When we need to deploy the script in Test and Prod environements , we must modify "dir" option of "file" sink. This is very easy when there is not a lot of options and when we have a small factory team. But in a big factory environment this will be problematic. In order to industrialize deployment, it would be convenient to implement in DSL a directory interface API or something equivalent like below: Suppose we call this directory interface XDDI ... like "XD Directory Interface" :-) The script can be like that: ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// stream1 = http | filter --expression=payload.contains('toto') | file --dir=XDDI('totoKey') stream2 = http | filter --expression=payload.contains('titi') | file --dir=XDDI('titiKey') ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// The XDDI keys are defined in a centralized directory interface (admin console or XDDI.properties) The XDDI keys/values in Dev environment: ///////////////////////////////////// totoKey=/tmp/toto titiKey=/tmp/titi ///////////////////////////////////// The XDDI keys/values in Test environment: ////////////////////////////////////////// totoKey=/tartempion/toto titiKey=/petaouchnok/titi ///////////////////////////////////////// The XDDI keys/values in Prod environment: ///////////////////////////////////////////////////// totoKey=/vavoirlabasijysuis/toto titiKey=/vavoirlabasijysuis/titi ///////////////////////////////////////////////////// When the script is deployed in Test or Prod environement, if the script contain a key that is not defined in centralized directory, the deployment fail. This will reduce errors risks in a big factory environnement (several hundred parameters and signifiant team turnover). | 3 |
333 | XD-1372 | 03/05/2014 14:40:58 | Update Reactor integration to align 1.1 changes | Need to update the spring-xd-extension-reactor support to reflect the changes to Reactor refactorings introduced in v1.1. | 0 |
334 | XD-1373 | 03/06/2014 05:56:54 | HSQL always started, even when using other database | I set the config/xd-config.yml properties to use MySQL including this profiles: active: default,mysql When XD ADmin starts I still see HSQL server started and localhost:9393/env shows: "profiles": [ "adminServer", "hsqldb", "default" ], | 5 |
335 | XD-1380 | 03/09/2014 17:24:57 | Can't create http source while TCP is used as a source and sink on singlenode | [Problem] Can't use tcp source, sink and http together on Single Node. While creating tests for CI I tried to create the following: [Steps to Reproduce] xd:>stream create fooOut --definition "tcp|file" Created new stream 'fooOut' xd:>stream create fooIn --definition "http --port=9002|tcp" Command failed org.springframework.xd.rest.client.impl.SpringXDException: Failed to bind to: 0.0.0.0/0.0.0.0:9000. Possibly the port is already in use. Even if I use different ports for the tcp I still get failures pointing to 9000. [Extra Notes] The stream below is works. xd:>stream create fooOut --definition "tcp|file" Created new stream 'fooOut' xd:>stream create fooIN --definition "time|tcp" *Stack Trace Attached* | 5 |
336 | XD-1389 | 03/11/2014 13:35:36 | Sometimes getting NPE when master step runs for ftphdfs job | Depending in the ftp server used there seems to be an error condition that generates an NullPointerException. These are the steps to reproduce this: {code} job create --name myftphdfs --definition "ftphdfs --host=ftp.sunet.se --port=21" job launch --name myftphdfs --params {"remoteDirectory":"/pub/music/Abba","hdfsDirectory":"/xd/ftp"} {code} Exception: {code} 16:31:38,385 ERROR redisInboundAdapter-redis:queue-inbound-channel-adapter1 step.AbstractStep:225 - Encountered an error executing the step java.lang.NullPointerException at org.springframework.batch.integration.partition.MessageChannelPartitionHandler.handle(MessageChannelPartitionHandler.java:140) at org.springframework.batch.core.partition.support.PartitionStep.doExecute(PartitionStep.java:105) at org.springframework.batch.core.step.AbstractStep.execute(AbstractStep.java:198) at org.springframework.batch.core.job.SimpleStepHandler.handleStep(SimpleStepHandler.java:144) at org.springframework.batch.core.job.flow.JobFlowExecutor.executeStep(JobFlowExecutor.java:64) at org.springframework.batch.core.job.flow.support.state.StepState.handle(StepState.java:67) at org.springframework.batch.core.job.flow.support.SimpleFlow.resume(SimpleFlow.java:163) at org.springframework.batch.core.job.flow.support.SimpleFlow.start(SimpleFlow.java:142) at org.springframework.batch.core.job.flow.FlowJob.doExecute(FlowJob.java:134) at org.springframework.batch.core.job.AbstractJob.execute(AbstractJob.java:304) at org.springframework.batch.core.launch.support.SimpleJobLauncher$1.run(SimpleJobLauncher.java:135) at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:50) at org.springframework.batch.core.launch.support.SimpleJobLauncher.run(SimpleJobLauncher.java:128) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.springframework.batch.core.configuration.annotation.SimpleBatchConfiguration$PassthruAdvice.invoke(SimpleBatchConfiguration.java:117) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) at com.sun.proxy.$Proxy40.run(Unknown Source) at org.springframework.batch.integration.launch.JobLaunchingMessageHandler.launch(JobLaunchingMessageHandler.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.expression.spel.support.ReflectiveMethodExecutor.execute(ReflectiveMethodExecutor.java:63) at org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:122) at org.springframework.expression.spel.ast.MethodReference.access$100(MethodReference.java:44) at org.springframework.expression.spel.ast.MethodReference$MethodValueRef.getValue(MethodReference.java:258) at org.springframework.expression.spel.ast.CompoundExpression.getValueInternal(CompoundExpression.java:85) at org.springframework.expression.spel.ast.SpelNodeImpl.getTypedValue(SpelNodeImpl.java:113) at org.springframework.expression.spel.standard.SpelExpression.getValue(SpelExpression.java:111) at org.springframework.integration.util.AbstractExpressionEvaluator.evaluateExpression(AbstractExpressionEvaluator.java:163) at org.springframework.integration.util.MessagingMethodInvokerHelper.processInternal(MessagingMethodInvokerHelper.java:268) at org.springframework.integration.util.MessagingMethodInvokerHelper.process(MessagingMethodInvokerHelper.java:142) at org.springframework.integration.handler.MethodInvokingMessageProcessor.processMessage(MethodInvokingMessageProcessor.java:75) at org.springframework.integration.handler.ServiceActivatingHandler.handleRequestMessage(ServiceActivatingHandler.java:71) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:170) at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:78) at org.springframework.integration.dispatcher.AbstractDispatcher.tryOptimizedDispatch(AbstractDispatcher.java:128) at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:101) at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:97) at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:255) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:223) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:114) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:44) at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:92) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.sendMessage(AbstractReplyProducingMessageHandler.java:260) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.sendReplyMessage(AbstractReplyProducingMessageHandler.java:241) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.produceReply(AbstractReplyProducingMessageHandler.java:205) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleResult(AbstractReplyProducingMessageHandler.java:199) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:177) at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:78) at org.springframework.integration.dispatcher.AbstractDispatcher.tryOptimizedDispatch(AbstractDispatcher.java:128) at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:101) at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:97) at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:255) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:223) at org.springframework.xd.dirt.plugins.job.JobPlugin.launch(JobPlugin.java:176) at org.springframework.xd.dirt.module.ModuleDeployer.launchModule(ModuleDeployer.java:380) at org.springframework.xd.dirt.module.ModuleDeployer.processLaunchRequest(ModuleDeployer.java:330) at org.springframework.xd.dirt.module.ModuleDeployer.handleLaunch(ModuleDeployer.java:316) at org.springframework.xd.dirt.module.ModuleDeployer.handleMessageInternal(ModuleDeployer.java:169) at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:78) at org.springframework.integration.config.ServiceActivatorFactoryBean$1.handleRequestMessage(ServiceActivatorFactoryBean.java:83) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:170) at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:78) at org.springframework.integration.dispatcher.AbstractDispatcher.tryOptimizedDispatch(AbstractDispatcher.java:128) at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:101) at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:97) at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:255) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:223) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:114) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:44) at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:92) at org.springframework.integration.endpoint.MessageProducerSupport.sendMessage(MessageProducerSupport.java:98) at org.springframework.integration.redis.inbound.RedisQueueMessageDrivenEndpoint.popMessageAndSend(RedisQueueMessageDrivenEndpoint.java:211) at org.springframework.integration.redis.inbound.RedisQueueMessageDrivenEndpoint.access$300(RedisQueueMessageDrivenEndpoint.java:50) at org.springframework.integration.redis.inbound.RedisQueueMessageDrivenEndpoint$ListenerTask.run(RedisQueueMessageDrivenEndpoint.java:290) at org.springframework.integration.util.ErrorHandlingTaskExecutor$1.run(ErrorHandlingTaskExecutor.java:52) at java.lang.Thread.run(Thread.java:724) {code} | 5 |
337 | XD-1390 | 03/11/2014 15:22:13 | Investigate missing stepExecutions in JobRepository.getLastJobExecution() | When the job is run with its jobParameters by SimpleJobLauncher, its lastJobExecution's stepExecutions are checked for UNKNOWN status to throw JobRestartException. It looks like the stepExecutions for the lastJobExecution are never set and the collection 'stepExecutions' is not fetched from job repository. Hence, not sure if the following condition in SimpleJobLauncher's run(final Job job, final JobParameters jobParameters) would ever get executed: for (StepExecution execution : lastExecution.getStepExecutions()) { if (execution.getStatus() == BatchStatus.UNKNOWN) { //throw throw new JobRestartException("Step [" + execution.getStepName() + "] is of status UNKNOWN"); }//end if }//end for | 3 |
338 | XD-1398 | 03/14/2014 11:01:54 | Admin servers should write streams to and delete them from ZooKeeper | This should also enable removal of any StreamDefinitionRepository code. The state should be written as a data node at the stream level (e.g. /xd/streams/mystream {state=...}) For now we at least need to support the boolean --deploy=true|false flag. If that is true, then the leader Admin will deploy the modules of the stream across available containers (XD-1399) | 8 |
339 | XD-1399 | 03/14/2014 11:04:03 | Admin leader should watch ZooKeeper for Stream deployment requests | The Stream deployment requests will be written to /xd/streams/streamname and the data on that node will include the state or a boolean indicator (for now) of whether it should be deployed. When a Stream is deployed, the leader will consult its Container cache and write the modules to the various /xd/deployments child nodes (see XD-1400). | 8 |
340 | XD-1400 | 03/14/2014 11:08:47 | Containers should listen for Module deployment requests and their deletions | The Admin leader will write each Module deployment request to a child node of /xd/deployments for a selected Container (see XD-1399). That Container-specific (persistent) child node needs to be created by the Container at the same time as it creates its ephemeral node under /xd/containers. The Container should then deploy the Module. If that same node is subsequently deleted, the Container should undeploy the Module. | 8 |
341 | XD-1401 | 03/14/2014 12:13:28 | Add new reactor tcp module | A reactor based TCP module that would support some basic CODECS. Should evaluate if this new TCP module would subsume the current reactor-syslog module functionality or if the reactor-syslog module should be enhanced/upgradted. | 8 |
342 | XD-1407 | 03/17/2014 11:06:23 | Create a throughput sink | The throughput module would expect a payload of the type Message<byte[]> and look for the byte[] to be START or STOP strings to trigger a throughput measurement. https://github.com/spring-projects/spring-xd/tree/master/extensions would be the place for the module to live. | 5 |
343 | XD-1409 | 03/17/2014 13:27:57 | GemFire sink properties missmatch | The documentation lists the gemfire-server sink module's attributes to be 'gemfireHost' and 'gemfirePort'. In the module/code they are 'host' and 'port'. The other attributes are correct. | 0 |
344 | XD-1410 | 03/17/2014 14:28:39 | XD EC2 needs to bootstrap ZOOKEEPER at installation time. | Startup zookeeper on EC2 cluster instances. | 5 |
345 | XD-1411 | 03/18/2014 09:24:23 | Create xd-yarn script | Create an xd-yarn script that is more "Cloud Foundry" like - xd-yarn push -p <path-to-unzipped-yearn-distro> xd-yarn start admin xd-yarn start container | 5 |
346 | XD-1416 | 03/18/2014 17:11:35 | When there are no wiretap listeners don't publish messages | Being able to listen to a stream at any point has a significant performance impact. The reason for the impact is the message needs to be "serialized + transported + deserialized" to other members even if there is no one listening. This "serialized + transported + deserialized" processes happens for each step in a flow - source | process | sink. Recommend creating some kind of protocol for wiretaps that allows members to know if there is someone listening in the grid so they will emit the data. Likewise we need to deregister the listener if the wiretap is deleted. | 8 |
347 | XD-1417 | 03/19/2014 03:26:00 | Create RPM for distribution | Package SpringXD into an RPM install path = /opt/pivotal/spring-xd-1.0.0.M5 with symlink /opt/pivotal/spring-xd -> current version init.d scripts to start/stop/status service springxd-admin start|stop|status service springxd-container start|stop|status user/group = springxd/pivotal Host springxd rpm in Pivotal repo yum install springxd Support RHEL/CentOS version 5 and 6? (tested on latest updates) Support for 32 and 64 bits Support Java 1.6 and 1.7 | 8 |
348 | XD-1418 | 03/19/2014 03:37:44 | Create subproject spring-xd-machine-learning-analytics | This project contains core abstractions that will allow for multiple implementations of a machine learning algorithm to be implemented via integration with various existing libraries or custom code implementations. The initial code for this has been developed in a separate github repo and is located here https://github.com/thomasdarimont/spring-xd/tree/feature/advanced-analytics-support/spring-xd-analytics/src/main/java/org/springframework/xd/analytics/model The model can assume its use in evaluation of the model inside a stream where the data structure is a Tuple. Note, it maybe useful to consider Message<Tuple> in case any metadata outside the core 'input data' is required to help guide the evaluation. The build.gradle file should be updated such that there is a new build artifact spring-xd-machine-learning-analytics.jar along the lines of our other build artifacts. Open to other naming suggestions. | 8 |
349 | XD-1420 | 03/19/2014 03:52:28 | Create a JPMML module that will evaluate a model. | A analytical model should be evaluated as a processor in a stream. The model evaluation will take the input variables from a Tuple and output variable will be placed into the tuple as well. A strawman of the stream definition can be stream create --definition " SOURCE | jpmml ‘fraud-detection’ | PROC1 … | PROCN " --name stream1 Using profiles and playing all implementations of the analytical model in the same module lib directory, it maybe possible to select one of multiple implementations in the form " SOURCE | analytic --library=jpmml --name=‘fraud-detection’ | PROC1 … | PROCN " such that the core module name is the same but parameterized by what library type to use. This may be problematic in that different libraries may have incompatible dependencies. The analytical model can define the names of input and output fields, so at a minimum a name is required, however to easily adapt a given analytic model evaluation to a specific source modules output, it seems desirable to specify which fields are to be used as input, overriding the names of the input fields could be done in a manner such as jpmml –name=linear-regresssion –inputFields=a,b,c | 8 |
350 | XD-1424 | 03/19/2014 11:30:41 | Docs could use link to Tuple artifacts | The Tuple documentation, http://docs.spring.io/spring-xd/docs/1.0.0.M5/reference/html/#tuples, has no link or reference to the Jar(s) and/or Maven artifacts required to use Tuples in a project. Took me a bit of searching to find the Maven artifacts. Would be nice to include the jar name and maven/gradle config. In Gradle (from the spring repo maven { url "http://repo.spring.io/libs-snapshot" }): compile 'org.springframework.xd:spring-xd-tuple:1.0.0.M5' | 0 |
351 | XD-1428 | 03/20/2014 08:35:59 | Log Hadoop Distro and ZK client connect info on Container startup | It would be nice to display container config logging with the hadoop distro and zookeeper client connect being used when the container starts up. | 3 |
352 | XD-1432 | 03/21/2014 13:22:19 | Configure servers to use VanillaHealthEndpoint | The standard SimpleHealthIndicator that boot performs a database test that fails in xd-container since it does not require the use of a database. | 3 |
353 | XD-1434 | 03/21/2014 15:11:15 | Improvements to Modules Tab | 1. Get listing of job modules 2. Remove version and action column 3. Text to say creating definitions from available modules in the UI is forthcoming, link to https://github.com/spring-projects/spring-xd/wiki/Batch-Jobs#creating-a-job for how to do this in the command line. 4. Hardcode an association between spring xd out of the box module names and a description. 5. Add button to display the XML file that defines the job module | 8 |
354 | XD-1435 | 03/21/2014 15:14:34 | Improvements to Executions Tab | 1. Add quick filter 2. The table should have columns for name | instance | execution id Getting the name might require a bit of extra work given some limitations with JSON serialization and cycles in the current object returned from spring batch. 3. The restart action should appear only if the job is restartable and the status was failed. | 1 |
355 | XD-1436 | 03/21/2014 15:17:29 | Misc cleanup in UI | 0. Remove home page with sign in and upper right hand corner with user login info. 1. Change the word template to modules in the tab 2. Different text for each of the tabs, “modules, definition, deployments, scheduled” 3. Definitions tab to have text along the lines "“allows you to deploy and undeploy batch job definitions" add links to help on how to do that in the CLI. 4. Deployments tab a creating new definitions, - parameters needs to be space on parameters, “Job Parameters for Job XYZ” after clicking launch. b. comment out scheduler button c. add quick filter 5. Scheduler tab a. comment out tab | 5 |
356 | XD-1438 | 03/22/2014 14:38:43 | RabbitMQ port wrong in Docs | The documentation (http://docs.spring.io/spring-xd/docs/1.0.0.M5/reference/html/#_using_rabbitmq) list the default RabbitMQ port as 5674. It is 5672 and is correct in the SXD config. | 0 |
357 | XD-1439 | 03/24/2014 04:16:15 | Investigate module classloader leakage | See report at https://github.com/spring-projects/spring-xd/issues/661 This should not happen as the module holds the classes that hold the classloader, but who knows. An integration test that verifies this would be nice, albeit tricky. | 5 |
358 | XD-1440 | 03/24/2014 04:20:54 | Allow re-use of a module classloader | See report at https://github.com/spring-projects/spring-xd/issues/661 It would be good indeed to allow this (eg by having a WeakHashMap<Classloader, type+name> map in the global context). The caveat though, is that any statics used by the module would be shared too. We can make this an opt-out though (I think that sharing by default makes sense) by having a flag in the module .properties manifest | 8 |
359 | XD-1442 | 03/24/2014 11:11:16 | Remove Hadoop distro Enum options | Please see the discussion here: https://github.com/spring-projects/spring-xd/pull/655/files#r10892925 | 3 |
360 | XD-1446 | 03/25/2014 09:29:10 | Update spring-data-hadoop dependency and add new Hadoop distros | Update to Spring for Apache Hadoop 2.0 RC3 Add support for new hadoop distros: - Pivotal HD 2.0 (phd20) - Hortonworks HDP 2.1 (hdp21) - Cloudera CDH5 (cdh5) | 8 |
361 | XD-1448 | 03/25/2014 13:44:55 | SpringXD logs error and large stack trace when metric can't be found. Distracting. | When a REST client of SpringXD (i.e., a dashboard) attempts to query (GET) a metric (e.g., counter, gauge, etc.) that does not exist the admin sever logs an ERROR and a large stack trace (attached). In usage of Spring XD we see this frequently because a dashboard is running but the streams and counters have not been created quite yet, or initialized by messages flowing through the streams. With a polling dashboard this results in a lot of distracting and large stack traces in the logs that are not actually issues. I would suggest logging a one line warning or info message instead of the error and stack trace. | 1 |
362 | XD-1456 | 03/28/2014 07:13:51 | Allow user to configure tests with DI | With the addition of sinks and sources that require connections with external entities (hadoop, JMS, JDBC, ...) the environment setup is getting unwieldy. * Integrate SpringJUnit4ClassRunner.class into acceptance tests. * Retrieve environment variables via Dependency injection from application.properties. * Utilize profiles for --local single node --local cluster --ec2 single node --ec2 cluster | 3 |
363 | XD-1460 | 03/31/2014 10:28:57 | Remove jmxEnabled as a cmdLine option and enable JMX by default | After some discussion and voting, we decided to remove "jmxEnabled" as a command line option and have JMX enabled by default. This can be disabled from xd-config.yml externally. | 3 |
364 | XD-1463 | 03/31/2014 13:55:17 | Delete post module and CF profile | This would get rid of the CF specific post module, keeping the general abstraction of 'http' source across CF and non-CF environments. | 1 |
365 | XD-1466 | 04/01/2014 01:18:32 | Update XdEc2Validation to reference <root>/management endpoint | change "/jolokia/list"; to "/management/jolokia/list"; etc. | 2 |
366 | XD-1474 | 04/02/2014 06:16:50 | Refactor StreamParser to return a StreamDefinition | {code} StreamDefinition sd = streamParser.parse(name, dslText); {code} We should also consider explicit methods such as parseStream (so that parseJob and parseComposedModule are at least separate methods, if not separate parser classes that share the common parser support class that is the core of today's parser). The parsing for "completion providers" should probably be spun off to its own class as well. In the end, there should be no need for a ParsingContext enum but rather, more explicitly named methods and dedicated classes if that seems like the right approach. the StreamDefinition should be composed of "ModuleDescriptors" (that name is not set in stone) and other Stream-level metadata like source/sink channels consider merging some of StreamFactory code there, and the rest into StreamDeployer merge ModuleDescriptor and ModuleDeploymentRequest as part of this effort (again, a new name could be considered, but ModuleDescriptor should take precedence over ModuleDeploymentRequest), and note in the process that ModuleDescriptor was originally designed to be immutable (taking constructor args), but as we migrated the prototype code into XD itself, this was violated. We may want to consider a builder approach, and we likely want to avoid the need for a ModuleDefinition within the ModuleDescriptor. | 8 |
367 | XD-1475 | 04/02/2014 06:23:18 | Improve Exception handling for ZooKeeper data access | Currently we have many catch(Exception) blocks that simply wrap and rethrow RuntimeExceptions. We should create at least a top-level RuntimeException of our own, within the XD Exception hierarchy, and possibly a hierarchy of RuntimeExceptions extending from that, and mapping to the various checked Exceptions that can occur in ZooKeeper data access. Also, we should not be re-wrapping those Exceptions that are already RuntimeExceptions, so we should consider a ZooKeeperExceptionHandler (and although I'm typically hesitant to recommend it, this might be a case where a static util method is the right approach). | 8 |
368 | XD-1479 | 04/02/2014 06:57:39 | DefaultContainerMatcher should make a better attempt at round-robin distribution | Currently the index is used globally but applied to a range of candidates that can differ based on the match criteria per invocation. | 2 |
369 | XD-1480 | 04/02/2014 07:25:44 | Merge Module.Type and ModuleType | Also likely rename, remove, or replace that Module (maybe can be supplanted by ModuleDescriptor when used in the refactored parser). Also, considering the "url" property is not necessary (vestige of the prototype), all we'd be left with here is the Module name and type, which are used to identify a Module uniquely. Therefore this Module could be renamed to ModuleKey or something. It could be used within the StreamDefinition itself (e.g. getDescriptor(moduleKey)). | 2 |
370 | XD-1493 | 04/06/2014 17:48:50 | xd-shell tab completion missing for http post/get | xd-shell tab completion missing for 'http post' and 'http get' cli commands. Typing "xd:>http post" <tab> <tab> gives no suggestions event though --file or --data are required. | 1 |
371 | XD-1494 | 04/06/2014 17:51:16 | OS commands no longer supports whitespace/arguments in M6 | OS commands, i.e., "!" doesn't support arguments in M6; it did in M5. The following gives an error: xd:>! ls / You cannot specify option '' more than once in a single command No arguments or whitespace works: xd:>! ls command is:ls spring-shell.log xd-shell xd-shell.bat | 1 |
372 | XD-1495 | 04/06/2014 20:02:06 | xd:>runtime modules gives error from CLI | xd:>runtime modules Command failed org.springframework.xd.rest.client.impl.SpringXDException: java.lang.RuntimeException: org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /xd/deployments/modules/4dc55d87-125b-4e4a-a76e-82bb6980820d/TickTock.sink.log-1/metadata This is on OSX running in distributed mode with --transport rabbit --hadoopDistro hadoop22, redis 2.8.8, rabbit 3.2.3, hadoop 2.2.0, and zookeeper 3.4.5. | 1 |
373 | XD-1496 | 04/07/2014 09:38:28 | Exception thrown when accessing Jolokia via the management context path | When trying to access Jolokia via the management/jolokia (http://localhost:9393/management/jolokia) I get the following exception. {"error_type":"java.lang.IllegalArgumentException","error":"java.lang.IllegalArgumentException : No type with name 'management' exists","status":400,"stacktrace":"java.lang.IllegalArgumentException: No type with name 'management' exists\n\tat org.jolokia.util.RequestType.getTypeByName(RequestType.java:69)\n\tat org.jolokia.request.JmxRequestFactory.createGetRequest(JmxRequestFactory.java:94)\n\tat org.jolokia.http.HttpRequestHandler.handleGetRequest(HttpRequestHandler.java:78)\n\tat org.jolokia.http.AgentServlet$3.handleRequest(AgentServlet.java:298)\n\tat org.jolokia.http.AgentServlet.handle(AgentServlet.java:229)\n\tat org.jolokia.http.AgentServlet.doGet(AgentServlet.java:194)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:621)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:728)\n\tat org.springframework.web.servlet.mvc.ServletWrappingController.handleRequestInternal(ServletWrappingController.java:158)\n\tat org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:154)\n\tat org.springframework.boot.actuate.endpoint.mvc.JolokiaMvcEndpoint.handle(JolokiaMvcEndpoint.java:120)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat java.lang.reflect.Method.invoke(Method.java:606)\n\tat org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:215)\n\tat org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132)\n\tat org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)\n\tat org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:749)\n\tat org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:689)\n\tat org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:83)\n\tat org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:938)\n\tat org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:870)\n\tat org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:961)\n\tat org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:852)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:621)\n\tat org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:837)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:728)\n\tat org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)\n\tat org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)\n\tat org.springframework.boot.actuate.trace.WebRequestTraceFilter.doFilter(WebRequestTraceFilter.java:115)\n\tat org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)\n\tat org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)\n\tat org.springframework.boot.actuate.autoconfigure.EndpointWebMvcAutoConfiguration$ApplicationContextFilterConfiguration$1.doFilterInternal(EndpointWebMvcAutoConfiguration.java:137)\n\tat org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:108)\n\tat org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)\n\tat org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)\n\tat org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:77)\n\tat org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:108)\n\tat org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)\n\tat org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)\n\tat org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:88)\n\tat org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:108)\n\tat org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)\n\tat org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)\n\tat org.springframework.boot.actuate.autoconfigure.MetricFilterAutoConfiguration$MetricsFilter.doFilterInternal(MetricFilterAutoConfiguration.java:85)\n\tat org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:108)\n\tat org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)\n\tat org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)\n\tat org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)\n\tat org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)\n\tat org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)\n\tat org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:680)\n\tat org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)\n\tat org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)\n\tat org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)\n\tat org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)\n\tat org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)\n\tat org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)\n\tat org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1680)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat java.lang.Thread.run(Thread.java:724)\n"} | 5 |
374 | XD-1500 | 04/07/2014 11:41:27 | Stream deployment race condition | When a container is started, the leader admin will scan the deployed streams to determine if any have modules that need to be deployed on the new container. When a stream is deployed, the leader admin will select containers to deploy modules to. If a new container and stream are deployed at the same time, there is the window for a race condition where both attempt to deploy a module to a container. This can be solved by (at least one) of the following: * Consider using a single thread in the admin leader to handle all ZooKeeper updates. This means that the handling of new containers and stream deployment requests will not happen concurrently. * Trap the {{NodeExists}} exception when creating the {{/xd/deployments/modules/...}} node in ZooKeeper | 5 |
375 | XD-1501 | 04/07/2014 11:44:19 | IP address used as default data when creating paths | Invoking {{Paths.ensurePath}} is creating a default value of the host IP address instead of the expected "empty" value. | 1 |
376 | XD-1502 | 04/07/2014 11:51:45 | Investigate failing LocalSingleNodeStreamDeploymentIntegrationTests | Investigate the failing test LocalSingleNodeStreamDeploymentIntegrationTests.moduleChannelsRegisteredWithMessageBus: {noformat} java.lang.AssertionError: expected:<3> but was:<0> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:555) at org.junit.Assert.assertEquals(Assert.java:542) at org.springframework.xd.dirt.stream.AbstractSingleNodeStreamDeploymentIntegrationTests.moduleChannelsRegisteredWithMessageBus(AbstractSingleNodeStreamDeploymentIntegrationTests.java:270) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) {noformat} This can be most easily reproduced on Ubuntu. | 1 |
377 | XD-1505 | 04/07/2014 15:58:58 | Documentation typo in JSON SPEL filter | In the JSON SPEL Filter twitter example here: http://docs.spring.io/spring-xd/docs/1.0.0.M5/reference/html/#filter "hashTags" should not have a capital 'T'. Should be "hashtags". | 1 |
378 | XD-1507 | 04/07/2014 16:45:16 | Prevent submiting jobs that are not currently deployed using Admin UI | Job modules "Launch" and "Schedule" command buttons are active even if the job module isn't deployed or has been destroyed. Get errors like: "Yikes, something bad happened while launching job myjob4" "The job named 'myjob4' is not currently deployed" | 3 |
379 | XD-1508 | 04/07/2014 16:47:31 | All jobs end up on the same container node | The jobs aren't spread evenly across available container nodes as they are created/deployed. I had 3 nodes but only one has the job modules. [zk: localhost:2181(CONNECTED) 56] ls /xd/deployments/modules/621230e0-a089-4fbe-afc8-611ae527fcbc [myjob9.job.jdbchdfs-0, myjob5.job.jdbchdfs-0, myjob8.job.jdbchdfs-0, myjob4.job.jdbchdfs-0, myjob6.job.jdbchdfs-0, myjob7.job.jdbchdfs-0] [zk: localhost:2181(CONNECTED) 57] ls /xd/deployments/modules/6969579c-0cf4-4cc1-8e21-e01d73a70965 [] [zk: localhost:2181(CONNECTED) 58] ls /xd/deployments/modules/d0667cd1-a57a-4279-b7fb-dd63e4dd40d4 [] | 3 |
380 | XD-1517 | 04/08/2014 17:06:29 | Change request mapping for removing a stream deployment in XDController | Currently _deployments - with an understore in XDController should be something else. Need to segment up the url space better for stream/jobs to avoid a clash. | 3 |
381 | XD-1520 | 04/09/2014 06:45:40 | Push ${xd.stream.name} into POJO defaults | See XD-1283. We've been waiting for 1283 to change constructs like {noformat} attr="${name:${xd.stream.name}}" to just {noformat} attr="${name}" {noformat} Turns out we can simply push down the ${xd.stream.name} bit in the default value (most likely initialization of a field in a POJO metadata class) and it will work just fine. We can also consider: - providing a fake value for those placeholders to use when doing "module info" (ie user will see "<name of the stream>" instead of "${xd.stream.name}" | 8 |
382 | XD-1524 | 04/09/2014 12:19:54 | Create small documentation section on jmx/monitoring functionalty | Should mention jolokia, how to turn on/off boot/jolokia http metric/monitoring and jmx. Mention the naming strategy to identify modules running in a stream. | 1 |
383 | XD-1525 | 04/09/2014 13:56:03 | Need better error handling for module info shell command | Would be better to provide a more useful message, e.g. "The module name must be of the form <module-type>:<module-name>" xd:>module info --name time java.lang.StringIndexOutOfBoundsException: Failed to convert 'time' to type QualifiedModuleName for option 'name,' String index out of range: -1 xd:>module info --name sink/time java.lang.StringIndexOutOfBoundsException: Failed to convert 'sink/time' to type QualifiedModuleName for option 'name,' String index out of range: -1 xd:>module info --name sink:time Command failed org.springframework.xd.rest.client.impl.SpringXDException: NullPointerException xd:>module info --name source:time Information about source module 'time': | 1 |
384 | XD-1526 | 04/09/2014 15:04:44 | Exception when accessing CDH4 namenode | Get exception when accessing cdh4 from shell - java.lang.UnsupportedOperationException: This is supposed to be overridden by subclasses. at com.google.protobuf.GeneratedMessage.getUnknownFields most likely due to protobuf-java-2.5.0.jar being on the main classpath now Full stack trace: {code} trisberg@carbon:~/Test$ ./spring-xd-1.0.0.BUILD-SNAPSHOT/shell/bin/xd-shell --hadoopDistro cdh4 16:55:22,680 WARN main conf.Configuration:824 - fs.default.name is deprecated. Instead, use fs.defaultFS _____ __ _______ / ___| (-) \ \ / / _ \ \ `--. _ __ _ __ _ _ __ __ _ \ V /| | | | `--. \ '_ \| '__| | '_ \ / _` | / ^ \| | | | /\__/ / |_) | | | | | | | (_| | / / \ \ |/ / \____/| .__/|_| |_|_| |_|\__, | \/ \/___/ | | __/ | |_| |___/ eXtreme Data 1.0.0.BUILD-SNAPSHOT | Admin Server Target: http://localhost:9393 Welcome to the Spring XD shell. For assistance hit TAB or type "help". xd:>hadoop config fs --namenode hdfs://cdh4:8020 xd:>hadoop fs ls / Hadoop configuration changed, re-initializing shell... 16:55:28,853 WARN Spring Shell util.NativeCodeLoader:62 - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable -ls: Fatal internal error java.lang.UnsupportedOperationException: This is supposed to be overridden by subclasses. at com.google.protobuf.GeneratedMessage.getUnknownFields(GeneratedMessage.java:180) at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$GetFileInfoRequestProto.getSerializedSize(ClientNamenodeProtocolProtos.java:30108) at com.google.protobuf.AbstractMessageLite.toByteString(AbstractMessageLite.java:49) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.constructRpcRequest(ProtobufRpcEngine.java:149) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:193) at com.sun.proxy.$Proxy43.getFileInfo(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:164) at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:83) at com.sun.proxy.$Proxy43.getFileInfo(Unknown Source) at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getFileInfo(ClientNamenodeProtocolTranslatorPB.java:629) at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:1545) at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:819) at org.apache.hadoop.fs.FileSystem.globStatusInternal(FileSystem.java:1646) at org.apache.hadoop.fs.FileSystem.globStatus(FileSystem.java:1592) at org.apache.hadoop.fs.FileSystem.globStatus(FileSystem.java:1567) at org.apache.hadoop.fs.shell.PathData.expandAsGlob(PathData.java:271) at org.apache.hadoop.fs.shell.Command.expandArgument(Command.java:224) at org.apache.hadoop.fs.shell.Command.expandArguments(Command.java:207) at org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:190) at org.apache.hadoop.fs.shell.Command.run(Command.java:154) at org.apache.hadoop.fs.FsShell.run(FsShell.java:254) at org.springframework.xd.shell.hadoop.FsShellCommands.run(FsShellCommands.java:412) at org.springframework.xd.shell.hadoop.FsShellCommands.runCommand(FsShellCommands.java:407) at org.springframework.xd.shell.hadoop.FsShellCommands.ls(FsShellCommands.java:110) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:196) at org.springframework.shell.core.SimpleExecutionStrategy.invoke(SimpleExecutionStrategy.java:64) at org.springframework.shell.core.SimpleExecutionStrategy.execute(SimpleExecutionStrategy.java:48) at org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:127) at org.springframework.shell.core.JLineShell.promptLoop(JLineShell.java:530) at org.springframework.shell.core.JLineShell.run(JLineShell.java:178) at java.lang.Thread.run(Thread.java:744) {code} | 3 |
385 | XD-1530 | 04/10/2014 10:53:38 | Error when removing HDFS files in shell | I get this: {code} xd:>hadoop fs rm /xd/test/time-3.log Error: run HDFS shell failed. Message is: org.apache.hadoop.fs.FileStatus.isDirectory()Z {code} so far I have seen this with --hadoopDistro hdp13 and hadoop12 same command works fine using shell from M5 release | 3 |
386 | XD-1531 | 04/10/2014 12:53:23 | Rename xd-config.yml to servers.yml and add modules/modules.yml to spring-xd-yarn | Make changes to XD on YARN config that correspond to XD-1499 changes | 3 |
387 | XD-1532 | 04/10/2014 13:19:15 | Clean up MBean registration for failed module deployments | When a module fails to deploy (for instance an http module configured with a port that is already bound) subsequent attempts to deploy the module fail due to a JMX exception: {noformat} java.lang.RuntimeException: org.springframework.context.ApplicationContextException: Failed to start bean 'org.springframework.integration.monitor.IntegrationMBeanExporter#0#beafb1fc-4423-4e4f-a88c-1655ea0fdcc5'; nested exception is org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [MessageChannelMonitor: [name=output, sends=0]] with key 'org.springframework.integration:type=MessageChannel,name=output'; nested exception is javax.management.InstanceAlreadyExistsException: xd.foo:module=http.0,component=MessageChannel,name=output at org.springframework.xd.dirt.server.ContainerRegistrar.deployStreamModule(ContainerRegistrar.java:447) at org.springframework.xd.dirt.server.ContainerRegistrar.onChildAdded(ContainerRegistrar.java:346) at org.springframework.xd.dirt.server.ContainerRegistrar.access$700(ContainerRegistrar.java:92) at org.springframework.xd.dirt.server.ContainerRegistrar$DeploymentListener.childEvent(ContainerRegistrar.java:655) at org.apache.curator.framework.recipes.cache.PathChildrenCache$5.apply(PathChildrenCache.java:494) at org.apache.curator.framework.recipes.cache.PathChildrenCache$5.apply(PathChildrenCache.java:488) at org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92) at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293) at org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83) at org.apache.curator.framework.recipes.cache.PathChildrenCache.callListeners(PathChildrenCache.java:485) at org.apache.curator.framework.recipes.cache.EventOperation.invoke(EventOperation.java:35) at org.apache.curator.framework.recipes.cache.PathChildrenCache$11.run(PathChildrenCache.java:755) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) Caused by: org.springframework.context.ApplicationContextException: Failed to start bean 'org.springframework.integration.monitor.IntegrationMBeanExporter#0#beafb1fc-4423-4e4f-a88c-1655ea0fdcc5'; nested exception is org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [MessageChannelMonitor: [name=output, sends=0]] with key 'org.springframework.integration:type=MessageChannel,name=output'; nested exception is javax.management.InstanceAlreadyExistsException: xd.foo:module=http.0,component=MessageChannel,name=output at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:176) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:346) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:149) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:112) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:773) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:485) at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:648) at org.springframework.boot.SpringApplication.run(SpringApplication.java:311) at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:130) at org.springframework.xd.module.core.SimpleModule.initialize(SimpleModule.java:240) at org.springframework.xd.dirt.module.ModuleDeployer.deploy(ModuleDeployer.java:184) at org.springframework.xd.dirt.module.ModuleDeployer.deployAndStore(ModuleDeployer.java:174) at org.springframework.xd.dirt.module.ModuleDeployer.deployAndStore(ModuleDeployer.java:164) at org.springframework.xd.dirt.server.ContainerRegistrar.deployModule(ContainerRegistrar.java:227) at org.springframework.xd.dirt.server.ContainerRegistrar.deployStreamModule(ContainerRegistrar.java:429) ... 18 more Caused by: org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [MessageChannelMonitor: [name=output, sends=0]] with key 'org.springframework.integration:type=MessageChannel,name=output'; nested exception is javax.management.InstanceAlreadyExistsException: xd.foo:module=http.0,component=MessageChannel,name=output at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:610) at org.springframework.integration.monitor.IntegrationMBeanExporter.registerChannels(IntegrationMBeanExporter.java:837) at org.springframework.integration.monitor.IntegrationMBeanExporter.doStart(IntegrationMBeanExporter.java:459) at org.springframework.integration.monitor.IntegrationMBeanExporter.start(IntegrationMBeanExporter.java:410) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:173) ... 33 more Caused by: javax.management.InstanceAlreadyExistsException: xd.foo:module=http.0,component=MessageChannel,name=output at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) at org.springframework.jmx.support.MBeanRegistrationSupport.doRegister(MBeanRegistrationSupport.java:195) at org.springframework.jmx.export.MBeanExporter.registerBeanInstance(MBeanExporter.java:663) at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:606) ... 37 more {noformat} | 2 |
388 | XD-1533 | 04/10/2014 13:20:34 | Admin needs to clean up failed deployment attempts | If a container fails to deploy a module, the admin needs to clean up the {{/xd/deployments/modules/CONTAINER-ID/module}} path so that another attempt can be made to deploy that module to that container. | 2 |
389 | XD-1543 | 04/11/2014 07:27:36 | Update instructions to how to setup admin to use RDBMS. | Need to update instructions to discuss the setup of the relational database requirement for the xd-admin. | 2 |
390 | XD-1547 | 04/11/2014 08:41:53 | clean up dead entries in ZooKeeper /xd/deployments/modules | When starting and stopping xd containers there are entries left in the /xd/deployments/modules directory that will cause 'runtime modules' command to fail. xd:>runtime modules Command failed org.springframework.xd.rest.client.impl.SpringXDException: java.lang.RuntimeException: org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /xd/deployments/modules/5201ac3f-e952-48a2-a807-4f0bb2dab82b/test.sink.hdfs-1/metadata here the "/xd/deployments/modules/5201ac3f-e952-48a2-a807-4f0bb2dab82b" container is no longer running, but there is some data left over. | 3 |
391 | XD-1550 | 04/11/2014 10:24:46 | Fix 'cannot find MessageBuilderFactory' warning | 5:27:47,887 WARN DeploymentsPathChildrenCache-0 org.springframework.integration.context.IntegrationContextUtils:195 - No 'beanFactory' supplied; cannot find MessageBuilderFactory, using default. a lot of those | 1 |
392 | XD-1552 | 04/11/2014 12:38:04 | Remove --transport option except for single node | Since transport is now shared by Admin and Container, a command line arg is not appropriate since it allows the user to set them to different values which would break XD. The recommend way to configure transport is in servers.yml. The command line arg is still valid for single node | 2 |
393 | XD-1555 | 04/11/2014 13:26:58 | transform processor with script option is broken | Creating the following stream throws exception: stream create s1 --definition "http | transform --script=transform.groovy | log" Command failed org.springframework.xd.rest.client.impl.SpringXDException: Error with option(s) for module transform of type processor: valid: the 'script' and 'expression' options are mutually exclusive The ExpressionOrScriptMixin's assertions to check if script and expression options are mutually exclusive `always` fails. | 2 |
394 | XD-1564 | 04/12/2014 08:39:57 | Rabbit Sink with explicit routingKey as 'string' SpEl literal expression fails | Following stream fails to work: tream create s3 --definition "http | rabbit --routingKey='mytest1'" --deploy Created and deployed new stream 's3' xd:>http post --data "testing" > POST (text/plain;Charset=UTF-8) http://localhost:9000 testing > 500 INTERNAL_SERVER_ERROR > 500 INTERNAL_SERVER_ERROR Error sending data 'testing' to 'http://localhost:9000' The exception at the container log is: 07:24:57,245 ERROR pool-18-thread-4 http.NettyHttpInboundChannelAdapter:171 - Error sending message org.springframework.messaging.MessageHandlingException: Expression evaluation failed: mytest1 at org.springframework.integration.util.AbstractExpressionEvaluator.evaluateExpression(AbstractExpressionEvaluator.java:126) at org.springframework.integration.handler.ExpressionEvaluatingMessageProcessor.processMessage(ExpressionEvaluatingMessageProcessor.java:76) at org.springframework.integration.amqp.outbound.AmqpOutboundEndpoint.handleRequestMessage(AmqpOutboundEndpoint.java:196) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:170) at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.springframework.integration.monitor.SimpleMessageHandlerMetrics.handleMessage(SimpleMessageHandlerMetrics.java:106) at org.springframework.integration.monitor.SimpleMessageHandlerMetrics.invoke(SimpleMessageHandlerMetrics.java:86) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) at com.sun.proxy.$Proxy109.handleMessage(Unknown Source) at org.springframework.integration.dispatcher.AbstractDispatcher.tryOptimizedDispatch(AbstractDispatcher.java:116) at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:101) at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:97) at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:255) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:223) at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.springframework.integration.monitor.DirectChannelMetrics.monitorSend(DirectChannelMetrics.java:113) at org.springframework.integration.monitor.DirectChannelMetrics.doInvoke(DirectChannelMetrics.java:97) at org.springframework.integration.monitor.DirectChannelMetrics.invoke(DirectChannelMetrics.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) at com.sun.proxy.$Proxy54.send(Unknown Source) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:114) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:44) at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:93) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.sendMessage(AbstractReplyProducingMessageHandler.java:260) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.sendReplyMessage(AbstractReplyProducingMessageHandler.java:241) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.produceReply(AbstractReplyProducingMessageHandler.java:205) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleResult(AbstractReplyProducingMessageHandler.java:199) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:177) at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:78) at org.springframework.integration.dispatcher.AbstractDispatcher.tryOptimizedDispatch(AbstractDispatcher.java:116) at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:101) at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:97) at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:255) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:223) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:114) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:44) at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:93) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.sendMessage(AbstractReplyProducingMessageHandler.java:260) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.sendReplyMessage(AbstractReplyProducingMessageHandler.java:241) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.produceReply(AbstractReplyProducingMessageHandler.java:205) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleResult(AbstractReplyProducingMessageHandler.java:199) at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:177) at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:78) at org.springframework.integration.dispatcher.AbstractDispatcher.tryOptimizedDispatch(AbstractDispatcher.java:116) at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:101) at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:97) at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:255) at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:223) at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.springframework.integration.monitor.DirectChannelMetrics.monitorSend(DirectChannelMetrics.java:113) at org.springframework.integration.monitor.DirectChannelMetrics.doInvoke(DirectChannelMetrics.java:97) at org.springframework.integration.monitor.DirectChannelMetrics.invoke(DirectChannelMetrics.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) at com.sun.proxy.$Proxy111.send(Unknown Source) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:114) at org.springframework.messaging.core.GenericMessagingTemplate.doSend(GenericMessagingTemplate.java:44) at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:93) at org.springframework.integration.endpoint.MessageProducerSupport.sendMessage(MessageProducerSupport.java:98) at org.springframework.integration.x.http.NettyHttpInboundChannelAdapter.access$300(NettyHttpInboundChannelAdapter.java:69) at org.springframework.integration.x.http.NettyHttpInboundChannelAdapter$Handler.messageReceived(NettyHttpInboundChannelAdapter.java:168) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.doRun(ChannelUpstreamEventRunnable.java:43) at org.jboss.netty.handler.execution.ChannelEventRunnable.run(ChannelEventRunnable.java:67) at org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$ChildExecutor.run(OrderedMemoryAwareThreadPoolExecutor.java:314) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.springframework.expression.spel.SpelEvaluationException: EL1008E:(pos 0): Property or field 'mytest1' cannot be found on object of type 'org.springframework.messaging.support.GenericMessage' - maybe not public? at org.springframework.expression.spel.ast.PropertyOrFieldReference.readProperty(PropertyOrFieldReference.java:215) at org.springframework.expression.spel.ast.PropertyOrFieldReference.getValueInternal(PropertyOrFieldReference.java:85) at org.springframework.expression.spel.ast.PropertyOrFieldReference.getValueInternal(PropertyOrFieldReference.java:78) at org.springframework.expression.spel.ast.SpelNodeImpl.getTypedValue(SpelNodeImpl.java:114) at org.springframework.expression.spel.standard.SpelExpression.getValue(SpelExpression.java:111) at org.springframework.integration.util.AbstractExpressionEvaluator.evaluateExpression(AbstractExpressionEvaluator.java:159) at org.springframework.integration.util.AbstractExpressionEvaluator.evaluateExpression(AbstractExpressionEvaluator.java:119) ... 91 more | 2 |
395 | XD-1565 | 04/12/2014 09:21:06 | Document append support, else filepollhdfs writes empty file to hdfs | When testing in both singlenode and cluster (redis), XD throws exception (stacktrace attached). The file is created on hdfs, but it is empty. [Steps to recreate Using Hadoop12] 1) job create myjob --definition "filepollhdfs --names=forename,surname,address" --deploy 2) stream create csvStream --definition "file --ref=true --dir=/tmp/dug --pattern=*.csv > queue:job:myjob" --deploy 3) use excel to create a 3 column spreadsheet and save as csv. 4) Copy csv to /tmp/dug directory | 3 |
396 | XD-1566 | 04/12/2014 10:12:08 | Document append configuration, else jdbchdfs writes empty file to hdfs | Similar to XD-1565 so I'd link these 2 together. [Steps to reproduce on Hadoop12] 1) Created Table People with columns forename,surname and address (use the result from filejdbc) 2) job create myjob --definition "jdbchdfs --sql='select col1,col2,col3 from some_table'" 3)job launch myjob 4) myjob is created on hdfs but with zero bytes 5) throws an exception, stack trace attached. | 3 |
397 | XD-1568 | 04/12/2014 18:43:36 | Update documentation related to transport and controlTransport | e.g. Need to update this section (maybe others): https://github.com/spring-projects/spring-xd/wiki/Running-Distributed-Mode Remove all mentions of Control Bus, and replace any mentions of the --transport cmd line arg with the xd.transport property in yml. | 2 |
398 | XD-1575 | 04/14/2014 15:42:10 | Add UDP support to reactor-syslog source module | Currently the reactor-syslog source module only supports TCP. Once we add UDP support, we can probably remove the existing syslog-tcp and syslog-udp modules. | 8 |
399 | XD-1576 | 04/14/2014 20:10:49 | Remove unused .properties files in config and update docs | There are some properties files in the config directory that no longer are needed. We should clean that up and also remove/update any documentation references to these files | 3 |
400 | XD-1581 | 04/15/2014 13:44:01 | XD config home should use XD_CONFIG_LOCATION if this is set | If XD_CONFIG_LOCATION is set, then XD runtime's xd.config.home should use that. otherwise, they point to two different paths. | 2 |
401 | XD-1585 | 04/16/2014 12:51:09 | Tab completion does not work for stream definition following > | >stream create "tap:stream:foo > does not suggest modules | 8 |
402 | XD-1586 | 04/16/2014 14:01:08 | Stream should not be in deployed state following module failure. | Run singlenode. Ensure twitterstream credentials are not valid. e.g., no consumerKey property. This is the default state. >stream create tweets --definition "twitterstream | log" --deploy Created and deployed stream 'tweets' Meanwhile, Singlenode throws an exception, the stacktrace below xd:>stream list Stream Name Stream Definition Status ----------- ------------------- -------- tweets twitterstream | log deployed {code} 15:54:07,298 ERROR DeploymentsPathChildrenCache-0 cache.PathChildrenCache:550 - java.lang.RuntimeException: org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'twitterTemplate' defined in URL [file:/Users/dturanski/spring-xd/spring-xd-1.0.0.M6/xd/modules/source/twitterstream/config/twitterstream.xml]: Could not resolve placeholder 'consumerKey' in string value "${consumerKey}"; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'consumerKey' in string value "${consumerKey}" at org.springframework.xd.dirt.server.ContainerRegistrar.deployStreamModule(ContainerRegistrar.java:448) at org.springframework.xd.dirt.server.ContainerRegistrar.onChildAdded(ContainerRegistrar.java:347) at org.springframework.xd.dirt.server.ContainerRegistrar.access$700(ContainerRegistrar.java:93) at org.springframework.xd.dirt.server.ContainerRegistrar$DeploymentListener.childEvent(ContainerRegistrar.java:678) at org.apache.curator.framework.recipes.cache.PathChildrenCache$5.apply(PathChildrenCache.java:494) at org.apache.curator.framework.recipes.cache.PathChildrenCache$5.apply(PathChildrenCache.java:488) at org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92) at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293) at org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83) at org.apache.curator.framework.recipes.cache.PathChildrenCache.callListeners(PathChildrenCache.java:485) at org.apache.curator.framework.recipes.cache.EventOperation.invoke(EventOperation.java:35) at org.apache.curator.framework.recipes.cache.PathChildrenCache$11.run(PathChildrenCache.java:755) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'twitterTemplate' defined in URL [file:/Users/dturanski/spring-xd/spring-xd-1.0.0.M6/xd/modules/source/twitterstream/config/twitterstream.xml]: Could not resolve placeholder 'consumerKey' in string value "${consumerKey}"; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'consumerKey' in string value "${consumerKey}" {/code} | 3 |
403 | XD-1587 | 04/16/2014 15:48:49 | Provide module configuration templates for twitter sources | Provide module templates including required property keys but not values for $XD_MODULE_CONFIG/source/twitter*/twitter*.properties. Also look for any other packaged modules that have required properties that should be statically configured and we cannot provide defaults. The Source modules document should be more clear regarding the configuration of these properties. | 2 |
404 | XD-1588 | 04/17/2014 09:09:16 | PropertySource leakage between runtime and modules | in EnvironmentAwareModuleOptionsMetadataResolver::loadPropertySources, the call to merge(parentEnv) was added to inherit the active profiles of the runtime. Sadly, it added the parentEnv property sources by side effect. Note that the jdbc module defaults rely on this bug | 5 |
405 | XD-1590 | 04/17/2014 15:01:00 | Move ephemeral nodes from /xd/streams to /xd/deployments/streams | To have a clear separation of definition vs runtime information, move the ephemeral nodes written by containers from {{/xd/streams/stream-name}} to {{/xd/deployments/streams/stream-name}}. Same for jobs. | 2 |
406 | XD-1591 | 04/17/2014 15:12:59 | Flatten out ephemeral nodes | Flatten out ephemeral nodes written by containers when deploying modules. For instance, instead of {{.../streams/moduleType/moduleLabel/container}} use {{.../streams/moduleType.moduleLabel.container}}. This change allows us to derive state for a stream/job without having to traverse multiple layers of znodes. This is a big deal because: * each level of children requires a network call * Curator can only cache one level of children | 5 |
407 | XD-1595 | 04/18/2014 15:11:44 | Remove aliasHint flag usage when binding producer/consumer to MessageBus | The MessageBus interface uses the aliasHint flag when binding consumer/producer on a point-to-point channel. Actually, the aliasHint is only needed when computing Source/Sink channel names in case named channel names. Otherwise, indexed channel names will be used for the input/output channel name. The only place where aliasHint is used in the message bus is on the LocalMessageBus where it provides a way to choose the channel provider (direct/queue channel) based on the alias hint. Otherwise, it is not needed in message bus bindproducer/consumer. We need to simplify this. | 3 |
408 | XD-1596 | 04/19/2014 13:54:07 | Rabbit Source Should Expose More Container Options | acknowlege-more, tx-size, prefetch-count, concurrency etc. | 3 |
409 | XD-1598 | 04/21/2014 13:52:58 | Use MessageBus Binding to start() underlying endpoint | The messagebus implementations, upon registration of consumer and producer from/to messagebus the corresponding endpoints start. Instead of directly calling the start() on adapter/consumer we can call the corresponding Binding's start() which calls the underlying endpoint to start. This is in-line with the way the corresponding endpoints are stopped (using Binding's stop()) during undeploy/destroy. | 1 |
410 | XD-1599 | 04/21/2014 14:03:59 | Change SpringSource references in pom.xml to Spring/spring.io | This is currently in the M6 pom: <organization> <name>SpringSource</name> <url>http://springsource.org</url> </organization> | 3 |
411 | XD-1600 | 04/21/2014 17:22:49 | Validate existence of batch job at the admin side | Since the batch job repository is not intended to be deleted, it is possible to have a batch job that already exists in the batch job repo even if the batch job definition is destroyed in XD. When a new job definition is created, we need to add a validation for the same job definition name against the batch job repository. Currently, we will only see a failure when the job is actually deployed into the container (when the batch job repository is updated during the deployment). | 1 |
412 | XD-1602 | 04/22/2014 07:53:02 | JMS Source on EC2 only uses localhost for activemq broker | [Problem] On a EC2 container jms-activemq.properties was configured to use a activemq broker on a different host, it still referred to localhost. On my local mac, I was able to updated the jms-activemq.properties with an activemq on a different host and it worked. [work-around] While not recommended you can set the amq.url in the jms-activemq-infrastructure-context.xml. [Steps to reproduce] 1) Deploy a single admin/container using xd-ec2. 2) create a jms-activemq.properties file in the spring-xd-1.0.0.BUILD-SNAPSHOT/xd/ where it refers to a broker on another machine (ec2-54-221-32-82.compute-1.amazonaws.com). 3) Create a stream with JMS as its source. | 3 |
413 | XD-1612 | 04/22/2014 16:10:04 | Simplify/Refactor UI controllers | The UI controllers in spring-xd/spring-xd-ui/app/scripts/controllers.js definitions look overly complicated to get the modularization work. We can possibly refactor and make it look clean; especially we will follow this as the example for subsequent controllers definitions. | 3 |
414 | XD-1613 | 04/23/2014 10:47:57 | Parser fails on + after literal within an expression | This fails: {code} xd:>stream create s --definition "http | transform --expression='hi'+payload | log" Command failed org.springframework.xd.rest.client.impl.SpringXDException: XD115E:(pos 34): unexpected data in stream definition '+' http | transform --expression='hi'+payload | log {code} But this works: {code} xd:>stream create s --definition "http | transform --expression=payload+'hi' | log" Created new stream 's' {code} | 2 |
415 | XD-1620 | 04/23/2014 14:09:25 | Fix JobCommandTests' verification of shell result table rows using specific index | Some of the tests in JobCommandTests use the verification of shell command results table row on a specific row (mostly first row) like this: String id = jobExecutions.getRows().get(0).getValue(1); displayJobExecution(id); It is possible that the list of table rows may have the intended row in different order. This poses inconsistent test failures. | 1 |
416 | XD-1622 | 04/23/2014 14:16:49 | Add support for typed Batch Steps | This may require additional support (Jiras) for Spring Batch | 8 |
Subsets and Splits