[JBossCache] - Re: Fails to run on Jboss4.2.2
by bstansberry＠jboss.com
I think it's this bit from jboss-web-cluster.sar/jboss-web-cluster.aop/META-INF/jboss-aop.xml that is causing you trouble:
| <!-- Make any POJO with a JDK5 PojoCacheable annotation as a Subject/Observerable -->
| <bind pointcut="set(* @org.jboss.cache.aop.annotation.PojoCacheable->*)">
| <interceptor class="org.jboss.aspects.patterns.observable.SubjectInterceptor"/>
| </bind>
|
| <introduction class="@org.jboss.cache.aop.annotation.PojoCacheable">
| <mixin>
| <interfaces>org.jboss.aspects.patterns.observable.Subject</interfaces>
| <class>org.jboss.aspects.patterns.observable.SubjectImpl</class>
| <construction>new org.jboss.aspects.patterns.observable.SubjectImpl(this)</construction>
| </mixin>
| </introduction>
|
The latter causes the AspectManager to insert a SubjectInterceptor when you deploy your class. But when you did your aopc, your jboss-aop.xml didn't include the "introduction" element. So your class doesn't implement the Subject interface and you get a CCE when the SubjectInterceptor gets invoked.
Two possible solutions:
1) Add the "introduction" element above to your jboss-aop.xml and run aopc again.
2) If you don't use FIELD granularity web session replication, remove the jboss-web-cluster.sar/jboss-web-cluster.aop file.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127242#4127242
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127242
18 years, 2 months
[EJB 3.0] - EJB3 & SSL not working in JBoss 5 Beta3?
by javidjamae
I'm trying to get a standalone client to communicate with an EJB over SSL. I tried following the directions here, but they didn't work: http://labs.jboss.com/jbossejb3/docs/tutorial/ssl/ssl.html
It complained that it didn't know what "jboss.aop:service=AspectDeployer" was. I figured that is because this was converted from an MBean into a Microcontainer bean since the time that article was written (or maybe a difference between 4.2 and 5.0).
This document (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMicrocontainerFAQ) told me that an MBean could depend on a Microcontainer bean, so I changed the depends in the configuration to this:
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:type=Connector,transport=socket3843,handler=ejb3">
| <depends>AspectDeployer</depends>
| <attribute name="InvokerLocator">sslsocket://0.0.0.0:3843</attribute>
| <attribute name="Configuration">
| <handlers>
| <handler subsystem="AOP">
| org.jboss.aspects.remoting.AOPRemotingInvocationHandler
| </handler>
| </handlers>
| </attribute>
| </mbean>
|
Unfortunately, that threw ClassNotFoundException's because of the whitespace around the classname in the handler tag. After getting rid of the whitespace, the server seemed to start without any errors.
But, when I try to access a remote bean without specifying a truststore on the client side (i.e. without using -Djavax.net.ssl.keyStore and keyStorePass), I am able to access the bean. I would expect that I wouldn't be able to. Here is my bean's remote interface:
| @Remote
| @RemoteBinding(clientBindUrl = "sslsocket://0.0.0.0:3843")
| public interface Greeter {
| public void greet(String message);
|
| public List<Greeting> getAllGreetings();
| }
|
As you can see, I have the RemoteBinding annotation with the clientBindUrl parameter specified.
Am I missing something? I expect to NOT be able to access the bean without having the server certificate in my client truststore and the truststore specified on the command line, but I am still able to. What's the best way to ensure that SSL is actually working?
...
As a side note, I opened a bug about whitespace in the jboss-web.xml files- http://jira.jboss.org/jira/browse/JBAS-5173 - and I've seen this in other places as well. It seems likely that these whitespace issues all be related to the same XML parsing code??
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127240#4127240
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127240
18 years, 2 months
[JBoss Seam] - Threads and @In JbpmContext
by jcarlos_andia
Hi.
I am using jbpm to push a project application but i am stuck when i want to implement states between tasks.
E.g. I have task1 and taskInstance2 and task2 have to start after x hours task1 finished.
I place a state between those tasks to prevent task2 starts inmediately after task1 finishes and there is a thread that is checking if the lagTime (x) has been reached in which case the thread signal the state causing the token to move to the next task. The problem come out when I want to get the rootToken children or when i signal a state
| [ConnectionManager] forcing batcher resource cleanup on transaction completion; forgot to close Scrollable Results/Iterator?
|
The line in which fails is not always the same, understandable considering that threads are involved. All transactions are with injected jbpmContext. Any idea of what is happening? Maybe a suggestion of how to implement this in a different way.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127233#4127233
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127233
18 years, 2 months
[JBoss jBPM] - Threads and jbpm
by jcarlos_andia
Hi.
I am using jbpm to push a project application but i am stuck when i want to implement states between tasks.
E.g. I have task1 and taskInstance2 and task2 have to start after x hours task1 finished.
I place a state between those tasks to prevent task2 starts inmediately after task1 finishes and there is a thread that is checking if the lagTime (x) has been reached in which case the thread signal the state causing the token to move to the next task. The problem come out when I want to get the rootToken children or when i signal a state
| [ConnectionManager] forcing batcher resource cleanup on transaction completion; forgot to close Scrollable Results/Iterator?
|
The line in which fails is not always the same, understandable considering that threads are involved. Any idea of what is happening? Maybe a suggestion of how to implement this in a different way.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127232#4127232
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127232
18 years, 2 months