March 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1329) Collections (unbounded xs:elements) can't be first element in xs:sequence

by Per-Anders Backstrom (JIRA)

Collections (unbounded xs:elements) can't be first element in xs:sequence ------------------------------------------------------------------------- Key: JBESB-1329 URL: http://jira.jboss.com/jira/browse/JBESB-1329 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Environment: JBoss 4.2.GA Reporter: Per-Anders Backstrom Collections can't be the first element in a xs:sequence or else the OGNL-mapping will fail. I have narrowed the bug down to the org.jboss.internal.soa.esb.soap.OGNLUtils class and the getOGNLExpression() method. The bug is easily reproduced, in the soapui-client test-cases, in file orderprocessing/OrderProcessingSchema.xsd, just see to that the element name "lineItems" gets positioned first in complexType named "order". Btw, collections are asserted in OGNLUtils.java by checking for the first occurrence of a comment-string containing "1 or more repetitions" at the parent node of the actual element, but as far as I can see my collections are always commented with "Zero or more repetitions". If the first comment is rather "Optional", e.g the collection isn't first element in the parent node, this assertion would probably fail anyway? -- 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

16 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1564) CourierException should be visible on higher than DEBUG level

by Jiri Pechanec (JIRA)

CourierException should be visible on higher than DEBUG level ------------------------------------------------------------- Key: JBESB-1564 URL: http://jira.jboss.com/jira/browse/JBESB-1564 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Assigned To: Mark Little Fix For: 4.2.1 CP2 When the Courier exception is thrown in courier (like Failed to serialize ESB message in JMS courier) the excpetion is logged by ServiceInvoker only at DEBUG level logger.debug("Badly formed EPR [" + targetEPR + "] for Service [" + service + "] and Message ["+message.getHeader()+"]. " + e.getMessage()); This makes identification of error extremly difficult and as it is erroneous state it should be logged at at least INFO level. -- 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

16 years, 9 months

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-1582) Scheduler jobs are not stateful, causing multiple instances of the same job to be fired in parallel

by Tom Fennelly (JIRA)

Scheduler jobs are not stateful, causing multiple instances of the same job to be fired in parallel --------------------------------------------------------------------------------------------------- Key: JBESB-1582 URL: http://jira.jboss.com/jira/browse/JBESB-1582 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Tom Fennelly Fix For: 4.2.1 CP2 Fix for this is on the bramley branch (workspace) -- 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

16 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1588) Property substitution in (action def in jboss-esb.xml) not working for NotifyFiles notification as for NotifyFTP

by Len DiMaggio (JIRA)

Property substitution in (action def in jboss-esb.xml) not working for NotifyFiles notification as for NotifyFTP ---------------------------------------------------------------------------------------------------------------- Key: JBESB-1588 URL: http://jira.jboss.com/jira/browse/JBESB-1588 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 CP1 Reporter: Len DiMaggio Priority: Minor Project JIRA for SOA-P JIRA: http://jira.jboss.com/jira/browse/SOA-461 -- 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

16 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1587) Management console compile error within SOA-P distribution

by Tom Cunningham (JIRA)

Management console compile error within SOA-P distribution ---------------------------------------------------------- Key: JBESB-1587 URL: http://jira.jboss.com/jira/browse/JBESB-1587 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2.1 CP2 See SOA-460 -- 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

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1552) Misspelling "timeoutInMillies" in org.jboss.soa.esb.actions.Aggregator

by Pavel Kadlec (JIRA)

Misspelling "timeoutInMillies" in org.jboss.soa.esb.actions.Aggregator ---------------------------------------------------------------------- Key: JBESB-1552 URL: http://jira.jboss.com/jira/browse/JBESB-1552 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Pavel Kadlec Misspelled aggreagator's attribute 'timeoutInMillies' -- 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

16 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-1554) JMSCourier incorrectly looks for topic

by Pavel Kadlec (JIRA)

JMSCourier incorrectly looks for topic -------------------------------------- Key: JBESB-1554 URL: http://jira.jboss.com/jira/browse/JBESB-1554 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Pavel Kadlec I created jms-bus topic and I am not able to deploy esb archive. I am getting this exception 13:49:02,459 ERROR [STDERR] org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer 13:49:02,462 ERROR [STDERR] at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:532) 13:49:02,466 ERROR [STDERR] at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:513) 13:49:02,479 ERROR [STDERR] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:223) 13:49:02,483 ERROR [STDERR] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:205) 13:49:02,496 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:304) 13:49:02,501 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:264) 13:49:02,506 ERROR [STDERR] at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java: 5) 13:49:02,515 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) 13:49:02,519 ERROR [STDERR] Caused by: org.jboss.soa.esb.couriers.CourierException: javax.jms.JMSException: This destination does not exist !TOPIC.t ic/aggregator 13:49:02,528 ERROR [STDERR] at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:642) 13:49:02,533 ERROR [STDERR] at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:524) 13:49:02,544 ERROR [STDERR] ... 7 more 13:49:02,548 ERROR [STDERR] Caused by: javax.jms.JMSException: This destination does not exist !TOPIC.topic/aggregator 13:49:02,552 ERROR [STDERR] at org.jboss.mq.server.JMSDestinationManager.createTopic(JMSDestinationManager.java:622) 13:49:02,557 ERROR [STDERR] at org.jboss.mq.server.JMSServerInterceptorSupport.createTopic(JMSServerInterceptorSupport.java:116) 13:49:02,562 ERROR [STDERR] at org.jboss.mq.server.TracingInterceptor.createTopic(TracingInterceptor.java:290) 13:49:02,567 ERROR [STDERR] at org.jboss.mq.server.JMSServerInvoker.createTopic(JMSServerInvoker.java:122) 13:49:02,575 ERROR [STDERR] at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:145) 13:49:02,580 ERROR [STDERR] at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:395) 13:49:02,585 ERROR [STDERR] at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398) 13:49:02,598 ERROR [STDERR] at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748) 13:49:02,603 ERROR [STDERR] ... 1 more I looked at the code of JMSCourier. There is function createMessageConsumer() and inside is else if (JMSEpr.TOPIC_TYPE.equals(sType)) { TopicSession tSess = (TopicSession) getJmsSession(_epr.getAcknowledgeMode()); Topic topic = tSess.createTopic(_epr.getDestinationName()); _messageConsumer = tSess.createConsumer(topic, _epr .getMessageSelector()); } I think that there should be something like else if (JMSEpr.TOPIC_TYPE.equals(sType)) { TopicSession tSess = (TopicSession) getJmsSession(_epr.getAcknowledgeMode()); Topic topic = null; try { topic = (Topic) oJndiCtx.lookup(_epr .getDestinationName()); } catch (NamingException ne) { topic = tSess.createTopic(_epr.getDestinationName()); } _messageConsumer = tSess.createConsumer(topic, _epr .getMessageSelector()); } Everything is OK with this change. -- 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

16 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1556) Provide an option for synchronous invocations of ServiceInvoker to throw an exception rather than retry.

by Kevin Conner (JIRA)

Provide an option for synchronous invocations of ServiceInvoker to throw an exception rather than retry. -------------------------------------------------------------------------------------------------------- Key: JBESB-1556 URL: http://jira.jboss.com/jira/browse/JBESB-1556 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP1 Reporter: Kevin Conner Fix For: 4.2.1 CP2, 4.3 In some circumstances it is desirable to have only one attempt at delivering a synchronous message. For those occasions we should allow the user to specify whether retries should be attempted or not. -- 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

16 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1072) JCA code uses org.jboss.logging.Logger whereas everything else uses org.apache.log4j.Logger

by Mark Little (JIRA)

JCA code uses org.jboss.logging.Logger whereas everything else uses org.apache.log4j.Logger ------------------------------------------------------------------------------------------- Key: JBESB-1072 URL: http://jira.jboss.com/jira/browse/JBESB-1072 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.2 Reporter: Mark Little Assigned To: Kevin Conner Priority: Minor Fix For: 4.2.1 -- 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

16 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1569) Unsafe tag access in JMSEpr

by Kevin Conner (JIRA)

Unsafe tag access in JMSEpr --------------------------- Key: JBESB-1569 URL: http://jira.jboss.com/jira/browse/JBESB-1569 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP2, 4.3 One of the JMSEpr constructors makes an unsafe access to the tag variable while testing for the TRANSACTED element. Unfortunately the value of this variable can only be null at this point. -- 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

16 years, 9 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2008