[Messaging, JMS & JBossMQ] - java.lang.VerifyError
by vri_97
Hi,
I'm trying to develop a simple client for EJB3's MDB, but somehow it will always raise exception in "(ConnectionFactory)ic.lookup("/ConnectionFactory")" statement (it's exactly the same with the sample in Jboss Messaging bundle)
InitialContext ic = new InitialContext();
ConnectionFactory cf = (ConnectionFactory)ic.lookup("/ConnectionFactory");
Queue queue = (Queue)ic.lookup("/queue/testQueue");
The exception :
Exception in thread "main" java.lang.VerifyError: (class: org/jboss/jms/client/delegate/ClientConnectionFactoryDelegate, method: getClientAOPStack signature: ()[B) Incompatible object argument for function call
I'm using JBoss AS 4.2, Eclipse 3.2.2, JBoss IDE2.0, and JBoss Messaging 1.3 GA. I can run the sample ejb3mdb from Jboss Messaging bundle with no problem. Does anyone know what is happening ?
Thank you.
Regards,
Ferry
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052005#4052005
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052005
18Â years, 10Â months
[JBoss Seam] - Integrating Seam Security with 3rd party
by gonzalad
Hello,
I have a problem overloading org.jboss.seam.security.Identity class, I would need to overload the subject - and this needs some modification in Seam Identity class.
Could this change be planned for a future release ?
My purpose is to integrate Seam security with Acegi (or another security system). So far, no problem (we didn't have Jaas Login Module, but just inherited from Identity), prototype is functional.
The main problem now is that the subject field of class Identity is private and that the class access it directly and not via the public getter [1].
Could there be a change in Identity class in order to alway access subject from it's getter so I can overload the getter method ?
Thanks
i.e. - extract from version 1.2.0.PATCH1 :
protected void unAuthenticate()
| {
| for ( Group sg : subject.getPrincipals(Group.class) )
| {
| if ( ROLES_GROUP.equals( sg.getName() ) )
| {
| subject.getPrincipals().remove(sg);
| break;
| }
| }
| }
I woud like sthing like :
protected void unAuthenticate()
| {
| for ( Group sg : getSubject().getPrincipals(Group.class) )
| {
| if ( ROLES_GROUP.equals( sg.getName() ) )
| {
| getSubject().getPrincipals().remove(sg);
| break;
| }
| }
| }
My purpose is afterward to overload getSubject with sthing like :
| public Subject getSubject() {
| return SeamAcegiAdapter.getSubject();
| }
[1] In detail : login via a Seam JSF page isn't the problem. I've made it with the current version of Seam. My overloaded Identity calls Acegi authenticationManager authenticate method. So far, so good.
My problem is now I want to log via SSO or X509 mechanism using acegi filter. In this case, Acegi authentication is called but not Seam authentication.
One solution would be to make a callback from Acegi authentication to Seam, but it doesn't seem to be the good solution.
The other solution would be to use the Acegi subject from seam by REFERENCE -> so my need to overload the subject getter in Seam Identity class.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052001#4052001
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052001
18Â years, 10Â months
[Installation, Configuration & Deployment] - Unable to create message factory for SOAP & Assembling the S
by linweichun
I used to use JBoss4.0.5.GA + MySQL 5.0 + juddi-0.9-rc4, and there was no any problems.
Now I'm using JBoss4.2.0.GA + MySQL 5.0 + juddi-0.9-rc4.
When I connect to http://localhost:8080/juddi/happyjuddi.jsp, all the configs are correct and display color Green.
But while I was using UDDI Browser 0.2 to check inquiry or publish, it returned HTTP STATUS 500 Error.
The detail are as follow:
10:53:24,250 INFO [STDOUT] 2007-06-05 10:53:24,250 [http-127.0.0.1-8080-1] ERROR org.apache.juddi.registry.AbstractService - Unable to create message factory
| for SOAP: org.jboss.ws.core.soap.MessageFactoryImpl
| 10:53:24,281 INFO [STDOUT] 2007-06-05 10:53:24,281 [http-127.0.0.1-8080-1] ERROR org.apache.juddi.registry.AbstractService - A serious error has occured while assembling the SOAP Fault.
| java.lang.NullPointerException
| at org.apache.juddi.registry.AbstractService.doPost(AbstractService.java:315)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:595)
| 10:53:24,281 INFO [STDOUT] 2007-06-05 10:53:24,281 [http-127.0.0.1-8080-1] ERROR org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/juddi].[UDDIV2InquiryService] - Servlet.service() for servlet UDDIV2InquiryService threw exception
| java.lang.NullPointerException
| at org.apache.juddi.registry.AbstractService.doPost(AbstractService.java:344)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:595)
| 11:03:29,062 INFO [STDOUT] 2007-06-05 11:03:29,062 [http-127.0.0.1-8080-1] ERROR org.apache.juddi.registry.AbstractService - Unable to create message factory
| for SOAP: org.jboss.ws.core.soap.MessageFactoryImpl
| 11:03:29,062 INFO [STDOUT] 2007-06-05 11:03:29,062 [http-127.0.0.1-8080-1] ERROR org.apache.juddi.registry.AbstractService - A serious error has occured while assembling the SOAP Fault.
| java.lang.NullPointerException
| at org.apache.juddi.registry.AbstractService.doPost(AbstractService.java:315)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:595)
| 11:03:29,078 INFO [STDOUT] 2007-06-05 11:03:29,078 [http-127.0.0.1-8080-1] ERROR org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/juddi].[UDDIV2InquiryService] - Servlet.service() for servlet UDDIV2InquiryService threw exception
| java.lang.NullPointerException
| at org.apache.juddi.registry.AbstractService.doPost(AbstractService.java:344)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:595)
Is there any one who can tell me why? or tell me how to fix it?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052000#4052000
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052000
18Â years, 10Â months
[JBoss Messaging] - Re: Bridging JMS providers
by thomasra
Hi Tim.
In brief: yes, that is what I am thinking, a remote replyto that would work across providers after bridging.
I've tried the bridge, and it is very handy. However, what I am thinking of is analogous to what you are suggesting: a remote replyto, but since replyto (which is a destination) does not apply across providers that does not seem to be a possible way to go. I'm thinking this scenario:
(sorry for long post)
1) A JMS client sends a message to a queue on JBossMessaging (messageid: 1) expecting a response (on a replyto temp destination)
2) A Bridge configuration picks up message 1 and sends it to a remote provider, expecting a reply (the remote message gets a provider-specific messageid, lets say "A" to differentiate them). Here we cannot use the same replyto destination given in 1) since we are going to another provider.
3) A remote JMS client (not able to talk to JBM) receives the message (A) and replies to it to a (for him) local queue with a new message (B), using "A" as the correlation id (these legacy clients typically don't obey a replyto header anyway, they just send a response where they usually put it. They do, however, use the correlationid)
4) A Bridge configuration picks up message B and puts it on the replyto destination given by the original JMS client
This scenario is quite common and is often (in the proprietary world) handled by bridging products where you configure how to map correlation/replies between providers. Now that JBM has a bridge, this kind of functionality could perhaps be added to it, making it even more powerful.
If a remote client respected the replyto destination given in the header and the remote provider supports temp destinations, the "outgoing" Bridge could see that there is a destination in the original request, create a remote temp queue and send the message using a replyto with the new (remote) temp queue. However, that would require that the "receiving" Bridge configuration would have to be able to listen to dynamically created remote queues and still have no understanding of where to put the received messages. If two bridge configurations were to be "aware" of each other (lets say a bridge xml could contain BOTH an in- and outbound route) they could also share this temporary queueing, AND know the mapping of messageid's since they get the remote provider's messageid after send().
If we cannot use temp destinations, the Bridge (if configured in in/out pairs) could still map correlationid's, which would be extremely powerful.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051997#4051997
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051997
18Â years, 10Â months
[EJB 3.0] - entity relationship from several jars
by deady_
I have
1. Client entity in client.jar:
| package object;
| @Entity
| public class Client { ... }
2. GuestbookEntry entity in guestbook.jar.
| package object;
| @Entity
| public class GuestbookEntry {
| ...
| @ManyToOne
| public Client getClient() {...}
| }
|
now I try to deploy these jars.
First guestbook.jar is deployed before client.jar and JBoss can't find class object.Client. How can I tell that guestbook.jar depends on client.jar and must be deployed after it?
If I redeploy guestbook.jar after client.jar is deployed, I get exception:
anonymous wrote : org.hibernate.AnnotationException: @OneToOne or @ManyToOne on object.Entry.client references an unknown entity: object.Client
I added
| <?xml version="1.0" encoding="UTF-8"?>
| <persistence xmlns="http://java.sun.com/xml/ns/persistence">
| <persistence-unit name="unit">
| <jta-data-source>java:/datasource</jta-data-source>
| <class>object.Client</class>
| </persistence-unit>
| </persistence>
|
and now every time I deploy guestbook.jar I can see that jboss binds Client entity, but it was already binded when client.jar was deployed. Does it creates on more pool for it?
Let's assume that Client has some relations with other entities from client.jar, now to deploy guestbook.jar I have to add <class>object.<CLASS_NAME></class>
lines for each relation class and they also get rebinded.
How can I tell that guestbook.jar must use entities from client.jar?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051989#4051989
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051989
18Â years, 10Â months