August 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2634) Can not use mode=OUT in @WebParam

by Lan Chen (JIRA)

Can not use mode=OUT in @WebParam --------------------------------- Key: JBESB-2634 URL: https://jira.jboss.org/jira/browse/JBESB-2634 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Affects Versions: 4.5 Environment: jbossesb-server-4.5.GA Reporter: Lan Chen I tried to add company required response header information (bottom up design, generate wsdl file by annotations) 1. By @WebResult (header=true) The header part published correctly in wsdl file but transfered in SOAP:body instead of SOAP:header 2. By @WebParam(mode=OUT) This cause deploy error. Any suggestions? Thanks. Lan -- 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

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2624) Error running bpm_orchestration3

by Marek Baluch (JIRA)

Error running bpm_orchestration3 -------------------------------- Key: JBESB-2624 URL: https://jira.jboss.org/jira/browse/JBESB-2624 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 CP2 Reporter: Marek Baluch Running this step of the quickstart: 5. In Window1, if the Instance ID you found in Step 4 was 1, type 'ant -Dtoken=1 signalProcess' produces the following error: Buildfile: build.xml BUILD FAILED Target "signalProcess" does not exist in the project "Quickstart_bpm_orchestration3". The signalProcess targer in the ant build file is needed in order to continue with the quickstart. -- 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

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2557) Transactions marked for rollback leave BPM token locked.

by Sean Burns (JIRA)

Transactions marked for rollback leave BPM token locked. -------------------------------------------------------- Key: JBESB-2557 URL: https://jira.jboss.org/jira/browse/JBESB-2557 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Environment: Jboss 4.2.3 with Jboss messaging and Jboss ESB 4.5 Reporter: Sean Burns When the ESB invokes a jBPM action it locks the token using "ESB_ASYNC_SIGNAL_ACTION". If the transaction is then marked for rollback (via a EJB throwing a Runtime Exception) the token is not unlocked, which means that there can be no more invocations of the process until that token is manually unlocked. -- 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

14 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2590) 'access_point_url' column in jUDDI schema too short

by Lukas Petrovicky (JIRA)

'access_point_url' column in jUDDI schema too short --------------------------------------------------- Key: JBESB-2590 URL: https://jira.jboss.org/jira/browse/JBESB-2590 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 CP5 Reporter: Lukas Petrovicky When running our quickstart tests on SOA-P 4.2.0 CP04 CR2 (configured for MySQL), the following regression has been identified. It happens on deploying of one of the quickstarts: 2009-05-25 15:08:38,450 ERROR [org.apache.juddi.function.SaveBindingFunction] com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'ACCESS_POINT_URL' at row 1 2009-05-25 15:08:38,451 ERROR [org.apache.juddi.registry.local.RequestHandler] com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'ACCESS_POINT_URL' at row 1 2009-05-25 15:08:38,454 ERROR [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Errors occurred during save. 2009-05-25 15:08:38,456 WARN [org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle] Unexpected exception caught while initialisation java.lang.NullPointerException at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.saveRegistryObject(JAXRRegistryImpl.java:632) at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.registerEPR(JAXRRegistryImpl.java:160) 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:597) at org.jboss.internal.soa.esb.services.registry.RegistryService$1.invoke(RegistryService.java:61) at $Proxy36.registerEPR(Unknown Source) 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:133) 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:83) 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:597) 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 sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:566) 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:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) 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:597) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266) 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:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:108) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180) 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:597) 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.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419) 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:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 2009-05-25 15:08:38,460 WARN [org.jboss.system.ServiceController] Problem starting service jboss.esb:deployment=Quickstart_JMS_Secured.esb org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: java.lang.NullPointerException ... The reason for this was found in the MySQL query log: INSERT INTO BINDING_TEMPLATE (SERVICE_KEY,BINDING_KEY,ACCESS_POINT_TYPE,ACCESS_POINT_URL,HOSTING_REDIRECTOR,LAST_UPDATE) VALUES ('C0BF8530-4928-11DE-8530-FA3BE6466A06','29631990-492D-11DE-9990-ED4379607B48','other','<wsa:From xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"><wsa:Address>jms:jnp://127.0.0.1:1099#queue/quickstart_jms_secured_Request_esb</wsa:Address><wsa:ReferenceProperties><jbossesb:java.naming.factory.initial xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">org.jnp.interfaces.NamingContextFactory</jbossesb:java.naming.factory.initial><jbossesb:java.naming.provider.url xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">jnp://127.0.0.1:1099</jbossesb:java.naming.provider.url><jbossesb:java.naming.factory.url.pkgs xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">org.jboss.naming:org.jnp.interfaces</jbossesb:java.naming.factory.url.pkgs><jbossesb:destination-type xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">queue</jbossesb:destination-type><jbossesb:destination-name xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">queue/quickstart_jms_secured_Request_esb</jbossesb:destination-name><jbossesb:specification-version xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">1.1</jbossesb:specification-version><jbossesb:connection-factory xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">ConnectionFactory</jbossesb:connection-factory><jbossesb:persistent xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">true</jbossesb:persistent><jbossesb:acknowledge-mode xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">AUTO_ACKNOWLEDGE</jbossesb:acknowledge-mode><jbossesb:jms-security-principal xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">esbuser</jbossesb:jms-security-principal><jbossesb:jms-security-credential xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">esbpassword</jbossesb:jms-security-credential><jbossesb:transacted xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">false</jbossesb:transacted><jbossesb:type xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">urn:jboss/esb/epr/type/jms</jbossesb:type></wsa:ReferenceProperties></wsa:From>',null,'2009-05-25 15:08:38') The 'access_point_url' is varchar(2000), but the text that we are trying to supply is longer than that. -- 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

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2447) Add quickstart for HttpGateway

by Jim Ma (JIRA)

Add quickstart for HttpGateway ------------------------------ Key: JBESB-2447 URL: https://jira.jboss.org/jira/browse/JBESB-2447 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.5 Reporter: Jim Ma -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2425) BeanConfigActionProcessor swallows specialized exceptions

by Hudaverdi Cakir (JIRA)

BeanConfigActionProcessor swallows specialized exceptions --------------------------------------------------------- Key: JBESB-2425 URL: https://jira.jboss.org/jira/browse/JBESB-2425 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Hudaverdi Cakir The current implementation of BeanConfigActionProcessor catches at java.lang.Exception level and re-packages these exceptions into an ActionProcessingException. But when a particular Action throws a specialized exception, e.g. ActionProcessingFaultException, the information gets lost and the processing can not be controlled as desired. -- 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

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2207) SqlTableGatewayListener does not support synchronous delivery.

by Tomasz Juchniewicz (JIRA)

SqlTableGatewayListener does not support synchronous delivery. -------------------------------------------------------------- Key: JBESB-2207 URL: https://jira.jboss.org/jira/browse/JBESB-2207 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Tomasz Juchniewicz -- 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

14 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-2100) InVM exception

by Joakim Sandström (JIRA)

InVM exception -------------- Key: JBESB-2100 URL: https://jira.jboss.org/jira/browse/JBESB-2100 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.4 Reporter: Joakim Sandström >From my forum post: My logs gets filled up with the following exception, any ideas what is wrong with my configuration? I'm using jboss-4.2.3.GA, jbossesb-4.4.GA, jboss messaging 1.4.0.SP3 and MySQL 5.0.67. 2008-10-07 05:07:20,334 DEBUG [org.jboss.internal.soa.esb.couriers.InVMCourier] InVMCourier for EPR 'invm://6f72646572636865636b437573746f6d657246455342/false?false#10000' is not activ e. Cannot pickup/deliver on this courier. java.lang.Exception at org.jboss.internal.soa.esb.couriers.InVMCourier.isCourierActive(InVMCourier.java:281) at org.jboss.internal.soa.esb.couriers.InVMCourier.pickup(InVMCourier.java:217) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216) at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280) at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) at java.lang.Thread.run(Thread.java:619) JBoss esb generates about 1GB of logs each minute due to this error, about 800K of InVM errors. -- 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

14 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2067) Revisit DataFilerScheduler and address scheduler

by Kevin Conner (JIRA)

Revisit DataFilerScheduler and address scheduler ------------------------------------------------ Key: JBESB-2067 URL: https://jira.jboss.org/jira/browse/JBESB-2067 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Kevin Conner It is currently setup to use the default quartz scheduler. -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2075) PreparedStatement Factory for debugging

by Mark Little (JIRA)

PreparedStatement Factory for debugging --------------------------------------- Key: JBESB-2075 URL: https://jira.jboss.org/jira/browse/JBESB-2075 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Testing Affects Versions: 4.4 Reporter: Mark Little Consider reworking JDBC transport code to use a PreparedStatement factory pattern that can return a debug-enabled instance for improved traceability. I've got an implementation from JBossTS and I think Kevin has one too. -- 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

14 years, 6 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2009