[JBoss JIRA] Created: (JBCACHE-1150) @Serializable triggers CCE in detach()
by Jason T. Greene (JIRA)
@Serializable triggers CCE in detach()
--------------------------------------
Key: JBCACHE-1150
URL: http://jira.jboss.com/jira/browse/JBCACHE-1150
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Jason T. Greene
Assigned To: Jason T. Greene
Fix For: 2.0.0.GA
Code:
_cache.start();
SystemW coreSystem = new SystemW();
coreSystem.setDo(new SystemS(100, 123, "core system", "CORE")); // <- @Serializable
_cache.attach("/systems/100", coreSystem);
_cache.attach("/systems/100", new SystemW()); // <- throws
whereas SystemW is advised and has a @org.jboss.cache.pojo.annotation.Serializable field _do. Something like this:
Code:
public class SystemW {
@org.jboss.cache.pojo.annotation.Serializable
private SystemS _do;
public void setDo(SystemS inDo) {
_do = inDo;
}
}
Stack trace:
Code:
java.lang.ClassCastException: ch.steria.jbcache.aopobjects.SystemS
at org.jboss.cache.pojo.impl.InternalHelper.getPojoReference(InternalHelper.java:46)
at org.jboss.cache.pojo.impl.InternalHelper.getPojo(InternalHelper.java:181)
at org.jboss.cache.pojo.impl.PojoCacheDelegate.getObject(PojoCacheDelegate.java:81)
at org.jboss.cache.pojo.impl.PojoCacheImpl.getObject(PojoCacheImpl.java:203)
at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$detach$aop(PojoC
acheImpl.java:150)
at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
at org.jboss.cache.pojo.impl.AdvisedPojoHandler.remove(AdvisedPojoHandler.java:215)
at org.jboss.cache.pojo.impl.PojoCacheDelegate.removeObject(PojoCacheDelegate.java:276)
at org.jboss.cache.pojo.impl.PojoCacheImpl.removeObject(PojoCacheImpl.java:170)
at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$detach$aop(PojoC
acheImpl.java:153)
at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:136)
at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoC
acheImpl.java:101)
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java)
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:93)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 12 months
[JBoss JIRA] Created: (JBCACHE-725) Reduce the amount of INFO logging
by Dimitris Andreadis (JIRA)
Reduce the amount of INFO logging
---------------------------------
Key: JBCACHE-725
URL: http://jira.jboss.com/jira/browse/JBCACHE-725
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 1.4.0
Reporter: Dimitris Andreadis
Assigned To: Manik Surtani
I've posted this to jboss-dev, and didn't get a reply, so:
No big deal, but you guys really need to reduce the amount of INFO logging that goes to the console.
This is from HEAD but Branch_4_x is not any better. Those should really be DEBUG level:
http://docs.jboss.org/process-guide/en/html/logging.html
(and why JGroups need to do that STDOUT printout anyway?)
14:40:24,374 INFO [TreeCache] setting cluster properties from xml to:
UDP(down_
thread=false;enable_bundling=true;ip_ttl=2;loopback=false;max_bundle_siz
e=64000;
max_bundle_timeout=30;mcast_addr=230.1.2.7;mcast_port=45577;mcast_recv_b
uf_size=
25000000;mcast_send_buf_size=640000;ucast_recv_buf_size=20000000;ucast_s
end_buf_
size=640000;up_thread=false;use_incoming_packet_handler=true;use_outgoin
g_packet
_handler=false):PING(down_thread=false;num_initial_members=3;timeout=200
0;up_thr
ead=false):MERGE2(down_thread=false;max_interval=100000;min_interval=200
00;up_th
read=false):FD(down_thread=false;max_tries=5;shun=true;timeout=2500;up_t
hread=fa
lse):VERIFY_SUSPECT(down_thread=false;timeout=1500;up_thread=false):pbca
st.NAKAC
K(discard_delivered_msgs=true;down_thread=false;gc_lag=50;max_xmit_size=
60000;re
transmit_timeout=100,200,300,600,1200,2400,4800;up_thread=false;use_mcas
t_xmit=f
alse):UNICAST(down_thread=false;timeout=300,600,1200,2400,3600;up_thread
=false):
pbcast.STABLE(desired_avg_gossip=50000;down_thread=false;max_bytes=21000
00;stabi
lity_delay=1000;up_thread=false):pbcast.GMS(down_thread=false;join_retry
_timeout
=2000;join_timeout=3000;print_local_addr=true;shun=true;up_thread=false)
:FC(down
_thread=false;max_credits=10000000;min_threshold=0.20;up_thread=false):F
RAG2(dow
n_thread=false;frag_size=60000;up_thread=false):pbcast.STATE_TRANSFER(do
wn_threa
d=false;up_thread=false)
14:40:24,434 INFO [BuddyManager] Using buddy communication timeout of 2000 mill is
14:40:24,454 INFO [TreeCache] Not using an EvictionPolicy
14:40:24,504 INFO [InterceptorChainFactory] interceptor chain is:
class org.jboss.cache.interceptors.CallInterceptor
class org.jboss.cache.interceptors.PessimisticLockInterceptor
class org.jboss.cache.interceptors.DataGravitatorInterceptor
class org.jboss.cache.interceptors.UnlockInterceptor
class org.jboss.cache.interceptors.ReplicationInterceptor
class org.jboss.cache.interceptors.TxInterceptor
class org.jboss.cache.interceptors.CacheMgmtInterceptor
14:40:24,524 INFO [TreeCache] cache mode is REPL_ASYNC
14:40:24,815 WARN [JChannel] option GET_STATE_EVENTS has been deprecated (it is always true now); this option is ignored
14:40:25,035 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.0.20:3384
-------------------------------------------------------
14:40:27,088 INFO [TreeCache] viewAccepted() for Tomcat-Cluster:
[192.168.0.20:
3384|0] [192.168.0.20:3384]
14:40:27,088 INFO [TreeCache] processNewView(): [192.168.0.20:3384|0] [192.168.
0.20:3384]
14:40:27,138 INFO [TreeCache] processNewView(): [192.168.0.20:3384|0] [192.168.
0.20:3384]
14:40:27,138 INFO [TreeCache] TreeCache local address is
192.168.0.20:3384
14:40:27,138 INFO [BuddyManager] Instance 192.168.0.20:3384 broadcasting member ship in buddy pool default to recipients null
14:40:27,138 WARN [NextMemberBuddyLocator] Expected to look for 1 buddies but c ould only find 0 suitable candidates - trying with colocated buddies as well.
14:40:27,138 WARN [NextMemberBuddyLocator] Expected to look for 1 buddies but c ould only find 0 suitable candidates - trying again, ignoring buddy pool hints.
14:40:27,138 WARN [NextMemberBuddyLocator] Expected to look for 1 buddies but c ould only find 0 suitable candidates - trying with colocated buddies as well.
14:40:27,138 WARN [NextMemberBuddyLocator] Expected to look for 1 buddies but c ould only find 0 suitable candidates!
14:40:27,168 INFO [TreeCache] parseConfig(): PojoCacheConfig is empty ...
14:40:34,609 INFO [TreeCache] setting cluster properties from xml to:
UDP(ip_mc
ast=true;ip_ttl=64;loopback=false;mcast_addr=228.1.2.3;mcast_port=45551;
mcast_re
cv_buf_size=80000;mcast_send_buf_size=150000;ucast_recv_buf_size=80000;u
cast_sen
d_buf_size=150000):PING(down_thread=false;num_initial_members=3;timeout=
2000;up_
thread=false):MERGE2(max_interval=20000;min_interval=10000):FD(down_thre
ad=false
;shun=true;up_thread=false):VERIFY_SUSPECT(down_thread=false;timeout=150
0;up_thr
ead=false):pbcast.NAKACK(down_thread=false;gc_lag=50;max_xmit_size=8192;
retransm
it_timeout=600,1200,2400,4800;up_thread=false):UNICAST(down_thread=false
;timeout
=600,1200,2400):pbcast.STABLE(desired_avg_gossip=20000;down_thread=false
;up_thre
ad=false):FRAG(down_thread=false;frag_size=8192;up_thread=false):pbcast.
GMS(join
_retry_timeout=2000;join_timeout=5000;print_local_addr=true;shun=true):p
bcast.ST
ATE_TRANSFER(down_thread=false;up_thread=false)
14:40:34,639 INFO [TreeCache] setEvictionPolicyConfig(): [config: null]
14:40:34,639 WARN [TreeCache] No transaction manager lookup class has been defi ned. Transactions cannot be used
14:40:34,669 WARN [TreeCache] Using deprecated configuration element 'EvictionP olicyProvider'. This is only provided for 1.2.x backward compatibility and may disappear in future releases.
14:40:34,709 INFO [InterceptorChainFactory] interceptor chain is:
class org.jboss.cache.interceptors.CallInterceptor
class org.jboss.cache.interceptors.EvictionInterceptor
class org.jboss.cache.interceptors.PessimisticLockInterceptor
class org.jboss.cache.interceptors.ActivationInterceptor
class org.jboss.cache.interceptors.UnlockInterceptor
class org.jboss.cache.interceptors.ReplicationInterceptor
class org.jboss.cache.interceptors.PassivationInterceptor
class org.jboss.cache.interceptors.TxInterceptor
class org.jboss.cache.interceptors.CacheMgmtInterceptor
14:40:34,759 INFO [TreeCache] cache mode is REPL_ASYNC
14:40:34,779 WARN [JChannel] option GET_STATE_EVENTS has been deprecated (it is always true now); this option is ignored
14:40:34,799 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.0.20:3391
-------------------------------------------------------
14:40:36,822 INFO [TreeCache] viewAccepted() for SFSB-Cache:
[192.168.0.20:3391
|0] [192.168.0.20:3391]
14:40:36,822 INFO [TreeCache] processNewView(): [192.168.0.20:3391|0] [192.168.
0.20:3391]
14:40:36,842 INFO [TreeCache] processNewView(): [192.168.0.20:3391|0] [192.168.
0.20:3391]
14:40:36,852 INFO [TreeCache] TreeCache local address is
192.168.0.20:3391
14:40:36,852 INFO [TreeCache] transferred state is null (may be first member in
cluster)
14:40:36,852 INFO [TreeCache] State could not be retrieved (we are the first me mber in group)
14:40:36,862 INFO [CacheLoaderManager] preloading transient state from cache lo ader org.jboss.cache.loader.FileCacheLoader@17d8769
14:40:36,872 INFO [CacheLoaderManager] preloading transient state from cache lo ader was successful (in 10 milliseconds)
14:40:36,872 INFO [RegionManager] Starting eviction timer
14:40:37,002 INFO [TreeCache] setting cluster properties from xml to:
UDP(ip_mc
ast=true;ip_ttl=2;loopback=false;mcast_addr=228.1.2.3;mcast_port=43333;m
cast_rec
v_buf_size=80000;mcast_send_buf_size=150000;ucast_recv_buf_size=80000;uc
ast_send
_buf_size=150000):PING(down_thread=false;num_initial_members=3;timeout=2
000;up_t
hread=false):MERGE2(max_interval=20000;min_interval=10000):FD(down_threa
d=true;s
hun=true;up_thread=true):VERIFY_SUSPECT(down_thread=false;timeout=1500;u
p_thread
=false):pbcast.NAKACK(down_thread=false;gc_lag=50;max_xmit_size=8192;ret
ransmit_
timeout=600,1200,2400,4800;up_thread=false):UNICAST(down_thread=false;mi
n_thresh
old=10;timeout=600,1200,2400;window_size=100):pbcast.STABLE(desired_avg_
gossip=2
0000;down_thread=false;up_thread=false):FRAG(down_thread=false;frag_size
=8192;up
_thread=false):pbcast.GMS(join_retry_timeout=2000;join_timeout=5000;prin
t_local_
addr=true;shun=true):pbcast.STATE_TRANSFER(down_thread=false;up_thread=f
alse)
14:40:37,022 INFO [TreeCache] setEvictionPolicyConfig(): [config: null]
14:40:37,032 WARN [TreeCache] Using deprecated configuration element 'EvictionP olicyProvider'. This is only provided for 1.2.x backward compatibility and may disappear in future releases.
14:40:37,032 INFO [InterceptorChainFactory] interceptor chain is:
class org.jboss.cache.interceptors.CallInterceptor
class org.jboss.cache.interceptors.EvictionInterceptor
class org.jboss.cache.interceptors.PessimisticLockInterceptor
class org.jboss.cache.interceptors.UnlockInterceptor
class org.jboss.cache.interceptors.ReplicationInterceptor
class org.jboss.cache.interceptors.TxInterceptor
class org.jboss.cache.interceptors.CacheMgmtInterceptor
14:40:37,102 INFO [TreeCache] cache mode is REPL_SYNC
14:40:37,122 ERROR [UNICAST] window_size is deprecated and will be ignored
14:40:37,122 ERROR [UNICAST] min_threshold is deprecated and will be ignored
14:40:37,122 WARN [JChannel] option GET_STATE_EVENTS has been deprecated (it is always true now); this option is ignored
14:40:37,142 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.0.20:3394
-------------------------------------------------------
14:40:39,185 INFO [TreeCache] viewAccepted() for EJB3-entity-cache:
[192.168.0.
20:3394|0] [192.168.0.20:3394]
14:40:39,185 INFO [TreeCache] processNewView(): [192.168.0.20:3394|0] [192.168.
0.20:3394]
14:40:39,185 INFO [TreeCache] processNewView(): [192.168.0.20:3394|0] [192.168.
0.20:3394]
14:40:39,185 INFO [TreeCache] TreeCache local address is
192.168.0.20:3394
14:40:39,185 INFO [TreeCache] transferred state is null (may be first member in
cluster)
14:40:39,185 INFO [TreeCache] State could not be retrieved (we are the first me mber in group)
14:40:39,185 INFO [RegionManager] Starting eviction timer
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 12 months
[JBoss JIRA] Commented: (EJBTHREE-281) Allow a default <security-domain> element in jboss.xml
by Abhishek Prakash (JIRA)
[ http://jira.jboss.com/jira/browse/EJBTHREE-281?page=comments#action_12370243 ]
Abhishek Prakash commented on EJBTHREE-281:
-------------------------------------------
This was actually a bug. Releases 4.2.0 onwards have the fix for the bug.
> Allow a default <security-domain> element in jboss.xml
> ------------------------------------------------------
>
> Key: EJBTHREE-281
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-281
> Project: EJB 3.0
> Issue Type: Feature Request
> Affects Versions: EJB 3.0 RC3
> Environment: - Jboss 4.0.3RC1, installed with the installer using the all configuration
> - Windows 2000
> Reporter: Eyal Lupu
> Assigned To: William DeCoste
> Fix For: EJB 3.0 RC3
>
>
> I'm using the DatabaseServerLoginModule to map principal and roles (client uses ClientLoginModule)
> I have a one SLSB with the following security definitions:
> @SecurityDomain("testApp-server")
> public class....... {
> @RolesAllowed("admin")
> public int add(int a, int b) {...}
> }
> Everything works fine - but I want to move the security domain's declaration to the DD:
> I removed the '@SecurityDomain' annotation and added a
> <security-domain>java:/jaas/testApp-server</security-domain> element to my jboss-app.xml file.
> It doesn't work - everyone can access my "secured" method.
> Additional tests I did:
> A. I know that the jboss-app.xml is being loaded since I added a service module (SAR) into it - and it is being loaded
> B. I tried to replace the name of the security domain with an none-exist security domain and again
> nothing happends (not even an error message)
> C. I tried both static login configuration (server/conf/login-config.xml) and a dynamic one (using the
> DynamicLoginConfig) - yet, nothing happends
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 12 months
[JBoss JIRA] Updated: (JGRP-176) Asynchronous dispatching of requests in RequestCorrelator
by Bela Ban (JIRA)
[ http://jira.jboss.com/jira/browse/JGRP-176?page=all ]
Bela Ban updated JGRP-176:
--------------------------
Fix Version/s: 2.x
(was: 2.6)
Moved to 2.x (unassigned), as JBCACHE-326 was pushed into 3.0. Most likely, we'll close this one when reviewing the 2.x issues...
> Asynchronous dispatching of requests in RequestCorrelator
> ---------------------------------------------------------
>
> Key: JGRP-176
> URL: http://jira.jboss.com/jira/browse/JGRP-176
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 2.2.9.1, 2.2.9, 2.2.8
> Reporter: Bela Ban
> Assigned To: Vladimir Blagojevic
> Fix For: 2.x
>
>
> In RequestCorrelator.handleRequest(), we call handle(Message) on the registered RequestHandler (RpcDispatcher in the case of JBossCache).
> Because of http://jira.jboss.com/jira/browse/JBCACHE-326, we need to provide an asynchronous way of calling handle(Message), which doesn't need to wait for the call to return, but is notified later when the response is ready (or not at all if the call is asynchronous).
> This could be implemented using a subinterface of RequestHandler (e.g. AsyncRequestHandler), and a *future*.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years