November 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1498) StackOverflowError caused by NamingContext

by Naveen Malik (JIRA)

StackOverflowError caused by NamingContext ------------------------------------------ Key: JBESB-1498 URL: http://jira.jboss.com/jira/browse/JBESB-1498 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Environment: JBoss AS 4.2.1, Java 1.5.0_12 Reporter: Naveen Malik When starting JBoss AS 4.2.1 with JBoss ESB 4.2.1GA installed a stack overflow exception is logged several times: 2008-01-17 16:13:52,336 WARN [org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle] Unexpected error from doRun() java.lang.StackOverflowError at java.lang.StringCoding.decode(StringCoding.java:228) at java.lang.String.<init>(String.java:405) at java.lang.String.<init>(String.java:433) at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at java.net.Socket.<init>(Socket.java:366) at java.net.Socket.<init>(Socket.java:266) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1387) at org.jnp.interfaces.NamingContext.list(NamingContext.java:795) at javax.naming.InitialContext.list(InitialContext.java:401) at org.jboss.ha.jndi.TreeHead.list(TreeHead.java:354) at org.jboss.ha.jndi.HAJNDI.list(HAJNDI.java:161) at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:258) at $Proxy70.list(Unknown Source) at org.jnp.interfaces.NamingContext.list(NamingContext.java:802) at javax.naming.InitialContext.list(InitialContext.java:401) at org.jboss.ha.jndi.TreeHead.list(TreeHead.java:354) at org.jboss.ha.jndi.HAJNDI.list(HAJNDI.java:161) at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:258) at $Proxy70.list(Unknown Source) at org.jnp.interfaces.NamingContext.list(NamingContext.java:802) at javax.naming.InitialContext.list(InitialContext.java:401) at org.jboss.ha.jndi.TreeHead.list(TreeHead.java:354) at org.jboss.ha.jndi.HAJNDI.list(HAJNDI.java:161) at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:258) at $Proxy70.list(Unknown Source) ... at org.jnp.interfaces.NamingContext.list(NamingContext.java:802) at javax.naming.InitialContext.list(InitialContext.java:401) at org.jboss.ha.jndi.TreeHead.list(TreeHead.java:354) at org.jboss.ha.jndi.HAJNDI.list(HAJNDI.java:161) at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:258) at $Proxy70.list(Unknown Source) -- 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

5
18
0 / 0

[JBoss JIRA] Created: (JBESB-952) Classloading issue for .war files within .ears

by Tom Cunningham (JIRA)

Classloading issue for .war files within .ears ---------------------------------------------- Key: JBESB-952 URL: http://jira.jboss.com/jira/browse/JBESB-952 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Reporter: Tom Cunningham Assigned To: Mark Little There seems to be a classloading problem on redeploy for .WAR files within .ESB packages - and also with .WAR files side by side .ESB files in an .EAR. This was seen in JBESB-721, which was fixed by repackaging things. Basically if you have an ESB file set up like this : --- My.esb --------My.jar --------My.war --------META-INF/jboss-esb.xml The classes references in My.jar don't seem to be flushed when the .esb redeploys, because if they are accessed from .esb actions, they cause ClassCastExceptions, yet they work from the .war. helloworld_hibernate_action in SVN revision 14780 are a decent test case for this. -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2128) Cross-Site scripting issues in ESB management console

by Kevin Conner (JIRA)

Cross-Site scripting issues in ESB management console ----------------------------------------------------- Key: JBESB-2128 URL: https://jira.jboss.org/jira/browse/JBESB-2128 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.4 CP1 Go through all jsp pages and make sure that all variable output is encoded for HTML display. -- 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, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-1996) Evaluate, if a AS/400 Dataqueue Ressource Adapter is usable for Jboss and/or Jboss ESB

by Heiko Wiesjbossner (JIRA)

Evaluate, if a AS/400 Dataqueue Ressource Adapter is usable for Jboss and/or Jboss ESB -------------------------------------------------------------------------------------- Key: JBESB-1996 URL: https://jira.jboss.org/jira/browse/JBESB-1996 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Reporter: Heiko Wiesjbossner A Dataqueue is like a jms queue on IBM's (AS/400 / Iseries / System i / and all the other names for the AS/400). Whith the Ressource Adapter i wrote you can transform the Dataqueue Message into a jms Message without any coding. Configuration is made with annotations. The rest is handled by the RA. I think, this is the best way to connect from old school RPG or Cobol Applications to J2EE. It is a very performant and ressource saving way. -- 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, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-1678) Style in ESB management console is invalid

by Jiri Pechanec (JIRA)

Style in ESB management console is invalid ------------------------------------------ Key: JBESB-1678 URL: http://jira.jboss.com/jira/browse/JBESB-1678 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 CP2 Reporter: Jiri Pechanec Assigned To: Tom Cunningham Priority: Minor The file style_master.css in ESB console contains invalid style definition, see snippet TH { background-color : #000099; color: #DEB887; font-weight: bold; }.bg_table { background-color : #DEB887; } }.bg_cell{ background-color : #ffffff; } The bg_cell definition is orphaned. -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1797) Repackage management console

by Kevin Conner (JIRA)

Repackage management console ---------------------------- Key: JBESB-1797 URL: http://jira.jboss.com/jira/browse/JBESB-1797 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.3 Reporter: Kevin Conner Fix For: 4.4 We need to revisit the packaging of the management console and come up with a solution that allows the modification of the database without recompiling the code. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2185) Patch for [jUDDI retains invalid EPRs]

by Joakim Sandström (JIRA)

Patch for [jUDDI retains invalid EPRs] -------------------------------------- Key: JBESB-2185 URL: https://jira.jboss.org/jira/browse/JBESB-2185 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Joakim Sandström Patch for 'jUDDI retains invalid EPRs' issue (JBESB-866). Patch: The RegistryUtil.register method unregisters matching EPR's using unregister(category, name, epr) before (re)registering the same EPR. Not included in the patch: Registry.unRegisterEPR(serviceCategoryName, serviceName, epr) could return a boolean true/false and not raise a ServiceNotFoundException if the service isn't found - to avoid unneccesary stack traces in the log. -- 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, 1 month

3
13
0 / 0

[JBoss JIRA] Created: (JBESB-1646) Add support for making schedule-provider Jobs clusterable

by Tom Fennelly (JIRA)

Add support for making schedule-provider Jobs clusterable --------------------------------------------------------- Key: JBESB-1646 URL: http://jira.jboss.com/jira/browse/JBESB-1646 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly This should support "singleton" execution of a job in a clustered env, with fail-over etc. See http://java-x.blogspot.com/2006/12/using-quartz-scheduler-in-cluster.html -- 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, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-2203) Duplicate service names during cluster startup

by Joakim Sandström (JIRA)

Duplicate service names during cluster startup ---------------------------------------------- Key: JBESB-2203 URL: https://jira.jboss.org/jira/browse/JBESB-2203 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 Environment: jboss esb cluster, replicated mysql 5.1. Reporter: Joakim Sandström If I startup more than one cluster node at the same time when uddi is empty it will be populated as follows: -Service A -- node1 EPR -Service A -- node2 EPR Expected uddi content; -Service A --node1 EPR --node2 EPR The esb cluster nodes access the same mysq node (transaction READ_COMMITTED). -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1936) Create a contract publisher to handle remote WS endpoints

by Kevin Conner (JIRA)

Create a contract publisher to handle remote WS endpoints --------------------------------------------------------- Key: JBESB-1936 URL: https://jira.jboss.org/jira/browse/JBESB-1936 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 We have a contract publisher that exposes wsdl for a co-located JBoss WS endpoint, WebserviceContractPublisher. We should have an equivalent that can be used to expose the wsdl of remote services through 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

17 years, 2 months

3
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 November 2008