[Remoting] - Re: Indefinite hangs on Socket reads using secure bisocket
by ron.sigal＠jboss.com
Hi Zach,
anonymous wrote :
| I tried setting the timeout parameter to something other than 0, like 10000, and when attempting to start up JBoss I get an error that the config does not appear to be correct and the service isn't deployed.
|
What was the message?
anonymous wrote :
| ... is there a way to push down some kind of reasonable timeout all the way down the stack so that we fail more quickly and retry again? Only occasionally does the socket eventually timeout, but even then its about 20 minutes later. Usually it hangs 'forever'.
|
| Heres my remoting config, the only thing different about it other than being straight out of one of the examples is adding of a callback timeout to 30000( 30 seconds ).
|
Note that the "timeout" parameter is global, in the sense that it applies throughout Remoting, client and server. The "callbackTimeout" parameter overrides "timeout", but it only applies to the operation of sending messages from the server to a consumer. Given that your problem is related to a transaction, I'm just guessing that "callbackTimeout" isn't relevent. Note also that the JBossMessaging team is rather committed to a "timeout" value of 0.
Zach, I can help you with the Remoting aspects of the problem, but the JBossMessaging guys would have a better understanding of the big picture. The forum for JBossMessaging users is at http://www.jboss.com/index.html?module=bb&op=viewforum&f=238.
-Ron
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166747#4166747
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166747
17 years, 9 months
[Security & JAAS/JBoss] - Re: Using database for authorization ONLY?
by sfisque
how did you achieve this? i am trying to do a similar thing:
1) attempt authentication via LDAP (using LdapExtLoginModule).
2) if failure, attempt authentication against the database (for "special case users" ) (using DatabaseServerLoginModule)
3) load the roles from the database regardless of which authentication succeeded.
i have the following login-config:
<application-policy name = "dual-auth">
<login-module code = "org.jboss.security.auth.spi.LdapExtLoginModule"
flag = "optional">
<module-option name="baseCtxDN">dc=psr,dc=kryptiq,dc=com</module-option>
<module-option name="bindDN">cn=admin,dc=psr,dc=kryptiq,dc=com</module-option>
<module-option name="bindCredential">secret00/module-option>
<module-option name="baseFilter">(cn={0})</module-option>
<module-option name="rolesCtxDN">dc=psr,dc=kryptiq,dc=com</module-option>
<module-option name="roleAttributeIsDN">false<module-option>
<module-option name="roleAttributeID">role</module-option>
</login-module>
<login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"
flag = "required">
<module-option name = "unauthenticatedIdentity">guest</module-option>
<module-option name = "dsJndiName">java:/jdbc/PSR</module-option>
<module-option name = "principalsQuery">SELECT PASSWORD as PASSWD FROM APP_USER WHERE LOGIN=?</module-option>
<module-option name = "rolesQuery">SELECT APP_PERMISSION.NAME as ROLEID, 'Roles' FROM APP_USER, APP_USER_ROLE, APP_ROLE_PERMISSION, APP_PERMISSION WHERE APP_USER.LOGIN=? AND APP_USER.ID = APP_USER_ROLE.USER_ID AND APP_USER_ROLE.ROLE_ID = APP_ROLE_PERMISSION.ROLE_ID AND APP_ROLE_PERMISSION.PERMISSION_ID = APP_PERMISSION.ID</module-option>
<module-option name="password-stacking">useFirstPass</module-option>
</login-module>
</application-policy>
if i comment out the LDAP part, it works fine for the "special case user" who exists only in the database. if i have both activated, the "special case user" never authenticates to my web-service (it is an ejb3 endpoint exposed via @WebService and @SecurityDomain annotations).
i made sure the "required" and "optional" flags are set and the "password-stacking" option is set. what else am i missing or is this setup not going to achieve what i need? does the "special" case user need to exist in the LDAP directory? i was under the impression that "optional" meant it would fail quietly and defer to later modules.
== stanton
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166746#4166746
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166746
17 years, 9 months
[JBoss Cache: Core Edition] - CacheException while getting object from CacheLoader
by cacheuser
I am writing an object to the cache that I get as a response from a soap call (using apache axis). The object implements Serializable and are auto generated using the wsdl. While reading the object (using get ) back from the cacheloader (jbdc) I get CacheException. As long as the object is in memory there is no problem getting the object but ones it is evicted from the memory and I try to read it back the exception shows
2008-07-24 18:38:00,589 [WARN ] IdentityPro RefID: '30d0d0e3-6fd1-40a3-af07-b811a74634ad' cns.reports.identity.IdentityReport.reportProcess(IdentityReport.java:150) - java.io.StreamCorruptedException (AIBR)
org.jboss.cache.CacheException: java.io.StreamCorruptedException
at org.jboss.cache.invocation.AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:135)
at org.jboss.cache.invocation.AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:64)
at org.jboss.cache.invocation.CacheInvocationDelegate.get(CacheInvocationDelegate.java:387)
at org.jboss.cache.invocation.CacheInvocationDelegate.get(CacheInvocationDelegate.java:392)
at cns.reports.identity.data.test.soap.WsDataServiceSoapStub.bpsReport(WsAccurintServiceSoapStub.java:10020)
at cns.reports.identity.data.test.BpsReport.call(BpsReport.java:87)
at cns.reports.identity.IdentityReport.reportProcess(IdentityReport.java:143)
at cns.reports.identity.IdentityReport.doReport(IdentityReport.java:219)
at cns.reports.features.callable.ReportCall$ReportCallable.call(ReportCall.java:154)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.StreamCorruptedException
at java.io.ObjectInputStream.readTypeString(ObjectInputStream.java:1378)
at java.io.ObjectStreamClass.readNonProxy(ObjectStreamClass.java:634)
at java.io.ObjectInputStream.readClassDescriptor(ObjectInputStream.java:789)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at org.jboss.cache.marshall.MarshalledValue.deserialize(MarshalledValue.java:80)
at org.jboss.cache.marshall.MarshalledValue.get(MarshalledValue.java:147)
at org.jboss.cache.interceptors.MarshalledValueInterceptor.invoke(MarshalledValueInterceptor.java:79)
at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111)
at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:456)
at org.jboss.cache.interceptors.TxInterceptor.handleGetKeyValueMethod(TxInterceptor.java:250)
at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)
at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111)
at org.jboss.cache.interceptors.CacheMgmtInterceptor.handleGetKeyValueMethod(CacheMgmtInterceptor.java:81)
at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)
at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111)
at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:73)
at org.jboss.cache.invocation.AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:123)
... 13 more
My Cache config is as follows (i did not know if there is xml2bbcode so I changed the < to [). I am using jbosscache-core-2.1.1.GA.
[?xml version="1.0" encoding="UTF-8"?]
[!-- ===================================================================== --]
[!-- --]
[!-- Sample JBoss Cache Service Configuration --]
[!-- --]
[!-- ===================================================================== --]
[server]
[!-- ==================================================================== --]
[!-- Defines JBoss Cache configuration --]
[!-- ==================================================================== --]
[!--
[mbean code="org.jboss.cache.TreeCache"
name="jboss.cache:service=TreeCache"]
--]
[mbean code="org.jboss.cache.jmx.CacheJmxWrapper"
name="jboss.ujjwalcache:service=Cache"]
[attribute name="IsolationLevel"]REPEATABLE_READ[/attribute]
[!-- Lock parent before doing node additions/removes --]
[attribute name="LockParentForChildInsertRemove"]true[/attribute]
[!-- Valid modes are LOCAL (default)
REPL_ASYNC
REPL_SYNC
INVALIDATION_ASYNC
INVALIDATION_SYNC --]
[attribute name="CacheMode"]LOCAL[/attribute]
[!-- Name of cluster. Needs to be the same for all JBoss Cache nodes in a
cluster in order to find each other.
--]
[attribute name="ClusterName"]JBossCache-Cluster[/attribute]
[attribute name="ClusterConfig"]
[config]
[!-- UDP: if you have a multihomed machine, set the bind_addr
attribute to the appropriate NIC IP address --]
[!-- UDP: On Windows machines, because of the media sense feature
being broken with multicast (even after disabling media sense)
set the loopback attribute to true --]
[UDP mcast_addr="228.1.2.3" mcast_port="48866"
ip_ttl="64" ip_mcast="true"
mcast_send_buf_size="150000" mcast_recv_buf_size="80000"
ucast_send_buf_size="150000" ucast_recv_buf_size="80000"
loopback="false"/]
[PING timeout="2000" num_initial_members="3"/]
[MERGE2 min_interval="10000" max_interval="20000"/]
[FD shun="true"/]
[FD_SOCK/]
[VERIFY_SUSPECT timeout="1500"/]
[pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800" /]
[UNICAST timeout="600,1200,2400,4800" /]
[pbcast.STABLE desired_avg_gossip="400000"/]
[FC max_credits="2000000" min_threshold="0.10"/]
[FRAG2 frag_size="8192"/]
[pbcast.GMS join_timeout="5000" shun="true" print_local_addr="true"/]
[pbcast.STATE_TRANSFER/]
[/config]
[/attribute]
[!--
The max amount of time (in milliseconds) we wait until the
initial state (ie. the contents of the cache) are retrieved from
existing members in a clustered environment
--]
[attribute name="StateRetrievalTimeout"]20000[/attribute]
[!--
Number of milliseconds to wait until all responses for a
synchronous call have been received.
--]
[attribute name="SyncReplTimeout"]20000[/attribute]
[!-- Max number of milliseconds to wait for a lock acquisition --]
[attribute name="LockAcquisitionTimeout"]15000[/attribute]
[!-- Shutdown hook behavior. Valid choices are: DEFAULT, REGISTER and DONT_REGISTER.
If this element is omitted, DEFAULT is used. --]
[attribute name="ShutdownHookBehavior"]DEFAULT[/attribute]
[!-- Enables or disables lazy unmarshalling. If omitted, the default is that lazy unmarshalling is enabled. --]
[attribute name="UseLazyDeserialization"]true[/attribute]
[!-- Specific eviction policy configurations. This is LRU --]
[attribute name="EvictionPolicyConfig"]
[config]
[attribute name="wakeUpIntervalSeconds"]60[/attribute]
[!-- This defaults to 200000 if not specified --]
[attribute name="eventQueueSize"]200000[/attribute]
[attribute name="policyClass"]org.jboss.cache.eviction.LRUPolicy[/attribute]
[!-- Cache wide default --]
[region name="/mycache"]
[attribute name="maxNodes"]5[/attribute]
[attribute name="maxAgeSeconds"]60[/attribute]
[attribute name="timeToLiveSeconds"]60[/attribute]
[/region]
[/config]
[/attribute]
[!-- Cache Passivation for Tree Cache
On pasivation, The objects are written to the backend store on eviction if CacheLoaderPassivation
is true, otheriwse the objects are persisted.
On activation, the objects are restored in the memory cache and removed from the cache loader
if CacheLoaderPassivation is true, otherwise the objects are only loaded from the cache loader --]
[attribute name="CacheLoaderConfig"]
[config]
[!-- if passivation is true, only the first cache loader is used; the rest are ignored --]
[passivation]false[/passivation]
[preload]/mycache[/preload]
[shared]true[/shared]
[!-- we can now have multiple cache loaders, which get chained --]
[cacheloader]
[class]org.jboss.cache.loader.JDBCCacheLoader[/class]
[!-- same as the old CacheLoaderConfig attribute --]
[properties]
cache.jdbc.table.name=jbosscachenew
cache.jdbc.table.create=true
cache.jdbc.table.drop=false
cache.jdbc.table.primarykey=jbosscachenew_pk
cache.jdbc.fqn.column=fqn
cache.jdbc.fqn.type=varchar(255)
cache.jdbc.node.column=node
cache.jdbc.node.type=blob
cache.jdbc.parent.column=parent
cache.jdbc.driver=com.mysql.jdbc.Driver
cache.jdbc.url=jdbc:mysql://testdb3:3315/GIS_DEV
cache.jdbc.user=gis
cache.jdbc.password=tester
cache.jdbc.sql-concat=concat(1,2)
[/properties]
[!-- whether the cache loader writes are asynchronous --]
[async]false[/async]
[!-- only one cache loader in the chain may set fetchPersistentState to true.
An exception is thrown if more than one cache loader sets this to true. --]
[fetchPersistentState]true[/fetchPersistentState]
[!-- determines whether this cache loader ignores writes - defaults to false. --]
[ignoreModifications]false[/ignoreModifications]
[!-- if set to true, purges the contents of this cache loader when the cache starts up.
Defaults to false. --]
[purgeOnStartup]false[/purgeOnStartup]
[/cacheloader]
[/config]
[/attribute]
[/mbean]
[/server]
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166744#4166744
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166744
17 years, 9 months
[Remoting] - Re: sending Streams using POJOS
by ron.sigal＠jboss.com
Hi Greg,
First of all, thank you for your interest in Remoting.
The fact is that the 2.x family of Remoting releases is reaching the end of its development life. The next major Remoting release should be 3.0.0.GA, and it's quite likely that there will never be a 2.4.1.
The good news is that Remoting 3 will support a flexible and symmetric streaming model.
We're now directing all of our resources to Remoting 3, so I can't really offer the possibility of diverting time to Remoting 2.
Of course, we would certainly consider the possibility of accepting contributions, if you have the development resources. By the way, you might want to check out the "remoting streams" thread in the "Design of JBoss Remoting, Unified Invokers" forum at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101558#4101558.
I hope we won't lose you as a Remoting user, but, well, reality is formidable.
-Ron
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166741#4166741
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166741
17 years, 9 months
[Installation, Configuration & DEPLOYMENT] - JBoss ESB Performance/optimal configurations
by Busrider2008
Been working with prototypes and some quickstarts from the JBoss ESB 4.3 GA application server and I have been a little confused with all the options of JBossMQ, JBossMessaging, using ActiveMQ with the ESB, and using straight vanilla JMS outside the bus.
Running some initial tests for performance on a series of actions in my test service (display message, Smooks transformation, XML2 Pojo, and dislaynewmessage) just so I can see where some bottlenecks might be...I am seeing that using the ESB with ActiveMQ as the JMS provider looks to be quickest per action.
The monitoring console available on localhost:8080 shows each ESB and has success, failure threads, and processing time. First question, the numbers for processing time are in what unit of time?
Second question, what is the suggested optimal configuration using the ESB? Maxthreads per JMS Listener? I have not seen a good thread yet on numbers people are seeing playing with different providers and libraries.
I will continue to profile the time for processing using JProbe with filtering by particular methods, but any suggestions would be great in the meantime.
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166740#4166740
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166740
17 years, 9 months
[JBoss jBPM] - org.hibernate.HibernateException: null index column for coll
by clandestino_bgd
Hi,
to be honest, I do not know why i am posting question on this forum, since I am the one who only answers on them, and I really do not think I will have an answer on this one :)
It seems, I feel really desperate :(
So the problem is the following:
I am using Jbpm-jpdl-3.2.3, hibernate 3.2.5, latest spring modules and basically use JBPM with Spring, passing the existing sessionFactory to jbpmContext.
Everything works fine within JUnit test cases (I extend AbstractTransactionalDataSourceSpringContextTests and at the end of each test method, I call setComplete() in order to commit in DB instead of default rollback.
But the same methods. e.g deploy/undeployProcessDefinition with the same process definition do not work under tomcat.
For example: method undeployProcessDefinition results in
| org.hibernate.HibernateException: null index column for collection: org.jbpm.graph.def.ProcessDefinition.nodes
|
And, by looking in DB, after executed method deployProcessDefinition, it is not wonder, since the field:
NODECOLLECTIONINDEX_ in JBPM_NODE table is NULL for every node record.
Just to note, when invoked the same method within JUnit the NODECOLLECTIONINDEX_ is NOT NULL.
I read user manual several times, along with the most JIRA issues, (no wonder since I am working with JBPM very long time).
Can somebody, possibly can have a clue what can be the reason for this?
Btw, I read Bernd's JIRA issue about the same exception when using JtaPersistenceServicefactory, but then he said that it was because of the wrong conf.
It is definitely not my case, at least extensive debug messages confirm that everything is initialised properly. I even compared the initialisation code in both cases (junit and tomcat) and everything looks just the same and without any problem.
NOTE: since I am using JBPM with spring and within a big enterprise application, I am not able to send short Unit test, that someone can try locally.
Thanks a lot for every hint.
Milan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166738#4166738
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166738
17 years, 9 months
[Installation, Configuration & DEPLOYMENT] - Re: Unable to stop jboss server
by PeterJ
OK, jbossas is not starting. Or actually, none of the services that matter, such as HTTP, started (is what I am guessing). Please post the entire console output after you enter ./run.sh.
What configuration changes did you make? I know you changed the log4j.xml file because there is no ORI appender in the file that comes with JBossAS. Also, did you change the login-config.xml file? It would appear that whatever editor you used to change it added unicode byte ordering characters to the start of the file (that is the most common reason for the error you are getting).
Please post any configuration files you changed (posting only the lines you added or changed is sufficient). Remember to enclose your XML text in UBBCode "code" tags - you can do this by selecting the XML text and clicking the Code button above the editor window. Also, click the Preview button to ensure that the formatting is correct and the XML text shows up before posting.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166737#4166737
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166737
17 years, 9 months