November 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3714) Null Pointer Exception when using Apache configuration files

by Brian L (Created) (JIRA)

Null Pointer Exception when using Apache configuration files ------------------------------------------------------------ Key: JBESB-3714 URL: https://issues.jboss.org/browse/JBESB-3714 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Affects Versions: 4.10 Environment: Windows 7 x64 Reporter: Brian L This is performed on a clean install of JBoss 5.1.0GA jdk6 , JBossESB 4.10 , and JBossWS CXF 3.4.0GA. If I use a Apache configuration file cxf.xml for an esb, an null pointer exception occurs when trying to deploy juddiv3.war {code:borderStyle=solid} 2011-11-23 09:54:55,654 INFO [org.jboss.wsf.stack.cxf.deployment.aspect.DescriptorDeploymentAspect] (main) CXF configuration found: vfsfile:/C:/jboss/server/default/deploy/cxf-bug.esb/cxf.xml 2011-11-23 09:54:56,293 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Real: name=vfszip:/C:/jboss/server/default/deploy/juddiv3.war/ state=PreReal mode=Manual requiredState=Real org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/C:/jboss/server/default/deploy/juddiv3.war/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.NullPointerException at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:96) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:110) at org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer.internalDeploy(WSDeploymentAspectDeployer.java:107) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) ... 29 more {code} This did not happen on previous versions of JBoss ESB and only started with 4.10 Thank you -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] (JBESB-3713) JCA EndpointProxy must handle toString method

by Rick Wagner (Created) (JIRA)

JCA EndpointProxy must handle toString method --------------------------------------------- Key: JBESB-3713 URL: https://issues.jboss.org/browse/JBESB-3713 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.10 CP1 Reporter: Rick Wagner Assignee: Kevin Conner Fix For: 4.10 CP2 Some JCA providers will call toString on the EndpointProxy, for example WSMQ, leading to the following exception (WorkManager(2)-7) java.lang.IllegalStateException: Multiple message delivery between before and after delivery is not allowed for message endpoint category: write service: updatejms jca adapter: wmq.jmsra.rar (WorkManager(2)-7) at org.jboss.soa.esb.listeners.jca.EndpointProxy.delivery(EndpointProxy.java:231) (WorkManager(2)-7) at org.jboss.soa.esb.listeners.jca.EndpointProxy.invoke(EndpointProxy.java:150) (WorkManager(2)-7) at $Proxy227.toString(Unknown Source) (WorkManager(2)-7) at com.ibm.msg.client.commonservices.trace.TableBuilder.append(TableBuilder.java:236) We should handle this within the proxy and, in addition, include hashcode and equals -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3712) JCA EndpointProxy must handle toString methodtr

by Kevin Conner (Created) (JIRA)

JCA EndpointProxy must handle toString methodtr ----------------------------------------------- Key: JBESB-3712 URL: https://issues.jboss.org/browse/JBESB-3712 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.10 CP1 Reporter: Kevin Conner Some JCA providers will call toString on the EndpointProxy, for example WSMQ, leading to the following exception (WorkManager(2)-7) java.lang.IllegalStateException: Multiple message delivery between before and after delivery is not allowed for message endpoint category: write service: updatejms jca adapter: wmq.jmsra.rar (WorkManager(2)-7) at org.jboss.soa.esb.listeners.jca.EndpointProxy.delivery(EndpointProxy.java:231) (WorkManager(2)-7) at org.jboss.soa.esb.listeners.jca.EndpointProxy.invoke(EndpointProxy.java:150) (WorkManager(2)-7) at $Proxy227.toString(Unknown Source) (WorkManager(2)-7) at com.ibm.msg.client.commonservices.trace.TableBuilder.append(TableBuilder.java:236) We should handle this within the proxy and, in addition, include hashcode and equals -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] (JBESB-3711) Services guide error in section 3.2.4 examples

by Fabricio González (Created) (JIRA)

Services guide error in section 3.2.4 examples ---------------------------------------------- Key: JBESB-3711 URL: https://issues.jboss.org/browse/JBESB-3711 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.10, 4.9 Environment: Doesn't matter Reporter: Fabricio González In section 3.2.4 the documentation shows an example of what just explained but the example is wrong. It shows <property name="namespaces"> <route-to prefix="ord" uri="http://www.acne.com/order" /> </property> when it should be <property name="namespaces"> <namespace prefix="ord" uri="http://www.acne.com/order" /> </property> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3710) DefaultJMSPropertiesSetter mapps Call.getMessagID to JMSCorrelationID

by Pontus Ullgren (Created) (JIRA)

DefaultJMSPropertiesSetter mapps Call.getMessagID to JMSCorrelationID --------------------------------------------------------------------- Key: JBESB-3710 URL: https://issues.jboss.org/browse/JBESB-3710 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.10 Reporter: Pontus Ullgren In DefaultJMSPropertiesSetter#setJMSMessageID( final org.jboss.soa.esb.message.Message fromESBMessage , final Message toJMSMessage ) the Call.getMessageId is mapped to toJMSMessage.setJMSCorrelationID( msgId ). >From the JavaDoc I would expect the Call.getMessageId to be mapped to toJMSMessage.setJMSMessageID(). Either way the JMSCorrelationID will be overwriten by the Call.getRelatesTo() in the setJMSCorrelationID. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] (JBESB-3709) quickstarts webservice_producer example does not call service

by Alonzo Burns (Created) (JIRA)

quickstarts webservice_producer example does not call service ------------------------------------------------------------- Key: JBESB-3709 URL: https://issues.jboss.org/browse/JBESB-3709 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.9 Environment: JBoss ESB 4.0 and JBoss AS 6.0.0 Reporter: Alonzo Burns Whenever, I run the quickstarts webservice producer example I receive the following error and am not sure why. I have seen postings of this issue as for back as 4.2.3. Has this been corrected? The ESB service is trying to expose a basic JBossWS web service that's attempted to be called via a JMS request. 15:25:15,187 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms:localhost:1099#queue/webservice_producer_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/webservice_producer_esb/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 77613280-8893-4e9e-8611-de3f21b3cb83 RelatesTo: jms:correlationID#77613280-8893-4e9e-8611-de3f21b3cb83 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3649) SmooksAction / ContentBasedRouter fails with input data containing a byte order mark (BOM)

by Tom Cunningham (JIRA)

SmooksAction / ContentBasedRouter fails with input data containing a byte order mark (BOM) ------------------------------------------------------------------------------------------ Key: JBESB-3649 URL: https://issues.jboss.org/browse/JBESB-3649 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Fennelly Fix For: 4.10 CP1 Calling a SmooksAction or a ContentBasedRouter with XML data with a preceding BOM, causes it to fail with a 'Content is not allowed in prolog' error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-3601) webservice_proxy_security needs to be updated

by Tom Cunningham (JIRA)

webservice_proxy_security needs to be updated --------------------------------------------- Key: JBESB-3601 URL: https://issues.jboss.org/browse/JBESB-3601 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Cunningham Priority: Minor Fix For: 4.10 In step 1 of the readme file the path to server.xml file is now jboss-as/server/production/deploy/jbossweb.sar/server.xml. Also step 2 mentions starting the server with version 4.x style path. --------------------------------------------------------------------- 1. BEFORE you start the server: type 'ant genkey' copy the contents of build/server.xml into copy into jbossesb-server-4.x/server/default/deploy/jboss-web.deployer/server.xml 2. start the server in jbossesb-server-4.x/bin/ with ./run.sh -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
6
0 / 0

[JBoss JIRA] (JBESB-3706) Upgrade jruby to 1.6.5

by Tom Cunningham (Created) (JIRA)

Upgrade jruby to 1.6.5 ---------------------- Key: JBESB-3706 URL: https://issues.jboss.org/browse/JBESB-3706 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Upgrade jruby to 1.6.5. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2011