[JBoss JIRA] (AS7-3884) Load testing application with Jmeter & jboss remoting throws exception saying "Too many channels open"
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-3884?page=com.atlassian.jira.plugin.s... ]
jaikiran pai commented on AS7-3884:
-----------------------------------
I've created REM3-144 to get a fix in JBoss Remoting. Once that is fixed, the org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_CHANNELS property can be passed for connection creation options to increase the number of allowed channels.
> Load testing application with Jmeter & jboss remoting throws exception saying "Too many channels open"
> ------------------------------------------------------------------------------------------------------
>
> Key: AS7-3884
> URL: https://issues.jboss.org/browse/AS7-3884
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB, Naming
> Affects Versions: 7.1.0.Final
> Environment: windows 64 bit
> Reporter: Prasad Deshpande
> Assignee: jaikiran pai
>
> I've created a sampler for JMeter for load testing application. When I ran that with say around 30 threads with rampup time 80 seconds, after a while I kept getting exception specified in https://community.jboss.org/thread/195709?tstart=0. I later tried to close InitialContext in teardown methods, but wasn't really helpful. I looked at no. of InitialContext intances present in the VM using visualvm heapdump & found that just before throwing exception, it was 24 & after throwing exception for all threads, it did reach to 30, but it wasn't useful..
> Please note that, I'm creating InitialContext with passing following parameters to it:
> java.naming.factory.url.pkgs=org.jboss.ejb.client.naming
> java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory
> java.naming.provider.url=remote://localhost:4447
> jboss.naming.client.ejb.context=true
> Here is the code for Java Sampler
> {code}
> package com;
> import org.apache.jmeter.config.Arguments;
> import org.apache.jmeter.protocol.java.sampler.AbstractJavaSamplerClient;
> import org.apache.jmeter.protocol.java.sampler.JavaSamplerContext;
> import org.apache.jmeter.samplers.SampleResult;
> import com.banctec.caseware.client.api.API;
> import com.banctec.caseware.client.api.RemoteClientAPI;
> import com.banctec.caseware.resources.CaseResource;
> import com.banctec.caseware.resources.LoginResource;
> import com.banctec.caseware.resources.Resource;
> public class EJBTest extends AbstractJavaSamplerClient {
> private API api = null;
> private Long typeId;
> private int setupTestCalled = 0;
> private int teardownTestCalled = 0;
> private int runTestCalled = 0;
>
> public Arguments getDefaultParameters() {
> Arguments defaultParameters = new Arguments();
> defaultParameters.addArgument("typeId", "1");
> defaultParameters.addArgument("RunLoop", "200");
> defaultParameters.addArgument("username", "abc");
> defaultParameters.addArgument("password", "abc");
> return defaultParameters;
> }
>
> public void setupTest(JavaSamplerContext context) {
> try {
> typeId = context.getLongParameter("typeId");
> api = new RemoteClientAPI();//this is where InitialContext gets created
> LoginResource loginResource = new LoginResource(context.getParameter("username"), context.getParameter("password"));
> loginResource.setUseDefaultRole(Boolean.valueOf(true));
> api.login(new Resource[] { loginResource });
> }catch (Exception e) {
> e.printStackTrace();
> }
> System.out.println(" Number of times setupTest called "+(++setupTestCalled));
> }
>
> public void teardownTest(JavaSamplerContext context) {
> try{
> if (api != null) {
> api.logout();//In this method InitialContext.close() get's called
> }
> }catch (Exception e) {
> e.printStackTrace();
> }
> System.out.println(" Number of times teardownTest called "+(++teardownTestCalled));
> }
>
> public SampleResult runTest(JavaSamplerContext context) {
> SampleResult result = new SampleResult();
> boolean success = true;
> int loopCount = context.getIntParameter("RunLoop");
> result.sampleStart();
> //Here goes the code that will call few business methods on remote EJB's in application
> // I've purposely removed this bit here..
> System.out.println(" Number of times runTest called "+(++runTestCalled));
> result.sampleEnd();
> result.setSuccessful(success);
> return result;
> }
> }
> {code}
--
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
12 years, 2 months
[JBoss JIRA] (AS7-3932) DataSource connection property problems
by Heiko Braun (JIRA)
Heiko Braun created AS7-3932:
--------------------------------
Summary: DataSource connection property problems
Key: AS7-3932
URL: https://issues.jboss.org/browse/AS7-3932
Project: Application Server 7
Issue Type: Bug
Components: JCA
Reporter: Heiko Braun
Assignee: Stefano Maestri
Fix For: 7.1.2.Final
We have several problems with DS connection properties:
A) they cannot be removed
1.) create a datasource
2.) add connection property
3.) enable, then disable DS
4.) try to remove connection property
leads to
{noformat}
[Server:server-one] 08:31:18,978 INFO [org.jboss.as.controller] (host-controller-connection-threads - 1) JBAS014774: Service status report
[Server:server-one] JBAS014775: New missing/unsatisfied dependencies:
[Server:server-one] service jboss.data-source-config.MyDS.connection-properties.testProp (missing) dependents: [service jboss.data-source-config.MyDS]
[Server:server-one]
{noformat}
--
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
12 years, 2 months
[JBoss JIRA] (AS7-3931) After removing datasource param, accessing Runtime DS subsystem view in Domain causes No handler for read-resource at address error
by William Bendrot (JIRA)
William Bendrot created AS7-3931:
------------------------------------
Summary: After removing datasource param, accessing Runtime DS subsystem view in Domain causes No handler for read-resource at address error
Key: AS7-3931
URL: https://issues.jboss.org/browse/AS7-3931
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Final
Environment: RHEL 5.4x in a Domain with one DC/1Server and one HC
Reporter: William Bendrot
Assignee: Heiko Braun
After removing a parameter from a data source in the console, when accessing the Datasource Subsystem panel on the Runtime page the following error is displayed:
Unknown error
Unexpected HTTP response: 500
Request
{
"address" => [
("host" => "SovereignIntDC"),
("server" => "SovereignInt01"),
("subsystem" => "datasources"),
("data-source" => "sovereign"),
("statistics" => "pool")
],
"operation" => "read-resource",
"include-runtime" => true
}
Response
Internal Server Error
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => "JBAS014739: No handler for read-resource at address [
(\"subsystem\" => \"datasources\"),
(\"data-source\" => \"sovereign\"),
(\"statistics\" => \"pool\")
]",
"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
12 years, 2 months
[JBoss JIRA] (AS7-3408) Classloading issue with HornetQLoggerFactory - possilbe problem with failback
by Miroslav Novak (JIRA)
Miroslav Novak created AS7-3408:
-----------------------------------
Summary: Classloading issue with HornetQLoggerFactory - possilbe problem with failback
Key: AS7-3408
URL: https://issues.jboss.org/browse/AS7-3408
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.0.CR1
Reporter: Miroslav Novak
Assignee: Andy Taylor
Priority: Critical
Fix For: 7.1.0.Final
Attachments: console-log-backup-server.txt, console-log-live-server.txt, reproducer.zip
Test scenario:
1. Start two servers AS7/EAP6 servers - live and its backup in dedicated topology - each on different machine
2. Kill live server using "kill -9 ..."
3. Start live server again
In step 3. there are unexpected messages in console log of live and backup server.
>From backup server:
{code}
12:07:26,165 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (Thread-78) HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [17700d86-45b2-11e1-a575-d48564b8e1e7] stopped
12:07:26,165 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (Thread-78) unable to restart server, please kill and restart manually: java.lang.IllegalArgumentException: Could not find class org.jboss.as.messaging.HornetQLoggerFactory
at org.hornetq.utils.ClassloadingUtil$1.run(ClassloadingUtil.java:42) [hornetq-core-2.2.7.Final.jar:]
at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_22]
at org.hornetq.utils.ClassloadingUtil.safeInitNewInstance(ClassloadingUtil.java:16) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.instantiateInstance(HornetQServerImpl.java:1868) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.initialiseLogging(HornetQServerImpl.java:1301) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:541) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreBackupActivation$1FailbackChecker$1.run(HornetQServerImpl.java:430) [hornetq-core-2.2.7.Final.jar:]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
{code}
>From live server:
{code}
12:07:51,993 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/topic/test
12:07:52,007 INFO [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 31092ms - Started 155 of 263 services (103 services are passive or on-demand)
12:07:53,292 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying reconnection attempt 1
12:07:53,292 DEBUG [org.hornetq.core.remoting.impl.netty.NettyConnector] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Started Netty Connector version 3.2.3.Final-r${buildNumber}
12:07:53,292 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying to connect at the main server using connector :org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5446&host=192-168-10-4
12:07:53,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Main server is not up. Hopefully there's a backup configured now!
12:07:55,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying reconnection attempt 2
12:07:55,293 DEBUG [org.hornetq.core.remoting.impl.netty.NettyConnector] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Started Netty Connector version 3.2.3.Final-r${buildNumber}
12:07:55,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying to connect at the main server using connector :org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5446&host=192-168-10-4
12:07:55,294 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Main server is not up. Hopefully there's a backup
{code}
I'm not fully sure but it looks like that backup server did not manage to get to "waiting for live to fail" state and live server is not able to detect it.
There is set "DEBUG" level logging for "org.hornetq" in attached logs.
I've attached reproducer.zip - steps to use:
1. Download and unzip "reproducer.zip"
2. Prepare live and backup server - "sh prepare.sh"
3. Start live - "sh start-server1.sh server1_hostname"
4. Start backup - "sh start-server2.sh server2_hostname"
5. Kill live server using "kill -9 server1_process_id"
6. Start live server again - "sh start-server1.sh server1_hostname"
Note:
In reproducer.zip are configuration files standalone-ha-A.xml, standalone-ha-B.xml (A for live, B for backup).
--
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
12 years, 2 months
[JBoss JIRA] (AS7-3317) ClassNotFoundException during start - org.jboss.as.messaging.jms.TransactionManagerLocator
by Miroslav Novak (JIRA)
Miroslav Novak created AS7-3317:
-----------------------------------
Summary: ClassNotFoundException during start - org.jboss.as.messaging.jms.TransactionManagerLocator
Key: AS7-3317
URL: https://issues.jboss.org/browse/AS7-3317
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.0.CR1
Reporter: Miroslav Novak
Assignee: Clebert Suconic
Fix For: 7.1.0.Final
When logging subsystem is set to DEBUG level for "org.hornetq" then ClassNotFoundException exception appears in console log:
{code}
12:45:01,163 DEBUG [org.hornetq.ra.Util] (MSC service thread 1-4) org.jboss.as.messaging.jms.TransactionManagerLocator from [Module "org.hornetq.ra:main" from local module loader @6e811c88 (roots: /mnt/shared/test-eap6/server1/jboss-eap-6.0/modules)]: java.lang.ClassNotFoundException: org.jboss.as.messaging.jms.TransactionManagerLocator from [Module "org.hornetq.ra:main" from local module loader @6e811c88 (roots: /mnt/shared/test-eap6/server1/jboss-eap-6.0/modules)]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:473)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:461)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:403)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:125)
at org.hornetq.ra.Util.locateTM(Util.java:261) [hornetq-ra-2.2.7.Final.jar:]
at org.hornetq.ra.HornetQResourceAdapter.locateTM(HornetQResourceAdapter.java:1555) [hornetq-ra-2.2.7.Final.jar:]
at org.hornetq.ra.HornetQResourceAdapter.start(HornetQResourceAdapter.java:210) [hornetq-ra-2.2.7.Final.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_22]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_22]
at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_22]
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:345) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final]
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2127) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final]
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1030) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final]
at org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator.doDeploy(ResourceAdapterActivatorService.java:148) [jboss-as-connector-7.1.0.CR1-redhat-1.jar:7.1.0.CR1-redhat-1]
at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:94) [jboss-as-connector-7.1.0.CR1-redhat-1.jar:7.1.0.CR1-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
{code}
--
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
12 years, 2 months
[JBoss JIRA] (AS7-4001) Bad reference to XSL transformation files in module jboss-as-testsuite-benchmark and jboss-as-testsuite-stress
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-4001?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek moved JBPAPP-8333 to AS7-4001:
---------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-4001 (was: JBPAPP-8333)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.1.Final
(was: EAP 6.0.0 ER 2)
Component/s: Test Suite
(was: Testsuite)
Security: (was: JBoss Internal)
Docs QE Status: (was: NEW)
> Bad reference to XSL transformation files in module jboss-as-testsuite-benchmark and jboss-as-testsuite-stress
> --------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4001
> URL: https://issues.jboss.org/browse/AS7-4001
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.1.Final
> Reporter: Pavel Janousek
> Assignee: Ondrej Zizka
> Priority: Blocker
>
> Transformation procedure is invoked, but it seems like bad configuration path or not correctly done clean-up in previous step. I caught this problem via warning:
> {code}
> [INFO] --- xml-maven-plugin:1.0:transform (ts.config-as.ip) @ jboss-as-testsuite-stress ---
> [WARNING] The directory /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/target/jbossas/standalone/configuration, which is a base directory of a ValidationSet or TransformationSet, does not exist.
> [WARNING] No files found for transformation by stylesheet /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/../integration/src/test/xslt/changeIPAddresses.xsl
> [WARNING] The directory /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/target/jbossas/standalone/configuration, which is a base directory of a ValidationSet or TransformationSet, does not exist.
> [WARNING] No files found for transformation by stylesheet /mnt/hudson_workspace/workspace/AS7-TS-linux-ipv6-experiments/testsuite/stress/../integration/src/test/xslt/addJmsDestinations.xsl
> {code}
> Further investigation says /build/target/... isn't copied to these modules at all.
> You can see this problem [there|https://hudson.qa.jboss.com/hudson/job/AS7-TS-linux-ipv6-experiment...].
--
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
12 years, 2 months