October 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBESB-1939) sample-bindings.xml contains referenses to jboss.esb.bind.address

by Kevin Conner (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-1939?page=com.atlassian.jira.plu... ] Kevin Conner closed JBESB-1939. ------------------------------- Resolution: Duplicate Issue > sample-bindings.xml contains referenses to jboss.esb.bind.address > ----------------------------------------------------------------- > > Key: JBESB-1939 > URL: https://jira.jboss.org/jira/browse/JBESB-1939 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Configuration, Examples > Affects Versions: 4.4 > Reporter: Daniel Bevenius > > When running the two-servers quickstart I got the following error in the server console: > 13:29:17,040 WARN [ServiceConfigurator] Failed to apply service binding override > java.net.UnknownHostException: ${jboss.esb.bind.address}: ${jboss.esb.bind.address} > at java.net.InetAddress.getAllByName0(InetAddress.java:1145) > at java.net.InetAddress.getAllByName(InetAddress.java:1072) > at java.net.InetAddress.getAllByName(InetAddress.java:1008) > at java.net.InetAddress.getByName(InetAddress.java:958) > at org.jboss.services.binding.ServiceBinding.setBindAddress(ServiceBinding.java:131) > at org.jboss.services.binding.ServiceBinding.<init>(ServiceBinding.java:87) > at org.jboss.services.binding.XMLServicesStore.parseBinding(XMLServicesStore.java:220) > at org.jboss.services.binding.XMLServicesStore.parseConfig(XMLServicesStore.java:181) > at org.jboss.services.binding.XMLServicesStore.parseServer(XMLServicesStore.java:147) > at org.jboss.services.binding.XMLServicesStore.load(XMLServicesStore.java:121) > at org.jboss.services.binding.ServiceBindingManager.initStore(ServiceBindingManager.java:346) > Seems that the jboss.esb.bind.address is being referenced in sample-bindings.xml but might not have been set. Is is set by JBossESBPropertyService but this code will not have be run at this stage in the startup. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2112) Handle security context during invm pass by reference

by Kevin Conner (JIRA)

Handle security context during invm pass by reference ----------------------------------------------------- Key: JBESB-2112 URL: https://jira.jboss.org/jira/browse/JBESB-2112 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 The security context is included in an ESB message when it is sent to a target service. If this is passed over InVM/pass by reference then the context will be removed from the shared message concurrently with the service processing. -- 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

15 years, 7 months

1
3
0 / 0

[JBoss JIRA] Commented: (JBESB-1939) sample-bindings.xml contains referenses to jboss.esb.bind.address

by Markus Heidt (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-1939?page=com.atlassian.jira.plu... ] Markus Heidt commented on JBESB-1939: ------------------------------------- This is a major issue for me as well. In my case I cannot use the ESB in a multiple instance environment. https://www.jboss.org/community/docs/DOC-9384 When I have esb on ports-01, the overwriting fails due to this error and it falls back to the default ports. And if I change ${jboss.esb.bind.address} to ${jboss.bind.address} in the sample-bindings, as I read in the forum, my esb service fails, which doesn't, when going the default route. > sample-bindings.xml contains referenses to jboss.esb.bind.address > ----------------------------------------------------------------- > > Key: JBESB-1939 > URL: https://jira.jboss.org/jira/browse/JBESB-1939 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Configuration, Examples > Affects Versions: 4.4 > Reporter: Daniel Bevenius > > When running the two-servers quickstart I got the following error in the server console: > 13:29:17,040 WARN [ServiceConfigurator] Failed to apply service binding override > java.net.UnknownHostException: ${jboss.esb.bind.address}: ${jboss.esb.bind.address} > at java.net.InetAddress.getAllByName0(InetAddress.java:1145) > at java.net.InetAddress.getAllByName(InetAddress.java:1072) > at java.net.InetAddress.getAllByName(InetAddress.java:1008) > at java.net.InetAddress.getByName(InetAddress.java:958) > at org.jboss.services.binding.ServiceBinding.setBindAddress(ServiceBinding.java:131) > at org.jboss.services.binding.ServiceBinding.<init>(ServiceBinding.java:87) > at org.jboss.services.binding.XMLServicesStore.parseBinding(XMLServicesStore.java:220) > at org.jboss.services.binding.XMLServicesStore.parseConfig(XMLServicesStore.java:181) > at org.jboss.services.binding.XMLServicesStore.parseServer(XMLServicesStore.java:147) > at org.jboss.services.binding.XMLServicesStore.load(XMLServicesStore.java:121) > at org.jboss.services.binding.ServiceBindingManager.initStore(ServiceBindingManager.java:346) > Seems that the jboss.esb.bind.address is being referenced in sample-bindings.xml but might not have been set. Is is set by JBossESBPropertyService but this code will not have be run at this stage in the startup. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2111) Remove addressing/security support from EBWS

by Kevin Conner (JIRA)

Remove addressing/security support from EBWS -------------------------------------------- Key: JBESB-2111 URL: https://jira.jboss.org/jira/browse/JBESB-2111 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1 Reporter: Kevin Conner Fix For: 4.4 CP1 There is more work needing doing before this is fit for purpose. We are removing this from the current codebase in order to allow a CR release of the platform to be created. This will be removed from the schema and documentation. -- 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

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2046) ScheduleListener ignores lifecycle events

by Kevin Conner (JIRA)

ScheduleListener ignores lifecycle events ----------------------------------------- Key: JBESB-2046 URL: https://jira.jboss.org/jira/browse/JBESB-2046 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 The ScheduleListener has its own way of doing lifecycle, distinct from the ManagedLifecycle. We need to change it to use the expected methods. -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2109) Revisit hibernate integration

by Kevin Conner (JIRA)

Revisit hibernate integration ----------------------------- Key: JBESB-2109 URL: https://jira.jboss.org/jira/browse/JBESB-2109 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Kevin Conner We need to revisit the hibernate integration and have another think about how this can be improved. The current implementation overwrites the hibernate session factory in JNDI without any checks to see whether it is safe to do so. Any active session at the JNDI location will be closed and a new one created using the gateway's configuration. This means that if the session factory had been previously setup by an application then we have no guarantee that we are duplicating the factory. Further complications arise when you consider that someone may want multiple listeners, doing different processing, on the same configuration. At present there is nothing to prevent the second instance from closing, then overwriting, the first. In addition, undeploying the listener will close the current factory leaving the application to cleanup, if indeed it can handle it. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2104) Lifecycle Controller does not configure thread context loader before invoking lifecycle methods

by Kevin Conner (JIRA)

Lifecycle Controller does not configure thread context loader before invoking lifecycle methods ----------------------------------------------------------------------------------------------- Key: JBESB-2104 URL: https://jira.jboss.org/jira/browse/JBESB-2104 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 The consequence of this is that invocations to start/stop occur within the context of a classloader which is not associated with the listener. -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2105) NPE when invoking secured service without credentials

by Martin Vecera (JIRA)

NPE when invoking secured service without credentials ----------------------------------------------------- Key: JBESB-2105 URL: https://jira.jboss.org/jira/browse/JBESB-2105 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Security Affects Versions: 4.4 Reporter: Martin Vecera Following exception is thrown when secured service is invoked directly using ServiceInvoker without credentials in the message. I'd expect SecurityServiceException instead. 11:20:34,090 INFO [ESBCallback] Cleaning message store 11:20:37,190 ERROR [STDERR] Exception in thread "pool-57-thread-1" 11:20:37,190 ERROR [STDERR] java.lang.NullPointerException 11:20:37,190 ERROR [STDERR] at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89) 11:20:37,190 ERROR [STDERR] at org.jboss.soa.esb.services.security.PublicCryptoUtil.decrypt(PublicCryptoUtil.java:198) 11:20:37,190 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipelineSecured(ActionProcessingPipeline.java:428) 11:20:37,190 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:389) 11:20:37,190 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:538) 11:20:37,190 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) 11:20:37,190 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) 11:20:37,190 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2102) InVMCourier should throw a courier exception if inactive

by Kevin Conner (JIRA)

InVMCourier should throw a courier exception if inactive -------------------------------------------------------- Key: JBESB-2102 URL: https://jira.jboss.org/jira/browse/JBESB-2102 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 The InVMCourier currently returns null for a pickup, false for a delivery, when it is inactive. Unfortunately this does not suggest a fault in the pickup case, resulting in the same courier being invoked shortly afterwards. In addition to this the courier is logging (at DEBUG) a message to say that it is inactive along with a stacktrace. This can very quickly swamps the logs. We need to have the check throw an exception (so that it is consistent in both cases) and therefore allow any retry/backoff functionality to kick in. -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2101) load_generator quickstart:the serviceCategory name is missing in groovy script

by Jim Ma (JIRA)

load_generator quickstart:the serviceCategory name is missing in groovy script ------------------------------------------------------------------------------ Key: JBESB-2101 URL: https://jira.jboss.org/jira/browse/JBESB-2101 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Jim Ma Fix For: 4.4 CP1 The load_generator quickstart is failing with this exception: load-report-secure: [java] USER=admin PASSWORD=admin [java] log4j:WARN No appenders could be found for logger (org.jboss.remoting.transport.socket.MicroSocketClientInvoker). [java] log4j:WARN Please initialize the log4j system properly. [java] log4j:WARN No appenders could be found for logger (org.jboss.security.SecurityAssociation). [java] log4j:WARN Please initialize the log4j system properly. [java] Exception in thread "main" javax.management.InstanceNotFoundException: jboss.esb:service-name=DummyJMSLoad,deployment=Quickstart_load_generator.esb,category=MessageCounter is not registered. After add service-category to MBean name in ServiceMessageCounter, load_generator quickstart needs to update. -- 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

15 years, 7 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2008