January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-304) exception in staticrouter

by Mark Little (JIRA)

exception in staticrouter ------------------------- Key: JBESB-304 URL: http://jira.jboss.com/jira/browse/JBESB-304 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.0 RC1 Reporter: Mark Little Assigned To: Burr Sutter Fix For: 4.0 java.lang.reflect.InvocationTargetException [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [java] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [java] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) [java] at org.jboss.soa.esb.listeners.gateway.GatewayListenerController.tryToLaunchGateway(GatewayListenerController.java:356) [java] at org.jboss.soa.esb.listeners.gateway.GatewayListenerController.run(GatewayListenerController.java:303) [java] at java.lang.Thread.run(Thread.java:595) [java] Caused by: java.net.MalformedURLException: For input string: "esbDir" [java] at java.net.URL.<init>(URL.java:601) [java] at java.net.URL.<init>(URL.java:464) [java] at java.net.URL.<init>(URL.java:413) [java] at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.checkMyParms(AbstractFileGateway.java:272) [java] java.lang.reflect.InvocationTargetException [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [java] at org.jboss.soa.esb.listeners.gateway.FileGatewayListener.checkMyParms(FileGatewayListener.java:49) [java] at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.checkMyParms(RemoteGatewayListener.java:47) [java] at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.<init>(AbstractFileGateway.java:70) [java] at org.jboss.soa.esb.listeners.gateway.FileGatewayListener.<init>(FileGatewayListener.java:43) [java] at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.<init>(RemoteGatewayListener.java:42) [java] ... 7 more [java] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [java] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) [java] at org.jboss.soa.esb.listeners.gateway.GatewayListenerController.tryToLaunchGateway(GatewayListenerController.java:356) [java] at org.jboss.soa.esb.listeners.gateway.GatewayListenerController.run(GatewayListenerController.java:303) [java] at java.lang.Thread.run(Thread.java:595) [java] Caused by: java.net.MalformedURLException: For input string: "esbDir" [java] at java.net.URL.<init>(URL.java:601) [java] at java.net.URL.<init>(URL.java:464) [java] at java.net.URL.<init>(URL.java:413) [java] at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.checkMyParms(AbstractFileGateway.java:272) [java] at org.jboss.soa.esb.listeners.gateway.FileGatewayListener.checkMyParms(FileGatewayListener.java:49) [java] at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.checkMyParms(RemoteGatewayListener.java:47) [java] at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.<init>(AbstractFileGateway.java:70) [java] at org.jboss.soa.esb.listeners.gateway.FileGatewayListener.<init>(FileGatewayListener.java:43) [java] at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.<init>(RemoteGatewayListener.java:42) [java] ... 7 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

17 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-722) The bingings containing the new FailedOverQueue need to be properly saved in the database (new field needed: failedNodeID)

by Ovidiu Feodorov (JIRA)

The bingings containing the new FailedOverQueue need to be properly saved in the database (new field needed: failedNodeID) -------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-722 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-722 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 -- 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

17 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-324) Review the helloworld_file_action readme.txt

by Burr Sutter (JIRA)

Review the helloworld_file_action readme.txt -------------------------------------------- Key: JBESB-324 URL: http://jira.jboss.com/jira/browse/JBESB-324 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.0 CR2 Reporter: Burr Sutter Assigned To: Esteban Schifman Fix For: 4.0 CR2 Please review the contents of the readme.txt in the helloworld_file_action quickstart. Specifically the section that tries to describe the attributes of the fs-message-filter tag. It is pasted below but if you need to make edits please update the one in SVN directly. Overview: ========= This is a basic example of using the File gateway feature of the JBoss ESB Files that are found in a particular directory with a particular extension are sent to a JMS queue with actions for processing. Before Running: =============== 1. Update the "jbosshome.dir" property in the quickstarts.properties file in "../". 2. Make sure the jbossesb.sar is deployed on your JBoss Application Server. 3. Make sure the JBoss Application server is running since it uses JBossMQ 4. Open the jbossesb.xml configuration file and review this section: <fs-bus busid="helloFileChannel" > <fs-message-filter directory="C:/tmp/ESBInput" input-suffix=".dat" work-suffix=".esbWorking" post-delete="false" post-directory="C:/tmp/ESBInputt" post-suffix=".sentToEsb" error-delete="false" error-directory="C:/tmp/ESBInput" error-suffix=".IN_ERROR" /> </fs-bus> You will need to create a tmp/ESBInput directory or modify this section of jbossesb.xml 5. If you change these settings make sure to also change the build.xml's runtest target To Run: ======= 1. In a command window type "ant run". You will see the service get registered in the JBoss AS server console as well as by the activity in the command window where the service runs. 2. Open another command window and type "ant runtest". This will create a new file called "MyInput.dat" in the directory "/tmp/ESBInput" with the contents "Hello World In A File" 3. You should see the output on the first command window running the service. 4. Change the file name and contents and re-test. What to look at in this Quickstart: =================================== This example demonstrates the use of a file gateway that by default loads the file and pushes into a JMS message queue. What follows is a more detailed discussion on the file gateway: * directory - the directory to be monitored for input file messages * input-suffix - the file extension to be monitored, other files will be ignored * work-suffix - the file extension that is used while the file is "in process" by the ESB. The file is considered to be "in process" while the gateway is passing it into the ESB listener/service (in this case JMS queue). * post-delete - "true" or "false". The file can be removed once has been successfully processed. * post-directory - The place where the "processed" file ends up assuming no errors and assuming post-delete="false" * post-suffix - The file extension that is used to mark the file as "completed" * error-delete - "true" or "false". If there is an internal error and the file fails to be loaded by the ESB, delete it. * error-directory - The place to drop any file that fails to be uploaded/processed * error-suffix - The file extension that is used to mark a file has had an internal error. Note: Error processing in this case means the file failed to pass through the gateway and into the waiting queue. This does NOT cover errors/exceptions in your action classes. -- 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

17 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-154) Change configuration for FTP listeners/actions to avoid need to replicate FTP parameters

by Esteban Schifman (JIRA)

Change configuration for FTP listeners/actions to avoid need to replicate FTP parameters ---------------------------------------------------------------------------------------- Key: JBESB-154 URL: http://jira.jboss.com/jira/browse/JBESB-154 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Reporter: Esteban Schifman Assigned To: Esteban Schifman Priority: Minor FTP server/username/password are needed both by the RemoteDirectoryPoller, and the FTP classes As it stands now, they need to be replicated in the xml configuration file for listeners and actions. This is not appropriate and we should find ways to avoid this need. -- 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

17 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-317) Converting CBR Listener

by Kurt Stam (JIRA)

Converting CBR Listener ----------------------- Key: JBESB-317 URL: http://jira.jboss.com/jira/browse/JBESB-317 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Priority: Blocker Fix For: 4.0 Attachments: CbrProxyActionUnitTest.java, CbrProxyActionUnitTest.xml A new CbrListener was created to replace the CbrJmsQueueListener. I have tried to use this new class in the CbrJmsQueueListenerTest, by updating the config xml and way the test starts the listeners. When the test CbrProxyActionUnitTest runs it gives me: [junit] 12:02:37,593 DEBUG [SocketManager] Created ObjectOutputStream [junit] 12:02:37,593 DEBUG [CbrListener] Sending message to the Content Based Router. [junit] 12:02:37,593 DEBUG [SocketManager] Created ObjectInputStream [junit] 12:02:37,593 DEBUG [UILClientILService] Starting [junit] 12:02:37,593 INFO [JBossRulesRouter] Reading ruleSet from file=JBossESBRules.drl [junit] 12:02:37,593 INFO [JBossRulesRouter] Going to read the rule: JBossESBRules.drl [junit] 12:02:37,609 DEBUG [SpyDestinationObjectFactory] SpyDestinationObjectFactory->getObjectInstance() [junit] 12:02:39,500 DEBUG [JBossRulesRouter] Obtained message=org.jboss.internal.soa.esb.message.format.xml.MessageImpl@edbca8 with ruleSet=JBossESBRules.drl [junit] 12:02:39,500 DEBUG [JBossRulesRouter] Obtained message=org.jboss.internal.soa.esb.message.format.xml.MessageImpl@d9205 with ruleSet=JBossESBRules.drl [junit] 12:02:39,515 INFO [JBossRulesRouter] Fire the JBossRules Engine [junit] 12:02:39,515 INFO [JBossRulesRouter] Fire the JBossRules Engine [junit] JBoss_XML [junit] JBoss_XML [junit] 12:02:39,515 DEBUG [JBossRulesRouter] Destination Services List: [test_category:JBOSS_XMLDestination] [junit] 12:02:39,515 DEBUG [JBossRulesRouter] Destination Services List: [test_category:JBOSS_XMLDestination] [junit] 12:02:39,515 DEBUG [CbrListener] Replying to caller [junit] 12:02:39,515 INFO [RegistryException] Going to load org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl [junit] 12:02:39,515 DEBUG [Factory] Using the Context ClassLoader [junit] 12:02:39,515 INFO [MessageRouter] Looking for EPRs for category=test_category and serviceName=JBOSS_XMLDestination [junit] 12:02:39,515 ERROR [CbrListener] Unable to reply to caller. Deliver courier for EPR not supported yet [junit] org.jboss.soa.esb.couriers.CourierException: Deliver courier for EPR not supported yet [junit] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.getDeliverCourier(TwoWayCourierImpl.java:90) [junit] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.setToEpr(TwoWayCourierImpl.java:64) [junit] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.<init>(TwoWayCourierImpl.java:55) [junit] at org.jboss.soa.esb.couriers.CourierFactory.getCourier(CourierFactory.java:78) [junit] at org.jboss.soa.esb.couriers.CourierFactory.getCourier(CourierFactory.java:52) [junit] at org.jboss.soa.esb.listeners.message.CbrListener.waitForEventAndProcess(CbrListener.java:120) [junit] at org.jboss.soa.esb.listeners.AbstractManagedListener.run(AbstractManagedListener.java:238) [junit] at java.lang.Thread.run(Thread.java:595) [junit] 12:02:39,515 DEBUG [JAXRRegistryImpl] Going to query the registry for name pattern [test_category, JBOSS_XMLDestination] [junit] 12:02:39,531 INFO [LocalTransport] Calling org.apache.juddi.registry.local.InquiryService#inquire locally [junit] 12:02:39,531 INFO [Registry] Loading jUDDI configuration. [junit] 12:02:39,531 INFO [Registry] Resources loaded from: /org/jboss/soa/esb/services/registry/juddi-qatest.properties [junit] 12:02:39,531 INFO [Registry] Initializing jUDDI components. [junit] 12:02:39,531 INFO [ConnectionManager] Not using Datasource as juddi.isUseDataSource=false [junit] 12:02:39,531 ERROR [MessageRouter] Could not obtain an EPR from the Registry. Message is not routed. Could not find service with category=test_category and serviceName=JBOSS_XMLDestination [junit] org.jboss.soa.esb.services.registry.RegistryException: Could not find service with category=test_category and serviceName=JBOSS_XMLDestination [junit] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:333) [junit] at org.jboss.soa.esb.services.routing.MessageRouter.deliverMessages(MessageRouter.java:74) [junit] at org.jboss.internal.soa.esb.services.routing.cbr.JBossRulesRouter.route(JBossRulesRouter.java:107) [junit] at org.jboss.soa.esb.listeners.message.CbrListener.waitForEventAndProcess(CbrListener.java:113) [junit] at org.jboss.soa.esb.listeners.AbstractManagedListener.run(AbstractManagedListener.java:238) [junit] at java.lang.Thread.run(Thread.java:595) [junit] Caused by: org.jboss.soa.esb.services.registry.RegistryException: Could not find service with category=test_category and serviceName=JBOSS_XMLDestination [junit] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:319) [junit] ... 5 more This should work for 4.0. -- 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

17 years, 4 months

3
5
0 / 0

[JBoss JIRA] Closed: (JBMICROCONT-92) Import Microcontainer projects into subversion

by Scott M Stark (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-92?page=all ] Scott M Stark closed JBMICROCONT-92. ------------------------------------ Fix Version/s: (was: JBossMC_2_0_0_CR1) JBossMC_2_0_0 Beta Resolution: Done > Import Microcontainer projects into subversion > ---------------------------------------------- > > Key: JBMICROCONT-92 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-92 > Project: JBoss MicroContainer > Issue Type: Sub-task > Components: General > Reporter: Adrian Brock > Fix For: JBossMC_2_0_0 Beta > > -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-300) exception in helloworld_file_action

by Mark Little (JIRA)

exception in helloworld_file_action ----------------------------------- Key: JBESB-300 URL: http://jira.jboss.com/jira/browse/JBESB-300 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.0 RC1 Reporter: Mark Little Assigned To: Burr Sutter Fix For: 4.0 [echo] Basic File Gateway and Listener [java] 14:18:06,565 INFO [main][Launcher] args passed into Launcher: 3 [java] 14:18:06,565 INFO [main][Launcher] arg[0]=0 [java] 14:18:06,565 INFO [main][Launcher] arg[1]=C:\projects\jbossesb\quickstarts\product\build\jbossesb\samples\quickstarts\helloworld_file_action/esb-config.xml [java] 14:18:06,565 INFO [main][Launcher] arg[2]=C:\projects\jbossesb\quickstarts\product\build\jbossesb\samples\quickstarts\helloworld_file_action/esb-config-gateway.xml [java] 14:18:06,625 INFO [main][HsqldbUtil] creating db from this script: build/hsqldb [java] [Server@73a34b]: [Thread[main,5,main]]: checkRunning(false) entered [java] [Server@73a34b]: [Thread[main,5,main]]: checkRunning(false) exited [java] [Server@73a34b]: Startup sequence initiated from main() method [java] [Server@73a34b]: Loaded properties from [C:\projects\jbossesb\quickstarts\product\build\jbossesb\samples\quickstarts\helloworld_file_action\server.properties] [java] [Server@73a34b]: Initiating startup sequence... [java] [Server@73a34b]: Server socket opened successfully in 10 ms. [java] [Server@73a34b]: Database [index=0, id=0, db=file:build/hsqldb, alias=jbossesb] opened sucessfully in 231 ms. [java] [Server@73a34b]: Startup sequence completed in 251 ms. [java] [Server@73a34b]: 2006-12-29 14:18:06.916 HSQLDB server 1.8.0 is online [java] [Server@73a34b]: To close normally, connect and execute SHUTDOWN SQL [java] [Server@73a34b]: From command line, use [Ctrl]+[C] to abort abruptly [java] Exception in thread "main" java.lang.NullPointerException [java] at java.io.Reader.<init>(Reader.java:61) [java] at java.io.InputStreamReader.<init>(InputStreamReader.java:55) [java] at org.jboss.soa.esb.testutils.FileUtil.readStream(FileUtil.java:61) -- 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

17 years, 4 months

2
3
0 / 0

[JBoss JIRA] Commented: (JBAS-3272) update JBossRemoting to version 2.0.0

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3272?page=comments#action_12349571 ] Dimitris Andreadis commented on JBAS-3272: ------------------------------------------ I updated to jboss remoting 2.0.0.GA since we up'ed jbossws to 1.2.0.CR1. Tom, I don't know if there is any special configuration needed, so I'm leaving the issue open for now. > update JBossRemoting to version 2.0.0 > ------------------------------------- > > Key: JBAS-3272 > URL: http://jira.jboss.com/jira/browse/JBAS-3272 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Remoting > Reporter: Tom Elrod > Assigned To: Tom Elrod > Priority: Critical > Fix For: JBossAS-4.2.0.CR1 > > > Need to update JBossAS to include jboss-remoting.jar for version 2.0.0.GA of JBossRemoting. -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-57) Interfaces for accessing JBossCache

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-57?page=all ] Manik Surtani closed JBCACHE-57. -------------------------------- Fix Version/s: 2.0.0.ALPHA2 Resolution: Done > Interfaces for accessing JBossCache > ----------------------------------- > > Key: JBCACHE-57 > URL: http://jira.jboss.com/jira/browse/JBCACHE-57 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Manik Surtani > Priority: Blocker > Fix For: 2.0.0.ALPHA2, 2.0.0.GA > > Original Estimate: 1 week, 3 days > Time Spent: 1 hour > Remaining Estimate: 1 week, 2 days, 7 hours > > - Access JBossCache through interfaces, not impl > - Factory-based approach, use either TreeCache or TreeCacheAop: > factory.createCache(XML file) > - How to provide JMX access ? -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-768) Finalise JMX interface for Cache

by Manik Surtani (JIRA)

Finalise JMX interface for Cache -------------------------------- Key: JBCACHE-768 URL: http://jira.jboss.com/jira/browse/JBCACHE-768 Project: JBoss Cache Issue Type: Sub-task Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 -- 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

17 years, 4 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007