February 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1650) Clean up OracleAQ documentation

by Tom Cunningham (JIRA)

Clean up OracleAQ documentation ------------------------------- Key: JBESB-1650 URL: http://jira.jboss.com/jira/browse/JBESB-1650 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.2.1 CP2 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2.1 CP3 Got some notes from Narayanan Raghavan about his experience with the OracleAQ message provider. They are using it and it is working well but the experience getting it configured could be a little smoother : - they didn't need ojdbc14.jar (need to double check this) - they needed the "full version" of cglib.jar (the full version is in the EAP) - they found the sample jboss-esb.xml confusing - it talks about moving a message from one OracleAQ -> another OracleAQ, and there should be a sample provided of moving a message from OracleAQ - > JBoss Messaging -- 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-1562) Investigate permgen usage

by Kevin Conner (JIRA)

Investigate permgen usage ------------------------- Key: JBESB-1562 URL: http://jira.jboss.com/jira/browse/JBESB-1562 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 We need to investigate the current permgen usage to make sure there are no leaks. -- 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-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-2217) Implement support for schema import in EBWS WSDL generation/action pipeline validation.

by Kevin Conner (JIRA)

Implement support for schema import in EBWS WSDL generation/action pipeline validation. --------------------------------------------------------------------------------------- Key: JBESB-2217 URL: https://jira.jboss.org/jira/browse/JBESB-2217 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Web Services Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 -- 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
11
0 / 0

[JBoss JIRA] Created: (JBESB-2323) Implement support for schema import in EBWS WSDL generation/action pipeline validation.

by Kevin Conner (JIRA)

Implement support for schema import in EBWS WSDL generation/action pipeline validation. --------------------------------------------------------------------------------------- Key: JBESB-2323 URL: https://jira.jboss.org/jira/browse/JBESB-2323 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Web Services Affects Versions: 4.4, 4.4 CP1 Reporter: Kevin Conner Fix For: 4.4 CP3 -- 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-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-2448) The Get or Post request 'http://localhost:8080/jbossesb/httpgateway/serviceA' can not be passed in ESB service through HttpGateway

by Jim Ma (JIRA)

The Get or Post request 'http://localhost:8080/jbossesb/httpgateway/serviceA' can not be passed in ESB service through HttpGateway ----------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-2448 URL: https://jira.jboss.org/jira/browse/JBESB-2448 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Jim Ma When context value of <http-bus> is configured to "/jbossesb/httpgateway/serviceA" ,the HttpGatewayListener will use name "jbossesb/httpgateway/serviceA" to create web context and use "/" to create servlet mapping . The Get or Post request for "http://localhost:8080/jbossesb/httpgateway/serviceA" can not be passed in HttpDistpatchServlet. I think we can use "jbossesb/httpgateway" to create web context and use "/serviceA/*" to create servlet mapping , then all the following requests can be passed in ESB service. http://localhost:8080/jbossesb/httpgateway/serviceA/1234 http://localhost:8080/jbossesb/httpgateway/serviceA/5678 http://localhost:8080/jbossesb/httpgateway/serviceA?a=b http://localhost:8080/jbossesb/httpgateway/serviceA/ -- 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
4
0 / 0

[JBoss JIRA] Created: (JBESB-2376) Check classloader configuration in the http gateway

by Kevin Conner (JIRA)

Check classloader configuration in the http gateway --------------------------------------------------- Key: JBESB-2376 URL: https://jira.jboss.org/jira/browse/JBESB-2376 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 Looks like it is deliberately ignoring the context class loader, need to make sure this is correct. My gut feeling is that it is wrong as it would appear to allow configuration of a composer class but, obviously, would not necessarily have access to it. Too late for 4.5. -- 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

4
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 February 2009