[JBoss JIRA] Created: (JBESB-3627) http_2way_ssl quickstart doesn't pass the HTTP header through JBR in the action chain
by Tom Cunningham (JIRA)
http_2way_ssl quickstart doesn't pass the HTTP header through JBR in the action chain
-------------------------------------------------------------------------------------
Key: JBESB-3627
URL: https://issues.jboss.org/browse/JBESB-3627
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.10 CP1
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.10 CP1
There is an issue in "http_2way_ssl" quickstart (that is a part of SOA-P distribution).
In the case of SOA-P 4.3.0_CP04 the HTTP header ("blah: blahval") that is configured/provided by HTTPRouter in the ESB action chain passes all the way to client response and its presence is confirmed in the server's log where the quickstart prints the output.
But in the case of SOA-P v5 the header is not passed to the end of ESB action chain. The quickstart practically wasn't changed between the SOA-P versions.
SOA-P 4.3.0_CP04.GA - quickstart's output in server's log:
...
15:35:51,886 INFO [STDOUT] =========== Server Request: ====================================
15:35:51,886 INFO [STDOUT] Message Payload:
15:35:51,886 INFO [STDOUT] [Request Payload!]
15:35:51,886 INFO [STDOUT] Headers:
15:35:51,886 INFO [STDOUT] host: localhost
15:35:51,886 INFO [STDOUT] Method: POST
15:35:51,886 INFO [STDOUT] Path: /x/y
15:35:51,886 INFO [STDOUT] user-agent: Jakarta Commons-HttpClient/3.0.1
15:35:51,887 INFO [STDOUT] content-type: text/xml;charset=UTF-8
15:35:51,887 INFO [STDOUT] ================================================================
15:35:51,940 INFO [STDOUT] =========== Client Response: ===================================
15:35:51,940 INFO [STDOUT] Message Payload:
15:35:51,940 INFO [STDOUT] [Http Response Payload!!]
15:35:51,940 INFO [STDOUT] Http Response:
15:35:51,940 INFO [STDOUT] Code: 200
15:35:51,940 INFO [STDOUT] Length: 23
15:35:51,940 INFO [STDOUT] Encoding: ISO-8859-1
15:35:51,940 INFO [STDOUT] Headers:
15:35:51,940 INFO [STDOUT] blah: blahval
15:35:51,940 INFO [STDOUT] Content-Type: text/xml;charset=UTF-8
15:35:51,940 INFO [STDOUT] User-Agent: Jakarta Commons-HttpClient/3.0.1
15:35:51,940 INFO [STDOUT] Host: localhost
15:35:51,940 INFO [STDOUT] Content-Length: 16
15:35:51,940 INFO [STDOUT] ================================================================
...
SOA-P 5.1.0.ER2 - quickstart's output in server's log:
...
15:44:22,936 INFO [STDOUT] =========== Server Request: ====================================
15:44:22,936 INFO [STDOUT] Message Payload:
15:44:22,937 INFO [STDOUT] [Request Payload!]
15:44:22,938 INFO [STDOUT] Headers:
15:44:22,972 INFO [STDOUT] host: localhost:9433
15:44:22,972 INFO [STDOUT] Method: POST
15:44:22,972 INFO [STDOUT] Path: /x/y
15:44:22,973 INFO [STDOUT] user-agent: Jakarta Commons-HttpClient/3.0.1
15:44:22,973 INFO [STDOUT] content-type: text/xml;charset=UTF-8
15:44:22,973 INFO [STDOUT] ================================================================
15:44:23,040 INFO [STDOUT] =========== Client Response: ===================================
15:44:23,040 INFO [STDOUT] Message Payload:
15:44:23,040 INFO [STDOUT] [Http Response Payload!!]
15:44:23,085 INFO [STDOUT] Http Response:
15:44:23,085 INFO [STDOUT] Code: 200
15:44:23,085 INFO [STDOUT] Length: 23
15:44:23,085 INFO [STDOUT] Encoding: ISO-8859-1
15:44:23,086 INFO [STDOUT] Headers:
15:44:23,086 INFO [STDOUT] Server: Apache-Coyote/1.1
15:44:23,086 INFO [STDOUT] ResponseCode: 200
15:44:23,086 INFO [STDOUT] ResponseCodeMessage: OK
15:44:23,086 INFO [STDOUT] remotingContentType: remotingContentTypeString
15:44:23,086 INFO [STDOUT] Content-Type: text/html
15:44:23,086 INFO [STDOUT] Content-Length: 23
15:44:23,086 INFO [STDOUT] Date: Wed, 13 Oct 2010 13:44:22 GMT
15:44:23,087 INFO [STDOUT] ================================================================
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBESB-3638) jUDDI error on boot after installing CXF
by Kevin Conner (JIRA)
jUDDI error on boot after installing CXF
----------------------------------------
Key: JBESB-3638
URL: https://issues.jboss.org/browse/JBESB-3638
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.10
Reporter: Kevin Conner
Assignee: Tom Cunningham
Fix For: 4.10 CP1
There are two more websevices that need to be removed from the web.xml
<servlet>
<servlet-name>ValueSetCachingService</servlet-name>
<servlet-class>org.apache.juddi.api.impl.UDDIValueSetCachingImpl</servlet-class>
</servlet>
<servlet>
<servlet-name>ValueSetValidationService</servlet-name>
<servlet-class>org.apache.juddi.api.impl.ValueSetValidationImpl.java</servlet-class>
</servlet>
Neither of these have the WebService annotation, and the second is wrong in any case.
The only classes with the WebService annotation are
./org/apache/juddi/api/impl/JUDDIApiImpl.class
./org/apache/juddi/api/impl/UDDICustodyTransferImpl.class
./org/apache/juddi/api/impl/UDDIInquiryImpl.class
./org/apache/juddi/api/impl/UDDIPublicationImpl.class
./org/apache/juddi/api/impl/UDDISecurityImpl.class
./org/apache/juddi/api/impl/UDDISubscriptionImpl.class
./org/apache/juddi/api/impl/UDDISubscriptionListenerImpl.class
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBESB-3637) Remove signing from commons-ssl in product/lib/ext
by Tom Cunningham (JIRA)
Remove signing from commons-ssl in product/lib/ext
--------------------------------------------------
Key: JBESB-3637
URL: https://issues.jboss.org/browse/JBESB-3637
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build and Release
Affects Versions: 4.10 CP1
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.10 CP1
(10:01:01 AM) dpalmer: tcunning1: I ran into a signing issue in MEAD
(10:01:34 AM) dpalmer: tcunning1: product/lib/ext/commons-ssl-0.3.4.jar is signed
(10:02:07 AM) dpalmer: tcunning1: mead signs it again and this prevents esb deployment
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBESB-3635) Distribution contains JAR files with inconsistent versions
by Tom Cunningham (JIRA)
Distribution contains JAR files with inconsistent versions
----------------------------------------------------------
Key: JBESB-3635
URL: https://issues.jboss.org/browse/JBESB-3635
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Build and Release
Affects Versions: 4.10
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.10 CP1
The build contain few JAR files that are inconsistent with version. It would be good to use the same version where possible
wstx.jar - 3.2.8 in esb.deployer, 3.2.9 in lib dir
jaxws-tools.jar - 2.1.7 in client, 2.1.1 in soap.esb
jaxws-rt.jar - same as above
streambuffer.jar - same as above
commons-httpclient.jar - 3.1 in client, 3.0.1 in lib
commons-lang.jar - 2.4 comes with CXF, 2.3 with ESB
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Moved: (JBESB-3636) ESB - SOAPProxy throws SAXParseException when soapAction is missing in WSDL and message has attachment
by Rick Wagner (JIRA)
[ https://issues.jboss.org/browse/JBESB-3636?page=com.atlassian.jira.plugin... ]
Rick Wagner moved SOA-3173 to JBESB-3636:
-----------------------------------------
Project: JBoss ESB (was: JBoss Enterprise SOA Platform)
Key: JBESB-3636 (was: SOA-3173)
Affects Version/s: 4.10
(was: 5.1.0 GA)
Component/s: Deployment
(was: JBossESB)
> ESB - SOAPProxy throws SAXParseException when soapAction is missing in WSDL and message has attachment
> ------------------------------------------------------------------------------------------------------
>
> Key: JBESB-3636
> URL: https://issues.jboss.org/browse/JBESB-3636
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Deployment
> Affects Versions: 4.10
> Environment: SOA-P 5.1 running on Mac 10.6 JDK 1.6
> Reporter: Rick Wagner
> Assignee: Tom Cunningham
>
> SOAPProxy throws SAXParseException when soapAction is missing in WSDL and message has attachment. If the soapAction ="" in the WSDL, then the message is not parsed. If there is no soapAction in the WSDL, then SOAPProxy attempts to parse the document to find the operation in the message, and throws a SAXParseException. See Steps to Reproduce below for more details.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBESB-3633) jBPM fails to start when using MySQL cluster as backing database
by Boris Belovic (JIRA)
jBPM fails to start when using MySQL cluster as backing database
----------------------------------------------------------------
Key: JBESB-3633
URL: https://issues.jboss.org/browse/JBESB-3633
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.9
Environment: SOA-P 5.1.GA, jdk1.6u22, MySQL Cluster 7.1.3
Reporter: Boris Belovic
JBQA-4748 requests certification of SOA-P with MySQL cluster database. I configured SOA-P using schema tool to run against internal MySQL cluster instance. Everything went OK, but when the server tried to initialize (or execute) JBPM related SQL files I got following exception:
INFO [DatabaseInitializer] Initializing java:/JbpmDS from listed sql files
14:49:58,186 ERROR [AbstractKernelController] Error installing to Start: name=jboss.esb:service=JBPMDatabaseInitializer state=Create mode=Manual requiredState=Installed
java.sql.SQLException: Unknown error 708
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1075)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3566)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3498)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1959)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2113)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2562)
at com.mysql.jdbc.LoadBalancedMySQLConnection.execSQL(LoadBalancedMySQLConnection.java:153)
at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1664)
at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1583)
at sun.reflect.GeneratedMethodAccessor284.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.mysql.jdbc.LoadBalancingConnectionProxy$ConnectionErrorFiringInvocationHandler.invoke(LoadBalancingConnectionProxy.java:103)
at $Proxy262.executeUpdate(Unknown Source)
at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:249)
at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.executeSql(DatabaseInitializer.java:145)
at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.initDatabase(DatabaseInitializer.java:122)
at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.startService(DatabaseInitializer.java:159)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
at sun.reflect.GeneratedMethodAccessor110.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:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
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:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:189)
at $Proxy38.start(Unknown Source)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:297)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.start(ServiceController.java:460)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
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:403)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
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)
It seems to me like ESB-JBPM integration issue, so I put it under ESB JIRA label.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months