January 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1301) jBPM integration needs revisiting

by Mark Little (JIRA)

jBPM integration needs revisiting --------------------------------- Key: JBESB-1301 URL: http://jira.jboss.com/jira/browse/JBESB-1301 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Kurt Stam Priority: Blocker Fix For: 4.2.1 CP1 -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1484) context.lookup() can return null

by Martin Vecera (JIRA)

context.lookup() can return null -------------------------------- Key: JBESB-1484 URL: http://jira.jboss.com/jira/browse/JBESB-1484 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Environment: SOA-P 4.2.0.beta1, Oracle DB Reporter: Martin Vecera I get the following bug in NotifyQueues: 2008-01-15 15:57:44,285 ERROR [STDERR] java.lang.reflect.InvocationTargetException 2008-01-15 15:57:44,286 ERROR [STDERR] at sun.reflect.GeneratedConstructorAccessor164.newInstance(Unknown Source) 2008-01-15 15:57:44,286 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) 2008-01-15 15:57:44,286 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) 2008-01-15 15:57:44,286 ERROR [STDERR] at org.jboss.soa.esb.notification.NotificationTarget.fromParams(NotificationTarget.java:144) 2008-01-15 15:57:44,286 ERROR [STDERR] at org.jboss.soa.esb.notification.NotificationList.notifyAll(NotificationList.java:162) 2008-01-15 15:57:44,286 ERROR [STDERR] at org.jboss.soa.esb.actions.Notifier.notifyOK(Notifier.java:93) 2008-01-15 15:57:44,287 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor180.invoke(Unknown Source) 2008-01-15 15:57:44,287 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2008-01-15 15:57:44,287 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 2008-01-15 15:57:44,287 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processSuccess(ActionProcessorMethodInfo.java:165) 2008-01-15 15:57:44,287 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.processSuccess(OverriddenActionLifecycleProcessor.java:108) 2008-01-15 15:57:44,287 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.notifySuccess(ActionProcessingPipeline.java:610) 2008-01-15 15:57:44,287 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:384) 2008-01-15 15:57:44,287 ERROR [STDERR] at org.jboss.soa.esb.listeners.jca.JcaMessageAwareListener.process(JcaMessageAwareListener.java:156) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.soa.esb.listeners.jca.JcaJMSInflowMessageProcessorAdapter.onMessage(JcaJMSInflowMessageProcessorAdapter.java:44) 2008-01-15 15:57:44,288 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source) 2008-01-15 15:57:44,288 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2008-01-15 15:57:44,288 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.soa.esb.listeners.jca.BaseJcaInflow$1.invoke(BaseJcaInflow.java:205) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.soa.esb.listeners.jca.EndpointProxy.delivery(EndpointProxy.java:242) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.soa.esb.listeners.jca.EndpointProxy.invoke(EndpointProxy.java:145) 2008-01-15 15:57:44,288 ERROR [STDERR] at $Proxy78.onMessage(Unknown Source) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:159) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:802) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect14.invoke(SessionAspect14.java) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.jms.client.JBossSession.run(JBossSession.java:199) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) 2008-01-15 15:57:44,288 ERROR [STDERR] at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) 2008-01-15 15:57:44,288 ERROR [STDERR] at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748) 2008-01-15 15:57:44,288 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) 2008-01-15 15:57:44,289 ERROR [STDERR] Caused by: java.lang.NullPointerException 2008-01-15 15:57:44,289 ERROR [STDERR] at org.jboss.soa.esb.notification.NotifyQueues.createProducer(NotifyQueues.java:112) 2008-01-15 15:57:44,289 ERROR [STDERR] at org.jboss.soa.esb.notification.NotifyJMS.setUpProducers(NotifyJMS.java:407) 2008-01-15 15:57:44,289 ERROR [STDERR] at org.jboss.soa.esb.notification.NotifyQueues.setQueues(NotifyQueues.java:79) 2008-01-15 15:57:44,289 ERROR [STDERR] at org.jboss.soa.esb.notification.NotifyQueues.<init>(NotifyQueues.java:74) 2008-01-15 15:57:44,289 ERROR [STDERR] ... 37 more 2008-01-15 15:57:44,291 ERROR [org.jboss.soa.esb.notification.NotificationList] Can't instantiate target <target class="NotifyQueues"> <queue jndiName="queue/A"/> </target> org.jboss.soa.esb.ConfigurationException: NotifyQueues does not extend NotificationTarget at org.jboss.soa.esb.notification.NotificationTarget.fromParams(NotificationTarget.java:151) at org.jboss.soa.esb.notification.NotificationList.notifyAll(NotificationList.java:162) at org.jboss.soa.esb.actions.Notifier.notifyOK(Notifier.java:93) at sun.reflect.GeneratedMethodAccessor180.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processSuccess(ActionProcessorMethodInfo.java:165) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.processSuccess(OverriddenActionLifecycleProcessor.java:108) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.notifySuccess(ActionProcessingPipeline.java:610) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:384) at org.jboss.soa.esb.listeners.jca.JcaMessageAwareListener.process(JcaMessageAwareListener.java:156) at org.jboss.soa.esb.listeners.jca.JcaJMSInflowMessageProcessorAdapter.onMessage(JcaJMSInflowMessageProcessorAdapter.java:44) at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.jca.BaseJcaInflow$1.invoke(BaseJcaInflow.java:205) at org.jboss.soa.esb.listeners.jca.EndpointProxy.delivery(EndpointProxy.java:242) at org.jboss.soa.esb.listeners.jca.EndpointProxy.invoke(EndpointProxy.java:145) at $Proxy78.onMessage(Unknown Source) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178) at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:159) at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:802) at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect14.invoke(SessionAspect14.java) at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java) at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java) at org.jboss.jms.client.JBossSession.run(JBossSession.java:199) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237) 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:748) at java.lang.Thread.run(Thread.java:595) This happened ~20 times of 10,000 messages processed. As a result, the message has been lost. The offending code in NotifyQueues.java (marked with >>> <<<): Context context = NamingContext.getServerContext(environment); Queue queue=null; try { >>> queue = (Queue) context.lookup(destinationName); <<< } This context.lookup() returns null sometimes. I was able to reproduce it only when the ESB listener's queue is served with >1 thread and the service was deployed on two nodes in the cluster (clustered JMS, ServiceInvoker used RoundRobin policy). BEWARE! The context.lookup() is used on many different places without checking the return value != null. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1489) Error in the documentation of load_generator quickstart

by Jehudi Castro (JIRA)

Error in the documentation of load_generator quickstart ------------------------------------------------------- Key: JBESB-1489 URL: http://jira.jboss.com/jira/browse/JBESB-1489 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Environment: JBoss SOA Platform ESB Embedded ESB Server - Version 4.2.0.beta1 Reporter: Jehudi Castro The documentation should be updated. This is the way to get the quickstark running: ant deploy-jms-dests ant deploy ant runtest ant undeploy ant undeploy-jms-dests -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1493) Missing figure in Registry Guide

by Mark Little (JIRA)

Missing figure in Registry Guide -------------------------------- Key: JBESB-1493 URL: http://jira.jboss.com/jira/browse/JBESB-1493 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Kurt Stam Priority: Minor Fix For: 4.2.1 CP1 Figure 7 is broken (missing) in the Registry guide. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1488) BRMS support for configuration files

by Mark Little (JIRA)

BRMS support for configuration files ------------------------------------ Key: JBESB-1488 URL: http://jira.jboss.com/jira/browse/JBESB-1488 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration, Registry and Repository Affects Versions: 4.2.1 Reporter: Mark Little Fix For: 5.0 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1482) Process flow is executed even when the process is cancelled

by Jiri Pechanec (JIRA)

Process flow is executed even when the process is cancelled ----------------------------------------------------------- Key: JBESB-1482 URL: http://jira.jboss.com/jira/browse/JBESB-1482 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 CP1 Environment: FC7/PostgreSQL Reporter: Jiri Pechanec Assigned To: Kevin Conner Priority: Critical Fix For: 4.2.1 CP1 The process orchestartion is executed even after the process was cancelled by Cancel command. Test scenario was 1) Start the jBPM process 2) jBPM process invokes long running service (10 second sleep) 3) CancelCommand was executed 4) The long running service has finished and went to Callback Service Here I excepted that the message would be ether ignored or exception will be thrown. Instead of it the rest of flow was executed - new messages generated etc. The Cancel command was really executed, snippet from log 2008-01-15 08:51:15,177 INFO [org.jbpm.command.AbstractCancelCommand] cancel process instance 2000 2008-01-15 08:51:15,186 INFO [org.jbpm.command.AbstractCancelCommand] cancel 0 tasks 2008-01-15 08:51:15,186 INFO [org.jbpm.command.AbstractCancelCommand] token 2001 canceled 2008-01-15 08:51:15,186 INFO [org.jbpm.command.AbstractCancelCommand] cancel 0 tokens 2008-01-15 08:51:15,188 INFO [org.jbpm.command.AbstractCancelCommand] finished process cancellation This can be issue even when the cancellation from GUI is executed. -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1476) 'Column lenght too short' SQL errors when deploying management console with mysql on Linux

by Bernard Tison (JIRA)

'Column lenght too short' SQL errors when deploying management console with mysql on Linux ------------------------------------------------------------------------------------------ Key: JBESB-1476 URL: http://jira.jboss.com/jira/browse/JBESB-1476 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Environment: OS: Fedora 8 RDBMS: MySQL 5.0.45 Reporter: Bernard Tison in the create_database.sql script in /console/management-esb/src/main/resources/mysql the JMXDATA.textvalue column is defined as varchar(255). This length is too short for certain messages, leading to SQL errors when trying to persist those messages. Setting the datatype of the JMXDATA.textvalue to text instead of varchar(255) seems top solve the problem. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1481) helloworld_tx_sql_action deployment error

by Daniel Bevenius (JIRA)

helloworld_tx_sql_action deployment error ----------------------------------------- Key: JBESB-1481 URL: http://jira.jboss.com/jira/browse/JBESB-1481 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Daniel Bevenius Fix For: 4.2.1 CP1 Upon deploying the quickstart I get: 16:51:48,566 ERROR [XmlValidatorImpl] 1-ERROR-null-6:cvc-complex-type.4: Attribute 'message-column' must appear on element 'sql-message-filter'. 16:51:48,682 WARN [ServiceController] Problem starting service jboss.esb:deployment=Quickstart_helloworld_TX_SQL_action.esb java.lang.RuntimeException: java.lang.IllegalStateException: ESB file had validation errors. at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:132) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:82) 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 sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2 Modifying jboss-esb.xml and adding: message-column="DATA_COL" insert-timestamp-column="TIMESTAMP_COL" to sql-bus named helloSQLChannel and deployment will succeed. I'll attach my jboss-esb.xml -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1478) Fixup webservice_mtom, webservice_wssecurity and webservice_wsaddressing

by Kevin Conner (JIRA)

Fixup webservice_mtom, webservice_wssecurity and webservice_wsaddressing ------------------------------------------------------------------------ Key: JBESB-1478 URL: http://jira.jboss.com/jira/browse/JBESB-1478 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP1 The webservice_mtom and webservice_wsaddressing quickstarts do not compile at present, DOMUtil and GenericSOAPHandler have changed packages. Additional jars are also required to run the clients, activation, mail, jboss-ejb3x and jboss-xml-binding. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1454) quickstart webservice_wsaddressing asking for wrong jboss remoting patch

by Trevor Kirby (JIRA)

quickstart webservice_wsaddressing asking for wrong jboss remoting patch ------------------------------------------------------------------------- Key: JBESB-1454 URL: http://jira.jboss.com/jira/browse/JBESB-1454 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Trevor Kirby The quickstart webservice_wsaddressing has a message that: This Quickstart requires the JBossRemoting 2.2.2SP2 patch to be applied. This simply involves downloading <a href="http://repository.jboss.org/jboss/remoting/2.2.2.SP2/lib/jboss-remoting.jar">jboss-remoting.jar</a> If you run ant deploy it barfs complaining: build file parsing, attempting to resolve. Future versions of Ant may support referencing ids defined in non-executed targets. [echo] JBR Version String: 'JBossRemoting Version 2.2.2.SP4 (Bluto)'. BUILD FAILED /shared/software/soa-p-standalone/jboss-soa-p-standalone.4.2.0/samples/quickstarts/conf/base-build.xml:494: Invalid version of JBossRemoting installed on target server. Please install version 2.2.2.SP2: http://repository.jboss.org/jboss/remoting/2.2.2.SP2/lib/jboss-remoting.jar So it looks like the version is 2.2.2.SP4, but the build script is looking for 2.2.2.SP2. -- 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, 4 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2008