[JBoss JIRA] Created: (JBAS-8991) Cannot start beta1 server on RHEL6 with OpenJDK 1.6
by Len DiMaggio (JIRA)
Cannot start beta1 server on RHEL6 with OpenJDK 1.6
---------------------------------------------------
Key: JBAS-8991
URL: https://issues.jboss.org/browse/JBAS-8991
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: [ldimaggi@ldimaggi jboss-7.0.0.Beta1]$ java -version
java version "1.6.0_17"
OpenJDK Runtime Environment (IcedTea6 1.7.10) (rhel-1.39.b17.el6_0-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
[ldimaggi@ldimaggi jboss-7.0.0.Beta1]$ uname -a
Linux ldimaggi.csb 2.6.32-71.18.2.el6.x86_64 #1 SMP Wed Mar 2 14:17:40 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
jboss-7.0.0.Beta1
Reporter: Len DiMaggio
The error returned is:
sh ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/local/jboss-7.0.0.Beta1
JAVA: /usr/lib/jvm/java-1.6.0-openjdk.x86_64/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
=========================================================================
14:26:48,515 INFO [org.jboss.modules] JBoss Modules version 1.0.0.Beta16
14:26:48,762 INFO [org.jboss.msc] JBoss MSC version 1.0.0.Beta7
14:26:48,819 INFO [org.jboss.as] JBoss AS 7.0.0.Beta1 "Ides of March" starting
14:26:49,357 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.as.server-controller: org.jboss.msc.service.StartException in service jboss.as.server-controller: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
at org.jboss.as.server.ServerControllerService.start(ServerControllerService.java:146)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_17]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_17]
Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:120)
at org.jboss.as.server.ServerControllerService.start(ServerControllerService.java:144)
... 4 more
Caused by: javax.xml.stream.XMLStreamException: org.jboss.jca.common.api.validator.ValidateException: jndiName (xml attribure jndi-name) is required in org.jboss.jca.common.metadata.ds.DataSourceImpl
at org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$NewDataSourceSubsystemParser.readElement(DataSourcesExtension.java:449)
at org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$NewDataSourceSubsystemParser.readElement(DataSourcesExtension.java:170)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100)
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
at org.jboss.as.controller.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:390)
at org.jboss.as.controller.parsing.StandaloneXml.readServerElement(StandaloneXml.java:159)
at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:92)
at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:80)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59)
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112)
... 5 more
Caused by: org.jboss.jca.common.api.validator.ValidateException: jndiName (xml attribure jndi-name) is required in org.jboss.jca.common.metadata.ds.DataSourceImpl
at org.jboss.jca.common.metadata.ds.DataSourceAbstractImpl.partialCommonValidation(DataSourceAbstractImpl.java:262)
at org.jboss.jca.common.metadata.ds.DataSourceAbstractImpl.<init>(DataSourceAbstractImpl.java:142)
at org.jboss.jca.common.metadata.ds.DataSourceImpl.<init>(DataSourceImpl.java:90)
at org.jboss.jca.common.metadata.ds.DsParser.parseDataSource(DsParser.java:375)
at org.jboss.jca.common.metadata.ds.DsParser.parseDataSources(DsParser.java:157)
at org.jboss.jca.common.metadata.ds.DsParser.parse(DsParser.java:112)
at org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$NewDataSourceSubsystemParser.readElement(DataSourcesExtension.java:437)
... 15 more
14:26:49,366 ERROR [org.jboss.as] JBoss AS 7.0.0.Beta1 "Ides of March" started (with errors) in 1132ms - Started 16 of 17 services (1 services failed or missing dependencies, 0 services are passive or on-demand)
14:26:49,367 ERROR [stderr] java.util.concurrent.ExecutionException: Operation failed
14:26:49,368 ERROR [stderr] at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
14:26:49,368 ERROR [stderr] at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
14:26:49,368 ERROR [stderr] at org.jboss.as.server.Main.main(Main.java:83)
14:26:49,368 ERROR [stderr] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
14:26:49,369 ERROR [stderr] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
14:26:49,369 ERROR [stderr] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
14:26:49,369 ERROR [stderr] at java.lang.reflect.Method.invoke(Method.java:616)
14:26:49,369 ERROR [stderr] at org.jboss.modules.Module.run(Module.java:261)
14:26:49,369 ERROR [stderr] at org.jboss.modules.Main.main(Main.java:236)
14:26:49,370 ERROR [stderr] Caused by: org.jboss.msc.service.StartException in service jboss.as.server-controller: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
14:26:49,370 ERROR [stderr] at org.jboss.as.server.ServerControllerService.start(ServerControllerService.java:146)
14:26:49,370 ERROR [stderr] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344)
14:26:49,371 ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
14:26:49,371 ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
14:26:49,371 ERROR [stderr] at java.lang.Thread.run(Thread.java:636)
14:26:49,371 ERROR [stderr] Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
14:26:49,371 ERROR [stderr] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:120)
14:26:49,372 ERROR [stderr] at org.jboss.as.server.ServerControllerService.start(ServerControllerService.java:144)
14:26:49,372 ERROR [stderr] ... 4 more
14:26:49,372 ERROR [stderr] Caused by: javax.xml.stream.XMLStreamException: org.jboss.jca.common.api.validator.ValidateException: jndiName (xml attribure jndi-name) is required in org.jboss.jca.common.metadata.ds.DataSourceImpl
14:26:49,372 ERROR [stderr] at org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$NewDataSourceSubsystemParser.readElement(DataSourcesExtension.java:449)
14:26:49,373 ERROR [stderr] at org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$NewDataSourceSubsystemParser.readElement(DataSourcesExtension.java:170)
14:26:49,373 ERROR [stderr] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100)
14:26:49,373 ERROR [stderr] at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
14:26:49,373 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:390)
14:26:49,373 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readServerElement(StandaloneXml.java:159)
14:26:49,374 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:92)
14:26:49,374 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:80)
14:26:49,374 ERROR [stderr] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100)
14:26:49,374 ERROR [stderr] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59)
14:26:49,375 ERROR [stderr] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112)
14:26:49,375 ERROR [stderr] ... 5 more
14:26:49,375 ERROR [stderr] Caused by: org.jboss.jca.common.api.validator.ValidateException: jndiName (xml attribure jndi-name) is required in org.jboss.jca.common.metadata.ds.DataSourceImpl
14:26:49,375 ERROR [stderr] at org.jboss.jca.common.metadata.ds.DataSourceAbstractImpl.partialCommonValidation(DataSourceAbstractImpl.java:262)
14:26:49,376 ERROR [stderr] at org.jboss.jca.common.metadata.ds.DataSourceAbstractImpl.<init>(DataSourceAbstractImpl.java:142)
14:26:49,376 ERROR [stderr] at org.jboss.jca.common.metadata.ds.DataSourceImpl.<init>(DataSourceImpl.java:90)
14:26:49,376 ERROR [stderr] at org.jboss.jca.common.metadata.ds.DsParser.parseDataSource(DsParser.java:375)
14:26:49,376 ERROR [stderr] at org.jboss.jca.common.metadata.ds.DsParser.parseDataSources(DsParser.java:157)
14:26:49,384 ERROR [stderr] at org.jboss.jca.common.metadata.ds.DsParser.parse(DsParser.java:112)
14:26:49,384 ERROR [stderr] at org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$NewDataSourceSubsystemParser.readElement(DataSourcesExtension.java:437)
14:26:49,384 ERROR [stderr] ... 15 more
14:26:49,405 INFO [org.jboss.as] JBoss AS 7.0.0.Beta1 "Ides of March" stopped in 3ms
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
by Savas Ali Tokmen (JIRA)
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: VFS
Affects Versions: 6.0.0.M3, JBossAS-5.1.0.GA, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA
Environment: JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
JBoss 6.0.0 M3 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x, and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.), we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5 and JBoss 6; in JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws: java.io.IOException: No context factory for http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
--
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
13 years
[JBoss JIRA] Created: (JBRULES-2858) misc. decision table bugs and improvements
by Wolfgang Laun (JIRA)
misc. decision table bugs and improvements
------------------------------------------
Key: JBRULES-2858
URL: https://issues.jboss.org/browse/JBRULES-2858
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-decisiontables
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Fix For: 5.2.0.M2
RuleTable and column headers (CONDITION, ACTION,...) are ignored when written with a leading space.
Errors are reported in row & column numbers; this should be done using cell names.
Duplicate columns for rule attributes are silently ignored; there should be a diagnostic.
NumberFormatException thrown on bad integer must be caught and result in a proper diagnostic.
Description entry is notwritten into the generated DRL.
Some attributes cannot be produced: lock-on-active, etc.
NPE thrown for certain entries
Documentation is rather "off" in several places.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (LOGTOOL-13) Exception constructing methods are not populating the message string
by David Lloyd (JIRA)
Exception constructing methods are not populating the message string
--------------------------------------------------------------------
Key: LOGTOOL-13
URL: https://issues.jboss.org/browse/LOGTOOL-13
Project: Log Tool
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.Beta5
Reporter: David Lloyd
Assignee: James Perkins
Priority: Critical
Fix For: 1.0.0.Beta6
...which sometimes leads to compile errors.
This input:
{code:title=InvocationMessages.java}
// ...
@Message(id = 3, value = "Null value passed in for parameter %s")
IllegalArgumentException nullParameter(String param);
@Message(id = 4, value = "Null value specified for serialized field %s")
InvalidObjectException nullField(String param);
@Message(id = 5, value = "The given interceptor instance is of the wrong type")
IllegalArgumentException wrongInterceptorType();
// ...
{code}
Yields this output:
{code:title=InvocationMessages_$bundle.java}
// ...
@Override
public final IllegalArgumentException nullParameter(final String param) {
IllegalArgumentException result = new IllegalArgumentException();
return result;
}
protected String nullParameter$str() {
return nullParameter;
}
@Override
public final InvalidObjectException nullField(final String param) {
InvalidObjectException result = new InvalidObjectException();
return result;
}
protected String nullField$str() {
return nullField;
}
@Override
public final IllegalArgumentException wrongInterceptorType() {
IllegalArgumentException result = new IllegalArgumentException();
return result;
}
protected String wrongInterceptorType$str() {
return wrongInterceptorType;
}
// ...
{code}
In particular this is an issue because InvalidObjectException does not have a no-arg constructor.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBAS-9140) Incorrect value for boolean parameter
by Brian Stansberry (JIRA)
Incorrect value for boolean parameter
-------------------------------------
Key: JBAS-9140
URL: https://issues.jboss.org/browse/JBAS-9140
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: CLI
Reporter: Brian Stansberry
Assignee: Alexey Loubyansky
With the latest from master, this operation:
/socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=fixed-port,value=true)
results in this operation on the server (incorrect value):
{
"operation" => "write-attribute",
"name" => "fixed-port",
"value" => false,
"address" => [
("socket-binding-group" => "standard-sockets"),
("socket-binding" => "http")
]
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBAS-8204) Deployment via a deployment plan
by Brian Stansberry (JIRA)
Deployment via a deployment plan
--------------------------------
Key: JBAS-8204
URL: https://jira.jboss.org/browse/JBAS-8204
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.M2
I want us to have some sort of deployment plan notion in our deployment API so users can specify in a document how a rolling upgrade should occur, e.g. here's the new deployment(s), first quiesce this set of servers, then upgrade, roll on to this set of servers, etc.
Basically describe in a document the set of operations that are meant to be atomic.
--
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
13 years