[JBoss JIRA] (LOGTOOL-109) Create @NotNull or @RequiresNonNull annotation to allow null checks with custom exception
by James Perkins (JIRA)
James Perkins created LOGTOOL-109:
-------------------------------------
Summary: Create @NotNull or @RequiresNonNull annotation to allow null checks with custom exception
Key: LOGTOOL-109
URL: https://issues.jboss.org/browse/LOGTOOL-109
Project: Log Tool
Issue Type: Feature Request
Reporter: James Perkins
Use an {{@NotNull}} or {{@RequiresNonNull}} annotation on a method to generate a {{null}} check and throw, by default, an {{IllegalArgumentException}} if null. Also clean the stack trace.
{code:java|title=Example Interface}
@Message(id = 123, value = "Name cannot be null")
@NotNull(IllegalArgumentException.class)
void requireNotNull(String name);
{code}
{code:java|title=Example Generated Code}
@Override
public void requireNotNull(final String name) {
if (name == null) {
final IllegalArgumentException result = new IllegalArgumentException(String.format(invalidUser$str(), name));
final StackTraceElement[] st = result.getStackTrace();
result.setStackTrace(Arrays.copyOfRange(st, 1, st.length));
}
}
{code}
The {{@Param}} annotation could be used along with {{@Pos}} for formatting possibly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6682) Upgrade Hibernate to 5.2.0
by Frank Langelage (JIRA)
Frank Langelage created WFLY-6682:
-------------------------------------
Summary: Upgrade Hibernate to 5.2.0
Key: WFLY-6682
URL: https://issues.jboss.org/browse/WFLY-6682
Project: WildFly
Issue Type: Component Upgrade
Components: JPA / Hibernate
Affects Versions: 10.0.0.Final
Reporter: Frank Langelage
Assignee: Scott Marlow
Priority: Critical
Fix For: 10.1.0.Final
Upgrade Hibernate to latest version 5.2.0.Final.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6681) @Singleton + @Schedule locks web container requests
by Alan Echer (JIRA)
[ https://issues.jboss.org/browse/WFLY-6681?page=com.atlassian.jira.plugin.... ]
Alan Echer updated WFLY-6681:
-----------------------------
Steps to Reproduce:
I created a simple application to illustrate the problem, this is a normal behavior or is there any way to run treads in the background without disturbing the running web application?
{code:java}
import javax.ejb.Schedule;
import javax.ejb.Singleton;
@Singleton(name = "Schedule")
public class ScheduleTest {
@Schedule(hour = "*", minute = "*", second = "30")
public void enviaResumoSemanalContaUsuario() {
System.out.println("Testing!");
}
}
{code}
Place debug the lines of "Testing," and the web page stops responding.
{code:html}
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<html>
<head>
<title>$Title$</title>
</head>
<body>
$END$
</body>
</html>
{code}
was:
I created a simple application to illustrate the problem
{code:java}
import javax.ejb.Schedule;
import javax.ejb.Singleton;
@Singleton(name = "Schedule")
public class ScheduleTest {
@Schedule(hour = "*", minute = "*", second = "30")
public void enviaResumoSemanalContaUsuario() {
System.out.println("Testing!");
}
}
{code}
Place debug the lines of "Testing," and the web page stops responding.
{code:html}
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<html>
<head>
<title>$Title$</title>
</head>
<body>
$END$
</body>
</html>
{code}
> @Singleton + @Schedule locks web container requests
> ---------------------------------------------------
>
> Key: WFLY-6681
> URL: https://issues.jboss.org/browse/WFLY-6681
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.0.0.Final
> Environment: java version "1.8.0_91"
> Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
> WildFly Full 10.0.0.Final
> Reporter: Alan Echer
>
> I'm having problems using a @Singleton with @Schedule along with a web application, because while the singleton is running the web application does not respond.
> bitbucket repo: https://bitbucket.org/alanecher/wfly-singleton-schedule
> PS: I <3 wildfly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6681) @Singleton + @Schedule locks web container requests
by Alan Echer (JIRA)
[ https://issues.jboss.org/browse/WFLY-6681?page=com.atlassian.jira.plugin.... ]
Alan Echer updated WFLY-6681:
-----------------------------
Steps to Reproduce:
I created a simple application to illustrate the problem
{code:java}
import javax.ejb.Schedule;
import javax.ejb.Singleton;
@Singleton(name = "Schedule")
public class ScheduleTest {
@Schedule(hour = "*", minute = "*", second = "30")
public void enviaResumoSemanalContaUsuario() {
System.out.println("Testing!");
}
}
{code}
Place debug the lines of "Testing," and the web page stops responding.
{code:html}
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<html>
<head>
<title>$Title$</title>
</head>
<body>
$END$
</body>
</html>
{code}
was:
I created a simple application to illustrate the problem
{code:java}
import javax.ejb.Schedule;
import javax.ejb.Singleton;
@Singleton(name = "Schedule")
public class ScheduleTest {
@Schedule(hour = "*", minute = "*", second = "30")
public void enviaResumoSemanalContaUsuario() {
System.out.println("Testing!");
}
}
{code}
Coloque o debug na linha do "Testing!", e a página web para de responder.
{code:html}
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<html>
<head>
<title>$Title$</title>
</head>
<body>
$END$
</body>
</html>
{code}
> @Singleton + @Schedule locks web container requests
> ---------------------------------------------------
>
> Key: WFLY-6681
> URL: https://issues.jboss.org/browse/WFLY-6681
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.0.0.Final
> Environment: java version "1.8.0_91"
> Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
> WildFly Full 10.0.0.Final
> Reporter: Alan Echer
>
> I'm having problems using a @Singleton with @Schedule along with a web application, because while the singleton is running the web application does not respond.
> bitbucket repo: https://bitbucket.org/alanecher/wfly-singleton-schedule
> PS: I <3 wildfly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6681) @Singleton + @Schedule locks web container requests
by Alan Echer (JIRA)
Alan Echer created WFLY-6681:
--------------------------------
Summary: @Singleton + @Schedule locks web container requests
Key: WFLY-6681
URL: https://issues.jboss.org/browse/WFLY-6681
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 10.0.0.Final
Environment: java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
WildFly Full 10.0.0.Final
Reporter: Alan Echer
I'm having problems using a @Singleton with @Schedule along with a web application, because while the singleton is running the web application does not respond.
bitbucket repo: https://bitbucket.org/alanecher/wfly-singleton-schedule
PS: I <3 wildfly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1581) AttributeDefinition.convertToExpectedType can convert LIST of PROPERTY to OBJECT
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1581:
----------------------------------------
Summary: AttributeDefinition.convertToExpectedType can convert LIST of PROPERTY to OBJECT
Key: WFCORE-1581
URL: https://issues.jboss.org/browse/WFCORE-1581
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
It's valid for callers to pass a param of ModelType.LIST with elements of type PROPERTY for use in attributes of type OBJECT. AttributeDefinition.convertToExpectedType can deal with this, thus avoiding storing an attribute value with a "usable" but not "per specification" type.
JBEAP-4767 shows an example case where this can of value is passed as a param.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6642) Automatic creation of transport config in IOR settings
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-6642?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski updated WFLY-6642:
---------------------------------
Description: I propose that the transport config parameters configured in ior settings, which later are present in the description of all corba object IORs created in the server, are created automatically. I don't like the idea of manual configuration as it provides invalid description of actual transport parameters in most circumstances. We are providing either standard socket transport or (if configured) SSL transport. Currently user is responsible for providing transport description. So if for example user configures SSL transport but doesn't change transport config then transport description in ior settings is invalid. What is more transport config is currently used to configure required SSL connection - that is if user wants to configure SSL connection he has to specify at least one SSL related transport field as required. This is imo inelegant and not much user friendly. I propose the following change: transport config is created automatically. If user configures SSL then all transport fields provided by SSL (f.e. confidentiality) will be set as supported. To configure required ssl connections server-requires-ssl field in security tag is introduced. If this field is set to true, then all SSL transport fields will be set as required, thus we will achieve factual transport description in ior-settings and provide user with simple SSL configuration. (was: I propose that the transport config parameters configured in ior settings, which later are present in the description of all corba object IORs created in the server, are created automatically. I don't like the idea of manual configuration as it provides invalid description of actual transport parameters in most circumstances. We are providing either standard socket transport or (if configured) SSL transport. Currently user is responsible for providing transport description. So if for example user configures SSL transport but doesn't change transport config then transport description in ior settings is invalid. What is more transport config is currently used to configure required SSL connection - that is if user wants to configure SSL connection he has to specify at least one SSL related transport field as required. This is imo inelegant and not much user friendly. I propose the following change: transport config is created automatically. If user configures SSL then all transport fields provided by SSL (f.e. confidentiality) will be set as supported. To configure required ssl connections server-requires-ssl field in security tag is introduced. If this field is set to true, then all SSL transport fields will be set as required. )
> Automatic creation of transport config in IOR settings
> ------------------------------------------------------
>
> Key: WFLY-6642
> URL: https://issues.jboss.org/browse/WFLY-6642
> Project: WildFly
> Issue Type: Enhancement
> Components: IIOP
> Affects Versions: 10.0.0.Final
> Reporter: Tomasz Adamski
> Assignee: Tomasz Adamski
> Priority: Minor
>
> I propose that the transport config parameters configured in ior settings, which later are present in the description of all corba object IORs created in the server, are created automatically. I don't like the idea of manual configuration as it provides invalid description of actual transport parameters in most circumstances. We are providing either standard socket transport or (if configured) SSL transport. Currently user is responsible for providing transport description. So if for example user configures SSL transport but doesn't change transport config then transport description in ior settings is invalid. What is more transport config is currently used to configure required SSL connection - that is if user wants to configure SSL connection he has to specify at least one SSL related transport field as required. This is imo inelegant and not much user friendly. I propose the following change: transport config is created automatically. If user configures SSL then all transport fields provided by SSL (f.e. confidentiality) will be set as supported. To configure required ssl connections server-requires-ssl field in security tag is introduced. If this field is set to true, then all SSL transport fields will be set as required, thus we will achieve factual transport description in ior-settings and provide user with simple SSL configuration.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1578) Better check of names of existing resources when adding '{local|remote-destination-outbound-socket-binding'
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1578?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1578:
------------------------------------------
Just an FYI: "CLI" component should only be used for client side issues.
> Better check of names of existing resources when adding '{local|remote-destination-outbound-socket-binding'
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1578
> URL: https://issues.jboss.org/browse/WFCORE-1578
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha1
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Minor
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> Lets have some {{/socket-binding-group=standard-sockets/socket-binding}} with particular name. Then when I create some {{/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding}} or {{/socket-binding-group=standard-sockets/local-destination-outbound-socket-binding}} using same name as of already existing {{socket-binding}} resource, {{add}} operation is successful but when I perform server reload, it crashes as it is not able to parse configuration. See:
> # Start EAP and log to CLI
> # create your own {{socket-binding}} resource and {{\{remote|local\}-destination-outbound-socket-binding}} resource with same names and perform reload
> {code}
> /socket-binding-group=standard-sockets/socket-binding=myBinding:add()
> /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=myBinding:add(host=localhost,port=8765)
> or
> /socket-binding-group=standard-sockets/local-destination-outbound-socket-binding=myBinding:add(socket-binding-ref=http)
> reload
> {code}
> # server crashes with following stacktrace in console log:
> {code}
> 17:31:40,447 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Stopped Driver service with driver-name = h2
> 17:31:40,453 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0008: Undertow HTTP listener default suspending
> 17:31:40,454 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
> 17:31:40,454 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.3.21.Final-redhat-1 stopping
> 17:31:40,458 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
> 17:31:40,461 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) stopped in 22ms
> 17:31:40,461 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) starting
> 17:31:40,489 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> at org.jboss.as.server.ServerService.boot(ServerService.java:356)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[410,9]
> Message: WFLYCTL0042: A socket-binding or a outbound-socket-binding myBinding already declared has already been declared in socket-binding-group standard-sockets
> at org.jboss.as.server.parsing.StandaloneXml_4.parseSocketBindingGroup(StandaloneXml_4.java:518)
> at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:254)
> at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
> ... 3 more
> 17:31:40,490 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 17:31:40,491 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
> 17:31:40,496 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) stopped in 3ms
> {code}
> After this occurs, one needs to fix {{./standalone/configuration/standalone.xml}} manually by removing duplicate resources.
> If there is a problem for those resources to have same names I would welcome that names are checked during the {{add}} operation already regarding to all resources in {{socket-binding}} and {{\{remote|local\}-destination-outbound-socket-binding}}.
> Note: not sure whether CLI component is appropriate, please change if there is better component for this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months