[JBoss JIRA] (AS7-3364) Admin console allows assigning multiple connectors to the same socket binding
by Jan Martiska (JIRA)
Jan Martiska created AS7-3364:
---------------------------------
Summary: Admin console allows assigning multiple connectors to the same socket binding
Key: AS7-3364
URL: https://issues.jboss.org/browse/AS7-3364
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Jan Martiska
Assignee: Heiko Braun
Priority: Minor
When creating a connector, the form checks that the value "Socket Binding" does not reference a socket binding that is already taken by another connector. If it is taken, validation of the form fails. However, when you successfully create a server and then CHANGE the Socket Binding using the 'Edit' button, this validation is not applied. Therefore it is possible to assign two different connectors to the same socket binding, e.g. to the same port.
This will cause a "java.lang.Exception: Socket bind failed: [98] Address already in use" when the server is restarted.
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3412) Unable to add ejb3 thread pool
by Jan Martiska (JIRA)
Jan Martiska created AS7-3412:
---------------------------------
Summary: Unable to add ejb3 thread pool
Key: AS7-3412
URL: https://issues.jboss.org/browse/AS7-3412
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Jan Martiska
Assignee: Heiko Braun
Fix For: 7.1.0.Final
In the latest update, ejb3 thread pools now require specifying the time unit for keepalive-time, until now, it has only been a simple number, now it is an object. Trying to create an ejb3 thread pool in admin console will fail:
{
"outcome" => "failed",
"failure-description" => "Attribute keepalive-time expects values of type OBJECT but got 100 of type INT",
"rolled-back" => true
}
--
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
14 years, 2 months
[JBoss JIRA] Created: (AS7-1758) CLI usability: operations need conventient help option too
by Radoslav Husar (JIRA)
CLI usability: operations need conventient help option too
----------------------------------------------------------
Key: AS7-1758
URL: https://issues.jboss.org/browse/AS7-1758
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.0.1.Final, 7.0.0.Final
Reporter: Radoslav Husar
Assignee: Alexey Loubyansky
Priority: Critical
This is a critical usability issue. We must provide a way to get help about operations usage too. Its difficult to comprehend how to use operations from this model:
{code}
[domain@localhost:9999 /] :read-operation-description(name="upload-deployment-url")
{
"outcome" => "success",
"result" => {
"operation-name" => "upload-deployment-url",
"description" => "Indicates that the deployment content available at the included URL should be added to the deployment content repository. Note that this operation does not indicate the content should be deployed into the runtime.",
"request-properties" => {"url" => {
"type" => STRING,
"description" => "The URL at which the deployment content is available for upload to the domain's or standalone server's deployment content repository.. Note that the URL must be accessible from the target of the operation (i.e. the Domain Controller or standalone server).",
"required" => true,
"min-length" => 1,
"nillable" => false
}},
"reply-properties" => {
"type" => BYTES,
"description" => "The hash of managed deployment content that has been uploaded to the domain's or standalone server's deployment content repository.",
"min-length" => 20,
"max-length" => 20,
"nillable" => false
}
}
}
[domain@localhost:9999 /]
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-2961) Context lookup fails during WebService constructor.
by Jeremy Whiting (Created) (JIRA)
Context lookup fails during WebService constructor.
----------------------------------------------------
Key: AS7-2961
URL: https://issues.jboss.org/browse/AS7-2961
Project: Application Server 7
Issue Type: Bug
Components: Web Services
Affects Versions: 7.1.0.Beta1
Environment: OpenJDK 6 on Fedora16
Reporter: Jeremy Whiting
Assignee: Alessio Soldano
Attachments: envEntryWeb.tar.gz
During a WebService constructor call my application is making a jndi context lookup that is failing. The lookup uses java:comp/env to lookup an entry. The web service is a JEE5 spec application.
The application defines an env-entry in the web deployment descriptor.
It looks as though the context is not established in time for the WebSevice constructor being called.
A sample application is provided to demonstrate the issue. When this application is deployed I am seeing the stack trace in the second attachment.
--
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
14 years, 2 months