[JBoss JIRA] Created: (AS7-1459) Add a commandline flag to the startup script to enable debugging
by Dan Allen (JIRA)
Add a commandline flag to the startup script to enable debugging
----------------------------------------------------------------
Key: AS7-1459
URL: https://issues.jboss.org/browse/AS7-1459
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Affects Versions: 7.0.0.Final
Reporter: Dan Allen
Assignee: Alexey Loubyansky
The startup script (standalone.sh & standalone.bat) should honor a commandline option that can be used to start the server with debugging enabled. Currently, the developer has to uncomment the JAVA_OPTS line in the standalone.conf file manually.
Proposal for starting the server with debugging enabled:
./bin/standalone.sh --debug
If necessary, the optional flag could accept the port as an optional argument.
./bin/standalone.sh --debug 8787
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-4461) Operation transformation infrastructure
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-4461:
-------------------------------------
Summary: Operation transformation infrastructure
Key: AS7-4461
URL: https://issues.jboss.org/browse/AS7-4461
Project: Application Server 7
Issue Type: Sub-task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Ability for extensions to register operation transformers. (This will likely be part of the resource transformation task AS7-4457.) Hooks to access that transformation registry during operation execution. This is to include:
1) Host level operations that target the slave HC directly but are proxied by the master HC.
2) Server level operations that target the slave HC's servers directly but are proxied by the master HC.
3) The first phase of domain-wide 2 phase operations where the master HC transmits the op to the slave HCs.
4) The second phase of domain-wide 2 phase operations where the master HC transmits server-level ops to the slave HCs for forwarding to their servers.
Item 4) above may be simple, as all the master HC is doing is executing ops according to instructions provided by the slave HCs in step 3). Those instructions will be correct for that slave HC.
--
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
13 years, 8 months
[JBoss JIRA] (AS7-4673) Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property
by Roger S (JIRA)
Roger S created AS7-4673:
----------------------------
Summary: Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property
Key: AS7-4673
URL: https://issues.jboss.org/browse/AS7-4673
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Environment: Red Hat Enterprise Linux Server release 5.7, JDK 7
Reporter: Roger S
I found that when the following is set in the standalone.xml of JBoss-7.1.1.Final, it will have a fatal error:
<xa-datasource....>
....
<xa-datasource-property name="ConnectionProperties">SetBigStringTryClob=true</xa-datasource-property>
....
</xa-datasource>
The error is:
Caused by: javax.resource.ResourceException: No property editor found for type: class java.util.Properties
at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:601)
at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:430)
When I don't define the SetBigStringTryClob setting, all is fine. However, the SetBigStringTryClob is really important for the application to work correctly. Hope there's at least a workaround.
This worked without problems in JBoss 4.2.3.
--
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
13 years, 8 months
[JBoss JIRA] (AS7-4913) Server sends "big interger <val>" for config entries when a reload is needed
by Heiko Rupp (JIRA)
Heiko Rupp created AS7-4913:
-------------------------------
Summary: Server sends "big interger <val>" for config entries when a reload is needed
Key: AS7-4913
URL: https://issues.jboss.org/browse/AS7-4913
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.2.Final (EAP)
Reporter: Heiko Rupp
Assignee: Brian Stansberry
Priority: Critical
RHQ sends JSON like this to change e.g. the max-pool-size setting of a data source:
{"operation":"composite","steps":[{"operation":"write-attribute","address":[{"subsystem":"datasources"},{"data-source":"ExampleDS"}],"name":"max-pool-size","value":75},{"operation":"write-attribute","address":[{"subsystem":"datasources"},{"data-source":"ExampleDS"}],"name":"use-fast-fail","value":false}],"address":[]}
Server returns success.
When I directly go to the cli afterwards I see:
[standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-attribute(name=max-pool-size)
{
"outcome" => "success",
"result" => big integer 75,
"response-headers" => {"process-state" => "restart-required"}
}
Note the "big integer"
[standalone@localhost:9999 /] /:reload
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-attribute(name=max-pool-size)
{
"outcome" => "success",
"result" => 75
}
[standalone@localhost:9999 /]
Now the server acts as always.
--
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
13 years, 8 months
[JBoss JIRA] (AS7-4237) Possible errrors
by Yamamoto Mie (JIRA)
Yamamoto Mie created AS7-4237:
---------------------------------
Summary: Possible errrors
Key: AS7-4237
URL: https://issues.jboss.org/browse/AS7-4237
Project: Application Server 7
Issue Type: Enhancement
Components: Documentation
Reporter: Yamamoto Mie
Priority: Minor
I have a few questions about AS7 and also found possible errors in the doc.
Questions:
- Null owned session update
can you explain when is this message shown?
- to multiple create* methods with different return types on home %s
when is this message shown?
to create* multiple methods?? or multiple create() methods?
- EJB component for address %s is in
Is this EJB component for address %s is in (state %s)?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Possible errors
- Class %s has more *that* one constructor annotated with @Inject
-> more than?
- Boolean to determine whether to create create the tables
- Boolean to determine whether to create drop the tables
- Timeout, in seconds, a deployment is allows to execute before being canceled. The default is 60 seconds.
- Filed to lookup: %s
- Specifies whether the ejb3 container need only (to?) provide the "LITE" profile of the specification. This value should only be false when using the "everything" distro.
- Removes a specific (a) bean instance pool which has a strict upper limit for bean instances
-No timed object invoke(d) for %s
--
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
13 years, 8 months