December 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2235) Upgrade jBPM to version 3.3.0

by Kevin Conner (JIRA)

Upgrade jBPM to version 3.3.0 ----------------------------- Key: JBESB-2235 URL: https://jira.jboss.org/jira/browse/JBESB-2235 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow 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

16 years, 1 month

3
22
0 / 0

[JBoss JIRA] Created: (JBESB-2227) Asynchronous sending of a fault message causes the fault to be raised

by Kevin Conner (JIRA)

Asynchronous sending of a fault message causes the fault to be raised --------------------------------------------------------------------- Key: JBESB-2227 URL: https://jira.jboss.org/jira/browse/JBESB-2227 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1, 4.4 Reporter: Kevin Conner Fix For: 4.5, 4.4 CP2 -- 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

16 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1711) ESB unit test suite hangs when run against SOA-P CP1

by Aleksandar Kostadinov (JIRA)

ESB unit test suite hangs when run against SOA-P CP1 ---------------------------------------------------- Key: JBESB-1711 URL: http://jira.jboss.com/jira/browse/JBESB-1711 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Aleksandar Kostadinov Assigned To: Aleksandar Kostadinov unzip SOA-P distribution in $WORKSPACE/jbosssoa chprop product.properties org.jboss.esb.server.home "$WORKSPACE/jbosssoa/jboss-as" chprop product.properties org.jboss.esb.server.config $SERVER_NAME chprop product.properties org.jboss.esb.test.ftp.hostname dev39.qa.atl.jboss.com chprop product.properties org.jboss.esb.test.ftp.user user chprop product.properties org.jboss.esb.test.ftp.pwd pass chprop product.properties org.jboss.esb.test.ftp.dir /esb-in-soa then: cd product ant org.jboss.esb.integration.test Test suite hangs after first few tests. -- 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

16 years, 1 month

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET

by Burr Sutter (JIRA)

EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET ------------------------------------------------------------------------------- Key: JBESB-2052 URL: https://jira.jboss.org/jira/browse/JBESB-2052 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Burr Sutter The WSDL and the quickstart that creates it are attached. Here is the exact error message from Visual Studio/Visual Basic: Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding 'FetchCustomerBinding' from namespace 'http://soa.jboss.org/ESBWebServiceSample'. The operation 'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace 'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The operation has no matching binding. Check if the operation, input and output names in the Binding section match with the corresponding names in the PortType section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My Project\Settings.settings 1 1 WindowsApplication1 -- 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

16 years, 1 month

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-2241) jUDDI does not work with MS-SQL

by Jervis Liu (JIRA)

jUDDI does not work with MS-SQL ------------------------------- Key: JBESB-2241 URL: https://jira.jboss.org/jira/browse/JBESB-2241 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 CP1 Reporter: Jervis Liu Assignee: Jervis Liu jUDDI does not work with MS-SQL, I got following exceptions: 2008-12-11 16:11:23,031 WARN [org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle] Unexpected exception caught while initialisation java.lang.NullPointerException at org.apache.ws.scout.registry.infomodel.ClassificationImpl.setClassificationScheme(ClassificationImpl.java:103) at org.apache.ws.scout.registry.LifeCycleManagerImpl.createClassification(LifeCycleManagerImpl.java:198) at org.apache.ws.scout.registry.LifeCycleManagerImpl.createClassification(LifeCycleManagerImpl.java:210) at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findService(JAXRRegistryImpl.java:425) at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.registerEPR(JAXRRegistryImpl.java:140) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.internal.soa.esb.services.registry.RegistryService$1.invoke(RegistryService.java:61) at $Proxy36.registerEPR(Unknown Source) at org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor.registerEPR(InVMRegistryInterceptor.java:51) at org.jboss.soa.esb.services.registry.RegistryFactory$HeadRegistryInterceptor.registerEPR(RegistryFactory.java:242) at org.jboss.soa.esb.listeners.RegistryUtil.register(RegistryUtil.java:143) at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:209) at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:134) at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:105) at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:62) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:105) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) This is because the juddi version we are currently using - juddi-2.0rc5 does not ship with scripts to create and popuate juddi tables for MS-SQL. We need to provide db scripts to create tables and populate data by ourself. These scripts should stay under jbossesb\product\install\jUDDI-registry\sql\mssql. -- 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

16 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-2242) JmsSession should cache the acknowledge mode rather than deferring to the underlying session

by Kevin Conner (JIRA)

JmsSession should cache the acknowledge mode rather than deferring to the underlying session -------------------------------------------------------------------------------------------- Key: JBESB-2242 URL: https://jira.jboss.org/jira/browse/JBESB-2242 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 The reason for this is to ensure that failed sessions do not remain in the 'in use' state if a subsequent call to getAcknowledgeMode generates an error. -- 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

16 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2223) Upgrade AS support to AS 4.2.3

by Kevin Conner (JIRA)

Upgrade AS support to AS 4.2.3 ------------------------------ Key: JBESB-2223 URL: https://jira.jboss.org/jira/browse/JBESB-2223 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 Update the standalone server and base it on the core of AS 4.2.3 -- 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

16 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2237) Revisit spring integration

by Kevin Conner (JIRA)

Revisit spring integration -------------------------- Key: JBESB-2237 URL: https://jira.jboss.org/jira/browse/JBESB-2237 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 We need to revisit the spring integration, paying particular attention to the scoping of the resources and classloader usage. -- 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

16 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2254) PermGen when running some of the quickstarts

by Daniel Bevenius (JIRA)

PermGen when running some of the quickstarts -------------------------------------------- Key: JBESB-2254 URL: https://jira.jboss.org/jira/browse/JBESB-2254 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Process flow Reporter: Daniel Bevenius Priority: Critical Fix For: 4.5 When running the following quickstarts I'm getting 'java.lang.OutOfMemoryError: PermGenSpace': messagefilter business_rules_service business_ruleservice_stateful This sounds similar to this jira: https://jira.jboss.org/jira/browse/SOA-74;jsessionid=20E22A84362612657DB6... Modifying the memory settings as describe by the above jira seems to get rid of this issue. Will check with Kev when he gets back about this. -- 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

16 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2232) Interrputed Exception in Embedded JBossESB server.

by Jeff Yu (JIRA)

Interrputed Exception in Embedded JBossESB server. -------------------------------------------------- Key: JBESB-2232 URL: https://jira.jboss.org/jira/browse/JBESB-2232 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.4 Reporter: Jeff Yu Priority: Minor Fix For: 4.5 Steps to reproduce the error: 0. Install the JBossESB 4.4.GA into JBoss AS 4.2.2. 1. start the server, bin/run.sh 2. Open another window, go to the samples/quickstarts/bpm_orchestration2 ant deploy ant deployProcess ant startProcess 3. Press 'Ctrl + C' in the server window. you will see following exception (Note:this error didn't happen on jbossesb-server-4.4.GA) ============================ 15:13:17,510 INFO [HypersonicDatabase] Database standalone closed clean 15:13:17,522 WARN [NewMsgsWorker] Interrupted waiting for new msg check java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at EDU.oswego.cs.dl.util.concurrent.Semaphore.acquire(Semaphore.java:108) at EDU.oswego.cs.dl.util.concurrent.SemaphoreControlledChannel.take(SemaphoreControlledChannel.java:131) at org.jboss.resource.adapter.mail.inflow.NewMsgsWorker.run(NewMsgsWorker.java:75) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) at java.lang.Thread.run(Thread.java:595) 15:13:17,743 INFO [TransactionManagerService] Stopping recovery manager 15:13:17,794 INFO [Server] Shutdown complete -- 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

16 years, 1 month

4
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues December 2008