October 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2145) Not working hellowordl_db_registration/readme.txt

by Ondrej Skutka (JIRA)

Not working hellowordl_db_registration/readme.txt ------------------------------------------------- Key: JBESB-2145 URL: https://jira.jboss.org/jira/browse/JBESB-2145 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Ondrej Skutka Priority: Minor When running helloworld_db_registration quickstart according to its readme.txt (and deploy-jms-dests && ant runtest), it fails. This readme should contain correct sequence for quickstart execution. -- 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

17 years, 5 months

2
16
0 / 0

[JBoss JIRA] Created: (JBESB-2119) Create a CertificateLoginModule

by Daniel Bevenius (JIRA)

Create a CertificateLoginModule ------------------------------- Key: JBESB-2119 URL: https://jira.jboss.org/jira/browse/JBESB-2119 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Examples, Security Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.4 CP1 Create a A JAAS Login module that performs authentication by verifying that the certificate that is passed to the ESB by the calling client can be verified against a certificate in a local keystore. -- 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

17 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2123) Overall message size not reflected at service level

by Kevin Conner (JIRA)

Overall message size not reflected at service level --------------------------------------------------- Key: JBESB-2123 URL: https://jira.jboss.org/jira/browse/JBESB-2123 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.4 CP1 The metrics are collected in jmx-console and displayed at the action level by the plugin. They do not, however, appear to be at the service level. -- 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

17 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2137) Support EL values in jbossesb-1.01.xsd

by Viacheslav Kabanovich (JIRA)

Support EL values in jbossesb-1.01.xsd -------------------------------------- Key: JBESB-2137 URL: https://jira.jboss.org/jira/browse/JBESB-2137 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Viacheslav Kabanovich Some attributes (etc. 'port') are restricted with type 'xsd:int', while it is encouraged to set values using EL, like port="${jbr.port}". IDE validation applying to EL values type 'xsd:int', considers it incorrect. It would be better to use a custom type like in components-2.1.xsd. -- 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

17 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2133) Connection failed still called method in "okMethod" ?

by Chris Au (JIRA)

Connection failed still called method in "okMethod" ? ----------------------------------------------------- Key: JBESB-2133 URL: https://jira.jboss.org/jira/browse/JBESB-2133 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Environment: jbossesb-server-4.4.GA OS : Windows-XP Reporter: Chris Au I used below config to test the okMethod and exceptionMethod and found that the okMethod will still be called even the console throws exception about connection failed : <action name="displayMessage" class="com.oi.test.MyJMSListenerAction" process="displayMessage" > <property name="exceptionMethod" value="myHandle"/> <property name="okMethod" value="displayMessage"/> </action> <action name="notificationAction" class="org.jboss.soa.esb.actions.Notifier"> <property name="okMethod" value="notifyOK" /> <property name="destinations"> <NotificationList type="OK"> <target class="NotifyQueues" > <queue connection-factory="SonicMQQueueConnectionFactory" jndi-URL="jnp://@domain@:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces" jndiName="SonicMQ_Queue_test" /> </target> </NotificationList> <NotificationList type="err"> <target class="NotifyConsole" /> <target class="NotifyFiles" > <file URI="/error.log" /> </target> </NotificationList> </property> </action> The connection to sonicMQ tested successful when I did not shut that down on purpose to test the connectivity problem. What I am trying to do is to catch exception when the connection fails. But there does not seem to be a suitable workflow for that. -- 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

17 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2138) Calling services from EJB using ServiceInvoker is broken

by Martin Vecera (JIRA)

Calling services from EJB using ServiceInvoker is broken -------------------------------------------------------- Key: JBESB-2138 URL: https://jira.jboss.org/jira/browse/JBESB-2138 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Martin Vecera Attachments: slsb_fun.tar.bz2 Attached is standalone example (just copy it to quickstarts and run ant deploy-ejb deploy runtest). It has two services, the first one uses EJBProcessor which calles the second service using ServiceInvoker. The behavior is quite strange (notice the two-minute delays and that the second service is called twice eventually): 14:16:31,418 INFO [STDOUT] @@@@@@ In Service1 @@@@@@: 14:16:31,418 INFO [STDOUT] [Message payload example(just a String) ]. 14:16:31,605 INFO [STDOUT] callService("SLSBFun", "Service2") invoked. 14:16:31,606 INFO [STDOUT] Sending message synchronously... 14:18:31,730 INFO [ServiceInvoker] Unresponsive EPR: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_slsbfun_Request2_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] for message: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_slsbfun_Request2_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_slsbfun_Request2_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='e579218d-8efc-4a36-9791-ce156dbca104'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 34eb5749-fbae-4c3c-afb9-462865522b33 ] 14:20:31,777 INFO [ServiceInvoker] Unresponsive EPR: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_slsbfun_Request2_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] for message: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_slsbfun_Request2_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_slsbfun_Request2_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='e579218d-8efc-4a36-9791-ce156dbca104'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 34eb5749-fbae-4c3c-afb9-462865522b33 ] 14:20:31,778 INFO [ServiceInvoker] Delivering message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_slsbfun_Request2_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_slsbfun_Request2_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='e579218d-8efc-4a36-9791-ce156dbca104'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 34eb5749-fbae-4c3c-afb9-462865522b33 ]] to DLQ. 14:20:31,873 INFO [STDOUT] @@@@@@ In Service2 @@@@@@: 14:20:31,874 INFO [STDOUT] [Hello World]. 14:20:31,881 INFO [STDOUT] @@@@@@ In Service2 @@@@@@: 14:20:31,882 INFO [STDOUT] [Hello World]. 14:20:31,900 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_slsbfun_Request1_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: e5b3cef7-880d-44da-b83d-053037509ed7 RelatesTo: jms:correlationID#e5b3cef7-880d-44da-b83d-053037509ed7 -- 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

17 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2140) Schema tools - detection of production/all configuration environment shouldn't be based on the configuration name.

by Pavel Macik (JIRA)

Schema tools - detection of production/all configuration environment shouldn't be based on the configuration name. ------------------------------------------------------------------------------------------------------------------ Key: JBESB-2140 URL: https://jira.jboss.org/jira/browse/JBESB-2140 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.4 Reporter: Pavel Macik -- 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

17 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1348) Make sure that test > 2000 chars is not inserted into JMXData

by Tom Cunningham (JIRA)

Make sure that test > 2000 chars is not inserted into JMXData ------------------------------------------------------------- Key: JBESB-1348 URL: http://jira.jboss.com/jira/browse/JBESB-1348 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 The management console has a JMXData table with a "textvalue" field. There needs to be some check to make sure that nothing greater than the textvalue field length is inserted. -- 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, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-2142) Add/Remove InVMCourier from CourierFactory cache when InVM EPR is registered/unregistered

by Tom Fennelly (JIRA)

Add/Remove InVMCourier from CourierFactory cache when InVM EPR is registered/unregistered ----------------------------------------------------------------------------------------- Key: JBESB-2142 URL: https://jira.jboss.org/jira/browse/JBESB-2142 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Transports Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.4 CP1 And manage the "active" state around these events i.e. set "active" when added, set "inactive" when removed. getInVMCourier should not play with state at all (resetting etc). -- 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

17 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2134) EJBProcessor cannot use EJBs deployed within .esb archive

by Martin Vecera (JIRA)

EJBProcessor cannot use EJBs deployed within .esb archive --------------------------------------------------------- Key: JBESB-2134 URL: https://jira.jboss.org/jira/browse/JBESB-2134 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Rosetta Affects Versions: 4.4 Reporter: Martin Vecera Normally it is possible to have .jar archive with EJBs inside .esb and use those EJBs in custom actions. Unfortunately, this is not true for EJBProcessor since it lookups the EJB in onInitialisation() method. It would be good to 1) put this information into release notes 2) implement new <depends> feture for deployment.xml like in case of .war archives -- 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

17 years, 6 months

2
9
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2008