[JBoss JIRA] (AS7-4319) Admin console: Modcluster ProxyList field cannot be set back to empty.
by Simeon Pinder (JIRA)
Simeon Pinder created AS7-4319:
----------------------------------
Summary: Admin console: Modcluster ProxyList field cannot be set back to empty.
Key: AS7-4319
URL: https://issues.jboss.org/browse/AS7-4319
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.1.Final
Environment: Admin console standalone or domain mode.
Reporter: Simeon Pinder
Assignee: Heiko Braun
0)Start AS7 standalone with profile that supports HA to enable ModCluster
1)Log into admin console AS7.1.1.Final
2)Navigate to Profile > Web > Modcluster and select the 'Proxies' tab.
3)If empty(at default) then set ProxyList to 'some_value:8888' and save. Now edit the information again and attempt to set the field to "". You will be unable to save.
This means that if you have a modcluster configuration that is incorrect or not configured anymore that you cannot disable it via the console. On startup you will get nasty exception unless you manually clear.
UI field should not be required to be non-empty.
--
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
[JBoss JIRA] (AS7-4374) whoami operation failing in domain mode but still returning a response
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-4374:
-------------------------------------
Summary: whoami operation failing in domain mode but still returning a response
Key: AS7-4374
URL: https://issues.jboss.org/browse/AS7-4374
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 7.1.2.Final
The whoami operation is both failing and returning a response in domain mode: -
[domain@192.168.1.158:9999 /] :whoami
{
"outcome" => "failed",
"result" => {"identity" => {
"username" => "mac",
"realm" => "ManagementRealm"
}},
"failure-description" => {"host-failure-descriptions" => [("mac" => "JBAS015249: No security context has been established.")]},
"rolled-back" => true
}
[domain@192.168.1.158:9999 /]
--
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
[JBoss JIRA] Created: (JBRULES-2590) Maven build fails in Linux with LANG=fr_FR.utf8
by Jean-Marc Vanel (JIRA)
Maven build fails in Linux with LANG=fr_FR.utf8
------------------------------------------------
Key: JBRULES-2590
URL: https://jira.jboss.org/browse/JBRULES-2590
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: % uname -a
Linux jmv-desktop 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux
% java -version
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
Reporter: Jean-Marc Vanel
Assignee: Mark Proctor
With sources from Subversion, making a Maven build on drools-trunk gives 3 errors :
Tests in error:
testDate(org.drools.base.FieldFactoryTest)
testString(org.drools.base.mvel.MVELCalendarCoercionTest)
testString(org.drools.base.mvel.MVELDateCoercionTest)
Tests run: 578, Failures: 0, Errors: 3, Skipped: 1
[ERROR] BUILD FAILURE
However this runs fine:
LANG=en mvn install
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (AS7-4377) Failed to create messaging connection factory
by Heiko Braun (JIRA)
Heiko Braun created AS7-4377:
--------------------------------
Summary: Failed to create messaging connection factory
Key: AS7-4377
URL: https://issues.jboss.org/browse/AS7-4377
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Heiko Braun
Assignee: Jeff Mesnil
Fix For: 7.1.2.Final
{noformat}
[INFO] {
[INFO] "compress-large-messages" => false,
[INFO] "failover-on-initial-connection" => false,
[INFO] "failover-on-server-shutdown" => false,
[INFO] "use-global-pools" => true,
[INFO] "address" => [
[INFO] ("subsystem" => "messaging"),
[INFO] ("hornetq-server" => "default"),
[INFO] ("connection-factory" => "TestCF")
[INFO] ],
[INFO] "operation" => "add",
[INFO] "entries" => ["java:/TestCF"]
[INFO] }
{noformat}
leads to
{noformat}
15:24:04,083 ERROR [org.jboss.msc.service.fail] (pool-5-thread-2) MSC00001: Failed to start service jboss.messaging.default.jms.connection-factory.TestCF: org.jboss.msc.service.StartException in service jboss.messaging.default.jms.connection-factory.TestCF: JBAS011639: Failed to create connection-factory
at org.jboss.as.messaging.jms.ConnectionFactoryService$1.run(ConnectionFactoryService.java:71) [jboss-as-messaging-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
Caused by: HornetQException[errorCode=104 message=Null Connector name passed to create ConnectionFactory]
at org.hornetq.jms.server.impl.JMSServerManagerImpl.internalCreateCFPOJO(JMSServerManagerImpl.java:1166) [hornetq-jms-2.2.13.Final.jar:]
at org.hornetq.jms.server.impl.JMSServerManagerImpl.internalCreateCF(JMSServerManagerImpl.java:1122) [hornetq-jms-2.2.13.Final.jar:]
at org.hornetq.jms.server.impl.JMSServerManagerImpl.access$1100(JMSServerManagerImpl.java:98) [hornetq-jms-2.2.13.Final.jar:]
at org.hornetq.jms.server.impl.JMSServerManagerImpl$3.runException(JMSServerManagerImpl.java:988) [hornetq-jms-2.2.13.Final.jar:]
at org.hornetq.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1666) [hornetq-jms-2.2.13.Final.jar:]
at org.hornetq.jms.server.impl.JMSServerManagerImpl.createConnectionFactory(JMSServerManagerImpl.java:976) [hornetq-jms-2.2.13.Final.jar:]
at org.jboss.as.messaging.jms.ConnectionFactoryService$1.run(ConnectionFactoryService.java:68) [jboss-as-messaging-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
... 3 more
15:24:04,092 INFO [org.jboss.as.controller] (HttpManagementService-threads - 1) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.messaging.default.jms.connection-factory.TestCF: org.jboss.msc.service.StartException in service jboss.messaging.default.jms.connection-factory.TestCF: JBAS011639: Failed to create connection-factory
{noformat}
--
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
[JBoss JIRA] (AS7-4387) CLONE - standalone.bat doesn't modify JAVA_OPTS correctly
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/AS7-4387?page=com.atlassian.jira.plugin.s... ]
Rostislav Svoboda reassigned AS7-4387:
--------------------------------------
Assignee: Brian Stansberry (was: Paul Gier)
JBPAPP-8618 was created for Paul to have changes in ER5 which was already rebased.
This change must get into upstream too.
> CLONE - standalone.bat doesn't modify JAVA_OPTS correctly
> ---------------------------------------------------------
>
> Key: AS7-4387
> URL: https://issues.jboss.org/browse/AS7-4387
> Project: Application Server 7
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 7.1.1.Final
> Reporter: Rostislav Svoboda
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 7.1.2.Final-redhat1
>
>
> standalone.bat doesn't modify JAVA_OPTS correctly because Only last change of JAVA_OPTS is reflected. JAVA_OPTS isn't dynamically changed withing 'if' part.
> {code}
> if not "%PRESERVE_JAVA_OPTS%" == "true" (
> rem Add -client to the JVM options, if supported (32 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I \-server > nul
> if errorlevel == 1 (
> "%JAVA%" -client -version 2>&1 | findstr /I /C:"Client VM" > nul
> if not errorlevel == 1 (
> set "JAVA_OPTS=-client %JAVA_OPTS%"
> )
> )
> rem Add compressed oops, if supported (64 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I "\-XX:\-UseCompressedOops \-client" > nul
> if errorlevel == 1 (
> "%JAVA%" -XX:+UseCompressedOops -version > nul 2>&1
> if not errorlevel == 1 (
> set "JAVA_OPTS=-XX:+UseCompressedOops %JAVA_OPTS%"
> )
> )
> rem Add tiered compilation, if supported (64 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I "\-XX:\-TieredCompilation \-client" > nul
> if errorlevel == 1 (
> "%JAVA%" -XX:+TieredCompilation -version > nul 2>&1
> if not errorlevel == 1 (
> set "JAVA_OPTS=-XX:+TieredCompilation %JAVA_OPTS%"
> )
> )
> )
> {code}
> must be changed to
> {code}
> if not "%PRESERVE_JAVA_OPTS%" == "true" (
> rem Add -client to the JVM options, if supported (32 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I \-server > nul
> if errorlevel == 1 (
> "%JAVA%" -client -version 2>&1 | findstr /I /C:"Client VM" > nul
> if not errorlevel == 1 (
> set "JAVA_OPTS=-client %JAVA_OPTS%"
> )
> )
> )
> if not "%PRESERVE_JAVA_OPTS%" == "true" (
> rem Add compressed oops, if supported (64 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I "\-XX:\-UseCompressedOops \-client" > nul
> if errorlevel == 1 (
> "%JAVA%" -XX:+UseCompressedOops -version > nul 2>&1
> if not errorlevel == 1 (
> set "JAVA_OPTS=-XX:+UseCompressedOops %JAVA_OPTS%"
> )
> )
> )
> if not "%PRESERVE_JAVA_OPTS%" == "true" (
> rem Add tiered compilation, if supported (64 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I "\-XX:\-TieredCompilation \-client" > nul
> if errorlevel == 1 (
> "%JAVA%" -XX:+TieredCompilation -version > nul 2>&1
> if not errorlevel == 1 (
> set "JAVA_OPTS=-XX:+TieredCompilation %JAVA_OPTS%"
> )
> )
> )
> {code}
--
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
[JBoss JIRA] (AS7-4387) CLONE - standalone.bat doesn't modify JAVA_OPTS correctly
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/AS7-4387?page=com.atlassian.jira.plugin.s... ]
Rostislav Svoboda moved JBPAPP-8619 to AS7-4387:
------------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-4387 (was: JBPAPP-8619)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.1.Final
(was: EAP 6.0.0 ER 4)
Component/s: Scripts
(was: Scripts and Commands)
Security: (was: Public)
Fix Version/s: 7.1.2.Final-redhat1
(was: EAP 6.0.0 ER 5)
Docs QE Status: (was: NEW)
> CLONE - standalone.bat doesn't modify JAVA_OPTS correctly
> ---------------------------------------------------------
>
> Key: AS7-4387
> URL: https://issues.jboss.org/browse/AS7-4387
> Project: Application Server 7
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 7.1.1.Final
> Reporter: Rostislav Svoboda
> Assignee: Paul Gier
> Priority: Critical
> Fix For: 7.1.2.Final-redhat1
>
>
> standalone.bat doesn't modify JAVA_OPTS correctly because Only last change of JAVA_OPTS is reflected. JAVA_OPTS isn't dynamically changed withing 'if' part.
> {code}
> if not "%PRESERVE_JAVA_OPTS%" == "true" (
> rem Add -client to the JVM options, if supported (32 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I \-server > nul
> if errorlevel == 1 (
> "%JAVA%" -client -version 2>&1 | findstr /I /C:"Client VM" > nul
> if not errorlevel == 1 (
> set "JAVA_OPTS=-client %JAVA_OPTS%"
> )
> )
> rem Add compressed oops, if supported (64 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I "\-XX:\-UseCompressedOops \-client" > nul
> if errorlevel == 1 (
> "%JAVA%" -XX:+UseCompressedOops -version > nul 2>&1
> if not errorlevel == 1 (
> set "JAVA_OPTS=-XX:+UseCompressedOops %JAVA_OPTS%"
> )
> )
> rem Add tiered compilation, if supported (64 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I "\-XX:\-TieredCompilation \-client" > nul
> if errorlevel == 1 (
> "%JAVA%" -XX:+TieredCompilation -version > nul 2>&1
> if not errorlevel == 1 (
> set "JAVA_OPTS=-XX:+TieredCompilation %JAVA_OPTS%"
> )
> )
> )
> {code}
> must be changed to
> {code}
> if not "%PRESERVE_JAVA_OPTS%" == "true" (
> rem Add -client to the JVM options, if supported (32 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I \-server > nul
> if errorlevel == 1 (
> "%JAVA%" -client -version 2>&1 | findstr /I /C:"Client VM" > nul
> if not errorlevel == 1 (
> set "JAVA_OPTS=-client %JAVA_OPTS%"
> )
> )
> )
> if not "%PRESERVE_JAVA_OPTS%" == "true" (
> rem Add compressed oops, if supported (64 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I "\-XX:\-UseCompressedOops \-client" > nul
> if errorlevel == 1 (
> "%JAVA%" -XX:+UseCompressedOops -version > nul 2>&1
> if not errorlevel == 1 (
> set "JAVA_OPTS=-XX:+UseCompressedOops %JAVA_OPTS%"
> )
> )
> )
> if not "%PRESERVE_JAVA_OPTS%" == "true" (
> rem Add tiered compilation, if supported (64 bit VM), and not overriden
> echo "%JAVA_OPTS%" | findstr /I "\-XX:\-TieredCompilation \-client" > nul
> if errorlevel == 1 (
> "%JAVA%" -XX:+TieredCompilation -version > nul 2>&1
> if not errorlevel == 1 (
> set "JAVA_OPTS=-XX:+TieredCompilation %JAVA_OPTS%"
> )
> )
> )
> {code}
--
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
[JBoss JIRA] (AS7-4348) deployment fails on jboss 7 with generic message.
by frank moss (JIRA)
frank moss created AS7-4348:
-------------------------------
Summary: deployment fails on jboss 7 with generic message.
Key: AS7-4348
URL: https://issues.jboss.org/browse/AS7-4348
Project: Application Server 7
Issue Type: Bug
Reporter: frank moss
https://community.jboss.org/message/726171#726171
4:11:44,831 INFO [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
14:11:46,814 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:11:46,819 INFO [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service
14:11:46,829 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:11:46,874 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBo...skipping...
13:26:53,012 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry servlet-api-2.5.jar in "/content/testing.war/WEB-INF/lib/google-api-client-extensions-1.6.0-beta.jar" does not point to a valid jar for a Class-Path reference.
13:26:53,013 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry httpclient-4.0.3.jar in "/content/testing.war/WEB-INF/lib/google-api-client-extensions-1.6.0-beta.jar" does not point to a valid jar for a Class-Path reference.
13:26:53,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry commons-logging-1.1.1.jar in "/content/testing.war/WEB-INF/lib/google-api-client-extensions-1.6.0-beta.jar" does not point to a valid jar for a Class-Path reference.
13:26:53,015 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry ridl.jar in "/content/testing.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference.
13:26:53,017 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry jurt.jar in "/content/testing.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference.
13:26:54,083 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."testing.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."testing.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "testing.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.createAdditionalModule(ManifestClassPathProcessor.java:193) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.handlingExistingClassPathEntry(ManifestClassPathProcessor.java:185) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.deploy(ManifestClassPathProcessor.java:162) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
13:26:54,093 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment testing.war in 0ms
13:26:54,093 INFO [org.jboss.as.server] (HttpManagementService-threads - 6) JBAS015870: Deploy of deployment "testing.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"testing.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"testing.war\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"testing.war\""}}
13:26:54,095 INFO [org.jboss.as.controller] (HttpManagementService-threads - 6) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."testing.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."testing.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "testing.war"
--
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