[JBoss JIRA] Created: (JBESB-2272) ESB testable against external binaries (product test suite)
by Aleksandar Kostadinov (JIRA)
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/jira/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP3, 4.2.1 CP2, 4.2.1 CP1, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
When running the ESB test …
[View More]suite against external binaries, there is currently a mismatch between libraries downloaded by the test suite and libraries found in the external distribution. This makes running the suite against the external JBoss AS distribution meaningless because doesn't prove ESB will work with the libraries found in the JBoss AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath point at the libraries in the JBoss AS rather than these generated during build and downloaded by the build script. Running the test suite against external binaries should be the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
13 years
[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 …
[View More]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
[View Less]
13 years
[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 …
[View More]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
[View Less]
13 years, 2 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/…
[View More]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
[View Less]
13 years, 4 months