November 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1363) Update standalone zip to JBossWS 2.0.1.SP2

by Kevin Conner (JIRA)

Update standalone zip to JBossWS 2.0.1.SP2 ------------------------------------------ Key: JBESB-1363 URL: http://jira.jboss.com/jira/browse/JBESB-1363 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Reporter: Kevin Conner Assigned To: Kevin Conner 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

18 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1377) JCRMessageStore may not recreate messages of the right type

by Mark Little (JIRA)

JCRMessageStore may not recreate messages of the right type ----------------------------------------------------------- Key: JBESB-1377 URL: http://jira.jboss.com/jira/browse/JBESB-1377 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.2.1 Reporter: Mark Little loadMessage says ... "Message message = MessageFactory.getInstance().getMessage();" and then uses message to redeliver (for example). That's fine if the default Message type was saved away, but if it wasn't then we are going to deliver a message of the wrong type. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1373) Problems with ESB/jBPM integration when JTA is used

by Jiri Pechanec (JIRA)

Problems with ESB/jBPM integration when JTA is used --------------------------------------------------- Key: JBESB-1373 URL: http://jira.jboss.com/jira/browse/JBESB-1373 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Jiri Pechanec To successfully use JTA in started via JCA listener inside jBPM process the jBPM config files must contain this values hibernate.cfg.xml <property name="hibernate.transaction.factory_class">org.hibernate.transaction.CMTTransactionFactory</property> <property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property> jbpm.cfg.xml <service name="persistence"> <factory> <bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory"> <field name="isTransactionEnabled"><false/></field> <field name="isCurrentSessionEnabled"><true/></field>  </bean> </factory> </service> When this configuration is used then the transaction started by JCA listener is propagated to jBPM and is not committed/closed by jBPM. But under this configuration the jBPM JobExecutor running inside ESB does not work 09:41:13,556 ERROR [JobExecutorThread] exception in job executor thread. waiting 20000 milliseconds org.hibernate.HibernateException: Unable to locate current JTA transaction at org.hibernate.context.JTASessionContext.currentSession(JTASessionContext.java:61) at org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:544) at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:104) at org.jbpm.persistence.db.DbPersistenceService.getJobSession(DbPersistenceService.java:359) at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:563) at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:112) at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:58) The obvious problem is that the Executor do not have any JTA transaction available. -- 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

18 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1372) JSR181 Webservices not being deployed

by Vinicius Carvalho (JIRA)

JSR181 Webservices not being deployed ------------------------------------- Key: JBESB-1372 URL: http://jira.jboss.com/jira/browse/JBESB-1372 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.2.1 Environment: JBoss 4.2.0.GA, JBoss WS 2.0.0, JBoss ESB 4.2.1 Reporter: Vinicius Carvalho Priority: Minor When packaging an ejb jar with a jsr 181 annotated SLSB Webservice inside esb module, the endpoint is not deployed. When the jar file is either on the deploy root dir or, inside a nested ear within the esb module it works ok. -- 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

18 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1371) Minor typo in print statement

by Mark Little (JIRA)

Minor typo in print statement ----------------------------- Key: JBESB-1371 URL: http://jira.jboss.com/jira/browse/JBESB-1371 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Priority: Trivial Fix For: 4.2.1 CP1 Received mis-spelling. -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1368) Unclear semantics for handling exceptions and JTA rollbacks when using JMS inflow

by Jiri Pechanec (JIRA)

Unclear semantics for handling exceptions and JTA rollbacks when using JMS inflow --------------------------------------------------------------------------------- Key: JBESB-1368 URL: http://jira.jboss.com/jira/browse/JBESB-1368 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Jiri Pechanec Priority: Critical Let's suppose we have following execution flow 1) JMS/JCA gateway starts JTA transaction and receives message 2) jBPM process is invoked 3) An exception occurs in the process and the transaction is marked as rollback only 4) ESB catches exception 5) ESB redelivers message 6) jBPM process is executed successfully 7) ESB tries to commit the transaction but exception is thrown as JTA transction is marked as rollback only 8) If redelivery < mx redelivery go to item 5) -- 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

18 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1356) parsing error using IPv6 format addresses other than ::1 (localhost) for JNDI URL in jboss-esb.xml

by Len DiMaggio (JIRA)

parsing error using IPv6 format addresses other than ::1 (localhost) for JNDI URL in jboss-esb.xml -------------------------------------------------------------------------------------------------- Key: JBESB-1356 URL: http://jira.jboss.com/jira/browse/JBESB-1356 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 CP1 Environment: revision 16707 Reporter: Len DiMaggio Priority: Minor It looks as though there is a parsing error using IPv6 format addresses other than ::1 (localhost) for the JNDI URL as expressed in jboss-esb.xml For example - this works: <providers> <jms-provider name="JBossMQ" connection-factory="ConnectionFactory" jndi-URL="jnp://::1:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces"> But this: <providers> <jms-provider name="JBossMQ" connection-factory="ConnectionFactory" jndi-URL="jnp://fe80::210:c6ff:fede:1c8f:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces"> Results in this exception: Caused by: javax.naming.CommunicationException: Could not obtain connection to any of these urls: fe80::210:c6ff:fede:1c8f:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server fe80:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server fe80:1099 [Root exception is java.net.UnknownHostException: fe80]]] org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected configuration exception from prepareMessageReceiver at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:118) at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133) at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:150) at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:69) 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: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 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) 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 sun.reflect.GeneratedMethodAccessor54.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.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 org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: org.jboss.soa.esb.ConfigurationException: Failed to obtain queue session from pool at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.prepareMessageReceiver(JmsGatewayListener.java:380) at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:106) ... 51 more Caused by: javax.naming.CommunicationException: Could not obtain connection to any of these urls: fe80::210:c6ff:fede:1c8f:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server fe80:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server fe80:1099 [Root exception is java.net.UnknownHostException: fe80]]] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1416) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:596) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.addAnotherSession(JmsConnectionPool.java:134) at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:201) at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.prepareMessageReceiver(JmsGatewayListener.java:377) ... 52 more Caused by: javax.naming.CommunicationException: Failed to connect to server fe80:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server fe80:1099 [Root exception is java.net.UnknownHostException: fe80]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1387) ... 58 more Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server fe80:1099 [Root exception is java.net.UnknownHostException: fe80] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243) ... 59 more Caused by: java.net.UnknownHostException: fe80 at java.net.InetAddress.getAllByName0(InetAddress.java:1150) at java.net.InetAddress.getAllByName(InetAddress.java:1072) at java.net.InetAddress.getAllByName(InetAddress.java:1008) at java.net.InetAddress.getByName(InetAddress.java:958) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:76) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239) -- 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

18 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1321) JMSUtil class missing in ESB-Server

by Tom Cunningham (JIRA)

JMSUtil class missing in ESB-Server ----------------------------------- Key: JBESB-1321 URL: http://jira.jboss.com/jira/browse/JBESB-1321 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Fennelly Fix For: 4.2.1 CP1 The jms_topic QS depends on a class : org/jboss/soa/esb/testutils/JMSUtil.java which is in product/rosetta/tests, but is never packaged into the ESB server. If you try running jms_topic from one of the downloadable ESB servers, and not the one from build, jms_topic Quickstart fails : runtest: [java] Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/soa/esb/testutils/JMSUtil -- 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

18 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1361) IllegalArgumentException in aggregator QS

by Jaroslaw Kijanowski (JIRA)

IllegalArgumentException in aggregator QS ----------------------------------------- Key: JBESB-1361 URL: http://jira.jboss.com/jira/browse/JBESB-1361 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP1 Reporter: Jaroslaw Kijanowski Just try to run the aggregator QS, enable DEBUG level for the aggreagtion service, send a message and watch the aggregator's console: [java] java.lang.IllegalArgumentException: value must be Serializable [java] at org.jboss.internal.soa.esb.message.format.xml.AttachmentImpl.addItem(AttachmentImpl.java:101) [java] at org.jboss.soa.esb.actions.Aggregator.createAggregateMessage(Aggregator.java:236) [java] at org.jboss.soa.esb.actions.Aggregator.process(Aggregator.java:185) [java] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) [java] at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) [java] at java.lang.Thread.run(Thread.java:595) . . . [java] 12:07:17,808 DEBUG [Thread-1][Aggregator] message is alive. [java] 12:07:17,808 DEBUG [Thread-1][Aggregator] Current time=12:07:17 PM message expiration=12:07:18 PM [java] 12:07:17,808 DEBUG [Thread-1][Aggregator] message is alive. [java] 12:07:18,309 DEBUG [Thread-1][Aggregator] Current time=12:07:18 PM message expiration=12:07:18 PM [java] 12:07:18,309 DEBUG [Thread-1][Aggregator] message expired. [java] Exception in thread "Thread-1" java.lang.NullPointerException [java] at org.jboss.soa.esb.actions.Aggregator$TimeoutChecker.run(Aggregator.java:297) -- 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

18 years, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-1357) Deprecated hint in javadoc for org.jboss.soa.esb.message.Body.getByteArray doesn't work

by jarkko Lietolahti (JIRA)

Deprecated hint in javadoc for org.jboss.soa.esb.message.Body.getByteArray doesn't work --------------------------------------------------------------------------------------- Key: JBESB-1357 URL: http://jira.jboss.com/jira/browse/JBESB-1357 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: jarkko Lietolahti Priority: Critical Javadoc for Body.getByteArray says:" Deprecated. As of 4.2 this has been replaced by get(BytesBody.BYTES_LOCATION) " But this doesn't work. BytesBody.BYTES_LOCATION is also deprecated without a proper hint where to go next! Following the javadoc and calling System.out.println("Body: " + message.getBody().get(BytesBody.BYTES_LOCATION)); in HelloWorld ( from Eclipse ESB create project ) shows "[STDOUT] Body: 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

18 years, 5 months

3
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 November 2007