[JBoss JIRA] (JBAS-9476) Weld integration and multi web application in ear doesn't work
by Wojciech Oczkowski (JIRA)
Wojciech Oczkowski created JBAS-9476:
----------------------------------------
Summary: Weld integration and multi web application in ear doesn't work
Key: JBAS-9476
URL: https://issues.jboss.org/browse/JBAS-9476
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Weld/CDI
Affects Versions: 6.1.0
Environment: windows jvm 1.6_u31 jboss 6.1.0 final
Reporter: Wojciech Oczkowski
Assignee: Marius Bogoevici
There is a problem with ear's which contains multiple war applications and weld integration.
In that kind of enviroment Weld integration finds bda's like ear, and war's and starts a single weld container for them, but it's imposible to work becaouse of war's classloader isolation.
It's seems like archive discovery is inconsistent with classloading mechanizm.
--
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, 1 month
[JBoss JIRA] (AS7-3811) Implement a timeout on EJB client invocations
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3811:
-----------------------------------
Summary: Implement a timeout on EJB client invocations
Key: AS7-3811
URL: https://issues.jboss.org/browse/AS7-3811
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Priority: Critical
Fix For: 7.1.1.Final
IMHO a client must support a timeout. Very often when things go wrong the clients get stuck indefinitely.
Maybe this problem go even deeper, something on the server failed but didnt reply to the client. This is often encoutered during failover undeploy test (50 of 200 clients got stuck :-) ).
{noformat}
"Runner - 16" daemon prio=10 tid=0x00007fb7a0025000 nid=0x4d7a in Object.wait() [0x00007fb78b3f2000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:330)
- locked <0x00000006c013ae50> (a java.lang.Object)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:140)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy0.getSerialAndIncrement(Unknown Source)
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
at java.lang.Thread.run(Thread.java:662)
{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
14 years, 1 month
[JBoss JIRA] (AS7-3986) Attribute mode unknown for ISPN cache
by Heiko Rupp (JIRA)
Heiko Rupp created AS7-3986:
-------------------------------
Summary: Attribute mode unknown for ISPN cache
Key: AS7-3986
URL: https://issues.jboss.org/browse/AS7-3986
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.Final
Reporter: Heiko Rupp
Assignee: Brian Stansberry
Domain-API says that the attribute 'mode' for a cache does not exist, while it clearly is shown on a :read-resource operation.
snert:~/downloads/jboss-eap-6.0 hrupp$ bin/jboss-cli.sh --connect
[standalone@localhost:9999 /] cd /subsystem=infinispan/cache-container=myContainer/local-cache=aCache
[standalone@localhost:9999 local-cache=aCache] :read-resource
read-resource read-resource-description
[standalone@localhost:9999 local-cache=aCache] :read-resource
{
"outcome" => "success",
"result" => {
"batching" => undefined,
"eviction" => undefined,
"expiration" => undefined,
"file-store" => undefined,
"indexing" => undefined,
"jdbc-store" => undefined,
"jndi-name" => undefined,
"locking" => undefined,
"mode" => "LOCAL",
"name" => "aCache",
"remote-store" => undefined,
"start" => undefined,
"store" => undefined,
"transaction" => undefined
}
}
[standalone@localhost:9999 local-cache=aCache] :write-attribute(name=mode,value=SYNC)
{
"outcome" => "failed",
"failure-description" => "JBAS014792: Unknown attribute mode",
"rolled-back" => true
}
same applies for other listed attributes like jdbc-store.
--
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, 1 month
[JBoss JIRA] (AS7-4120) Update jbosgi bundle versions to use Final qualifier
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-4120:
-----------------------------------
Summary: Update jbosgi bundle versions to use Final qualifier
Key: AS7-4120
URL: https://issues.jboss.org/browse/AS7-4120
Project: Application Server 7
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.1.1.Final
{code}
[tdiesler@tdvaio modules]$ find -name *.jar | grep -v Final | grep -v GA | grep -v FINAL | grep jbosgi
./org/jboss/osgi/repository/main/jbosgi-repository-api-1.0.5.jar
./org/jboss/osgi/repository/main/jbosgi-repository-core-1.0.5.jar
[tdiesler@tdvaio bundles]$ find -name *.jar | grep -v Final | grep -v GA | grep -v FINAL | grep jboss
./org/jboss/osgi/logging/main/jboss-osgi-logging-1.0.0.jar
{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
14 years, 1 month
[JBoss JIRA] (AS7-4124) Character Set Filter stops working in 7.1.1 looks like a regression
by Cody Lerum (JIRA)
Cody Lerum created AS7-4124:
-------------------------------
Summary: Character Set Filter stops working in 7.1.1 looks like a regression
Key: AS7-4124
URL: https://issues.jboss.org/browse/AS7-4124
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Reporter: Cody Lerum
This is a regression from 7.1.0.Final
Using the filter at http://code.google.com/p/webutilities/wiki/CharacterEncodingFilter I am able to force my charset to UTF-8 for requests but the filter has no effect in 7.1.1.Final
It does work fine in 7.1.0.Final
{code}
<filter>
<filter-name>forceUTF8CharSet</filter-name>
<filter-class>com.googlecode.webutilities.filters.CharacterEncodingFilter</filter-class>
<init-param>
<param-name>encoding</param-name>
<param-value>UTF-8</param-value>
</init-param>
<init-param>
<param-name>force</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>ignoreURLPattern</param-name>
<param-value>.*\.(png|jpg|gif)|.*/image?/.*</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>forceUTF8CharSet</filter-name>
<url-pattern>*</url-pattern>
</filter-mapping>
{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
14 years, 1 month
[JBoss JIRA] (AS7-4125) ServerEnvironment.getFilesFromProperties reads path.separator from the wrong place
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-4125:
-------------------------------------
Summary: ServerEnvironment.getFilesFromProperties reads path.separator from the wrong place
Key: AS7-4125
URL: https://issues.jboss.org/browse/AS7-4125
Project: Application Server 7
Issue Type: Bug
Components: Server
Reporter: Brian Stansberry
Assignee: Jason Greene
String sep = props.getProperty("path.separator");
should be
String sep = SecurityActions.getSystemProperty("path.separator");
The passed in "props" is not the system property map in a managed domain, so this incorrect call will lead to an NPE
[Server:server-two] java.lang.NullPointerException
[Server:server-two] at java.util.regex.Pattern.quote(Pattern.java:1089)
[Server:server-two] at org.jboss.as.server.ServerEnvironment.getFilesFromProperty(ServerEnvironment.java:1018)
[Server:server-two] at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:320)
[Server:server-two] at org.jboss.as.server.ServerStartTask.run(ServerStartTask.java:117)
[Server:server-two] at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:129)
[Server:server-two] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[Server:server-two] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
[Server:server-two] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[Server:server-two] at java.lang.reflect.Method.invoke(Method.java:600)
[Server:server-two] at org.jboss.modules.Module.run(Module.java:260)
[Server:server-two] at org.jboss.modules.Main.main(Main.java:291)
--
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, 1 month
[JBoss JIRA] (AS7-4117) Intermittent failure in StrictMaxUnitTestCase.testMultiThread()
by Ondrej Zizka (JIRA)
Ondrej Zizka created AS7-4117:
---------------------------------
Summary: Intermittent failure in StrictMaxUnitTestCase.testMultiThread()
Key: AS7-4117
URL: https://issues.jboss.org/browse/AS7-4117
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.1.1.Final
Reporter: Ondrej Zizka
Assignee: Andrew Rubinger
Priority: Minor
Fix For: 7.1.2.Final
{code}
junit.framework.AssertionFailedError: expected:<10> but was:<9>
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.failNotEquals(Assert.java:287)
at junit.framework.Assert.assertEquals(Assert.java:67)
at junit.framework.Assert.assertEquals(Assert.java:199)
at junit.framework.Assert.assertEquals(Assert.java:205)
at org.jboss.as.ejb3.pool.strictmax.StrictMaxUnitTestCase.testMultiThread(StrictMaxUnitTestCase.java:119)
{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
14 years, 1 month