[JBoss JIRA] (AS7-3495) Unexpected auth dir in standalone/tmp when -Djboss.server.temp.dir is used
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created AS7-3495:
--------------------------------------
Summary: Unexpected auth dir in standalone/tmp when -Djboss.server.temp.dir is used
Key: AS7-3495
URL: https://issues.jboss.org/browse/AS7-3495
Project: Application Server 7
Issue Type: Feature Request
Components: Server
Affects Versions: 7.1.0.CR1b
Reporter: Rostislav Svoboda
Assignee: Brian Stansberry
Fix For: 7.1.0.Final
Unexpected 'auth' dir is created in standalone/tmp when -Djboss.server.temp.dir is used.
There shouldn't be tmp directory at all.
Steps to reproduce:
- remove everything from 'standalone' directory with exception for 'configuration' and 'deployments' sub-directories
- run standalone - 'bin/standalone.sh -Djboss.server.log.dir=xx-log -Djboss.server.data.dir=xx-data -Djboss.server.temp.dir=xx-temp -Djboss.server.deploy.dir=xx-deployments'
- list recursively 'standalone' directory -- 'tmp' directory with 'auth' subdirectory is created
'jboss.server.temp.dir' property is not 100% reflected.
--
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, 4 months
[JBoss JIRA] (AS7-3738) Errors in resource adapters subsystem checking
by Vladimir Rastseluev (JIRA)
Vladimir Rastseluev created AS7-3738:
----------------------------------------
Summary: Errors in resource adapters subsystem checking
Key: AS7-3738
URL: https://issues.jboss.org/browse/AS7-3738
Project: Application Server 7
Issue Type: Bug
Components: JCA
Reporter: Vladimir Rastseluev
Assignee: Stefano Maestri
Fix For: 7.1.1.Final
There are possible errors, found by RA metrics tests:
1)it's possible to add 2 <archive> elements (maxOccur=1 in xsd)
2)it's possible to add 2 <connection-property> elements with the same "name" attribute
3) it's possible to add an empty <transactionn-support/> element
4) it's possible to add 2 <transactionn-support> elements
5) it's possible to add <transaction-support> element with XATransaction value and just <pool> subelement(instead of <xa-pool>) to the connection definition and vice versa (<transaction-support>LocalTransaction and <xa-pool>)
6) it's possible to set min-pool-size>max-pool-size in <pool> element
7) default value for <wrap-xa-resource> in xsd schema is false, but always set to true after RA creation
8) it's possible to add all <security> subelements together simultaneously(e.g. <application> and <security-domain>) in all possible combinations despite of choose:xsd annotation
9) it's possible to add 2 <security-domain> elements
10) it's possible to add <background-validation-millis> element with a negative value
--
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, 4 months
[JBoss JIRA] (AS7-3749) Remote JNDI EJB call does not work for method defined as asynchronous
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created AS7-3749:
-------------------------------------
Summary: Remote JNDI EJB call does not work for method defined as asynchronous
Key: AS7-3749
URL: https://issues.jboss.org/browse/AS7-3749
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.CR1b
Reporter: Ondřej Chaloupka
Assignee: John Bailey
EJB was bound by JNDI remote call. An exception is thrown when a called method is defined as asynchronous.
{code}
testRemoteAsynchronousCall(org.jboss.as.test.integration.ejb.async.AsyncMethodTestCase) Time elapsed: 0.245 sec <<< ERROR!
java.lang.IllegalMonitorStateException
at java.lang.Object.notifyAll(Native Method)
at org.jboss.ejb.client.EJBClientInvocationContext.setDiscardResult(EJBClientInvocationContext.java:353)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:150)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy26.asyncMethod(Unknown Source)
at org.jboss.as.test.integration.ejb.async.AsyncMethodTestCase.testRemoteAsynchronousCall(AsyncMethodTestCase.java:260)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270)
at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)
at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)
at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
{code}
Please, check my testcase: https://github.com/ochaloup/jboss-as/blob/JBQA-5271-tests-async-pull/test...
--
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, 4 months
[JBoss JIRA] (AS7-3547) Unable to add infinispan caches in admin console
by Jan Martiska (JIRA)
Jan Martiska created AS7-3547:
---------------------------------
Summary: Unable to add infinispan caches in admin console
Key: AS7-3547
URL: https://issues.jboss.org/browse/AS7-3547
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Jan Martiska
Assignee: Heiko Braun
Priority: Critical
Fix For: 7.1.1.Final
The forms for creation of infinispan caches don't correspond to the correct model and console doesn't provide some required attributes, therefore the creation fails. Only 'local caches' seem to work, all other types are broken.
Distributed cache, replicated cache, invalidation cache:
JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "hibernate"),
("distributed-cache" => "fg")
]): java.util.NoSuchElementException: No child 'mode' exists
--
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, 4 months
[JBoss JIRA] (AS7-3925) Management - :reload operation changes java.naming.factory.url.pkgs system property
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-3925:
-------------------------------------
Summary: Management - :reload operation changes java.naming.factory.url.pkgs system property
Key: AS7-3925
URL: https://issues.jboss.org/browse/AS7-3925
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Dominik Pospisil
Assignee: Brian Stansberry
:reload operation on standalone server changes server's java.naming.factory.url.pkgs system property. After each restart "org.jboss.as.naming.interfaces:" is prepended to the property.
The property content after couple of :reloads
"java.naming.factory.url.pkgs" => "org.jboss.as.naming.interfaces:org.jboss.as.naming.interfaces:org.jboss.as.naming.interfaces:org.jboss.as.naming.interfaces:org.jboss.as.naming.interfaces:org.jboss.as.naming.interfaces:org.jboss.ejb.client.naming"
Steps to reproduce:
1) Start standalone server
2) Connect to it using CLI
3) issue :reload operation:
[standalone@localhost:9999 /] :reload
4) check the property:
[standalone@localhost:9999 /] /core-service=platform-mbean/type=runtime:read-attribute(name="system-properties")
--
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, 4 months
[JBoss JIRA] (AS7-3856) Host Controller path resources do not result in runtime services
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-3856:
-------------------------------------
Summary: Host Controller path resources do not result in runtime services
Key: AS7-3856
URL: https://issues.jboss.org/browse/AS7-3856
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.Final
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Critical
Fix For: 7.1.1.Final
On the HC, the add handler for the host.xml path resources is not installing any runtime services. It just updates the model.
That makes the path configuration data available for use on servers created by the HC, but any services running on the HC itself cannot utilize the path. For example, a security-realm used for the management interfaces that pointed to keystore, trusstore or properties file could not use one of these paths. It could only use the automatically created paths derived from the the HostEnvironment.
--
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, 4 months