February 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2341) local date translating error when run esb smooks examples

by Feng Qian (JIRA)

local date translating error when run esb smooks examples --------------------------------------------------------- Key: JBESB-2341 URL: https://jira.jboss.org/jira/browse/JBESB-2341 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Feng Qian I am a jboss tools guy. When I did the task for importing ESB examples to eclipse workspace, I got a issue like: https://jira.jboss.org/jira/browse/JBIDE-3654. I just fixed this issue by adding <param name="locale-language">en</param> to smooks file. I do not know if the runtime examples has this issue because I can test it on my machine. If not, please close this jira. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2124) Message Count and Message Count (avg) don't differ

by Jaroslaw Kijanowski (JIRA)

Message Count and Message Count (avg) don't differ -------------------------------------------------- Key: JBESB-2124 URL: https://jira.jboss.org/jira/browse/JBESB-2124 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 CP1 Reporter: Jaroslaw Kijanowski $SUBJECT (see avg.png) + what does it mean to have a message count average? An average over what time? per minute? I guess per 'collection interval' ... but we have already an avg column for all metrics... why a separate metric? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
14
0 / 0

[JBoss JIRA] Created: (JBESB-2051) Exception thrown by wise soap client during deployment are not easy to understand

by Stefano Maestri (JIRA)

Exception thrown by wise soap client during deployment are not easy to understand --------------------------------------------------------------------------------- Key: JBESB-2051 URL: https://jira.jboss.org/jira/browse/JBESB-2051 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Reporter: Stefano Maestri Assignee: Stefano Maestri -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1992) EBWS Security needs rework and unification

by Jiri Pechanec (JIRA)

EBWS Security needs rework and unification ------------------------------------------ Key: JBESB-1992 URL: https://jira.jboss.org/jira/browse/JBESB-1992 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Security, Web Services Affects Versions: 4.4 Reporter: Jiri Pechanec There is now security implementation at two levels - specifying webservice="security" attribute enables JBossWS security handler - specifying security elemnt enables WSSecuritySoapExtractor The WSSecuritySoapExtractor operates at XML/DOM level which means that is completely independent on JBossWS security handler. Please consider unifying the configuration and JBossWS facility use. Morever check the WSSecurityInfoExtractor if there is also a way to use JBossWS functions instead of Smooks parsing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-3189) Upgrade SQLprovider

by Quinton Anderson (JIRA)

Upgrade SQLprovider ------------------- Key: JBESB-3189 URL: https://jira.jboss.org/jira/browse/JBESB-3189 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Environment: JBoss AS jboss-5.1.0.GA, OpenMQ 4.4, Postgres 8.4, CentOS 64 Bit, Jdk 1.6 Reporter: Quinton Anderson I need to use the the SQLprovider with against a postgres database, with a table structure that doesn't exactly match what the provider expects. I would therefore like to the add the following features to this provider: -Message ID can be of any type -Status column can be of any type -I can specify the different state values for the status column in the esb provider definition in the jboss-esb.xml file -The timestamp is optional and can be either bigint or an actual datetime stamp field -The message data column can be of any type. As part of this I need to ensure that this provider works with Postgres, as currently postgres does not support implicit type casts, which this component seems to use. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3185) Related to JBESB-1742 - with an .esb archive that includes a schema import deployed, stopping and starting the server fials

by Len DiMaggio (JIRA)

Related to JBESB-1742 - with an .esb archive that includes a schema import deployed, stopping and starting the server fials --------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3185 URL: https://jira.jboss.org/jira/browse/JBESB-3185 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Environment: revision 31778 Reporter: Len DiMaggio Found this by accident while looking at the bug fix for JBESB-3076 Steps to recreate: 1) Deploy the quickstart attached to JBESB-3076 to an ESB server - any one of the imports illustrated in that quickstart can be used. 2) Stop the server 3) Start the server - the server startup will not complete - in looking at the logs, the server does not seem to be hung as these statements continue to be written to the log every 5 seconds: 2010-02-22 13:44:48,758 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open ResultSet (open ResultSets: 0, globally: 0) 2010-02-22 13:44:48,758 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close ResultSet (open ResultSets: 1, globally: 1) 2010-02-22 13:44:48,758 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close PreparedStatement (open PreparedStatements: 1, globally: 1) 2010-02-22 13:44:48,758 DEBUG [org.hibernate.jdbc.ConnectionManager] aggressively releasing JDBC connection 2010-02-22 13:44:48,758 DEBUG [org.hibernate.jdbc.ConnectionManager] releasing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)] 4) Attempt to stop the server - the server becomes unresponsive. Attachments: * server.log.one - covers steps 1 and 2 * server.log.two - covers steps 3 and 4 * jboss-esb.xml - simplest version from the quickstart * webservice_proxy_import.zip - the quickstart from JBESB-3076 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-3183) Remove stax-api-1.0.1.jar from esb deployment

by Daniel Bevenius (JIRA)

Remove stax-api-1.0.1.jar from esb deployment --------------------------------------------- Key: JBESB-3183 URL: https://jira.jboss.org/jira/browse/JBESB-3183 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.7 Reporter: Daniel Bevenius Priority: Minor Currently the esb deployment contains two stax-api jars. One is stax-1.0.1.jar and the other stax-1.0-2.jar. Notice that stax-1.0-2.jar is actually version 1.0 (see manifest.mf) and this version matches the EAP version. The 1.0.1 version is brought in by a ivy dependency and we need to exclude it or filter it out when deploying the esb. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3182) two_servers QS readme.txt needs changes

by Tom Cunningham (JIRA)

two_servers QS readme.txt needs changes --------------------------------------- Key: JBESB-3182 URL: https://jira.jboss.org/jira/browse/JBESB-3182 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.7 Reporter: Tom Cunningham Assignee: Tom Cunningham In the two_servers QS, we give the following instructiongs for running on AS5 : 3. In Window 2, if AS 4.x: start the first application server (./run.sh -c first) if AS 5.x: start the first application server (./run.sh -c first -Djboss.service.binding.set=ports-01) 4. In Window 3, if AS 4.x: start the second application server (./run.sh -c second) if AS 5.x: start the second application server (./run.sh -c second -Djboss.service.binding.set=ports-02) In these two steps, the order of -Djboss.service.binding.set=port2-01 and -c first need to be reversed for the port binding property to take effect. These should read : 3. In Window 2, if AS 4.x: start the first application server (./run.sh -c first) if AS 5.x: start the first application server (./run.sh -Djboss.service.binding.set=ports-01 -c first) 4. In Window 3, if AS 4.x: start the second application server (./run.sh -c second) if AS 5.x: start the second application server (./run.sh -Djboss.service.binding.set=ports-02 -c second ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2273) Extend BusinessRulesProcessor action to support entry-point

by Burr Sutter (JIRA)

Extend BusinessRulesProcessor action to support entry-point ----------------------------------------------------------- Key: JBESB-2273 URL: https://jira.jboss.org/jira/browse/JBESB-2273 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1 Reporter: Burr Sutter BusinessRulesProcessor allows for a "stateful" rules session as of ESB 4.4, however, it doesn't allow subsequent inbound messages to inject those messages into the already existing stateful rules session via the entry-point API. <action class="org.jboss.soa.esb.actions.BusinessRulesProcessor" name="OrderDiscountBasedOnCustomerHistory"> <property name="ruleSet" value="OrderDiscountOnMultipleOrders.drl" /> <property name="ruleReload" value="false" /> <property name="stateful" value="true" /> <property name="object-paths"> <object-path esb="body.TheOrderHeader" /> <object-path esb="body.TheCustomer" /> </property> </action> We might extend this like so: <object-path esb="body.TheOrderHeader" entry-point="OrderStream" /> <object-path esb="body.TheCustomer" entry-point="CustomerStream" /> The date time stamp should be based on message DOB but perhaps overrideable here as well. The use of entry-points would also mean that the Rules session is "self cleaning" as it automatically garbage collects stale facts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

6
10
0 / 0

[JBoss JIRA] Created: (JBESB-3178) XPath Router couldn't create new DOM document

by Lukáš Petrovický (JIRA)

XPath Router couldn't create new DOM document --------------------------------------------- Key: JBESB-3178 URL: https://jira.jboss.org/jira/browse/JBESB-3178 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.7 CP1 Reporter: Lukáš Petrovický Attachments: server.log.gz Regression testing on SOA-P 5.0 CR1 (unsigned) revealed the following problem in fun_cbr QS, see the server log: 2010-02-09 16:30:32,427 DEBUG [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (pool-27-thread-1) Unexpected exception caught while processing the action pipeline org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. at org.apache.xerces.dom.ParentNode.internalInsertBefore(Unknown Source) at org.apache.xerces.dom.ParentNode.insertBefore(Unknown Source) at org.apache.xerces.dom.CoreDocumentImpl.insertBefore(Unknown Source) at org.apache.xerces.dom.NodeImpl.appendChild(Unknown Source) at org.jboss.internal.soa.esb.util.wstx.ESBDOMWrappingWriter.appendLeaf(ESBDOMWrappingWriter.java:501) at org.jboss.internal.soa.esb.util.wstx.ESBDOMWrappingWriter.writeCharacters(ESBDOMWrappingWriter.java:244) at com.ctc.wstx.evt.WstxEventWriter.add(WstxEventWriter.java:168) at com.ctc.wstx.evt.WstxEventWriter.add(WstxEventWriter.java:230) at org.jboss.internal.soa.esb.util.XMLHelper.copyXMLEventStream(XMLHelper.java:343) at org.jboss.internal.soa.esb.util.XMLHelper.copyXMLEventStream(XMLHelper.java:315) at org.jboss.internal.soa.esb.util.XMLHelper.createDocument(XMLHelper.java:610) at org.jboss.soa.esb.actions.cbr.XPathRouter$XPathRoutingRule.evaluate(XPathRouter.java:95) at org.jboss.soa.esb.actions.cbr.AbstractPropertyRulesRouter.route(AbstractPropertyRulesRouter.java:108) at org.jboss.soa.esb.actions.cbr.XPathRouter.route(XPathRouter.java:44) at org.jboss.soa.esb.actions.cbr.AbstractPropertyRulesRouter.route(AbstractPropertyRulesRouter.java:92) at org.jboss.soa.esb.actions.cbr.XPathRouter.route(XPathRouter.java:44) at org.jboss.soa.esb.actions.ContentBasedWiretap.executeRules(ContentBasedWiretap.java:172) at org.jboss.soa.esb.actions.ContentBasedWiretap.process(ContentBasedWiretap.java:144) at org.jboss.soa.esb.actions.ContentBasedRouter.process(ContentBasedRouter.java:58) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:634) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:588) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:419) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) The message that is being processed at the moment looks like this: 2010-02-09 16:30:32,354 INFO [STDOUT] (pool-27-thread-1) Message structure: 2010-02-09 16:30:32,354 INFO [STDOUT] (pool-27-thread-1) [<Order xmlns="http://org.jboss.soa.esb/Order" orderId="1" orderDate="Wed Nov 15 13:45:28 EST 2006" statusCode="0" netAmount="59.97" totalAmount="64.92" tax="4.95"> <Customer userName="user1" firstName="Harry" lastName="Fletcher" state="SD"/> <OrderLines> <OrderLine position="1" quantity="1"> <Product productId="364" title="The 40-Year-Old Virgin " price="29.98"/> </OrderLine> <OrderLine position="2" quantity="1"> <Product productId="299" title="Pulp Fiction" price="29.99"/> </OrderLine> </OrderLines> </Order> ]. It seems that it is impossible to create the DOM tree from this message. This is a regression since this QS ran fine with SOA-P 5.0 ER8. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2010