July 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1883) quickstart: business_ruleservice_ruleAgent has an extraneous processDefinition directory

by Burr Sutter (JIRA)

quickstart: business_ruleservice_ruleAgent has an extraneous processDefinition directory ---------------------------------------------------------------------------------------- Key: JBESB-1883 URL: https://jira.jboss.org/jira/browse/JBESB-1883 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 Reporter: Burr Sutter Priority: Minor The business_ruleservice_ruleAgent quickstart should have its processDefinition folder removed. -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-511) Add integration test for default SFTP EPR.

by Mark Little (JIRA)

Add integration test for default SFTP EPR. ------------------------------------------ Key: JBESB-511 URL: http://jira.jboss.com/jira/browse/JBESB-511 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Testing Reporter: Mark Little Assigned To: Bruno Georges Fix For: 4.2 -- 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

15 years, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (JBESB-506) Consider Mina support

by Mark Little (JIRA)

Consider Mina support --------------------- Key: JBESB-506 URL: http://jira.jboss.com/jira/browse/JBESB-506 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Reporter: Mark Little Assigned To: Mark Little Priority: Optional Fix For: 5.0 http://mina.apache.org/ -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time

by Jiri Pechanec (JIRA)

Odd jUDDI behaviour when under the load for longer time ------------------------------------------------------- Key: JBESB-1507 URL: http://jira.jboss.com/jira/browse/JBESB-1507 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 Reporter: Jiri Pechanec Priority: Critical Attachments: server.log I have run something like performance/stress test simulating access to jUDDI by many clients. After few runs the jUDDI started to generate exceptions. See attached log -- 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

15 years, 7 months

6
30
0 / 0

[JBoss JIRA] Created: (JBESB-1801) bpm_orchestartion3 quickstart does not report the token id for signalling

by Jiri Pechanec (JIRA)

bpm_orchestartion3 quickstart does not report the token id for signalling ------------------------------------------------------------------------- Key: JBESB-1801 URL: http://jira.jboss.com/jira/browse/JBESB-1801 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP3 Environment: Embedded, production Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP3 The quickstart should print on the screen the id of token that should be used for signalling -- 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

15 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-1695) jBPM datasource should be XA datasource

by Jiri Pechanec (JIRA)

jBPM datasource should be XA datasource --------------------------------------- Key: JBESB-1695 URL: http://jira.jboss.com/jira/browse/JBESB-1695 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow, Rosetta Affects Versions: 4.2.1 CP2 Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP3 If the SQL listener with transactions is used configured according helloworld_tx_sql and is enhanced with jBPM use - start service, it fails because both datasources are local. To prevent the issue these steps should be done 1) Change the jBPM DS to be XA datasource - this means that schme toll must be also modified 2) Change QS to use H2 database and XA datasource - it serves users as guidline 3) Switch to h2 database for all datasources -- 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

15 years, 8 months

3
15
0 / 0

[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

15 years, 8 months

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

15 years, 8 months

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

15 years, 8 months

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

15 years, 8 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2008