[JBoss JIRA] Created: (JBWEB-203) Segfault if not enought threads
by Dmitry Murashenkov (JIRA)
Segfault if not enought threads
-------------------------------
Key: JBWEB-203
URL: https://issues.jboss.org/browse/JBWEB-203
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tomcat
Environment: JBoss 6, Debian 6.0.1, JBoss native APR connector 2.0.9
Reporter: Dmitry Murashenkov
Assignee: Remy Maucherat
Attachments: hs_err_pid13822.log
If number of requests to server is larger than the max number of worker threads - segmentation fault is raised very often. This bug was originally reported against tomcat native library, but is present in jboss native connector too:
https://issues.apache.org/bugzilla/show_bug.cgi?id=49595
TC:
1. Setup ARP. In case of debian we tried: libs (libtcnative and its dependencies) that are available in debian repository, jboss native 2.0.9 linux binary package, tried compiling 2.0.9 package from source. In all cases we validated that neccessary lib is used via ldd and pmap.
2. Setup few worker threads in http connector:
<Connector ... maxThreads="1"/>
3. Start sending http requests to server in parallel. In our case load client is sending requests in 40 parallel threads. So it tries to open new connection and send request to maintain parallel sending rate, often get Connection reset by peer exception and tries again. After 15-25 seconds of such load jboss crashes with segmentation fault. In our case the bug is reproduced in 100% cases in this period of time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1346) Adding RA fails
by Heiko Braun (JIRA)
Adding RA fails
---------------
Key: AS7-1346
URL: https://issues.jboss.org/browse/AS7-1346
Project: Application Server 7
Issue Type: Bug
Components: JCA
Reporter: Heiko Braun
Assignee: Jesper Pedersen
Fix For: 7.1.0.Alpha1
Adding a new RA fails:
{noformat}
Request:
[INFO] {
[INFO] "operation" => "add",
[INFO] "address" => [
[INFO] ("subsystem" => "resource-adapters"),
[INFO] ("resource-adapter" => "xmpp")
[INFO] ],
[INFO] "archive" => "xmpp-ra.rar",
[INFO] "transaction-support" => "NoTransaction",
[INFO] "connection-definitions" => [{
[INFO] "class-name" => "com.ramphastos.xmpp.XmppConnectionFactory",
[INFO] "jndi-name" => "eis/xmpp2",
[INFO] "pool-name" => "xmpp_Pool"
[INFO] }]
[INFO] }
Server Log:
11:11:43,826 ERROR [org.jboss.as.controller] (pool-2-thread-2) Operation ("remove") failed - address: ([
("subsystem" => "resource-adapters"),
("resource-adapter" => "xmpp")
]): java.util.NoSuchElementException: "resource-adapter" => "xmpp"
at org.jboss.as.controller.registry.BasicResource.requireChild(BasicResource.java:95)
at org.jboss.as.controller.OperationContextImpl.readModel(OperationContextImpl.java:697)
at org.jboss.as.connector.subsystems.resourceadapters.RaRemove.execute(RaRemove.java:51)
at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:351)
at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298)
at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223)
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1212) :read-operation-description(name=add) shows pool-name as optional, but deploy without pool-name fail
by Heiko Rupp (JIRA)
:read-operation-description(name=add) shows pool-name as optional, but deploy without pool-name fail
----------------------------------------------------------------------------------------------------
Key: AS7-1212
URL: https://issues.jboss.org/browse/AS7-1212
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.CR1
Reporter: Heiko Rupp
Assignee: Brian Stansberry
[domain@localhost:9999 subsystem=datasources] ./data-source=java\:jboss\/datasources\/ExampleDS:read-operation-description(name=add)
{
"outcome" => "success",
"result" => {
"operation-name" => "add",
"description" => "Adds a new data-source",
"request-properties" => {
....
"pool-name" => {
"description" => "Specifies the pool name for the datasource used for management",
"type" => STRING,
"required" => false
},
So the pool-name is optional, but when I deploy a data source without pool name, deployment fails:
[Server:server-one] 17:26:49,124 ERROR [stderr] (pool-1-thread-42) org.jboss.jca.common.api.validator.ValidateException: IJ010068: Missing required attribute pool-name in org.jboss.jca.common.metadata.ds.DataSourceImpl
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1339) Expose RA config properties in DMR
by Heiko Braun (JIRA)
Expose RA config properties in DMR
----------------------------------
Key: AS7-1339
URL: https://issues.jboss.org/browse/AS7-1339
Project: Application Server 7
Issue Type: Feature Request
Components: JCA
Reporter: Heiko Braun
Assignee: Jesper Pedersen
Fix For: 7.1.0.Beta1
The config attributes are not exposed:
<subsystem xmlns="urn:jboss:domain:resource-adapters:1.0">
[...]
<config-property name="host">talk.google.com</config-property>
<config-property name="port">5222</config-property>
[...]
</resource-adapters>
[standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=xmpp-ra.rar:read-resource
{
"outcome" => "success",
"result" => {
"archive" => "xmpp-ra.rar",
"background-validation" => undefined,
"background-validation-minutes" => undefined,
"blocking-timeout-wait-millis" => undefined,
"connection-definitions" => [{
"class-name" => "com/ramphastos/xmpp/jca/XmppManagedConnectionFactory",
"jndi-name" => "java:/eis/ra-xmpp",
"pool-name" => "XmppFactoryPool",
"enabled" => true,
"use-java-context" => true,
"use-ccm" => true,
"max-pool-size" => 100,
"min-pool-size" => 10,
"pool-prefill" => false,
"pool-use-strict-min" => false,
"flush-strategy" => "FAILING_CONNECTION_ONLY",
"security-application" => true
}],
"idle-timeout-minutes" => undefined,
"max-pool-size" => undefined,
"min-pool-size" => undefined,
"pool-prefill" => undefined,
"pool-use-strict-min" => undefined,
"transaction-support" => "NoTransaction",
"use-fast-fail" => undefined
}
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBAS-9242) Ports in use message better
by Jim Tyrrell (JIRA)
Ports in use message better
---------------------------
Key: JBAS-9242
URL: https://issues.jboss.org/browse/JBAS-9242
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 7.0.0.Beta2
Reporter: Jim Tyrrell
When starting up two instances of JBoss AS 7 beta 2, I get the following error message that is not descriptive enough. This error should output the IP address and the port number that was not available.
[Host Controller] 16:13:50,135 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.host.controller.management.communication: org.jboss.msc.service.StartException in service jboss.host.controller.management.communication: Failed to start server socket
[Host Controller] at org.jboss.as.host.controller.mgmt.ManagementCommunicationService.start(ManagementCommunicationService.java:94)
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344)
[Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
[Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
[Host Controller] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
[Host Controller] Caused by: java.net.BindException: Address already in use
[Host Controller] at java.net.PlainSocketImpl.socketBind(Native Method) [:1.6.0_24]
[Host Controller] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [:1.6.0_24]
[Host Controller] at java.net.ServerSocket.bind(ServerSocket.java:328) [:1.6.0_24]
[Host Controller] at org.jboss.as.protocol.ProtocolServer.start(ProtocolServer.java:118)
[Host Controller] at org.jboss.as.host.controller.mgmt.ManagementCommunicationService.start(ManagementCommunicationService.java:92)
[Host Controller] ... 4 more
[Host Controller]
[Host Controller] 16:13:50,138 ERROR [org.jboss.as.host.controller] (MSC service thread 1-3) Service [service jboss.host.controller.management.communication] failed.: org.jboss.msc.service.StartException in service jboss.host.controller.management.communication: Failed to start server socket
[Host Controller] at org.jboss.as.host.controller.mgmt.ManagementCommunicationService.start(ManagementCommunicationService.java:94)
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344)
[Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
[Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
[Host Controller] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
[Host Controller] Caused by: java.net.BindException: Address already in use
[Host Controller] at java.net.PlainSocketImpl.socketBind(Native Method) [:1.6.0_24]
[Host Controller] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [:1.6.0_24]
[Host Controller] at java.net.ServerSocket.bind(ServerSocket.java:328) [:1.6.0_24]
[Host Controller] at org.jboss.as.protocol.ProtocolServer.start(ProtocolServer.java:118)
[Host Controller] at org.jboss.as.host.controller.mgmt.ManagementCommunicationService.start(ManagementCommunicationService.java:92)
[Host Controller] ... 4 more
[Host Controller]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months