November 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2469) Remote directory cannot be relative for (S)FTP(S) gateway

by Martin Vecera (JIRA)

Remote directory cannot be relative for (S)FTP(S) gateway --------------------------------------------------------- Key: JBESB-2469 URL: https://jira.jboss.org/jira/browse/JBESB-2469 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP2 Reporter: Martin Vecera FtpImpl, SecureFtpImpl and FtpsImpl are calling "cd" with the directory specified in jboss-esb.xml every time they are getting list of files. When the directory is specified relatively you would need structure like ftp_dir/ftp_dir/ftp_dir/ftp_dir... This must be at least documented, but doing cd every X seconds is waste of time. It should be sufficient only once IMHO. -- 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

12 years, 3 months

5
6
0 / 0

[JBoss JIRA] Created: (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service

by Jiri Pechanec (JIRA)

It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service --------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3022 URL: https://jira.jboss.org/jira/browse/JBESB-3022 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Jiri Pechanec Attachments: soapproxy-diffauth.zip There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed from the client then everything works correctly. But if I have different credentials required for ESB client and different credentials are required by proxied Web Service then I use property <property name="clientCredentialsRequired" value="false" /> to set static credentials for proxied web service. This property works correctly if the ESB service is unsecured. Unfortunately if it is secured then probably the credentials stored in HTTP header stored in ESB message overwrites the static credentials set by the SOAPProxy action. The attached example is modified webservice_proxy_secure QS and has static credentials set to wrong values - so proxied web service should not be invoked. But if ant runtest is executed then the wrong credentials are not used. -- 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

12 years, 3 months

5
11
0 / 0

[JBoss JIRA] Created: (JBESB-3641) JSF issues with jbpm-console and AS6

by Tom Cunningham (JIRA)

JSF issues with jbpm-console and AS6 ------------------------------------ Key: JBESB-3641 URL: https://issues.jboss.org/browse/JBESB-3641 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Investigate / Release note the JSF errors occurring in the jbpm-console on AS6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3357) Mavenise the ESB build

by Kevin Conner (JIRA)

Mavenise the ESB build ---------------------- Key: JBESB-3357 URL: https://jira.jboss.org/browse/JBESB-3357 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.8 Reporter: Kevin Conner Priority: Optional Fix For: 4.9 To be done for 4.9 if we have time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2272) ESB testable against external binaries (product test suite)

by Aleksandar Kostadinov (JIRA)

ESB testable against external binaries (product test suite) ----------------------------------------------------------- Key: JBESB-2272 URL: https://jira.jboss.org/jira/browse/JBESB-2272 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 CP3, 4.2.1 CP2, 4.2.1 CP1, 4.2.1 CP4 Reporter: Aleksandar Kostadinov When running the ESB test suite against external binaries, there is currently a mismatch between libraries downloaded by the test suite and libraries found in the external distribution. This makes running the suite against the external JBoss AS distribution meaningless because doesn't prove ESB will work with the libraries found in the JBoss AS server. As a solution I see, the various junit tasks run by the testsuite should have classpath point at the libraries in the JBoss AS rather than these generated during build and downloaded by the build script. Running the test suite against external binaries should be the same as verifying an ESB installation (be it on top of JBoss AS or standalone). The issue supersedes JBESB-1513 and is the cause of JBESB-1711. -- 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

12 years, 3 months

4
17
0 / 0

[JBoss JIRA] Created: (JBESB-3644) Create pom for rosetta JAR

by Tom Cunningham (JIRA)

Create pom for rosetta JAR -------------------------- Key: JBESB-3644 URL: https://issues.jboss.org/browse/JBESB-3644 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Need a pom.xml detailing the dependencies of the rosetta JAR so that we can release this to maven repositories. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3629) Provide alternative registry implementation

by Tom Cunningham (JIRA)

Provide alternative registry implementation ------------------------------------------- Key: JBESB-3629 URL: https://issues.jboss.org/browse/JBESB-3629 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 The issue here is: in a cluster environment, after a malfunction on JBoss (e.g. JVM crash, erroneous deployment etc) the registry remains with invalid endpoints and the ESB has an erroneous behavior by using those endpoints. Even your removeDeadEPR property is unusable, because as stated in the documentation the "the end-point reference for a service that is [...] slow to respond may, inadvertently, be removed from the registry by mistake". Since we have a cluster and to manually clean the DB is not just to drop the tables and restart the server, this is a major issue for us, because it can lead to erroneous service calls if a server node crashes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3669) Don't copy AS 5 admin-console.war for AS 6 deployments

by Tom Cunningham (JIRA)

Don't copy AS 5 admin-console.war for AS 6 deployments ------------------------------------------------------ Key: JBESB-3669 URL: https://issues.jboss.org/browse/JBESB-3669 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 We're copying in the AS 5 admin-console.war into AS 6 in AS 6 deployment scenarios. We need to copy the ESB plugin into common/deploy/admin-console.war/plugins instead. This is causing a StackOverflowError : Caused by: java.lang.StackOverflowError at java.util.logging.Logger.getResourceBundle(Logger.java:409) [:1.6.0_20] at org.jboss.logmanager.Logger.logRaw(Logger.java:626) [jboss-logmanager.jar:1.2.0.CR9] at org.jboss.logmanager.Logger.log(Logger.java:600) [jboss-logmanager.jar:1.2.0.CR9] at org.jboss.logmanager.Logger.log(Logger.java:612) [jboss-logmanager.jar:1.2.0.CR9] at org.jboss.logmanager.log4j.BridgeLogger.error(BridgeLogger.java:72) [:] at org.jboss.seam.interop.jul.Log4JConversionFilter.logWithThro ... at org.jboss.seam.interop.jul.Log4JConversionFilter.isLoggable(Log4JConversionFilter.java:68) [:2.1.0.SP1] at org.jboss.logmanager.Logger.logRaw(Logger.java:640) [jboss-logmanager.jar:1.2.0.CR9] at org.jboss.logmanager.Logger.log(Logger.java:600) [jboss-logmanager.jar:1.2.0.CR9] at org.jboss.logmanager.Logger.log(Logger.java:612) [jboss-logmanager.jar:1.2.0.CR9] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
4
0 / 0

[JBoss JIRA] (JBESB-3716) IllegalStateException in: JMS listener -> Action -> (EJB using weld/cdi)

by Marco Piraccini (Created) (JIRA)

IllegalStateException in: JMS listener -> Action -> (EJB using weld/cdi) ------------------------------------------------------------------------ Key: JBESB-3716 URL: https://issues.jboss.org/browse/JBESB-3716 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.10 Environment: JBoss 6.0 Reporter: Marco Piraccini We have an integration of this type: (something) -> JMSRouter -> JMS listener -> Action -> EJB (in an EAR deployed in the same JBoss 6.0). The EJB code uses CDI (fires and observes some events). When that happens, the error below is raised. If we don't use the jms-listener, it works perfectly. That seems to be related to that: https://issues.jboss.org/browse/SEAMJMS-16 2011-11-28 15:15:26,960 DEBUG [org.jboss.weld.Event] (Thread-3 (group:HornetQ-client-global-threads-2089334124)) throwing: java.lang.IllegalStateException: Singleton not set for BaseClassLoader@c2909a1{vfs:///E:/Workspace/jboss6/server/default/deploy/xxx.esb} at org.jboss.weld.integration.provider.JBossSingletonProvider$EarSingleton.get(JBossSingletonProvider.java:59) [:6.0.0.Final] at org.jboss.weld.Container.instance(Container.java:58) [:6.0.0.Final] at org.jboss.weld.event.DeferredEventNotification$RunInRequest.isRequestContextActive(DeferredEventNotification.java:119) [:6.0.0.Final] at org.jboss.weld.event.DeferredEventNotification$RunInRequest.run(DeferredEventNotification.java:97) [:6.0.0.Final] at org.jboss.weld.event.DeferredEventNotification.run(DeferredEventNotification.java:64) [:6.0.0.Final] at org.jboss.weld.event.TransactionSynchronizedRunnable.afterCompletion(TransactionSynchronizedRunnable.java:62) [:6.0.0.Final] at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:117) [:6.0.0.Final] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:371) [:6.0.0.Final] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:104) [:6.0.0.Final] at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:159) [:6.0.0.Final] at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1158) [:6.0.0.Final] at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:119) [:6.0.0.Final] at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) [:6.0.0.Final] at org.jboss.soa.esb.listeners.jca.EndpointProxy.endTransaction(EndpointProxy.java:401) [:] at org.jboss.soa.esb.listeners.jca.EndpointProxy.finish(EndpointProxy.java:295) [:] at org.jboss.soa.esb.listeners.jca.EndpointProxy.after(EndpointProxy.java:219) [:] at org.jboss.soa.esb.listeners.jca.EndpointProxy.invoke(EndpointProxy.java:146) [:] at $Proxy290.afterDelivery(Unknown Source) at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:260) [:6.0.0.Final] at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:822) [:6.0.0.Final] at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.Final] at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:940) [:6.0.0.Final] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.0.0.Final] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] (JBESB-3715) Html error on the web page of JBossESB Overview

by Stefan Bunciak (Created) (JIRA)

Html error on the web page of JBossESB Overview ----------------------------------------------- Key: JBESB-3715 URL: https://issues.jboss.org/browse/JBESB-3715 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Environment: Fedora 15, Firefox 8.0 Reporter: Stefan Bunciak Priority: Minor Error in the html code on url http://www.jboss.org/jbossesb/resources/Overview . Anchor tag causing the following error when clicked on the image (probably bad quotes) : Not Found The requested URL /jbossesb/docs/4.0Beta1/manuals/html/ProgrammersGuide_files/image021.png" rel="lightbox was not found on this server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2011