[JBoss Seam] - Re: Tutorial Feedback
by dbatcn
As somebody who is also working with Seam without having previously used JSF/EJB3, I have another observation: I am only very slowly perceiving the boundaries of what's done by Seam vs. Facelets vs. JSF vs. Persistence API vs. EJB3, as well as conversations and a slightly different EL. Sometimes it takes a bit of sleuthing to figure out which piece(s) (if any) provides desired functionality. It's even a bit more difficult since so many things seem to happen by "magic" because 1. there is so much going on behind the scenes, 2. it's taking a little while to get used to the annotations, and 3. sometimes there are conflicting bits of documentation (e.g. meaning of "$" and "#" in EL). I am a fan of declarative programming and DRY though and do think that it's very cool that a lot of functionality is getting implemented with relatively little code to maintain.
I can see that some of the problem comes from the fact that Seam can work with many different stacks of packages and that that is in fact a _good_ thing. I've picked JSF, facelets, and EJB3 for my new project based largely on the recommendations I've seen from Gavin.
Before I started any coding, I did go through pretty much the complete O'Reilly EBJ3 book by Bill Burke (ISBN 0-596-00978-X, and no, I don't have a financial interest in it) and that has helped a great deal. I keep the Seam reference up in Acrobat constantly. I am also googling a lot.
I do know that these manuals are a pain in the *** to write and am very grateful that a lot of serious work has obviously gone into it. I suppose that the answer that I just need to become more familiar with all the various technologies may well be legitimate. I'm sorry that I don't have a constructive alternative but perhaps people who are more immersed in these technologies might see a way to make it clearer to newbies. I expect that the real answer is that when various JSRs are finally adopted, there will be an accepted standard Java EE way of doing this and that this is just the price of using stuff on the bleeding edge. Sigh.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960841#3960841
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960841
19 years, 9 months
[JBossCache] - Re: PojoCache Weblogic 91 and JConsole issue!!
by sphinxmember
Just tried that , here is my observations.
1. There is no classcast exception in the jvm running stand alone cache client
2. The Jconsole mbean view of the treecache , under the attibutes tab I see the following attributes as red.
Name Value
a. Instance Unavailable (in red font on hovering the mouse it shows the following exception ...
//java.rmi.unmarshalexception error unmarshalling return , nested exception is java.io.WriteAbortedException, writing aborted; java.io.NotSerializableException; org.jboss.cache.TreeCache
b. Interceptors
c. members
3. when I click on the operation tab the jconsole throws following exceptions
Error setting Operation panel :org.jboss.cache.TreeCacheListener
Error setting Operation panel :org.jboss.cache.TreeCacheListener
Error setting Operation panel :org.jboss.cache.Fqn
Error setting Operation panel :org.jboss.cache.Fqn
Error setting Operation panel :org.jboss.cache.Fqn
Error setting Operation panel :org.jboss.cache.Fqn
Error setting Operation panel :org.jboss.cache.Fqn
Error setting Operation panel :org.jboss.cache.GlobalTransaction
Error setting Operation panel :org.jboss.cache.GlobalTransaction
Error setting Operation panel :org.jboss.cache.GlobalTransaction
Error setting Operation panel :org.jboss.cache.GlobalTransaction
I am using following java version
C:\Documents and Settings\shgoe>java -version
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)
Jboss cache stand alone client code (Sleep is introduced just for it to wait for the jconsole to connect)
public class SampleTreeCache {
public static void main (String[] a)
{
SampleTreeCache sampleTreeCache = new SampleTreeCache();
TreeCache cache1 = null;
try
{
cache1 = sampleTreeCache.createCache();
cache1.put("/jboss-cache-manager", "Sample Cache Entry", "This is a sample");
Thread.currentThread().sleep(600000);
}catch(Exception e)
{
e.printStackTrace();
}
}
private TreeCache createCache() throws Exception
{
TreeCache cache = new TreeCache();
PropertyConfigurator config = new PropertyConfigurator();
config.configure(cache, "invalidationSync-service.xml");
System.out.println("Tree cache configured with META-INF/invalidationSync-service.xml ");
cache.startService();
return cache;
}
sample configuration file
<?xml version="1.0" encoding="UTF-8"?>
|
| <!-- ===================================================================== -->
| <!-- -->
| <!-- Sample TreeCache Service Configuration -->
| <!-- -->
| <!-- ===================================================================== -->
|
| <server>
|
| <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar"/>
|
|
| <!-- ==================================================================== -->
| <!-- Defines TreeCache configuration -->
| <!-- ==================================================================== -->
|
| <mbean code="org.jboss.cache.TreeCache"
| name="jboss.cache:service=TreeCache">
|
| <depends>jboss:service=Naming</depends>
| <depends>jboss:service=TransactionManager</depends>
|
| <!--
| Configure the TransactionManager
| -->
| <!--attribute name="TransactionManagerLookupClass">org.jboss.cache.DummyTransactionManagerLookup</attribute-->
|
| <!--
| Isolation level : SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
| -->
| <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
|
| <!--
| Valid modes are LOCAL
| REPL_ASYNC
| REPL_SYNC
| INVALIDATION_ASYNC
| INVALIDATION_SYNC
| -->
| <attribute name="CacheMode">INVALIDATION_SYNC</attribute>
|
| <!--
| Just used for async repl: use a replication queue
| -->
| <attribute name="UseReplQueue">false</attribute>
|
| <!--
| Replication interval for replication queue (in ms)
| -->
| <attribute name="ReplQueueInterval">0</attribute>
|
| <!--
| Max number of elements which trigger replication
| -->
| <attribute name="ReplQueueMaxElements">0</attribute>
|
| <!-- Name of cluster. Needs to be the same for all clusters, in order
| to find each other
| -->
| <attribute name="ClusterName">TreeCache-Cluster</attribute>
|
| <!-- JGroups protocol stack properties. Can also be a URL,
| e.g. file:/home/bela/default.xml
| <attribute name="ClusterProperties"></attribute>
| -->
|
| <attribute name="ClusterConfig">
| <config>
| <!-- UDP: if you have a multihomed machine,
| set the bind_addr attribute to the appropriate NIC IP address, e.g bind_addr="192.168.0.2"
| -->
| <!-- 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"
| up_thread="false" down_thread="false"/>
| <MERGE2 min_interval="10000" max_interval="20000"/>
| <!-- <FD shun="true" up_thread="true" down_thread="true" />-->
| <FD_SOCK/>
| <VERIFY_SUSPECT timeout="1500"
| up_thread="false" down_thread="false"/>
| <pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800"
| max_xmit_size="8192" up_thread="false" down_thread="false"/>
| <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10"
| down_thread="false"/>
| <pbcast.STABLE desired_avg_gossip="20000"
| up_thread="false" down_thread="false"/>
| <FRAG frag_size="8192"
| down_thread="false" up_thread="false"/>
| <pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
| shun="true" print_local_addr="true"/>
| <pbcast.STATE_TRANSFER up_thread="true" down_thread="true"/>
| </config>
| </attribute>
|
|
| <!--
| Whether or not to fetch state on joining a cluster
| NOTE this used to be called FetchStateOnStartup and has been renamed to be more descriptive.
| -->
| <attribute name="FetchInMemoryState">true</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="InitialStateRetrievalTimeout">15000</attribute>
|
| <!--
| Number of milliseconds to wait until all responses for a
| synchronous call have been received.
| -->
| <attribute name="SyncReplTimeout">15000</attribute>
|
| <!-- Max number of milliseconds to wait for a lock acquisition -->
| <attribute name="LockAcquisitionTimeout">10000</attribute>
|
| <!-- Name of the eviction policy class. -->
| <attribute name="EvictionPolicyClass"></attribute>
|
| <!--
| Indicate whether to use region based marshalling or not. Set this to true if you are running under a scoped
| class loader, e.g., inside an application server. Default is "false".
| -->
| <attribute name="UseRegionBasedMarshalling">false</attribute>
| </mbean>
|
|
| <!-- Uncomment to get a graphical view of the TreeCache MBean above -->
| <!-- <mbean code="org.jboss.cache.TreeCacheView" name="jboss.cache:service=TreeCacheView">-->
| <!-- <depends>jboss.cache:service=TreeCache</depends>-->
| <!-- <attribute name="CacheService">jboss.cache:service=TreeCache</attribute>-->
| <!-- </mbean>-->
|
|
| </server>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960836#3960836
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960836
19 years, 9 months
Illegal access (timeout error)
by Murtaza Hussain
Hi All,
We are running Jboss 4 and we get the following error when we leave a client
session (browser) idle for about 40 minutes.
The symptoms are similar to a session timeout error that one usually gets
but it doesn't seem to be that.
Can someone please assist. The stack trace is included.
java.lang.SecurityException: Illegal access
at
org.apache.jsp.www.admin.GIQteFind_jsp._jspService(org.apache.jsp.www.admin.
GIQteFind_jsp:1190)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
22)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:173)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.ja
va:81)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:178)
at
org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalVal
ve.java:39)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssoci
ationValve.java:153)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:
59)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126
)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105
)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:744)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.jav
a:527)
at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThre
ad.java:112)
at java.lang.Thread.run(Thread.java:595)
19 years, 9 months