[JBoss JIRA] Created: (JBESB-3629) Provide alternative registry implementation
by Tom Cunningham (JIRA)
Provide alternative registry implementation
-------------------------------------------
Key: JBESB-3629
URL: https://issues.jboss.org/browse/JBESB-3629
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.10 CP1
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.10 CP1
The issue here is: in a cluster environment, after a malfunction on JBoss (e.g. JVM crash, erroneous deployment etc) the registry remains with invalid endpoints and the ESB has an erroneous behavior by using those endpoints. Even your removeDeadEPR property is unusable, because as stated in the documentation the "the end-point reference for a service that is [...] slow to respond may, inadvertently, be removed from the registry by mistake".
Since we have a cluster and to manually clean the DB is not just to drop the tables and restart the server, this is a major issue for us, because it can lead to erroneous service calls if a server node crashes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] Created: (JBESB-3669) Don't copy AS 5 admin-console.war for AS 6 deployments
by Tom Cunningham (JIRA)
Don't copy AS 5 admin-console.war for AS 6 deployments
------------------------------------------------------
Key: JBESB-3669
URL: https://issues.jboss.org/browse/JBESB-3669
Project: JBoss ESB
Issue Type: Bug
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
We're copying in the AS 5 admin-console.war into AS 6 in AS 6 deployment scenarios. We need to copy the ESB plugin into common/deploy/admin-console.war/plugins instead. This is causing a StackOverflowError :
Caused by: java.lang.StackOverflowError
at java.util.logging.Logger.getResourceBundle(Logger.java:409) [:1.6.0_20]
at org.jboss.logmanager.Logger.logRaw(Logger.java:626) [jboss-logmanager.jar:1.2.0.CR9]
at org.jboss.logmanager.Logger.log(Logger.java:600) [jboss-logmanager.jar:1.2.0.CR9]
at org.jboss.logmanager.Logger.log(Logger.java:612) [jboss-logmanager.jar:1.2.0.CR9]
at org.jboss.logmanager.log4j.BridgeLogger.error(BridgeLogger.java:72) [:]
at org.jboss.seam.interop.jul.Log4JConversionFilter.logWithThro
...
at org.jboss.seam.interop.jul.Log4JConversionFilter.isLoggable(Log4JConversionFilter.java:68) [:2.1.0.SP1]
at org.jboss.logmanager.Logger.logRaw(Logger.java:640) [jboss-logmanager.jar:1.2.0.CR9]
at org.jboss.logmanager.Logger.log(Logger.java:600) [jboss-logmanager.jar:1.2.0.CR9]
at org.jboss.logmanager.Logger.log(Logger.java:612) [jboss-logmanager.jar:1.2.0.CR9]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[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
[JBoss JIRA] Created: (JBESB-3555) Allow for pluggable password encryption/decryption mechanism in esb
by Matt Davis (JIRA)
Allow for pluggable password encryption/decryption mechanism in esb
-------------------------------------------------------------------
Key: JBESB-3555
URL: https://issues.jboss.org/browse/JBESB-3555
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.8, 4.7 CP2
Reporter: Matt Davis
The customer would like the ability to plugin their own encryption implementation for FilePassword. For instance, in the jbossesb-properties, they would like to specify <property name="org.jboss.soa.esb.services.security.publicKeystorePassword" value="testKeystorePassword"/> using their own plugin implementation. Currently the implementation is hard coded and not pluggable.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (JBESB-3647) Please document Smooks transformation with POJO input
by Tom Cunningham (JIRA)
Please document Smooks transformation with POJO input
-----------------------------------------------------
Key: JBESB-3647
URL: https://issues.jboss.org/browse/JBESB-3647
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Transformation Service
Affects Versions: 4.10 CP1
Reporter: Tom Cunningham
Assignee: Tom Fennelly
Fix For: 4.10 CP1
The user had to rely on source code-reading to use Smooks with POJO input. This is a valid usage of Smooks and is alluded to several times in the documentation, but it is never spelled out how to accomplish it. (In particular, the beanId to use with FreeMarker is not spelled out.) Please add this information to Section 12.1.9.4 of the Programmer's Guide.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (JBESB-3648) Router in Smooks Creates Inverse Persistence
by Tom Cunningham (JIRA)
Router in Smooks Creates Inverse Persistence
--------------------------------------------
Key: JBESB-3648
URL: https://issues.jboss.org/browse/JBESB-3648
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
Smooks' JMS Router configures message persistence incorrectly. The documentation suggests the following configuration will result in persistent messages to the ESB:
<jms:router routeOnElement="student" beanId="studentFragment" destination="queue/StudentRecordQueue">
<jms:message deliveryMode="persistent"/>
</jms:router>
Instead, this leads to non-persistent messages. This is due to a bug in org.milyn.routing.jms.JMSRouter:
final int deliveryModeInt = "non-persistent".equals( jmsProperties.getDeliveryMode() ) ? DeliveryMode.PERSISTENT : DeliveryMode.NON_PERSISTENT;
This should instead be the inverse:
final int deliveryModeInt = "non-persistent".equals( jmsProperties.getDeliveryMode() ) ? DeliveryMode.NON_PERSISTENT : DeliveryMode.PERSISTENT;
This is a particularly major bug because the work around will cause incorrect functionality in future versions of the ESB, which will hopefully fix the issue with a patched version of Smooks' JMS Cartridge.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (JBESB-3667) Upgrade Apache HttpClient to 4.x
by Douglas Palmer (JIRA)
Upgrade Apache HttpClient to 4.x
--------------------------------
Key: JBESB-3667
URL: https://issues.jboss.org/browse/JBESB-3667
Project: JBoss ESB
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Affects Versions: 4.10
Reporter: Douglas Palmer
Assignee: Tom Cunningham
Fix For: 4.10 CP1
Can you investigate whether or not you can upgrade from commons-httpclient:commons-httpclient:3.1 to org.apache.httpcomponents:httpclient:4.0? Don't commit this yet though as we need to investigate whether RiftSaw can upgrade too.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (JBESB-3665) Quickstart and base-build.xml reference obsolete JMS provider config files
by Len DiMaggio (JIRA)
Quickstart and base-build.xml reference obsolete JMS provider config files
--------------------------------------------------------------------------
Key: JBESB-3665
URL: https://issues.jboss.org/browse/JBESB-3665
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.10
Reporter: Len DiMaggio
Priority: Minor
These files:
jbossesb-listener.xml
jbossesb-gateway.xml
Are no longer be included in ESB releases.
But - there are (2) references to these files:
$ grep -r "jbossesb-listener.xml" *
samples/quickstarts/helloworld_ftp_action/build.xml: <include name="jbossesb-listener.xml"/>
samples/quickstarts/conf/base-build.xml: <include name="jbossesb-listener.xml"/>
$ grep -r "jbossesb-gateway.xml" *
samples/quickstarts/helloworld_ftp_action/build.xml: <include name="jbossesb-gateway.xml"/>
samples/quickstarts/conf/base-build.xml: <include name="jbossesb-gateway.xml"/>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months