Yes, I am using trunk. Is there a more stable branch/version I should be using? I had updated again hoping it was just something with the time I checked out and then ran into the problems Heiko Braun ran into compiling it. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 8:52 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages What version of ErraiBus are you using? Are you getting it from trunk? On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: DefaultBlockingServlet seems to have the same effect. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 2:56 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages I will check into this. We're still working on getting the AIO stuff sorted, and I wouldn't consider the Tomcat or JBoss adapters to be production ready. You're best to use the DefaultBlockingServlet -- which will provide adequate performance for development while we get the AIO adapters squared away over the next few days. On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: I’m having trouble getting a message to go through using ErraiBus. I’m using this on the client side: CommandMessage msg = (CommandMessage) CommandMessage.create().toSubject("Items").set("SerialNumber", serialInput.getValue()); bus.conversationWith(msg, new MessageCallback() { @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); Item item = message.get(Item.class, "Item"); MessageBox.alert("Errai", item.getSerialNumber().toString(), null); } }); With this on the server side: @Service("Items") public class Items implements MessageCallback { private MessageBus bus; @Inject public Items(MessageBus bus) { this.bus = bus; System.out.println("Got a bus..."); } @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); System.out.println("Incoming message..."); Long serialNum = message.get(Long.class, "SerialNumber"); System.out.println(serialNum); Item item = new Item(); item.setSerialNumber(serialNum); ConversationMessage.create(message).set("Item",item).sendNowWith(bus); } } However, all it seems to send is: {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"temp:Conversation:2","PriorityProcessing":"1"} I don’t see where it actually sends my body or the subject that I fill out in my message. Nothing also gets to the Service class. Am I doing something wrong? I have Tomcat running NIO and everything else seems set up correctly. It will keep a GET connection open and do the POST of the JSON above, but nowhere does it seem to send what I want it to. I also seem to be getting these occasionally, usually on some of the first requests to in.erraiBus: java.lang.NullPointerException at org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(TomcatCometServlet.java:105) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unknown Source) at org.apache.catalina.core.StandardWrapperValve.event(Unknown Source) at org.apache.catalina.core.StandardContextValve.event(Unknown Source) at org.apache.catalina.core.StandardHostValve.event(Unknown Source) at org.apache.catalina.valves.ValveBase.event(Unknown Source) at org.apache.catalina.core.StandardEngineValve.event(Unknown Source) at org.apache.catalina.connector.CoyoteAdapter.event(Unknown Source) at org.apache.coyote.http11.Http11NioProcessor.event(Unknown Source) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.event(Unknown Source) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Can anyone point me at what I’m missing? _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users

Just updated and it compiled fine. Now to see if any of my connection problems are fixed. From: Heiko Braun [mailto:hbraun@redhat.com] Sent: Monday, January 11, 2010 8:59 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Hi Kevin, the compilation problems should be fixed already. On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: Yes, I am using trunk. Is there a more stable branch/version I should be using? I had updated again hoping it was just something with the time I checked out and then ran into the problems Heiko Braun ran into compiling it. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 8:52 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages What version of ErraiBus are you using? Are you getting it from trunk? On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: DefaultBlockingServlet seems to have the same effect. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 2:56 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages I will check into this. We're still working on getting the AIO stuff sorted, and I wouldn't consider the Tomcat or JBoss adapters to be production ready. You're best to use the DefaultBlockingServlet -- which will provide adequate performance for development while we get the AIO adapters squared away over the next few days. On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: I’m having trouble getting a message to go through using ErraiBus. I’m using this on the client side: CommandMessage msg = (CommandMessage) CommandMessage.create().toSubject("Items").set("SerialNumber", serialInput.getValue()); bus.conversationWith(msg, new MessageCallback() { @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); Item item = message.get(Item.class, "Item"); MessageBox.alert("Errai", item.getSerialNumber().toString(), null); } }); With this on the server side: @Service("Items") public class Items implements MessageCallback { private MessageBus bus; @Inject public Items(MessageBus bus) { this.bus = bus; System.out.println("Got a bus..."); } @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); System.out.println("Incoming message..."); Long serialNum = message.get(Long.class, "SerialNumber"); System.out.println(serialNum); Item item = new Item(); item.setSerialNumber(serialNum); ConversationMessage.create(message).set("Item",item).sendNowWith(bus); } } However, all it seems to send is: {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"temp:Conversation:2","PriorityProcessing":"1"} I don’t see where it actually sends my body or the subject that I fill out in my message. Nothing also gets to the Service class. Am I doing something wrong? I have Tomcat running NIO and everything else seems set up correctly. It will keep a GET connection open and do the POST of the JSON above, but nowhere does it seem to send what I want it to. I also seem to be getting these occasionally, usually on some of the first requests to in.erraiBus: java.lang.NullPointerException at org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(TomcatCometServlet.java:105) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unknown Source) at org.apache.catalina.core.StandardWrapperValve.event(Unknown Source) at org.apache.catalina.core.StandardContextValve.event(Unknown Source) at org.apache.catalina.core.StandardHostValve.event(Unknown Source) at org.apache.catalina.valves.ValveBase.event(Unknown Source) at org.apache.catalina.core.StandardEngineValve.event(Unknown Source) at org.apache.catalina.connector.CoyoteAdapter.event(Unknown Source) at org.apache.coyote.http11.Http11NioProcessor.event(Unknown Source) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.event(Unknown Source) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Can anyone point me at what I’m missing? _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users

Switching it back to the listener config seems to make it work again through the DefaultBlockingServlet. From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] Sent: Thursday, January 14, 2010 11:22 AM To: 'Mike Brock' Cc: &#39;errai-users(a)lists.jboss.org&#39; Subject: RE: [errai-users] Trouble sending messages Yeah, I’m using the NIO connector. And actually if I configure the TomcatCometServlet manually I get the same error again. I know that used to happen when I was accessing it through my AJP connected Apache instance, but now I’m accessing it directly through port 8443 on Tomcat. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 14, 2010 10:55 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Are you using the NIO connector in Tomcat? Errai by default will try to use Tomcat's AIO system, which requires that the NIO or APR connecter be used. On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: I tried the AutoServlet and it seems to pick the TomcatCometServlet which makes it spin over and over on this message every time it tries to access it: ************************************************************************************************* ** PROBLEM! ** It appears something has been incorrectly configured. In order to use ErraiBus ** on Tomcat, you must ensure that you are using the NIO or APR connector. Also ** make sure that you have added these lines to your WEB-INF/web.xml file: ** --- ** <servlet> ** <servlet-name>TomcatErraiServlet</servlet-name> ** <servlet-class>org.jboss.errai.bus.server.servlet.TomcatCometServlet</servlet-class> ** <load-on-startup>1</load-on-startup> ** </servlet> ** ** <servlet-mapping> ** <servlet-name>TomcatErraiServlet</servlet-name> ** <url-pattern>*.erraiBus</url-pattern> ** </servlet-mapping> ** --- ** If you have the following lines in your WEB-INF/web.xml, you must comment or remove them: ** --- ** <listener> ** <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listener-class> ** </listener> ************************************************************************************************* From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 14, 2010 10:06 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages By the way, if you want, we're on IRC on irc.freenode.net in channel #errai -- I'm "cbrock" on there if you want help troubleshooting directly. On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, and IE on Windows 7. I’m using Tomcat. I’ll try the AutoServlet to see if it makes a difference. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Wednesday, January 13, 2010 8:35 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages If you update to the latest version of trunk, simply get rid of the listener and replace your web.xml config with this: <servlet> <servlet-name>ErraiAutoServlet</servlet-name> <servlet-class>org.jboss.errai.bus.server.servlet.ErraiAutoServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>ErraiAutoServlet</servlet-name> <url-pattern>*.erraiBus</url-pattern> </servlet-mapping> This problem you're having is curious, though. We haven't seen it in our internal testing. Can you tell me what browser, what appserver, and what OS you're on? On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: I’m using the following on the client side: bus.subscribe("ItemFound", new MessageCallback() { @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); MessageBox.alert("Success", "In Callback", null); /*Map<String,Object> parts = message.getParts(); Set<String> keys = parts.keySet(); for (String key : keys) { MessageBox.alert("Key",key,null); }*/ //Item item = message.get(Item.class, "Item"); //MessageBox.alert("Return", item.getSerialNumber().toString(), null); } }); MessageBuilder.createMessage().toSubject("Items").signalling().with(MessageParts.ReplyTo, "ItemFound").with("SerialNumber", serialInput.getValue().toString()).errorsHandledBy(new ErrorCallback() { @Override public boolean error(Message message, Throwable throwable) { //throw new UnsupportedOperationException("Not supported yet."); MessageBox.alert("Error", throwable.getMessage(), null); return true; } }).sendNowWith(bus); Which sends: {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489"} Although I’ve now noticed that it takes 2 tries to get it to send that and a 3rd one to get the response back for the first one. Server portion looks like: @Service("Items") public class Items implements MessageCallback { private MessageBus bus; @Inject public Items(MessageBus bus) { this.bus = bus; System.out.println("Got a bus..."); } @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); System.out.println("Incoming message..."); String serialNum = message.get(String.class, "SerialNumber"); System.out.println(serialNum); Item item = new Item(); item.setSerialNumber(Long.parseLong(serialNum)); MessageBuilder.createConversation(message).subjectProvided().signalling().with("Item", item).errorsHandledBy(new ErrorCallback() { @Override public boolean error(Message message, Throwable throwable) { //throw new UnsupportedOperationException("Not supported yet."); throwable.printStackTrace(); return true; } }).sendNowWith(bus); } } Response on the second POST is: [{"ItemFound":{"Item":{__EncodedType:'com.xteconline.system.Item',id:null,serialNumber:1201489,part:null,storageLocation:null,storageUnit:null,customer:null,oemSerial:null,manufacturer:null,status:null,itemInfos:null},"ToSubject":"ItemFound"}}] All others seem to get: [{"HeartBeat":null}] And on the first time I try to submit, it still seems to be kind of setting up stuff since it sends: {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerBus","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"AuthorizationService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ClientNegotiationService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ClientBus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ClientBusErrors"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Items"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerBus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"AuthorizationService"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ClientNegotiationService"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService"} And {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ItemFound","PriorityProcessing":"1"} But doesn’t send my stuff until I submit again. And about the only other relevant thing I can think of for Errai is the servlet config: <listener> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listener-class> </listener> Which I believe sets up the DefaultBlockingServlet. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Tuesday, January 12, 2010 11:48 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages We have a fairly significant application that makes extensive use of this type of paradigm and we haven't ever experienced any dropped messages. Can you provide me some examples of your code so we can troubleshoot what's going on? On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: The MessageParts.ReplyTo was what I was missing in there. However, my callback doesn’t seem to be called. I get something back when my request is POSTed, but it never seems to call my callback. They do seem to work sometimes though. I had accidentally named my callback subject and the server subject the same and when I created a message to that subject, both the client callback and the server callback were called correctly. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Tuesday, January 12, 2010 9:07 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages The sender needs to create a listening service that can be replied to. The best way to do this is like so: //client-side code bus.subscribe("MyResponseSvc", new MessageCallback() { public void callback(Message msg) { ... } } ); MessageBuilder.createMessage().toSubject("ConversationalService").signalling() .with(MessageParts.ReplyTo, "MyResponseSvc") .with("SomeMessagePart", "Foo") .noErrorHandling() .sendNowWith(bus); ... //server-side code MessageBuilder.createConversation(message) .subjectProvided().signalling() .with("MyResponseData", "Bar") .noErrorHandling() .sendNowWith(bus); ... Note: we may make this more straight forward in the future, such as with the RPC API. On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: I won’t be able to use the Swing monitor on the server I’m deploying to since it has no interface. However, I did start enabling logging in various places and it does seem that my services weren’t getting started. I was lacking an ErraiApp.properties which I guess is used as the root for where it should start looking for services. After adding that, they started and stuff started to go through. Does the client keep a record of services or something then? Why wouldn’t it try to contact the service and then fail that it couldn’t find it? Also, looking at the revised Message API, how do you listen for the reply in a conversation? Do I need to create a separate listener? Before you could specify a MessageCallback to get the response in the conversation, but I can’t find anywhere in the call chain to do that and it’s not covered in the SVN book. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 11, 2010 3:16 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Kevin, I'm not sure how you're launching your app, but can you provide this command line option which will bring up the bus monitor, and at least tell me if you've probably deployed your services: -Derrai.bus.showmonitor=true Also, can you email me the log output from when your startup the application? On 2010-01-11, at 3:35 PM, Kevin Jordan wrote: Changing to a createCall and making a @Endpoint annotated method on the server seems to make it send something again: {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Items.getItem:RespondTo:1","PriorityProcessing":"1"} With a response of: [{"HeartBeat":null}] However, I still so nowhere where it passes the parameter I give it with: MessageBuilder.createCall().call("Items").endpoint("getItem", serialInput.getValue()).respondTo(Item.class, new RemoteCallback<Item>() { @Override public void callback(Item response) { //throw new UnsupportedOperationException("Not supported yet."); MessageBox.alert("Return",item.getSerialNumber().toString(),null); } }).noErrorHandling().sendNowWith(bus); From: errai-users-bounces(a)lists.jboss.org [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin Jordan Sent: Monday, January 11, 2010 1:46 PM To: 'Mike Brock' Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Made the changes specified in the userguide, but now it doesn’t send anything. I’m using the following: MessageBuilder.createMessage().toSubject("Items").signalling().with("SerialNumber", "Test").noErrorHandling().sendNowWith(bus); It still seems to be set up just fine since the in.erraiBus servlet is created and the client long polls it, but the code above doesn’t seem to send anything. I’m using the following way to make it for the DefaultBlockingServlet: <listener> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listener-class> </listener> Should I be using that? I figure it shouldn’t affect the client any though unless the servlet is incorrectly set up as a consequence, which it doesn’t seem to be since they communicate just fine for the initial setup. What should I look at to see why it’s not sending? From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 11, 2010 12:43 PM To: Kevin Jordan Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages You should be aware we have made changes and are retiring the use of the CommandMessage API. Be sure to read the documentation in the userguide/src/main/docbook/en/master.xml file. You can use: mvn jdocbook:generate to create an HTML file from the userguide/ directory. On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: Just updated and it compiled fine. Now to see if any of my connection problems are fixed. From: Heiko Braun [mailto:hbraun@redhat.com] Sent: Monday, January 11, 2010 8:59 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Hi Kevin, the compilation problems should be fixed already. On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: Yes, I am using trunk. Is there a more stable branch/version I should be using? I had updated again hoping it was just something with the time I checked out and then ran into the problems Heiko Braun ran into compiling it. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 8:52 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages What version of ErraiBus are you using? Are you getting it from trunk? On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: DefaultBlockingServlet seems to have the same effect. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 2:56 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages I will check into this. We're still working on getting the AIO stuff sorted, and I wouldn't consider the Tomcat or JBoss adapters to be production ready. You're best to use the DefaultBlockingServlet -- which will provide adequate performance for development while we get the AIO adapters squared away over the next few days. On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: I’m having trouble getting a message to go through using ErraiBus. I’m using this on the client side: CommandMessage msg = (CommandMessage) CommandMessage.create().toSubject("Items").set("SerialNumber", serialInput.getValue()); bus.conversationWith(msg, new MessageCallback() { @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); Item item = message.get(Item.class, "Item"); MessageBox.alert("Errai", item.getSerialNumber().toString(), null); } }); With this on the server side: @Service("Items") public class Items implements MessageCallback { private MessageBus bus; @Inject public Items(MessageBus bus) { this.bus = bus; System.out.println("Got a bus..."); } @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); System.out.println("Incoming message..."); Long serialNum = message.get(Long.class, "SerialNumber"); System.out.println(serialNum); Item item = new Item(); item.setSerialNumber(serialNum); ConversationMessage.create(message).set("Item",item).sendNowWith(bus); } } However, all it seems to send is: {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"temp:Conversation:2","PriorityProcessing":"1"} I don’t see where it actually sends my body or the subject that I fill out in my message. Nothing also gets to the Service class. Am I doing something wrong? I have Tomcat running NIO and everything else seems set up correctly. It will keep a GET connection open and do the POST of the JSON above, but nowhere does it seem to send what I want it to. I also seem to be getting these occasionally, usually on some of the first requests to in.erraiBus: java.lang.NullPointerException at org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(TomcatCometServlet.java:105) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unknown Source) at org.apache.catalina.core.StandardWrapperValve.event(Unknown Source) at org.apache.catalina.core.StandardContextValve.event(Unknown Source) at org.apache.catalina.core.StandardHostValve.event(Unknown Source) at org.apache.catalina.valves.ValveBase.event(Unknown Source) at org.apache.catalina.core.StandardEngineValve.event(Unknown Source) at org.apache.catalina.connector.CoyoteAdapter.event(Unknown Source) at org.apache.coyote.http11.Http11NioProcessor.event(Unknown Source) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.event(Unknown Source) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Can anyone point me at what I’m missing? _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users

Yes. It’s still working the way it was before where I have to submit more than once and the response comes back on the POST but the callback doesn’t get called. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 14, 2010 11:44 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Are you still losing messages? On 2010-01-14, at 12:31 PM, Kevin Jordan wrote: Switching it back to the listener config seems to make it work again through the DefaultBlockingServlet. From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] Sent: Thursday, January 14, 2010 11:22 AM To: 'Mike Brock' Cc: &#39;errai-users(a)lists.jboss.org&#39; Subject: RE: [errai-users] Trouble sending messages Yeah, I’m using the NIO connector. And actually if I configure the TomcatCometServlet manually I get the same error again. I know that used to happen when I was accessing it through my AJP connected Apache instance, but now I’m accessing it directly through port 8443 on Tomcat. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 14, 2010 10:55 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Are you using the NIO connector in Tomcat? Errai by default will try to use Tomcat's AIO system, which requires that the NIO or APR connecter be used. On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: I tried the AutoServlet and it seems to pick the TomcatCometServlet which makes it spin over and over on this message every time it tries to access it: ************************************************************************************************* ** PROBLEM! ** It appears something has been incorrectly configured. In order to use ErraiBus ** on Tomcat, you must ensure that you are using the NIO or APR connector. Also ** make sure that you have added these lines to your WEB-INF/web.xml file: ** --- ** <servlet> ** <servlet-name>TomcatErraiServlet</servlet-name> ** <servlet-class>org.jboss.errai.bus.server.servlet.TomcatCometServlet</servlet-class> ** <load-on-startup>1</load-on-startup> ** </servlet> ** ** <servlet-mapping> ** <servlet-name>TomcatErraiServlet</servlet-name> ** <url-pattern>*.erraiBus</url-pattern> ** </servlet-mapping> ** --- ** If you have the following lines in your WEB-INF/web.xml, you must comment or remove them: ** --- ** <listener> ** <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listener-class> ** </listener> ************************************************************************************************* From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 14, 2010 10:06 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages By the way, if you want, we're on IRC on irc.freenode.net in channel #errai -- I'm "cbrock" on there if you want help troubleshooting directly. On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, and IE on Windows 7. I’m using Tomcat. I’ll try the AutoServlet to see if it makes a difference. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Wednesday, January 13, 2010 8:35 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages If you update to the latest version of trunk, simply get rid of the listener and replace your web.xml config with this: <servlet> <servlet-name>ErraiAutoServlet</servlet-name> <servlet-class>org.jboss.errai.bus.server.servlet.ErraiAutoServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>ErraiAutoServlet</servlet-name> <url-pattern>*.erraiBus</url-pattern> </servlet-mapping> This problem you're having is curious, though. We haven't seen it in our internal testing. Can you tell me what browser, what appserver, and what OS you're on? On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: I’m using the following on the client side: bus.subscribe("ItemFound", new MessageCallback() { @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); MessageBox.alert("Success", "In Callback", null); /*Map<String,Object> parts = message.getParts(); Set<String> keys = parts.keySet(); for (String key : keys) { MessageBox.alert("Key",key,null); }*/ //Item item = message.get(Item.class, "Item"); //MessageBox.alert("Return", item.getSerialNumber().toString(), null); } }); MessageBuilder.createMessage().toSubject("Items").signalling().with(MessageParts.ReplyTo, "ItemFound").with("SerialNumber", serialInput.getValue().toString()).errorsHandledBy(new ErrorCallback() { @Override public boolean error(Message message, Throwable throwable) { //throw new UnsupportedOperationException("Not supported yet."); MessageBox.alert("Error", throwable.getMessage(), null); return true; } }).sendNowWith(bus); Which sends: {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489"} Although I’ve now noticed that it takes 2 tries to get it to send that and a 3rd one to get the response back for the first one. Server portion looks like: @Service("Items") public class Items implements MessageCallback { private MessageBus bus; @Inject public Items(MessageBus bus) { this.bus = bus; System.out.println("Got a bus..."); } @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); System.out.println("Incoming message..."); String serialNum = message.get(String.class, "SerialNumber"); System.out.println(serialNum); Item item = new Item(); item.setSerialNumber(Long.parseLong(serialNum)); MessageBuilder.createConversation(message).subjectProvided().signalling().with("Item", item).errorsHandledBy(new ErrorCallback() { @Override public boolean error(Message message, Throwable throwable) { //throw new UnsupportedOperationException("Not supported yet."); throwable.printStackTrace(); return true; } }).sendNowWith(bus); } } Response on the second POST is: [{"ItemFound":{"Item":{__EncodedType:'com.xteconline.system.Item',id:null,serialNumber:1201489,part:null,storageLocation:null,storageUnit:null,customer:null,oemSerial:null,manufacturer:null,status:null,itemInfos:null},"ToSubject":"ItemFound"}}] All others seem to get: [{"HeartBeat":null}] And on the first time I try to submit, it still seems to be kind of setting up stuff since it sends: {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerBus","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"AuthorizationService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ClientNegotiationService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ClientBus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ClientBusErrors"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Items"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerBus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"AuthorizationService"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ClientNegotiationService"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService"} And {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ItemFound","PriorityProcessing":"1"} But doesn’t send my stuff until I submit again. And about the only other relevant thing I can think of for Errai is the servlet config: <listener> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listener-class> </listener> Which I believe sets up the DefaultBlockingServlet. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Tuesday, January 12, 2010 11:48 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages We have a fairly significant application that makes extensive use of this type of paradigm and we haven't ever experienced any dropped messages. Can you provide me some examples of your code so we can troubleshoot what's going on? On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: The MessageParts.ReplyTo was what I was missing in there. However, my callback doesn’t seem to be called. I get something back when my request is POSTed, but it never seems to call my callback. They do seem to work sometimes though. I had accidentally named my callback subject and the server subject the same and when I created a message to that subject, both the client callback and the server callback were called correctly. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Tuesday, January 12, 2010 9:07 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages The sender needs to create a listening service that can be replied to. The best way to do this is like so: //client-side code bus.subscribe("MyResponseSvc", new MessageCallback() { public void callback(Message msg) { ... } } ); MessageBuilder.createMessage().toSubject("ConversationalService").signalling() .with(MessageParts.ReplyTo, "MyResponseSvc") .with("SomeMessagePart", "Foo") .noErrorHandling() .sendNowWith(bus); ... //server-side code MessageBuilder.createConversation(message) .subjectProvided().signalling() .with("MyResponseData", "Bar") .noErrorHandling() .sendNowWith(bus); ... Note: we may make this more straight forward in the future, such as with the RPC API. On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: I won’t be able to use the Swing monitor on the server I’m deploying to since it has no interface. However, I did start enabling logging in various places and it does seem that my services weren’t getting started. I was lacking an ErraiApp.properties which I guess is used as the root for where it should start looking for services. After adding that, they started and stuff started to go through. Does the client keep a record of services or something then? Why wouldn’t it try to contact the service and then fail that it couldn’t find it? Also, looking at the revised Message API, how do you listen for the reply in a conversation? Do I need to create a separate listener? Before you could specify a MessageCallback to get the response in the conversation, but I can’t find anywhere in the call chain to do that and it’s not covered in the SVN book. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 11, 2010 3:16 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Kevin, I'm not sure how you're launching your app, but can you provide this command line option which will bring up the bus monitor, and at least tell me if you've probably deployed your services: -Derrai.bus.showmonitor=true Also, can you email me the log output from when your startup the application? On 2010-01-11, at 3:35 PM, Kevin Jordan wrote: Changing to a createCall and making a @Endpoint annotated method on the server seems to make it send something again: {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Items.getItem:RespondTo:1","PriorityProcessing":"1"} With a response of: [{"HeartBeat":null}] However, I still so nowhere where it passes the parameter I give it with: MessageBuilder.createCall().call("Items").endpoint("getItem", serialInput.getValue()).respondTo(Item.class, new RemoteCallback<Item>() { @Override public void callback(Item response) { //throw new UnsupportedOperationException("Not supported yet."); MessageBox.alert("Return",item.getSerialNumber().toString(),null); } }).noErrorHandling().sendNowWith(bus); From: errai-users-bounces(a)lists.jboss.org [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin Jordan Sent: Monday, January 11, 2010 1:46 PM To: 'Mike Brock' Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Made the changes specified in the userguide, but now it doesn’t send anything. I’m using the following: MessageBuilder.createMessage().toSubject("Items").signalling().with("SerialNumber", "Test").noErrorHandling().sendNowWith(bus); It still seems to be set up just fine since the in.erraiBus servlet is created and the client long polls it, but the code above doesn’t seem to send anything. I’m using the following way to make it for the DefaultBlockingServlet: <listener> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listener-class> </listener> Should I be using that? I figure it shouldn’t affect the client any though unless the servlet is incorrectly set up as a consequence, which it doesn’t seem to be since they communicate just fine for the initial setup. What should I look at to see why it’s not sending? From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 11, 2010 12:43 PM To: Kevin Jordan Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages You should be aware we have made changes and are retiring the use of the CommandMessage API. Be sure to read the documentation in the userguide/src/main/docbook/en/master.xml file. You can use: mvn jdocbook:generate to create an HTML file from the userguide/ directory. On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 2:56 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages I will check into this. We're still working on getting the AIO stuff sorted>Monday, January 11, 2010 8:59 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Hi Kevin, the compilation problems should be fixed already. On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: Yes, I am using trunk. Is there a more stable branch/version I should be using? I had updated again hoping it was just something with the time I checked out and then ran into the problems Heiko Braun ran into compiling it. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 8:52 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages What version of ErraiBus are you using? Are you getting it from trunk? On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: DefaultBlockingServlet seems to have the same effect. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 2:56 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages I will check into this. We're still working on getting the AIO stuff sorted, and I wouldn't consider the Tomcat or JBoss adapters to be production ready. You're best to use the DefaultBlockingServlet -- which will provide adequate performance for development while we get the AIO adapters squared away over the next few days. On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: I’m having trouble getting a message to go through using ErraiBus. I’m using this on the client side: CommandMessage msg = (CommandMessage) CommandMessage.create().toSubject("Items").set("SerialNumber", serialInput.getValue()); bus.conversationWith(msg, new MessageCallback() { @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); Item item = message.get(Item.class, "Item"); MessageBox.alert("Errai", item.getSerialNumber().toString(), null); } }); With this on the server side: @Service("Items") public class Items implements MessageCallback { private MessageBus bus; @Inject public Items(MessageBus bus) { this.bus = bus; System.out.println("Got a bus..."); } @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); System.out.println("Incoming message..."); Long serialNum = message.get(Long.class, "SerialNumber"); System.out.println(serialNum); Item item = new Item(); item.setSerialNumber(serialNum); ConversationMessage.create(message).set("Item",item).sendNowWith(bus); } } However, all it seems to send is: {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"temp:Conversation:2","PriorityProcessing":"1"} I don’t see where it actually sends my body or the subject that I fill out in my message. Nothing also gets to the Service class. Am I doing something wrong? I have Tomcat running NIO and everything else seems set up correctly. It will keep a GET connection open and do the POST of the JSON above, but nowhere does it seem to send what I want it to. I also seem to be getting these occasionally, usually on some of the first requests to in.erraiBus: java.lang.NullPointerException at org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(TomcatCometServlet.java:105) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unknown Source) at org.apache.catalina.core.StandardWrapperValve.event(Unknown Source) at org.apache.catalina.core.StandardContextValve.event(Unknown Source) at org.apache.catalina.core.StandardHostValve.event(Unknown Source) at org.apache.catalina.valves.ValveBase.event(Unknown Source) at org.apache.catalina.core.StandardEngineValve.event(Unknown Source) at org.apache.catalina.connector.CoyoteAdapter.event(Unknown Source) at org.apache.coyote.http11.Http11NioProcessor.event(Unknown Source) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.event(Unknown Source) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Can anyone point me at what I’m missing? _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users

I think I've found out one problem. Somehow Errai has trouble if your

is in an external jar, or in my case another Netbeans project. GWT will compile my project just fine, but it at least seems to be that once I go

another project/jar for my POJO it fails to get to my callback and does

behavior I've previously described. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 15, 2010 4:20 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Yes, that will work, of course. On 2010-01-15, at 4:59 PM, Kevin Jordan wrote: I haven't yet. But I'll try it and let you know if it works. So the default constructor provided by the JVM if you don't specify one won't work? From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 15, 2010 3:55 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Have you updated to trunk -- I think that will fix the InstantiationException? Any serializable class *must* have a default constructor. On 2010-01-15, at 4:48 PM, Kevin Jordan wrote: Well, I think I've figured it out on my callback problems. I went back

just passing a string back and forth and that worked. I then made a simpler POJO to pass back and forth with just implementing Serializable which didn't work (no callback call). I then added the annotation that I just saw in the docs and that didn't work (no callback call). I then removed

and the callback gets called, but it gets an error when it tries to get

POJO out of the message. Is there anything extra I need to do for POJOs? From: errai-users-bounces(a)lists.jboss.org [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin Jordan Sent: Thursday, January 14, 2010 4:21 PM To: 'Mike Brock' Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Whenever I do that, I seem to get: java.lang.InstantiationException: org.jboss.errai.bus.server.servlet.DefaultBlockingServlet at java.lang.Class.newInstance0(Class.java:340) at java.lang.Class.newInstance(Class.java:308) at org.apache.catalina.core.StandardWrapper.loadServlet(Unknown Source) at org.apache.catalina.core.StandardWrapper.load(Unknown Source) at org.apache.catalina.core.StandardContext.loadOnStartup(Unknown Source) at org.apache.catalina.core.StandardContext.start(Unknown Source) at

Source) at org.apache.catalina.core.ContainerBase.addChild(Unknown

at org.apache.catalina.core.StandardHost.addChild(Unknown Source) at

Source) at

Source) at

Source) at

Source) at

hildren(Unknown Source) at

hildren(Unknown Source) at

own Source) at java.lang.Thread.run(Thread.java:619) Even in a new project I've created to see if anything is interfering with Errai somehow. Trying TomcatCometServlet or ErraiAutoServlet also yields the same results as before in both cases. Using the listener/Guice

works. I've also gotten it so a callback works in my new minimal

So now I'm wondering if something else is interfering with it. I've got Spring Security protecting pretty much everything, although I think I've tried taking that out before and had the same effect. I've also got GXT (http://www.extjs.com/products/gxt/) in there. Along with Mule and SOAFaces, although SOAFaces can probably go away since I'll be communicating to Mule via Errai when that works so I can have better asynchronous communication and also push communication. I suppose what I'll try first is ripping out GXT since that's probably the most likely culprit in my mind. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 14, 2010 12:12 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages We will actually be removing the Guice filter as it's created problems

deploying on some appservers. We're falling back on directly declaring the servlet. So you might want to switch to directly declaring the DefaultBlockingServlet like so: <servlet <servlet-name>ErraiServlet</servlet-name

rvlet-class <load-on-startup>1</load-on-startup </servlet <servlet-mapping <servlet-name>ErraiServlet</servlet-name <url-pattern>*.erraiBus</url-pattern </servlet-mapping . On 2010-01-14, at 12:45 PM, Kevin Jordan wrote: Yes. It's still working the way it was before where I have to submit

than once and the response comes back on the POST but the callback

get called. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 14, 2010 11:44 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Are you still losing messages? On 2010-01-14, at 12:31 PM, Kevin Jordan wrote: Switching it back to the listener config seems to make it work again through the DefaultBlockingServlet. From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] Sent: Thursday, January 14, 2010 11:22 AM To: 'Mike Brock' Cc: &#39;errai-users(a)lists.jboss.org&#39; Subject: RE: [errai-users] Trouble sending messages Yeah, I'm using the NIO connector. And actually if I configure the TomcatCometServlet manually I get the same error again. I know that used to happen when I was accessing it through my AJP connected Apache instance, but now I'm accessing it directly through port 8443 on Tomcat. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 14, 2010 10:55 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Are you using the NIO connector in Tomcat? Errai by default will try to use Tomcat's AIO system, which requires that the NIO or APR connecter be

On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: I tried the AutoServlet and it seems to pick the TomcatCometServlet which makes it spin over and over on this message every time it tries to access it:

********************* ** PROBLEM! ** It appears something has been incorrectly configured. In order to use ErraiBus ** on Tomcat, you must ensure that you are using the NIO or APR

Also ** make sure that you have added these lines to your WEB-INF/web.xml

** --- ** <servlet ** <servlet-name>TomcatErraiServlet</servlet-name **

t-class ** <load-on-startup>1</load-on-startup ** </servlet ** ** <servlet-mapping ** <servlet-name>TomcatErraiServlet</servlet-name ** <url-pattern>*.erraiBus</url-pattern ** </servlet-mapping ** --- ** If you have the following lines in your WEB-INF/web.xml, you must comment or remove them: ** --- ** <listener **

s ** </listener

********************* From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 14, 2010 10:06 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages By the way, if you want, we're on IRC on irc.freenode.net in channel

-- I'm "cbrock" on there if you want help troubleshooting directly. On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, and IE on Windows 7. I'm using Tomcat. I'll try the AutoServlet to see if it makes a difference. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Wednesday, January 13, 2010 8:35 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages If you update to the latest version of trunk, simply get rid of the listener and replace your web.xml config with this: <servlet <servlet-name>ErraiAutoServlet</servlet-name

class <load-on-startup>1</load-on-startup </servlet <servlet-mapping <servlet-name>ErraiAutoServlet</servlet-name <url-pattern>*.erraiBus</url-pattern </servlet-mapping This problem you're having is curious, though. We haven't seen it in our internal testing. Can you tell me what browser, what appserver, and what OS you're on? On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: I'm using the following on the client side: bus.subscribe("ItemFound", new MessageCallback() { @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); MessageBox.alert("Success", "In

null); /*Map<String,Object> parts = message.getParts(); Set<String> keys = parts.keySet(); for (String key : keys) { MessageBox.alert("Key",key,null); }*/ //Item item = message.get(Item.class, "Item"); //MessageBox.alert("Return", item.getSerialNumber().toString(), null); } });

arts.ReplyTo, "ItemFound").with("SerialNumber", serialInput.getValue().toString()).errorsHandledBy(new ErrorCallback() { @Override public boolean error(Message message,

throwable) { //throw new UnsupportedOperationException("Not supported yet."); MessageBox.alert("Error", throwable.getMessage(), null); return true; } }).sendNowWith(bus); Which sends: {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489"} Although I've now noticed that it takes 2 tries to get it to send that

a 3rd one to get the response back for the first one. Server portion looks like: @Service("Items") public class Items implements MessageCallback { private MessageBus bus; @Inject public Items(MessageBus bus) { this.bus = bus; System.out.println("Got a bus..."); } @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported

System.out.println("Incoming message..."); String serialNum = message.get(String.class, "SerialNumber"); System.out.println(serialNum); Item item = new Item(); item.setSerialNumber(Long.parseLong(serialNum));

th("Item", item).errorsHandledBy(new ErrorCallback() { @Override public boolean error(Message message, Throwable

{ //throw new UnsupportedOperationException("Not supported yet."); throwable.printStackTrace(); return true; } }).sendNowWith(bus); } } Response on the second POST is:

":"ItemFound"}}] All others seem to get: [{"HeartBeat":null}] And on the first time I try to submit, it still seems to be kind of

type of paradigm and we haven't ever experienced any dropped messages.

you provide me some examples of your code so we can troubleshoot what's going on? On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: The MessageParts.ReplyTo was what I was missing in there. However, my callback doesn't seem to be called. I get something back when my request is POSTed, but it never seems to call my callback. They do seem to work sometimes though. I had accidentally named my callback subject and the server subject the same and when I created a message to that subject,

the client callback and the server callback were called correctly. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Tuesday, January 12, 2010 9:07 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages The sender needs to create a listening service that can be replied to.

() .with(MessageParts.ReplyTo, "MyResponseSvc") .with("SomeMessagePart", "Foo") .noErrorHandling() .sendNowWith(bus); ... //server-side code MessageBuilder.createConversation(message) .subjectProvided().signalling() .with("MyResponseData", "Bar") .noErrorHandling() .sendNowWith(bus); ... Note: we may make this more straight forward in the future, such as with the RPC API. On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: I won't be able to use the Swing monitor on the server I'm deploying to since it has no interface. However, I did start enabling logging in various places and it does seem that my services weren't getting started. I was lacking an ErraiApp.properties which I guess is used as the root for

it should start looking for services. After adding that, they started

stuff started to go through. Does the client keep a record of services

something then? Why wouldn't it try to contact the service and then fail that it couldn't find it? Also, looking at the revised Message API, how do you listen for the reply in a conversation? Do I need to create a separate listener? Before you

tItem:RespondTo:1","PriorityProcessing":"1"} With a response of: [{"HeartBeat":null}] However, I still so nowhere where it passes the parameter I give it with: MessageBuilder.createCall().call("Items").endpoint("getItem", serialInput.getValue()).respondTo(Item.class, new RemoteCallback<Item>()

unless the servlet is incorrectly set up as a consequence, which it

seem to be since they communicate just fine for the initial setup. What should I look at to see why it's not sending? From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 11, 2010 12:43 PM To: Kevin Jordan Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages You should be aware we have made changes and are retiring the use of the CommandMessage API. Be sure to read the documentation in the userguide/src/main/docbook/en/master.xml file. You can use: mvn jdocbook:generate to create an HTML file from the userguide/ directory. On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 2:56 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages I will check into this. We're still working on getting the AIO stuff sorted>Monday, January 11, 2010 8:59 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Hi Kevin, the compilation problems should be fixed already. On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: Yes, I am using trunk. Is there a more stable branch/version I should be using? I had updated again hoping it was just something with the time I checked out and then ran into the problems Heiko Braun ran into compiling it. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 8:52 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages What version of ErraiBus are you using? Are you getting it from trunk? On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: DefaultBlockingServlet seems to have the same effect. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Friday, January 08, 2010 2:56 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages I will check into this. We're still working on getting the AIO stuff sorted, and I wouldn't consider the Tomcat or JBoss adapters to be production ready. You're best to use the DefaultBlockingServlet -- which will provide adequate performance for development while we get the AIO adapters squared away over the next few days. On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: I'm having trouble getting a message to go through using ErraiBus. I'm using this on the client side: CommandMessage msg = (CommandMessage) CommandMessage.create().toSubject("Items").set("SerialNumber", serialInput.getValue()); bus.conversationWith(msg, new MessageCallback() { @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported yet."); Item item = message.get(Item.class, "Item"); MessageBox.alert("Errai", item.getSerialNumber().toString(), null); } }); With this on the server side: @Service("Items") public class Items implements MessageCallback { private MessageBus bus; @Inject public Items(MessageBus bus) { this.bus = bus; System.out.println("Got a bus..."); } @Override public void callback(Message message) { //throw new UnsupportedOperationException("Not supported

versation:2","PriorityProcessing":"1"} I don't see where it actually sends my body or the subject that I fill

in my message. Nothing also gets to the Service class. Am I doing something wrong? I have Tomcat running NIO and everything else seems set up correctly. It will keep a GET connection open and do the POST of the

above, but nowhere does it seem to send what I want it to. I also seem

n Source) at org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unknown Source) at org.apache.catalina.core.StandardWrapperValve.event(Unknown Source) at org.apache.catalina.core.StandardContextValve.event(Unknown Source) at org.apache.catalina.core.StandardHostValve.event(Unknown

nown Source) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknown

08) at java.lang.Thread.run(Thread.java:619) Can anyone point me at what I'm missing? _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users

Not sure what you mean by that, but I'm using Netbeans and my domain POJOs

-----Original Message----- From: Thomas SEGISMONT [mailto:tsegismont@gmail.com] Sent: Monday, January 18, 2010 10:12 AM To: Kevin Jordan Cc: Mike Brock; errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Have you tried to include your project/jar source code in your launch

It sounds more like a GWT configuration problem than an Errai one. If you're using Maven to build your project, you can read this : http://mojo.codehaus.org/gwt-maven-plugin/user-guide/multiproject.html Thomas On Mon, 18 Jan 2010 09:50:40 -0600, "Kevin Jordan" <kevin.jordan(a)xteconline.com&gt; wrote: > I think I've found out one problem. Somehow Errai has trouble if > your POJO > is in an external jar, or in my case another Netbeans project. GWT > will compile my project just fine, but it at least seems to be that > once I go to > another project/jar for my POJO it fails to get to my callback and > does the > behavior I've previously described. > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Friday, January 15, 2010 4:20 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > Yes, that will work, of course. > > > > On 2010-01-15, at 4:59 PM, Kevin Jordan wrote: > > > > > > I haven't yet. But I'll try it and let you know if it works. > > > > So the default constructor provided by the JVM if you don't specify > one won't work? > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Friday, January 15, 2010 3:55 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > Have you updated to trunk -- I think that will fix the > InstantiationException? Any serializable class *must* have a default > constructor. > > > > On 2010-01-15, at 4:48 PM, Kevin Jordan wrote: > > > > > > > Well, I think I've figured it out on my callback problems. I went > back to > just passing a string back and forth and that worked. I then made a > simpler POJO to pass back and forth with just implementing > Serializable which didn't work (no callback call). I then added the > annotation that I just saw in the docs and that didn't work (no > callback call). I then removed Serializable > and the callback gets called, but it gets an error when it tries to > get the > POJO out of the message. > > > > Is there anything extra I need to do for POJOs? > > > > From: errai-users-bounces(a)lists.jboss.org > [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin > Jordan > Sent: Thursday, January 14, 2010 4:21 PM > To: 'Mike Brock' > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > Whenever I do that, I seem to get: > > java.lang.InstantiationException: > org.jboss.errai.bus.server.servlet.DefaultBlockingServlet > > at java.lang.Class.newInstance0(Class.java:340) > > at java.lang.Class.newInstance(Class.java:308) > > at > org.apache.catalina.core.StandardWrapper.loadServlet(Unknown > Source) > > at org.apache.catalina.core.StandardWrapper.load(Unknown > Source) > > at > org.apache.catalina.core.StandardContext.loadOnStartup(Unknown > Source) > > at org.apache.catalina.core.StandardContext.start(Unknown > Source) > > at org.apache.catalina.core.ContainerBase.addChildInternal(Unknown > Source) > > at org.apache.catalina.core.ContainerBase.addChild(Unknown Source) > > at org.apache.catalina.core.StandardHost.addChild(Unknown > Source) > > at org.apache.catalina.startup.HostConfig.deployDescriptor(Unknown > Source) > > at org.apache.catalina.startup.HostConfig.deployDescriptors(Unknown > Source) > > at org.apache.catalina.startup.HostConfig.deployApps(Unknown > Source) > > at org.apache.catalina.startup.HostConfig.check(Unknown > Source) > > at > org.apache.catalina.startup.HostConfig.lifecycleEvent(Unknown > Source) > > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknown > Source) > > at org.apache.catalina.core.ContainerBase.backgroundProcess(Unknown > Source) > > at > org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.pr ocessC > hildren(Unknown Source) > > at > org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.pr ocessC > hildren(Unknown Source) > > at > org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.ru n(Unkn > own Source) > > at java.lang.Thread.run(Thread.java:619) > > > > Even in a new project I've created to see if anything is interfering > with Errai somehow. Trying TomcatCometServlet or ErraiAutoServlet > also yields the same results as before in both cases. Using the > listener/Guice filter > works. I've also gotten it so a callback works in my new minimal project. > So now I'm wondering if something else is interfering with it. I've > got Spring Security protecting pretty much everything, although I > think I've tried taking that out before and had the same effect. > I've also got GXT > (http://www.extjs.com/products/gxt/) in there. Along with Mule and > SOAFaces, although SOAFaces can probably go away since I'll be > communicating to Mule via Errai when that works so I can have better > asynchronous communication and also push communication. I suppose > what I'll try first is ripping out GXT since that's probably the most > likely culprit in my mind. > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Thursday, January 14, 2010 12:12 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > We will actually be removing the Guice filter as it's created > problems for > deploying on some appservers. We're falling back on directly declaring > the > servlet. So you might want to switch to directly declaring the > DefaultBlockingServlet like so: > > > > <servlet> > > <servlet-name>ErraiServlet</servlet-name> > > > <servlet-class>org.jboss.errai.bus.server.servlet.DefaultBlockingServl et</se > rvlet-class> > > <load-on-startup>1</load-on-startup> > > </servlet> > > > > <servlet-mapping> > > <servlet-name>ErraiServlet</servlet-name> > > <url-pattern>*.erraiBus</url-pattern> > > </servlet-mapping> > > > > . > > > > On 2010-01-14, at 12:45 PM, Kevin Jordan wrote: > > > > Yes. It's still working the way it was before where I have to submit more > than once and the response comes back on the POST but the callback doesn't > get called. > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Thursday, January 14, 2010 11:44 AM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > Are you still losing messages? > > > > On 2010-01-14, at 12:31 PM, Kevin Jordan wrote: > > > > > > > > Switching it back to the listener config seems to make it work again > through the DefaultBlockingServlet. > > > > From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] > Sent: Thursday, January 14, 2010 11:22 AM > To: 'Mike Brock' > Cc: &#39;errai-users(a)lists.jboss.org&#39; > Subject: RE: [errai-users] Trouble sending messages > > > > Yeah, I'm using the NIO connector. And actually if I configure the > TomcatCometServlet manually I get the same error again. I know that > used to happen when I was accessing it through my AJP connected > Apache instance, but now I'm accessing it directly through port 8443 > on Tomcat. > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Thursday, January 14, 2010 10:55 AM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > Are you using the NIO connector in Tomcat? Errai by default will try > to use Tomcat's AIO system, which requires that the NIO or APR > connecter be used. > > > > On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: > > > > I tried the AutoServlet and it seems to pick the TomcatCometServlet > which makes it spin over and over on this message every time it tries > to access > it: > > ********************************************************************** ****** > ********************* > > ** PROBLEM! > > ** It appears something has been incorrectly configured. In order to > use ErraiBus > > ** on Tomcat, you must ensure that you are using the NIO or APR connector. > Also > > ** make sure that you have added these lines to your WEB-INF/web.xml file: > > ** --- > > ** <servlet> > > ** <servlet-name>TomcatErraiServlet</servlet-name> > > ** > <servlet-class>org.jboss.errai.bus.server.servlet.TomcatCometServlet</ servle > t-class> > > ** <load-on-startup>1</load-on-startup> > > ** </servlet> > > ** > > ** <servlet-mapping> > > ** <servlet-name>TomcatErraiServlet</servlet-name> > > ** <url-pattern>*.erraiBus</url-pattern> > > ** </servlet-mapping> > > ** --- > > ** If you have the following lines in your WEB-INF/web.xml, you must > comment or remove them: > > ** --- > > ** <listener> > > ** > <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listene r-clas > s> > > ** </listener> > > ********************************************************************** ****** > ********************* > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Thursday, January 14, 2010 10:06 AM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > By the way, if you want, we're on IRC on irc.freenode.net in channel #errai > -- I'm "cbrock" on there if you want help troubleshooting directly. > > > > On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: > > > > > > > > > It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, and IE > on Windows 7. I'm using Tomcat. > > > > I'll try the AutoServlet to see if it makes a difference. > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Wednesday, January 13, 2010 8:35 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > If you update to the latest version of trunk, simply get rid of the > listener and replace your web.xml config with this: > > > > <servlet> > > <servlet-name>ErraiAutoServlet</servlet-name> > > > <servlet-class>org.jboss.errai.bus.server.servlet.ErraiAutoServlet</se rvlet- > class> > > <load-on-startup>1</load-on-startup> > > </servlet> > > > > <servlet-mapping> > > <servlet-name>ErraiAutoServlet</servlet-name> > > <url-pattern>*.erraiBus</url-pattern> > > </servlet-mapping> > > > > This problem you're having is curious, though. We haven't seen it in > our internal testing. Can you tell me what browser, what appserver, > and what OS you're on? > > > > On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: > > > > > > > > > > I'm using the following on the client side: > > bus.subscribe("ItemFound", new MessageCallback() { > > > > @Override > > public void callback(Message message) { > > //throw new > UnsupportedOperationException("Not supported yet."); > > MessageBox.alert("Success", "In Callback", > null); > > /*Map<String,Object> parts = > message.getParts(); > > Set<String> keys = parts.keySet(); > > for (String key : keys) { > > MessageBox.alert("Key",key,null); > > }*/ > > //Item item = message.get(Item.class, > "Item"); > > //MessageBox.alert("Return", > item.getSerialNumber().toString(), null); > > } > > }); > > > MessageBuilder.createMessage().toSubject("Items").signalling().with(Me ssageP > arts.ReplyTo, "ItemFound").with("SerialNumber", > serialInput.getValue().toString()).errorsHandledBy(new > ErrorCallback() { > > > > @Override > > public boolean error(Message message, Throwable > throwable) { > > //throw new > UnsupportedOperationException("Not supported yet."); > > MessageBox.alert("Error", > throwable.getMessage(), null); > > return true; > > } > > }).sendNowWith(bus); > > > > Which sends: > > {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489"} > > > > Although I've now noticed that it takes 2 tries to get it to send > that and > a > 3rd one to get the response back for the first one. > > > > Server portion looks like: > > @Service("Items") > > public class Items implements MessageCallback { > > private MessageBus bus; > > > > @Inject > > public Items(MessageBus bus) { > > this.bus = bus; > > System.out.println("Got a bus..."); > > } > > > > @Override > > public void callback(Message message) { > > //throw new UnsupportedOperationException("Not supported yet."); > > System.out.println("Incoming message..."); > > String serialNum = message.get(String.class, > "SerialNumber"); > > System.out.println(serialNum); > > Item item = new Item(); > > item.setSerialNumber(Long.parseLong(serialNum)); > > > MessageBuilder.createConversation(message).subjectProvided().signallin g().wi > th("Item", item).errorsHandledBy(new ErrorCallback() { > > > > @Override > > public boolean error(Message message, Throwable throwable) > { > > //throw new UnsupportedOperationException("Not > supported yet."); > > throwable.printStackTrace(); > > return true; > > } > > }).sendNowWith(bus); > > } > > } > > > > Response on the second POST is: > > [{"ItemFound":{"Item":{__EncodedType:'com.xteconline.system.Item',id:n ull,se >

> null,oemSerial:null,manufacturer:null,status:null,itemInfos:null},"ToS ubject > ":"ItemFound"}}] > > > > All others seem to get: > > [{"HeartBeat":null}] > > > > And on the first time I try to submit, it still seems to be kind of setting > up stuff since it sends: > > {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Se rverBu >

> ServerBus","Subject":"AuthorizationService","PriorityProcessing":"1"}| |{"Com > mandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"ClientN egotia > tionService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscrib e","To > Subject":"ServerBus","Subject":"ServerEchoService","PriorityProcessing ":"1"} > ||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" ||Cl ||ient > Bus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subje ct":"C >

> Subject":"Items"}||{"CommandType":"RemoteSubscribe","ToSubject":"Serve rBus", > "Subject":"ServerBus"}||{"CommandType":"RemoteSubscribe","ToSubject":" Server > Bus","Subject":"AuthorizationService"}||{"CommandType":"RemoteSubscrib e","To >

> RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService" > } > > > > And > > > > {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"It emFoun > d","PriorityProcessing":"1"} > > > > But doesn't send my stuff until I submit again. > > > > And about the only other relevant thing I can think of for Errai is > the servlet config: > > <listener> > > > <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listene r-clas > s> > > </listener> > > > > Which I believe sets up the DefaultBlockingServlet. > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Tuesday, January 12, 2010 11:48 AM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > We have a fairly significant application that makes extensive use of this > type of paradigm and we haven't ever experienced any dropped messages. Can > you provide me some examples of your code so we can troubleshoot > what's going on? > > > > On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: > > > > > > > > > > > The MessageParts.ReplyTo was what I was missing in there. However, > my callback doesn't seem to be called. I get something back when my > request is POSTed, but it never seems to call my callback. They do > seem to work sometimes though. I had accidentally named my callback > subject and the server subject the same and when I created a message > to that subject, both > the client callback and the server callback were called correctly. > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Tuesday, January 12, 2010 9:07 AM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > The sender needs to create a listening service that can be replied to. The > best way to do this is like so: > > > > > > //client-side code > > bus.subscribe("MyResponseSvc", > > new MessageCallback() { > > public void callback(Message msg) { > > ... > > } > > } > > ); > > > > MessageBuilder.createMessage().toSubject("ConversationalService").sign alling > () > > .with(MessageParts.ReplyTo, "MyResponseSvc") > > .with("SomeMessagePart", "Foo") > > .noErrorHandling() > > .sendNowWith(bus); > > > > ... > > //server-side code > > > > MessageBuilder.createConversation(message) > > .subjectProvided().signalling() > > .with("MyResponseData", "Bar") > > .noErrorHandling() > > .sendNowWith(bus); > > > > ... > > > > Note: we may make this more straight forward in the future, such as > with the RPC API. > > > > > > > > On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: > > > > > > > > > > > > I won't be able to use the Swing monitor on the server I'm deploying > to since it has no interface. However, I did start enabling logging > in various places and it does seem that my services weren't getting > started. I was lacking an ErraiApp.properties which I guess is used > as the root for where > it should start looking for services. After adding that, they > started and > stuff started to go through. Does the client keep a record of > services or > something then? Why wouldn't it try to contact the service and then > fail that it couldn't find it? > > > > Also, looking at the revised Message API, how do you listen for the > reply in a conversation? Do I need to create a separate listener? > Before you could > specify a MessageCallback to get the response in the conversation, > but I can't find anywhere in the call chain to do that and it's not > covered in the SVN book. > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Monday, January 11, 2010 3:16 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > Kevin, > > > > I'm not sure how you're launching your app, but can you provide this > command line option which will bring up the bus monitor, and at least > tell me if you've probably deployed your services: > -Derrai.bus.showmonitor=true > > > > Also, can you email me the log output from when your startup the > application? > > > > On 2010-01-11, at 3:35 PM, Kevin Jordan wrote: > > > > > > > > > > > > > Changing to a createCall and making a @Endpoint annotated method on > the server seems to make it send something again: > > {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"It ems.ge > tItem:RespondTo:1","PriorityProcessing":"1"} > > > > With a response of: > > [{"HeartBeat":null}] > > > > However, I still so nowhere where it passes the parameter I give it with: > > MessageBuilder.createCall().call("Items").endpoint("getItem", > serialInput.getValue()).respondTo(Item.class, new > RemoteCallback<Item>() { > > > > @Override > > public void callback(Item response) { > > //throw new > UnsupportedOperationException("Not supported yet."); > > > MessageBox.alert("Return",item.getSerialNumber().toString(),null); > > } > > > > }).noErrorHandling().sendNowWith(bus); > > > > > > > > From: errai-users-bounces(a)lists.jboss.org > [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin > Jordan > Sent: Monday, January 11, 2010 1:46 PM > To: 'Mike Brock' > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > Made the changes specified in the userguide, but now it doesn't send > anything. I'm using the following: > > MessageBuilder.createMessage().toSubject("Items").signalling().with("S erialN > umber", "Test").noErrorHandling().sendNowWith(bus); > > > > It still seems to be set up just fine since the in.erraiBus servlet > is created and the client long polls it, but the code above doesn't > seem to send anything. I'm using the following way to make it for > the > DefaultBlockingServlet: > > <listener> > > > <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listene r-clas > s> > > </listener> > > > > Should I be using that? I figure it shouldn't affect the client any though > unless the servlet is incorrectly set up as a consequence, which it doesn't > seem to be since they communicate just fine for the initial setup. > What should I look at to see why it's not sending? > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Monday, January 11, 2010 12:43 PM > To: Kevin Jordan > Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > You should be aware we have made changes and are retiring the use of > the CommandMessage API. Be sure to read the documentation in the > userguide/src/main/docbook/en/master.xml file. You can use: mvn > jdocbook:generate to create an HTML file from the userguide/ directory. > > > > On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Friday, January 08, 2010 2:56 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > I will check into this. We're still working on getting the AIO stuff > sorted>Monday, January 11, 2010 8:59 AM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > > > Hi Kevin, the compilation problems should be fixed already. > > > > > > On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: > > > > > > > > > > > > > > Yes, I am using trunk. Is there a more stable branch/version I > should be using? I had updated again hoping it was just something > with the time I checked out and then ran into the problems Heiko > Braun ran into compiling it. > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Friday, January 08, 2010 8:52 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > What version of ErraiBus are you using? Are you getting it from trunk? > > > > On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: > > > > DefaultBlockingServlet seems to have the same effect. > > > > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Friday, January 08, 2010 2:56 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > > > I will check into this. We're still working on getting the AIO stuff > sorted, and I wouldn't consider the Tomcat or JBoss adapters to be > production ready. You're best to use the DefaultBlockingServlet -- > which will provide adequate performance for development while we get > the AIO adapters squared away over the next few days. > > > > On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: > > > > > > > > > > > > > > > I'm having trouble getting a message to go through using ErraiBus. > I'm using this on the client side: > > CommandMessage msg = (CommandMessage) > CommandMessage.create().toSubject("Items").set("SerialNumber", > serialInput.getValue()); > > bus.conversationWith(msg, new MessageCallback() { > > > > @Override > > public void callback(Message message) { > > //throw new > UnsupportedOperationException("Not supported yet."); > > Item item = message.get(Item.class, > "Item"); > > MessageBox.alert("Errai", > item.getSerialNumber().toString(), null); > > } > > }); > > > > With this on the server side: > > @Service("Items") > > public class Items implements MessageCallback { > > private MessageBus bus; > > > > @Inject > > public Items(MessageBus bus) { > > this.bus = bus; > > System.out.println("Got a bus..."); > > } > > > > @Override > > public void callback(Message message) { > > //throw new UnsupportedOperationException("Not supported yet."); > > System.out.println("Incoming message..."); > > Long serialNum = message.get(Long.class, "SerialNumber"); > > System.out.println(serialNum); > > Item item = new Item(); > > item.setSerialNumber(serialNum); > > > ConversationMessage.create(message).set("Item",item).sendNowWith(bus) > ; > > } > > > > } > > > > However, all it seems to send is: > > {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"te mp:Con > versation:2","PriorityProcessing":"1"} > > > > I don't see where it actually sends my body or the subject that I > fill out > in my message. Nothing also gets to the Service class. Am I doing > something wrong? I have Tomcat running NIO and everything else seems > set up correctly. It will keep a GET connection open and do the POST > of the JSON > above, but nowhere does it seem to send what I want it to. I also > seem to > be getting these occasionally, usually on some of the first requests > to > in.erraiBus: > > java.lang.NullPointerException > > at > org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(TomcatCome tServl > et.java:105) > > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent( Unknow > n Source) > > at > org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unknown > Source) > > at org.apache.catalina.core.StandardWrapperValve.event(Unknown > Source) > > at org.apache.catalina.core.StandardContextValve.event(Unknown > Source) > > at org.apache.catalina.core.StandardHostValve.event(Unknown Source) > > at org.apache.catalina.valves.ValveBase.event(Unknown Source) > > at org.apache.catalina.core.StandardEngineValve.event(Unknown > Source) > > at org.apache.catalina.connector.CoyoteAdapter.event(Unknown > Source) > > at org.apache.coyote.http11.Http11NioProcessor.event(Unknown > Source) > > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.eve nt(Unk > nown Source) > > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknown Source) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu tor.ja > va:886) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. java:9 > 08) > > at java.lang.Thread.run(Thread.java:619) > > > > Can anyone point me at what I'm missing? > > _______________________________________________ > errai-users mailing list > errai-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/errai-users > > > > > > _______________________________________________ > errai-users mailing list > errai-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/errai-users > > > > _______________________________________________ > errai-users mailing list > errai-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/errai-users > > > > > > > > _______________________________________________ > errai-users mailing list > errai-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/errai-users

Is there any logging I have to set up for a particular class or package or any configuration I have to do for that? Normally, even when it works, the only output I see from Errai while compiling is: 0 [main] INFO Configuration - configuration scan targets 0 [main] INFO Configuration - ->

0-SNAPSHOT.jar 0 [main] INFO Configuration - -> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\src\java 0 [main] INFO Configuration - -> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB-INF\ classe s 63 [main] INFO Configuration - caching context 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-persist ence-1 .0-SNAPSHOT.jar:*' 188 [main] INFO Configuration - caching context 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB-INF \class es' And I'm not even really using persistence (i.e. it's not inherited in my .gwt.xml, but somehow it's getting run anyways either via ErraiBus or ErraiCommons). -----Original Message----- From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 18, 2010 10:39 AM To: Kevin Jordan Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages This is an interesting theory. You should be able to determine whether the stub is generated or not since at compile-time the Errai generators show log output for each stub. You should see a log output that says: "Generated marshaller/demarshaller for: <classname>" for each entity you've annotated. On 2010-01-18, at 11:32 AM, Kevin Jordan wrote: > Not sure what you mean by that, but I'm using Netbeans and my domain > POJOs are in a separate project which gets included by my web project. The projects compile file and I've used my domain POJOs via SOAFace's UniversalClient and regular GWT-RPC before without issues. And they get put across the wire with Errai, it's just when the class is in a separate project that there seems to be a problem and my callback isn't called. So I'm wondering if it's an issue with the stub getting

> > -----Original Message----- > From: Thomas SEGISMONT [mailto:tsegismont@gmail.com] > Sent: Monday, January 18, 2010 10:12 AM > To: Kevin Jordan > Cc: Mike Brock; errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > Have you tried to include your project/jar source code in your launch configuration ? > > It sounds more like a GWT configuration problem than an Errai one. > > If you're using Maven to build your project, you can read this : > http://mojo.codehaus.org/gwt-maven-plugin/user-guide/multiproject.htm > l > > Thomas > > On Mon, 18 Jan 2010 09:50:40 -0600, "Kevin Jordan" > <kevin.jordan(a)xteconline.com&gt; wrote: >> I think I've found out one problem. Somehow Errai has trouble if >> your > POJO >> is in an external jar, or in my case another Netbeans project. GWT >> will compile my project just fine, but it at least seems to be that >> once I go > to >> another project/jar for my POJO it fails to get to my callback and >> does > the >> behavior I've previously described. >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Friday, January 15, 2010 4:20 PM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> Yes, that will work, of course. >> >> >> >> On 2010-01-15, at 4:59 PM, Kevin Jordan wrote: >> >> >> >> >> >> I haven't yet. But I'll try it and let you know if it works. >> >> >> >> So the default constructor provided by the JVM if you don't specify >> one won't work? >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Friday, January 15, 2010 3:55 PM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> Have you updated to trunk -- I think that will fix the >> InstantiationException? Any serializable class *must* have a >> default constructor. >> >> >> >> On 2010-01-15, at 4:48 PM, Kevin Jordan wrote: >> >> >> >> >> >> >> Well, I think I've figured it out on my callback problems. I went >> back > to >> just passing a string back and forth and that worked. I then made a >> simpler POJO to pass back and forth with just implementing >> Serializable which didn't work (no callback call). I then added the >> annotation that I just saw in the docs and that didn't work (no >> callback call). I then removed > Serializable >> and the callback gets called, but it gets an error when it tries to >> get > the >> POJO out of the message. >> >> >> >> Is there anything extra I need to do for POJOs? >> >> >> >> From: errai-users-bounces(a)lists.jboss.org >> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >> Jordan >> Sent: Thursday, January 14, 2010 4:21 PM >> To: 'Mike Brock' >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> Whenever I do that, I seem to get: >> >> java.lang.InstantiationException: >> org.jboss.errai.bus.server.servlet.DefaultBlockingServlet >> >> at java.lang.Class.newInstance0(Class.java:340) >> >> at java.lang.Class.newInstance(Class.java:308) >> >> at >> org.apache.catalina.core.StandardWrapper.loadServlet(Unknown >> Source) >> >> at org.apache.catalina.core.StandardWrapper.load(Unknown >> Source) >> >> at >> org.apache.catalina.core.StandardContext.loadOnStartup(Unknown >> Source) >> >> at org.apache.catalina.core.StandardContext.start(Unknown >> Source) >> >> at > org.apache.catalina.core.ContainerBase.addChildInternal(Unknown >> Source) >> >> at org.apache.catalina.core.ContainerBase.addChild(Unknown > Source) >> >> at org.apache.catalina.core.StandardHost.addChild(Unknown >> Source) >> >> at > org.apache.catalina.startup.HostConfig.deployDescriptor(Unknown >> Source) >> >> at > org.apache.catalina.startup.HostConfig.deployDescriptors(Unknown >> Source) >> >> at org.apache.catalina.startup.HostConfig.deployApps(Unknown >> Source) >> >> at org.apache.catalina.startup.HostConfig.check(Unknown >> Source) >> >> at >> org.apache.catalina.startup.HostConfig.lifecycleEvent(Unknown >> Source) >> >> at >> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknown >> Source) >> >> at > org.apache.catalina.core.ContainerBase.backgroundProcess(Unknown >> Source) >> >> at >> > org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p > r > ocessC >> hildren(Unknown Source) >> >> at >> > org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p > r > ocessC >> hildren(Unknown Source) >> >> at >> > org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.r > u > n(Unkn >> own Source) >> >> at java.lang.Thread.run(Thread.java:619) >> >> >> >> Even in a new project I've created to see if anything is interfering >> with Errai somehow. Trying TomcatCometServlet or ErraiAutoServlet >> also yields the same results as before in both cases. Using the >> listener/Guice > filter >> works. I've also gotten it so a callback works in my new minimal > project. >> So now I'm wondering if something else is interfering with it. I've >> got Spring Security protecting pretty much everything, although I >> think I've tried taking that out before and had the same effect. >> I've also got GXT >> (http://www.extjs.com/products/gxt/) in there. Along with Mule and >> SOAFaces, although SOAFaces can probably go away since I'll be >> communicating to Mule via Errai when that works so I can have better >> asynchronous communication and also push communication. I suppose >> what I'll try first is ripping out GXT since that's probably the >> most likely culprit in my mind. >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Thursday, January 14, 2010 12:12 PM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> We will actually be removing the Guice filter as it's created >> problems > for >> deploying on some appservers. We're falling back on directly declaring >> the >> servlet. So you might want to switch to directly declaring the >> DefaultBlockingServlet like so: >> >> >> >> <servlet> >> >> <servlet-name>ErraiServlet</servlet-name> >> >> >> > <servlet-class>org.jboss.errai.bus.server.servlet.DefaultBlockingServ > l > et</se >> rvlet-class> >> >> <load-on-startup>1</load-on-startup> >> >> </servlet> >> >> >> >> <servlet-mapping> >> >> <servlet-name>ErraiServlet</servlet-name> >> >> <url-pattern>*.erraiBus</url-pattern> >> >> </servlet-mapping> >> >> >> >> . >> >> >> >> On 2010-01-14, at 12:45 PM, Kevin Jordan wrote: >> >> >> >> Yes. It's still working the way it was before where I have to >> submit > more >> than once and the response comes back on the POST but the callback > doesn't >> get called. >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Thursday, January 14, 2010 11:44 AM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> Are you still losing messages? >> >> >> >> On 2010-01-14, at 12:31 PM, Kevin Jordan wrote: >> >> >> >> >> >> >> >> Switching it back to the listener config seems to make it work again >> through the DefaultBlockingServlet. >> >> >> >> From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] >> Sent: Thursday, January 14, 2010 11:22 AM >> To: 'Mike Brock' >> Cc: &#39;errai-users(a)lists.jboss.org&#39; >> Subject: RE: [errai-users] Trouble sending messages >> >> >> >> Yeah, I'm using the NIO connector. And actually if I configure the >> TomcatCometServlet manually I get the same error again. I know that >> used to happen when I was accessing it through my AJP connected >> Apache instance, but now I'm accessing it directly through port 8443 >> on Tomcat. >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Thursday, January 14, 2010 10:55 AM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> Are you using the NIO connector in Tomcat? Errai by default will >> try to use Tomcat's AIO system, which requires that the NIO or APR >> connecter be > used. >> >> >> >> On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: >> >> >> >> I tried the AutoServlet and it seems to pick the TomcatCometServlet >> which makes it spin over and over on this message every time it >> tries to access >> it: >> >> > ********************************************************************* > * > ****** >> ********************* >> >> ** PROBLEM! >> >> ** It appears something has been incorrectly configured. In order to >> use ErraiBus >> >> ** on Tomcat, you must ensure that you are using the NIO or APR > connector. >> Also >> >> ** make sure that you have added these lines to your WEB-INF/web.xml > file: >> >> ** --- >> >> ** <servlet> >> >> ** <servlet-name>TomcatErraiServlet</servlet-name> >> >> ** >> > <servlet-class>org.jboss.errai.bus.server.servlet.TomcatCometServlet< > / > servle >> t-class> >> >> ** <load-on-startup>1</load-on-startup> >> >> ** </servlet> >> >> ** >> >> ** <servlet-mapping> >> >> ** <servlet-name>TomcatErraiServlet</servlet-name> >> >> ** <url-pattern>*.erraiBus</url-pattern> >> >> ** </servlet-mapping> >> >> ** --- >> >> ** If you have the following lines in your WEB-INF/web.xml, you must >> comment or remove them: >> >> ** --- >> >> ** <listener> >> >> ** >> > <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listen > e > r-clas >> s> >> >> ** </listener> >> >> > ********************************************************************* > * > ****** >> ********************* >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Thursday, January 14, 2010 10:06 AM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> By the way, if you want, we're on IRC on irc.freenode.net in channel > #errai >> -- I'm "cbrock" on there if you want help troubleshooting directly. >> >> >> >> On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: >> >> >> >> >> >> >> >> >> It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, and IE >> on Windows 7. I'm using Tomcat. >> >> >> >> I'll try the AutoServlet to see if it makes a difference. >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Wednesday, January 13, 2010 8:35 PM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> If you update to the latest version of trunk, simply get rid of the >> listener and replace your web.xml config with this: >> >> >> >> <servlet> >> >> <servlet-name>ErraiAutoServlet</servlet-name> >> >> >> > <servlet-class>org.jboss.errai.bus.server.servlet.ErraiAutoServlet</s > e > rvlet- >> class> >> >> <load-on-startup>1</load-on-startup> >> >> </servlet> >> >> >> >> <servlet-mapping> >> >> <servlet-name>ErraiAutoServlet</servlet-name> >> >> <url-pattern>*.erraiBus</url-pattern> >> >> </servlet-mapping> >> >> >> >> This problem you're having is curious, though. We haven't seen it >> in our internal testing. Can you tell me what browser, what >> appserver, and what OS you're on? >> >> >> >> On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: >> >> >> >> >> >> >> >> >> >> I'm using the following on the client side: >> >> bus.subscribe("ItemFound", new MessageCallback() { >> >> >> >> @Override >> >> public void callback(Message message) { >> >> //throw new >> UnsupportedOperationException("Not supported yet."); >> >> MessageBox.alert("Success", "In > Callback", >> null); >> >> /*Map<String,Object> parts = >> message.getParts(); >> >> Set<String> keys = parts.keySet(); >> >> for (String key : keys) { >> >> MessageBox.alert("Key",key,null); >> >> }*/ >> >> //Item item = message.get(Item.class, >> "Item"); >> >> //MessageBox.alert("Return", >> item.getSerialNumber().toString(), null); >> >> } >> >> }); >> >> >> > MessageBuilder.createMessage().toSubject("Items").signalling().with(M > e > ssageP >> arts.ReplyTo, "ItemFound").with("SerialNumber", >> serialInput.getValue().toString()).errorsHandledBy(new >> ErrorCallback() { >> >> >> >> @Override >> >> public boolean error(Message message, > Throwable >> throwable) { >> >> //throw new >> UnsupportedOperationException("Not supported yet."); >> >> MessageBox.alert("Error", >> throwable.getMessage(), null); >> >> return true; >> >> } >> >> }).sendNowWith(bus); >> >> >> >> Which sends: >> >> {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489"} >> >> >> >> Although I've now noticed that it takes 2 tries to get it to send >> that > and >> a >> 3rd one to get the response back for the first one. >> >> >> >> Server portion looks like: >> >> @Service("Items") >> >> public class Items implements MessageCallback { >> >> private MessageBus bus; >> >> >> >> @Inject >> >> public Items(MessageBus bus) { >> >> this.bus = bus; >> >> System.out.println("Got a bus..."); >> >> } >> >> >> >> @Override >> >> public void callback(Message message) { >> >> //throw new UnsupportedOperationException("Not supported > yet."); >> >> System.out.println("Incoming message..."); >> >> String serialNum = message.get(String.class, >> "SerialNumber"); >> >> System.out.println(serialNum); >> >> Item item = new Item(); >> >> item.setSerialNumber(Long.parseLong(serialNum)); >> >> >> > MessageBuilder.createConversation(message).subjectProvided().signalli > n > g().wi >> th("Item", item).errorsHandledBy(new ErrorCallback() { >> >> >> >> @Override >> >> public boolean error(Message message, Throwable > throwable) >> { >> >> //throw new UnsupportedOperationException("Not >> supported yet."); >> >> throwable.printStackTrace(); >> >> return true; >> >> } >> >> }).sendNowWith(bus); >> >> } >> >> } >> >> >> >> Response on the second POST is: >> >> > [{"ItemFound":{"Item":{__EncodedType:'com.xteconline.system.Item',id: > n > ull,se >> >

>> > null,oemSerial:null,manufacturer:null,status:null,itemInfos:null},"To > S > ubject >> ":"ItemFound"}}] >> >> >> >> All others seem to get: >> >> [{"HeartBeat":null}] >> >> >> >> And on the first time I try to submit, it still seems to be kind of > setting >> up stuff since it sends: >> >> > {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"S > e > rverBu >> >

>> > ServerBus","Subject":"AuthorizationService","PriorityProcessing":"1"} > | > |{"Com >> > mandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Client > N > egotia >> > tionService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscri > b > e","To >> > Subject":"ServerBus","Subject":"ServerEchoService","PriorityProcessin > g > ":"1"} >> > ||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" > ||Cl > ||ient >> > Bus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subj > e > ct":"C >> >

>> > Subject":"Items"}||{"CommandType":"RemoteSubscribe","ToSubject":"Serv > e > rBus", >> > "Subject":"ServerBus"}||{"CommandType":"RemoteSubscribe","ToSubject":" > Server >> > Bus","Subject":"AuthorizationService"}||{"CommandType":"RemoteSubscri > b > e","To >> >

>> RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService" >> } >> >> >> >> And >> >> >> >> > {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"I > t > emFoun >> d","PriorityProcessing":"1"} >> >> >> >> But doesn't send my stuff until I submit again. >> >> >> >> And about the only other relevant thing I can think of for Errai is >> the servlet config: >> >> <listener> >> >> >> > <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listen > e > r-clas >> s> >> >> </listener> >> >> >> >> Which I believe sets up the DefaultBlockingServlet. >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Tuesday, January 12, 2010 11:48 AM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> We have a fairly significant application that makes extensive use >> of > this >> type of paradigm and we haven't ever experienced any dropped messages. > Can >> you provide me some examples of your code so we can troubleshoot >> what's going on? >> >> >> >> On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: >> >> >> >> >> >> >> >> >> >> >> The MessageParts.ReplyTo was what I was missing in there. However, >> my callback doesn't seem to be called. I get something back when my >> request is POSTed, but it never seems to call my callback. They do >> seem to work sometimes though. I had accidentally named my callback >> subject and the server subject the same and when I created a message >> to that subject, > both >> the client callback and the server callback were called correctly. >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Tuesday, January 12, 2010 9:07 AM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> The sender needs to create a listening service that can be replied to. > The >> best way to do this is like so: >> >> >> >> >> >> //client-side code >> >> bus.subscribe("MyResponseSvc", >> >> new MessageCallback() { >> >> public void callback(Message msg) { >> >> ... >> >> } >> >> } >> >> ); >> >> >> >> > MessageBuilder.createMessage().toSubject("ConversationalService").sig > n > alling >> () >> >> .with(MessageParts.ReplyTo, "MyResponseSvc") >> >> .with("SomeMessagePart", "Foo") >> >> .noErrorHandling() >> >> .sendNowWith(bus); >> >> >> >> ... >> >> //server-side code >> >> >> >> MessageBuilder.createConversation(message) >> >> .subjectProvided().signalling() >> >> .with("MyResponseData", "Bar") >> >> .noErrorHandling() >> >> .sendNowWith(bus); >> >> >> >> ... >> >> >> >> Note: we may make this more straight forward in the future, such as >> with the RPC API. >> >> >> >> >> >> >> >> On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: >> >> >> >> >> >> >> >> >> >> >> >> I won't be able to use the Swing monitor on the server I'm deploying >> to since it has no interface. However, I did start enabling logging >> in various places and it does seem that my services weren't getting >> started. I was lacking an ErraiApp.properties which I guess is used >> as the root for > where >> it should start looking for services. After adding that, they >> started > and >> stuff started to go through. Does the client keep a record of >> services > or >> something then? Why wouldn't it try to contact the service and then >> fail that it couldn't find it? >> >> >> >> Also, looking at the revised Message API, how do you listen for the >> reply in a conversation? Do I need to create a separate listener? >> Before you > could >> specify a MessageCallback to get the response in the conversation, >> but I can't find anywhere in the call chain to do that and it's not >> covered in the SVN book. >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Monday, January 11, 2010 3:16 PM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> Kevin, >> >> >> >> I'm not sure how you're launching your app, but can you provide this >> command line option which will bring up the bus monitor, and at >> least tell me if you've probably deployed your services: >> -Derrai.bus.showmonitor=true >> >> >> >> Also, can you email me the log output from when your startup the >> application? >> >> >> >> On 2010-01-11, at 3:35 PM, Kevin Jordan wrote: >> >> >> >> >> >> >> >> >> >> >> >> >> Changing to a createCall and making a @Endpoint annotated method on >> the server seems to make it send something again: >> >> > {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"I > t > ems.ge >> tItem:RespondTo:1","PriorityProcessing":"1"} >> >> >> >> With a response of: >> >> [{"HeartBeat":null}] >> >> >> >> However, I still so nowhere where it passes the parameter I give it

>> >> MessageBuilder.createCall().call("Items").endpoint("getItem", >> serialInput.getValue()).respondTo(Item.class, new >> RemoteCallback<Item>() > { >> >> >> >> @Override >> >> public void callback(Item response) { >> >> //throw new >> UnsupportedOperationException("Not supported yet."); >> >> >> MessageBox.alert("Return",item.getSerialNumber().toString(),null); >> >> } >> >> >> >> }).noErrorHandling().sendNowWith(bus); >> >> >> >> >> >> >> >> From: errai-users-bounces(a)lists.jboss.org >> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >> Jordan >> Sent: Monday, January 11, 2010 1:46 PM >> To: 'Mike Brock' >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> Made the changes specified in the userguide, but now it doesn't send >> anything. I'm using the following: >> >> > MessageBuilder.createMessage().toSubject("Items").signalling().with(" > S > erialN >> umber", "Test").noErrorHandling().sendNowWith(bus); >> >> >> >> It still seems to be set up just fine since the in.erraiBus servlet >> is created and the client long polls it, but the code above doesn't >> seem to send anything. I'm using the following way to make it for >> the >> DefaultBlockingServlet: >> >> <listener> >> >> >> > <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</listen > e > r-clas >> s> >> >> </listener> >> >> >> >> Should I be using that? I figure it shouldn't affect the client any > though >> unless the servlet is incorrectly set up as a consequence, which it > doesn't >> seem to be since they communicate just fine for the initial setup. >> What should I look at to see why it's not sending? >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Monday, January 11, 2010 12:43 PM >> To: Kevin Jordan >> Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> You should be aware we have made changes and are retiring the use of >> the CommandMessage API. Be sure to read the documentation in the >> userguide/src/main/docbook/en/master.xml file. You can use: mvn >> jdocbook:generate to create an HTML file from the userguide/ directory. >> >> >> >> On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Friday, January 08, 2010 2:56 PM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> I will check into this. We're still working on getting the AIO >> stuff >> sorted>Monday, January 11, 2010 8:59 AM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> >> >> Hi Kevin, the compilation problems should be fixed already. >> >> >> >> >> >> On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: >> >> >> >> >> >> >> >> >> >> >> >> >> >> Yes, I am using trunk. Is there a more stable branch/version I >> should be using? I had updated again hoping it was just something >> with the time I checked out and then ran into the problems Heiko >> Braun ran into compiling it. >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Friday, January 08, 2010 8:52 PM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> What version of ErraiBus are you using? Are you getting it from trunk? >> >> >> >> On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: >> >> >> >> DefaultBlockingServlet seems to have the same effect. >> >> >> >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Friday, January 08, 2010 2:56 PM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> >> >> I will check into this. We're still working on getting the AIO >> stuff sorted, and I wouldn't consider the Tomcat or JBoss adapters >> to be production ready. You're best to use the >> DefaultBlockingServlet -- which will provide adequate performance >> for development while we get the AIO adapters squared away over the next

>> >> >> >> On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> I'm having trouble getting a message to go through using ErraiBus. >> I'm using this on the client side: >> >> CommandMessage msg = (CommandMessage) >> CommandMessage.create().toSubject("Items").set("SerialNumber", >> serialInput.getValue()); >> >> bus.conversationWith(msg, new MessageCallback() { >> >> >> >> @Override >> >> public void callback(Message message) { >> >> //throw new >> UnsupportedOperationException("Not supported yet."); >> >> Item item = message.get(Item.class, >> "Item"); >> >> MessageBox.alert("Errai", >> item.getSerialNumber().toString(), null); >> >> } >> >> }); >> >> >> >> With this on the server side: >> >> @Service("Items") >> >> public class Items implements MessageCallback { >> >> private MessageBus bus; >> >> >> >> @Inject >> >> public Items(MessageBus bus) { >> >> this.bus = bus; >> >> System.out.println("Got a bus..."); >> >> } >> >> >> >> @Override >> >> public void callback(Message message) { >> >> //throw new UnsupportedOperationException("Not supported > yet."); >> >> System.out.println("Incoming message..."); >> >> Long serialNum = message.get(Long.class, "SerialNumber"); >> >> System.out.println(serialNum); >> >> Item item = new Item(); >> >> item.setSerialNumber(serialNum); >> >> >> ConversationMessage.create(message).set("Item",item).sendNowWith(bus >> ) >> ; >> >> } >> >> >> >> } >> >> >> >> However, all it seems to send is: >> >> > {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"t > e > mp:Con >> versation:2","PriorityProcessing":"1"} >> >> >> >> I don't see where it actually sends my body or the subject that I >> fill > out >> in my message. Nothing also gets to the Service class. Am I doing >> something wrong? I have Tomcat running NIO and everything else >> seems set up correctly. It will keep a GET connection open and do >> the POST of the > JSON >> above, but nowhere does it seem to send what I want it to. I also >> seem > to >> be getting these occasionally, usually on some of the first requests >> to >> in.erraiBus: >> >> java.lang.NullPointerException >> >> at >> > org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(TomcatCom > e > tServl >> et.java:105) >> >> at >> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent > ( > Unknow >> n Source) >> >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unknow >> n >> Source) >> >> at org.apache.catalina.core.StandardWrapperValve.event(Unknown >> Source) >> >> at org.apache.catalina.core.StandardContextValve.event(Unknown >> Source) >> >> at org.apache.catalina.core.StandardHostValve.event(Unknown > Source) >> >> at org.apache.catalina.valves.ValveBase.event(Unknown Source) >> >> at org.apache.catalina.core.StandardEngineValve.event(Unknown >> Source) >> >> at org.apache.catalina.connector.CoyoteAdapter.event(Unknown >> Source) >> >> at org.apache.coyote.http11.Http11NioProcessor.event(Unknown >> Source) >> >> at >> > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.ev > e > nt(Unk >> nown Source) >> >> at >> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknown > Source) >> >> at >> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec > u > tor.ja >> va:886) >> >> at >> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. > java:9 >> 08) >> >> at java.lang.Thread.run(Thread.java:619) >> >> >> >> Can anyone point me at what I'm missing? >> >> _______________________________________________ >> errai-users mailing list >> errai-users(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/errai-users >> >> >> >> >> >> _______________________________________________ >> errai-users mailing list >> errai-users(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/errai-users >> >> >> >> _______________________________________________ >> errai-users mailing list >> errai-users(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/errai-users >> >> >> >> >> >> >> >> _______________________________________________ >> errai-users mailing list >> errai-users(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/errai-users >

Yeah, that's the only stuff that comes out during the compile phase. Not sure if I have something misconfigured in my logging, but that's the only places that print out. -----Original Message----- From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 18, 2010 10:45 AM To: Kevin Jordan Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages This is for the compile-phase stuff. If you're running in hosted mode, you need to look in the GWT Development Mode logger. On 2010-01-18, at 11:43 AM, Kevin Jordan wrote: > Is there any logging I have to set up for a particular class or > package or any configuration I have to do for that? Normally, even > when it works, the only output I see from Errai while compiling is: > 0 [main] INFO Configuration - configuration scan targets > 0 [main] INFO Configuration - -> >

> 0-SNAPSHOT.jar > 0 [main] INFO Configuration - -> > C:\Users\kjordan\Documents\NetBeansProjects\Desktop\src\java > 0 [main] INFO Configuration - -> > C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB-INF > \ > classe > s > 63 [main] INFO Configuration - caching context > 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-persis > t > ence-1 > .0-SNAPSHOT.jar:*' > 188 [main] INFO Configuration - caching context > 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB-IN > F > \class > es' > > And I'm not even really using persistence (i.e. it's not inherited in > my .gwt.xml, but somehow it's getting run anyways either via ErraiBus > or ErraiCommons). > -----Original Message----- > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Monday, January 18, 2010 10:39 AM > To: Kevin Jordan > Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > This is an interesting theory. You should be able to determine > whether the stub is generated or not since at compile-time the Errai > generators show log output for each stub. > > You should see a log output that says: "Generated > marshaller/demarshaller > for: <classname>" for each entity you've annotated. > > On 2010-01-18, at 11:32 AM, Kevin Jordan wrote: > >> Not sure what you mean by that, but I'm using Netbeans and my domain >> POJOs > are in a separate project which gets included by my web project. The > projects compile file and I've used my domain POJOs via SOAFace's > UniversalClient and regular GWT-RPC before without issues. And they > get put across the wire with Errai, it's just when the class is in a > separate project that there seems to be a problem and my callback > isn't called. So I'm wondering if it's an issue with the stub > getting generated or something. > >> >> -----Original Message----- >> From: Thomas SEGISMONT [mailto:tsegismont@gmail.com] >> Sent: Monday, January 18, 2010 10:12 AM >> To: Kevin Jordan >> Cc: Mike Brock; errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> Have you tried to include your project/jar source code in your >> launch > configuration ? >> >> It sounds more like a GWT configuration problem than an Errai one. >> >> If you're using Maven to build your project, you can read this : >> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/multiproject.ht >> m >> l >> >> Thomas >> >> On Mon, 18 Jan 2010 09:50:40 -0600, "Kevin Jordan" >> <kevin.jordan(a)xteconline.com&gt; wrote: >>> I think I've found out one problem. Somehow Errai has trouble if >>> your >> POJO >>> is in an external jar, or in my case another Netbeans project. GWT >>> will compile my project just fine, but it at least seems to be that >>> once I go >> to >>> another project/jar for my POJO it fails to get to my callback and >>> does >> the >>> behavior I've previously described. >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Friday, January 15, 2010 4:20 PM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> Yes, that will work, of course. >>> >>> >>> >>> On 2010-01-15, at 4:59 PM, Kevin Jordan wrote: >>> >>> >>> >>> >>> >>> I haven't yet. But I'll try it and let you know if it works. >>> >>> >>> >>> So the default constructor provided by the JVM if you don't specify >>> one won't work? >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Friday, January 15, 2010 3:55 PM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> Have you updated to trunk -- I think that will fix the >>> InstantiationException? Any serializable class *must* have a >>> default constructor. >>> >>> >>> >>> On 2010-01-15, at 4:48 PM, Kevin Jordan wrote: >>> >>> >>> >>> >>> >>> >>> Well, I think I've figured it out on my callback problems. I went >>> back >> to >>> just passing a string back and forth and that worked. I then made >>> a simpler POJO to pass back and forth with just implementing >>> Serializable which didn't work (no callback call). I then added >>> the annotation that I just saw in the docs and that didn't work (no >>> callback call). I then removed >> Serializable >>> and the callback gets called, but it gets an error when it tries to >>> get >> the >>> POJO out of the message. >>> >>> >>> >>> Is there anything extra I need to do for POJOs? >>> >>> >>> >>> From: errai-users-bounces(a)lists.jboss.org >>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>> Jordan >>> Sent: Thursday, January 14, 2010 4:21 PM >>> To: 'Mike Brock' >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> Whenever I do that, I seem to get: >>> >>> java.lang.InstantiationException: >>> org.jboss.errai.bus.server.servlet.DefaultBlockingServlet >>> >>> at java.lang.Class.newInstance0(Class.java:340) >>> >>> at java.lang.Class.newInstance(Class.java:308) >>> >>> at >>> org.apache.catalina.core.StandardWrapper.loadServlet(Unknown >>> Source) >>> >>> at org.apache.catalina.core.StandardWrapper.load(Unknown >>> Source) >>> >>> at >>> org.apache.catalina.core.StandardContext.loadOnStartup(Unknown >>> Source) >>> >>> at org.apache.catalina.core.StandardContext.start(Unknown >>> Source) >>> >>> at >> org.apache.catalina.core.ContainerBase.addChildInternal(Unknown >>> Source) >>> >>> at org.apache.catalina.core.ContainerBase.addChild(Unknown >> Source) >>> >>> at org.apache.catalina.core.StandardHost.addChild(Unknown >>> Source) >>> >>> at >> org.apache.catalina.startup.HostConfig.deployDescriptor(Unknown >>> Source) >>> >>> at >> org.apache.catalina.startup.HostConfig.deployDescriptors(Unknown >>> Source) >>> >>> at org.apache.catalina.startup.HostConfig.deployApps(Unknown >>> Source) >>> >>> at org.apache.catalina.startup.HostConfig.check(Unknown >>> Source) >>> >>> at >>> org.apache.catalina.startup.HostConfig.lifecycleEvent(Unknown >>> Source) >>> >>> at >>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknow >>> n >>> Source) >>> >>> at >> org.apache.catalina.core.ContainerBase.backgroundProcess(Unknown >>> Source) >>> >>> at >>> >> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >> p >> r >> ocessC >>> hildren(Unknown Source) >>> >>> at >>> >> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >> p >> r >> ocessC >>> hildren(Unknown Source) >>> >>> at >>> >> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >> r >> u >> n(Unkn >>> own Source) >>> >>> at java.lang.Thread.run(Thread.java:619) >>> >>> >>> >>> Even in a new project I've created to see if anything is >>> interfering with Errai somehow. Trying TomcatCometServlet or >>> ErraiAutoServlet also yields the same results as before in both >>> cases. Using the listener/Guice >> filter >>> works. I've also gotten it so a callback works in my new minimal >> project. >>> So now I'm wondering if something else is interfering with it. >>> I've got Spring Security protecting pretty much everything, >>> although I think I've tried taking that out before and had the same

>>> I've also got GXT >>> (http://www.extjs.com/products/gxt/) in there. Along with Mule and >>> SOAFaces, although SOAFaces can probably go away since I'll be >>> communicating to Mule via Errai when that works so I can have >>> better asynchronous communication and also push communication. I >>> suppose what I'll try first is ripping out GXT since that's >>> probably the most likely culprit in my mind. >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Thursday, January 14, 2010 12:12 PM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> We will actually be removing the Guice filter as it's created >>> problems >> for >>> deploying on some appservers. We're falling back on directly

>>> the >>> servlet. So you might want to switch to directly declaring the >>> DefaultBlockingServlet like so: >>> >>> >>> >>> <servlet> >>> >>> <servlet-name>ErraiServlet</servlet-name> >>> >>> >>> >> <servlet-class>org.jboss.errai.bus.server.servlet.DefaultBlockingSer >> v >> l >> et</se >>> rvlet-class> >>> >>> <load-on-startup>1</load-on-startup> >>> >>> </servlet> >>> >>> >>> >>> <servlet-mapping> >>> >>> <servlet-name>ErraiServlet</servlet-name> >>> >>> <url-pattern>*.erraiBus</url-pattern> >>> >>> </servlet-mapping> >>> >>> >>> >>> . >>> >>> >>> >>> On 2010-01-14, at 12:45 PM, Kevin Jordan wrote: >>> >>> >>> >>> Yes. It's still working the way it was before where I have to >>> submit >> more >>> than once and the response comes back on the POST but the callback >> doesn't >>> get called. >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Thursday, January 14, 2010 11:44 AM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> Are you still losing messages? >>> >>> >>> >>> On 2010-01-14, at 12:31 PM, Kevin Jordan wrote: >>> >>> >>> >>> >>> >>> >>> >>> Switching it back to the listener config seems to make it work >>> again through the DefaultBlockingServlet. >>> >>> >>> >>> From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] >>> Sent: Thursday, January 14, 2010 11:22 AM >>> To: 'Mike Brock' >>> Cc: &#39;errai-users(a)lists.jboss.org&#39; >>> Subject: RE: [errai-users] Trouble sending messages >>> >>> >>> >>> Yeah, I'm using the NIO connector. And actually if I configure the >>> TomcatCometServlet manually I get the same error again. I know >>> that used to happen when I was accessing it through my AJP >>> connected Apache instance, but now I'm accessing it directly >>> through port 8443 on Tomcat. >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Thursday, January 14, 2010 10:55 AM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> Are you using the NIO connector in Tomcat? Errai by default will >>> try to use Tomcat's AIO system, which requires that the NIO or APR >>> connecter be >> used. >>> >>> >>> >>> On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: >>> >>> >>> >>> I tried the AutoServlet and it seems to pick the TomcatCometServlet >>> which makes it spin over and over on this message every time it >>> tries to access >>> it: >>> >>> >> ******************************************************************** >> * >> * >> ****** >>> ********************* >>> >>> ** PROBLEM! >>> >>> ** It appears something has been incorrectly configured. In order >>> to use ErraiBus >>> >>> ** on Tomcat, you must ensure that you are using the NIO or APR >> connector. >>> Also >>> >>> ** make sure that you have added these lines to your >>> WEB-INF/web.xml >> file: >>> >>> ** --- >>> >>> ** <servlet> >>> >>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>> >>> ** >>> >> <servlet-class>org.jboss.errai.bus.server.servlet.TomcatCometServlet >> < >> / >> servle >>> t-class> >>> >>> ** <load-on-startup>1</load-on-startup> >>> >>> ** </servlet> >>> >>> ** >>> >>> ** <servlet-mapping> >>> >>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>> >>> ** <url-pattern>*.erraiBus</url-pattern> >>> >>> ** </servlet-mapping> >>> >>> ** --- >>> >>> ** If you have the following lines in your WEB-INF/web.xml, you >>> must comment or remove them: >>> >>> ** --- >>> >>> ** <listener> >>> >>> ** >>> >> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</liste >> n >> e >> r-clas >>> s> >>> >>> ** </listener> >>> >>> >> ******************************************************************** >> * >> * >> ****** >>> ********************* >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Thursday, January 14, 2010 10:06 AM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> By the way, if you want, we're on IRC on irc.freenode.net in >>> channel >> #errai >>> -- I'm "cbrock" on there if you want help troubleshooting directly. >>> >>> >>> >>> On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, and >>> IE on Windows 7. I'm using Tomcat. >>> >>> >>> >>> I'll try the AutoServlet to see if it makes a difference. >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Wednesday, January 13, 2010 8:35 PM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> If you update to the latest version of trunk, simply get rid of the >>> listener and replace your web.xml config with this: >>> >>> >>> >>> <servlet> >>> >>> <servlet-name>ErraiAutoServlet</servlet-name> >>> >>> >>> >> <servlet-class>org.jboss.errai.bus.server.servlet.ErraiAutoServlet</ >> s >> e >> rvlet- >>> class> >>> >>> <load-on-startup>1</load-on-startup> >>> >>> </servlet> >>> >>> >>> >>> <servlet-mapping> >>> >>> <servlet-name>ErraiAutoServlet</servlet-name> >>> >>> <url-pattern>*.erraiBus</url-pattern> >>> >>> </servlet-mapping> >>> >>> >>> >>> This problem you're having is curious, though. We haven't seen it >>> in our internal testing. Can you tell me what browser, what >>> appserver, and what OS you're on? >>> >>> >>> >>> On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> I'm using the following on the client side: >>> >>> bus.subscribe("ItemFound", new MessageCallback() { >>> >>> >>> >>> @Override >>> >>> public void callback(Message message) { >>> >>> //throw new >>> UnsupportedOperationException("Not supported yet."); >>> >>> MessageBox.alert("Success", "In >> Callback", >>> null); >>> >>> /*Map<String,Object> parts = >>> message.getParts(); >>> >>> Set<String> keys = parts.keySet(); >>> >>> for (String key : keys) { >>> >>> MessageBox.alert("Key",key,null); >>> >>> }*/ >>> >>> //Item item = message.get(Item.class, >>> "Item"); >>> >>> //MessageBox.alert("Return", >>> item.getSerialNumber().toString(), null); >>> >>> } >>> >>> }); >>> >>> >>> >> MessageBuilder.createMessage().toSubject("Items").signalling().with( >> M >> e >> ssageP >>> arts.ReplyTo, "ItemFound").with("SerialNumber", >>> serialInput.getValue().toString()).errorsHandledBy(new >>> ErrorCallback() { >>> >>> >>> >>> @Override >>> >>> public boolean error(Message message, >> Throwable >>> throwable) { >>> >>> //throw new >>> UnsupportedOperationException("Not supported yet."); >>> >>> MessageBox.alert("Error", >>> throwable.getMessage(), null); >>> >>> return true; >>> >>> } >>> >>> }).sendNowWith(bus); >>> >>> >>> >>> Which sends: >>> >>> {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489" >>> } >>> >>> >>> >>> Although I've now noticed that it takes 2 tries to get it to send >>> that >> and >>> a >>> 3rd one to get the response back for the first one. >>> >>> >>> >>> Server portion looks like: >>> >>> @Service("Items") >>> >>> public class Items implements MessageCallback { >>> >>> private MessageBus bus; >>> >>> >>> >>> @Inject >>> >>> public Items(MessageBus bus) { >>> >>> this.bus = bus; >>> >>> System.out.println("Got a bus..."); >>> >>> } >>> >>> >>> >>> @Override >>> >>> public void callback(Message message) { >>> >>> //throw new UnsupportedOperationException("Not supported >> yet."); >>> >>> System.out.println("Incoming message..."); >>> >>> String serialNum = message.get(String.class, >>> "SerialNumber"); >>> >>> System.out.println(serialNum); >>> >>> Item item = new Item(); >>> >>> item.setSerialNumber(Long.parseLong(serialNum)); >>> >>> >>> >> MessageBuilder.createConversation(message).subjectProvided().signall >> i >> n >> g().wi >>> th("Item", item).errorsHandledBy(new ErrorCallback() { >>> >>> >>> >>> @Override >>> >>> public boolean error(Message message, Throwable >> throwable) >>> { >>> >>> //throw new UnsupportedOperationException("Not >>> supported yet."); >>> >>> throwable.printStackTrace(); >>> >>> return true; >>> >>> } >>> >>> }).sendNowWith(bus); >>> >>> } >>> >>> } >>> >>> >>> >>> Response on the second POST is: >>> >>> >> [{"ItemFound":{"Item":{__EncodedType:'com.xteconline.system.Item',id: >> n >> ull,se >>> >> >

>>> >> null,oemSerial:null,manufacturer:null,status:null,itemInfos:null},"T >> o >> S >> ubject >>> ":"ItemFound"}}] >>> >>> >>> >>> All others seem to get: >>> >>> [{"HeartBeat":null}] >>> >>> >>> >>> And on the first time I try to submit, it still seems to be kind of >> setting >>> up stuff since it sends: >>> >>> >> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >> S >> e >> rverBu >>> >> >

>>> >> ServerBus","Subject":"AuthorizationService","PriorityProcessing":"1" >> } >> | >> |{"Com >>> >> mandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Clien >> t >> N >> egotia >>> >> tionService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscr >> i >> b >> e","To >>> >> Subject":"ServerBus","Subject":"ServerEchoService","PriorityProcessi >> n >> g >> ":"1"} >>> >> ||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >> ||Cl >> ||ient >>> >> Bus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Sub >> j >> e >> ct":"C >>> >> >

>>> >> Subject":"Items"}||{"CommandType":"RemoteSubscribe","ToSubject":"Ser >> v >> e >> rBus", >>> >> "Subject":"ServerBus"}||{"CommandType":"RemoteSubscribe","ToSubject":" >> Server >>> >> Bus","Subject":"AuthorizationService"}||{"CommandType":"RemoteSubscr >> i >> b >> e","To >>> >> >

>>> RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService" >>> } >>> >>> >>> >>> And >>> >>> >>> >>> >> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >> I >> t >> emFoun >>> d","PriorityProcessing":"1"} >>> >>> >>> >>> But doesn't send my stuff until I submit again. >>> >>> >>> >>> And about the only other relevant thing I can think of for Errai is >>> the servlet config: >>> >>> <listener> >>> >>> >>> >> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</liste >> n >> e >> r-clas >>> s> >>> >>> </listener> >>> >>> >>> >>> Which I believe sets up the DefaultBlockingServlet. >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Tuesday, January 12, 2010 11:48 AM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> We have a fairly significant application that makes extensive use >>> of >> this >>> type of paradigm and we haven't ever experienced any dropped messages. >> Can >>> you provide me some examples of your code so we can troubleshoot >>> what's going on? >>> >>> >>> >>> On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> The MessageParts.ReplyTo was what I was missing in there. However, >>> my callback doesn't seem to be called. I get something back when >>> my request is POSTed, but it never seems to call my callback. They >>> do seem to work sometimes though. I had accidentally named my >>> callback subject and the server subject the same and when I created >>> a message to that subject, >> both >>> the client callback and the server callback were called correctly. >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Tuesday, January 12, 2010 9:07 AM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> The sender needs to create a listening service that can be replied to. >> The >>> best way to do this is like so: >>> >>> >>> >>> >>> >>> //client-side code >>> >>> bus.subscribe("MyResponseSvc", >>> >>> new MessageCallback() { >>> >>> public void callback(Message msg) { >>> >>> ... >>> >>> } >>> >>> } >>> >>> ); >>> >>> >>> >>> >> MessageBuilder.createMessage().toSubject("ConversationalService").si >> g >> n >> alling >>> () >>> >>> .with(MessageParts.ReplyTo, "MyResponseSvc") >>> >>> .with("SomeMessagePart", "Foo") >>> >>> .noErrorHandling() >>> >>> .sendNowWith(bus); >>> >>> >>> >>> ... >>> >>> //server-side code >>> >>> >>> >>> MessageBuilder.createConversation(message) >>> >>> .subjectProvided().signalling() >>> >>> .with("MyResponseData", "Bar") >>> >>> .noErrorHandling() >>> >>> .sendNowWith(bus); >>> >>> >>> >>> ... >>> >>> >>> >>> Note: we may make this more straight forward in the future, such as >>> with the RPC API. >>> >>> >>> >>> >>> >>> >>> >>> On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> I won't be able to use the Swing monitor on the server I'm >>> deploying to since it has no interface. However, I did start >>> enabling logging in various places and it does seem that my >>> services weren't getting started. I was lacking an >>> ErraiApp.properties which I guess is used as the root for >> where >>> it should start looking for services. After adding that, they >>> started >> and >>> stuff started to go through. Does the client keep a record of >>> services >> or >>> something then? Why wouldn't it try to contact the service and >>> then fail that it couldn't find it? >>> >>> >>> >>> Also, looking at the revised Message API, how do you listen for the >>> reply in a conversation? Do I need to create a separate listener? >>> Before you >> could >>> specify a MessageCallback to get the response in the conversation, >>> but I can't find anywhere in the call chain to do that and it's not >>> covered in the SVN book. >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Monday, January 11, 2010 3:16 PM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> Kevin, >>> >>> >>> >>> I'm not sure how you're launching your app, but can you provide >>> this command line option which will bring up the bus monitor, and >>> at least tell me if you've probably deployed your services: >>> -Derrai.bus.showmonitor=true >>> >>> >>> >>> Also, can you email me the log output from when your startup the >>> application? >>> >>> >>> >>> On 2010-01-11, at 3:35 PM, Kevin Jordan wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> Changing to a createCall and making a @Endpoint annotated method on >>> the server seems to make it send something again: >>> >>> >> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >> I >> t >> ems.ge >>> tItem:RespondTo:1","PriorityProcessing":"1"} >>> >>> >>> >>> With a response of: >>> >>> [{"HeartBeat":null}] >>> >>> >>> >>> However, I still so nowhere where it passes the parameter I give it with: >>> >>> MessageBuilder.createCall().call("Items").endpoint("getItem", >>> serialInput.getValue()).respondTo(Item.class, new >>> RemoteCallback<Item>() >> { >>> >>> >>> >>> @Override >>> >>> public void callback(Item response) { >>> >>> //throw new >>> UnsupportedOperationException("Not supported yet."); >>> >>> >>> MessageBox.alert("Return",item.getSerialNumber().toString(),null); >>> >>> } >>> >>> >>> >>> }).noErrorHandling().sendNowWith(bus); >>> >>> >>> >>> >>> >>> >>> >>> From: errai-users-bounces(a)lists.jboss.org >>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>> Jordan >>> Sent: Monday, January 11, 2010 1:46 PM >>> To: 'Mike Brock' >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> Made the changes specified in the userguide, but now it doesn't >>> send anything. I'm using the following: >>> >>> >> MessageBuilder.createMessage().toSubject("Items").signalling().with(" >> S >> erialN >>> umber", "Test").noErrorHandling().sendNowWith(bus); >>> >>> >>> >>> It still seems to be set up just fine since the in.erraiBus servlet >>> is created and the client long polls it, but the code above doesn't >>> seem to send anything. I'm using the following way to make it for >>> the >>> DefaultBlockingServlet: >>> >>> <listener> >>> >>> >>> >> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</liste >> n >> e >> r-clas >>> s> >>> >>> </listener> >>> >>> >>> >>> Should I be using that? I figure it shouldn't affect the client >>> any >> though >>> unless the servlet is incorrectly set up as a consequence, which it >> doesn't >>> seem to be since they communicate just fine for the initial setup. >>> What should I look at to see why it's not sending? >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Monday, January 11, 2010 12:43 PM >>> To: Kevin Jordan >>> Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> You should be aware we have made changes and are retiring the use >>> of the CommandMessage API. Be sure to read the documentation in >>> the userguide/src/main/docbook/en/master.xml file. You can use: >>> mvn jdocbook:generate to create an HTML file from the userguide/

>>> >>> >>> >>> On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Friday, January 08, 2010 2:56 PM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> I will check into this. We're still working on getting the AIO >>> stuff >>> sorted>Monday, January 11, 2010 8:59 AM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> >>> >>> Hi Kevin, the compilation problems should be fixed already. >>> >>> >>> >>> >>> >>> On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> Yes, I am using trunk. Is there a more stable branch/version I >>> should be using? I had updated again hoping it was just something >>> with the time I checked out and then ran into the problems Heiko >>> Braun ran into compiling it. >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Friday, January 08, 2010 8:52 PM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> What version of ErraiBus are you using? Are you getting it from trunk? >>> >>> >>> >>> On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: >>> >>> >>> >>> DefaultBlockingServlet seems to have the same effect. >>> >>> >>> >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Friday, January 08, 2010 2:56 PM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> >>> >>> I will check into this. We're still working on getting the AIO >>> stuff sorted, and I wouldn't consider the Tomcat or JBoss adapters >>> to be production ready. You're best to use the >>> DefaultBlockingServlet -- which will provide adequate performance >>> for development while we get the AIO adapters squared away over the >>> next few days. >>> >>> >>> >>> On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> I'm having trouble getting a message to go through using ErraiBus. >>> I'm using this on the client side: >>> >>> CommandMessage msg = (CommandMessage) >>> CommandMessage.create().toSubject("Items").set("SerialNumber", >>> serialInput.getValue()); >>> >>> bus.conversationWith(msg, new MessageCallback() { >>> >>> >>> >>> @Override >>> >>> public void callback(Message message) { >>> >>> //throw new >>> UnsupportedOperationException("Not supported yet."); >>> >>> Item item = message.get(Item.class, >>> "Item"); >>> >>> MessageBox.alert("Errai", >>> item.getSerialNumber().toString(), null); >>> >>> } >>> >>> }); >>> >>> >>> >>> With this on the server side: >>> >>> @Service("Items") >>> >>> public class Items implements MessageCallback { >>> >>> private MessageBus bus; >>> >>> >>> >>> @Inject >>> >>> public Items(MessageBus bus) { >>> >>> this.bus = bus; >>> >>> System.out.println("Got a bus..."); >>> >>> } >>> >>> >>> >>> @Override >>> >>> public void callback(Message message) { >>> >>> //throw new UnsupportedOperationException("Not supported >> yet."); >>> >>> System.out.println("Incoming message..."); >>> >>> Long serialNum = message.get(Long.class, "SerialNumber"); >>> >>> System.out.println(serialNum); >>> >>> Item item = new Item(); >>> >>> item.setSerialNumber(serialNum); >>> >>> >>> ConversationMessage.create(message).set("Item",item).sendNowWith(bu >>> s >>> ) >>> ; >>> >>> } >>> >>> >>> >>> } >>> >>> >>> >>> However, all it seems to send is: >>> >>> >> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >> t >> e >> mp:Con >>> versation:2","PriorityProcessing":"1"} >>> >>> >>> >>> I don't see where it actually sends my body or the subject that I >>> fill >> out >>> in my message. Nothing also gets to the Service class. Am I doing >>> something wrong? I have Tomcat running NIO and everything else >>> seems set up correctly. It will keep a GET connection open and do >>> the POST of the >> JSON >>> above, but nowhere does it seem to send what I want it to. I also >>> seem >> to >>> be getting these occasionally, usually on some of the first >>> requests to >>> in.erraiBus: >>> >>> java.lang.NullPointerException >>> >>> at >>> >> org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(TomcatCo >> m >> e >> tServl >>> et.java:105) >>> >>> at >>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEven >> t >> ( >> Unknow >>> n Source) >>> >>> at >>> org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unkno >>> w >>> n >>> Source) >>> >>> at org.apache.catalina.core.StandardWrapperValve.event(Unknown >>> Source) >>> >>> at org.apache.catalina.core.StandardContextValve.event(Unknown >>> Source) >>> >>> at org.apache.catalina.core.StandardHostValve.event(Unknown >> Source) >>> >>> at org.apache.catalina.valves.ValveBase.event(Unknown Source) >>> >>> at org.apache.catalina.core.StandardEngineValve.event(Unknown >>> Source) >>> >>> at org.apache.catalina.connector.CoyoteAdapter.event(Unknown >>> Source) >>> >>> at org.apache.coyote.http11.Http11NioProcessor.event(Unknown >>> Source) >>> >>> at >>> >> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.e >> v >> e >> nt(Unk >>> nown Source) >>> >>> at >>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknown >> Source) >>> >>> at >>> >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExe >> c >> u >> tor.ja >>> va:886) >>> >>> at >>> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. >> java:9 >>> 08) >>> >>> at java.lang.Thread.run(Thread.java:619) >>> >>> >>> >>> Can anyone point me at what I'm missing? >>> >>> _______________________________________________ >>> errai-users mailing list >>> errai-users(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/errai-users >>> >>> >>> >>> >>> >>> _______________________________________________ >>> errai-users mailing list >>> errai-users(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/errai-users >>> >>> >>> >>> _______________________________________________ >>> errai-users mailing list >>> errai-users(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/errai-users >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> errai-users mailing list >>> errai-users(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/errai-users >> > >

Okay, in debug mode I see the logging. It definitely doesn't generate anything for one in a jar file. -----Original Message----- From: errai-users-bounces(a)lists.jboss.org [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin Jordan Sent: Monday, January 18, 2010 1:09 PM To: 'Mike Brock' Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Sometimes, although seeing as my application will be secured with authentication and very soon will depend on it, that may not be an option for much longer. Usually I just compile and deploy it. There shouldn't be anything really special about the way it's compiled, seeing as I can compile it using Hudson as well since Netbeans just uses Ant. -----Original Message----- From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 18, 2010 1:01 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages I'm not really familiar with NetBeans. Are you using the GWT Development Mode for testing? On 2010-01-18, at 1:53 PM, Kevin Jordan wrote: > Yeah, that's the only stuff that comes out during the compile phase. > Not sure if I have something misconfigured in my logging, but that's > the only places that print out. > > -----Original Message----- > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Monday, January 18, 2010 10:45 AM > To: Kevin Jordan > Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > This is for the compile-phase stuff. If you're running in hosted > mode, you need to look in the GWT Development Mode logger. > > On 2010-01-18, at 11:43 AM, Kevin Jordan wrote: > >> Is there any logging I have to set up for a particular class or >> package or any configuration I have to do for that? Normally, even >> when it works, the only output I see from Errai while compiling is: >> 0 [main] INFO Configuration - configuration scan targets >> 0 [main] INFO Configuration - -> >> > C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-persistence-1. >> 0-SNAPSHOT.jar >> 0 [main] INFO Configuration - -> >> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\src\java >> 0 [main] INFO Configuration - -> >> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB-INF >> \ >> classe >> s >> 63 [main] INFO Configuration - caching context >> 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-persis >> t >> ence-1 >> .0-SNAPSHOT.jar:*' >> 188 [main] INFO Configuration - caching context >> 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB-IN >> F >> \class >> es' >> >> And I'm not even really using persistence (i.e. it's not inherited in >> my .gwt.xml, but somehow it's getting run anyways either via ErraiBus >> or ErraiCommons). >> -----Original Message----- >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Monday, January 18, 2010 10:39 AM >> To: Kevin Jordan >> Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> This is an interesting theory. You should be able to determine >> whether the stub is generated or not since at compile-time the Errai >> generators show log output for each stub. >> >> You should see a log output that says: "Generated >> marshaller/demarshaller >> for: <classname>" for each entity you've annotated. >> >> On 2010-01-18, at 11:32 AM, Kevin Jordan wrote: >> >>> Not sure what you mean by that, but I'm using Netbeans and my domain >>> POJOs >> are in a separate project which gets included by my web project. The >> projects compile file and I've used my domain POJOs via SOAFace's >> UniversalClient and regular GWT-RPC before without issues. And they >> get put across the wire with Errai, it's just when the class is in a >> separate project that there seems to be a problem and my callback >> isn't called. So I'm wondering if it's an issue with the stub >> getting > generated or something. >> >>> >>> -----Original Message----- >>> From: Thomas SEGISMONT [mailto:tsegismont@gmail.com] >>> Sent: Monday, January 18, 2010 10:12 AM >>> To: Kevin Jordan >>> Cc: Mike Brock; errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> Have you tried to include your project/jar source code in your >>> launch >> configuration ? >>> >>> It sounds more like a GWT configuration problem than an Errai one. >>> >>> If you're using Maven to build your project, you can read this : >>> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/multiproject.ht >>> m >>> l >>> >>> Thomas >>> >>> On Mon, 18 Jan 2010 09:50:40 -0600, "Kevin Jordan" >>> <kevin.jordan(a)xteconline.com&gt; wrote: >>>> I think I've found out one problem. Somehow Errai has trouble if >>>> your >>> POJO >>>> is in an external jar, or in my case another Netbeans project. GWT >>>> will compile my project just fine, but it at least seems to be that >>>> once I go >>> to >>>> another project/jar for my POJO it fails to get to my callback and >>>> does >>> the >>>> behavior I've previously described. >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Friday, January 15, 2010 4:20 PM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> Yes, that will work, of course. >>>> >>>> >>>> >>>> On 2010-01-15, at 4:59 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> >>>> >>>> I haven't yet. But I'll try it and let you know if it works. >>>> >>>> >>>> >>>> So the default constructor provided by the JVM if you don't specify >>>> one won't work? >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Friday, January 15, 2010 3:55 PM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> Have you updated to trunk -- I think that will fix the >>>> InstantiationException? Any serializable class *must* have a >>>> default constructor. >>>> >>>> >>>> >>>> On 2010-01-15, at 4:48 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> Well, I think I've figured it out on my callback problems. I went >>>> back >>> to >>>> just passing a string back and forth and that worked. I then made >>>> a simpler POJO to pass back and forth with just implementing >>>> Serializable which didn't work (no callback call). I then added >>>> the annotation that I just saw in the docs and that didn't work (no >>>> callback call). I then removed >>> Serializable >>>> and the callback gets called, but it gets an error when it tries to >>>> get >>> the >>>> POJO out of the message. >>>> >>>> >>>> >>>> Is there anything extra I need to do for POJOs? >>>> >>>> >>>> >>>> From: errai-users-bounces(a)lists.jboss.org >>>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>>> Jordan >>>> Sent: Thursday, January 14, 2010 4:21 PM >>>> To: 'Mike Brock' >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> Whenever I do that, I seem to get: >>>> >>>> java.lang.InstantiationException: >>>> org.jboss.errai.bus.server.servlet.DefaultBlockingServlet >>>> >>>> at java.lang.Class.newInstance0(Class.java:340) >>>> >>>> at java.lang.Class.newInstance(Class.java:308) >>>> >>>> at >>>> org.apache.catalina.core.StandardWrapper.loadServlet(Unknown >>>> Source) >>>> >>>> at org.apache.catalina.core.StandardWrapper.load(Unknown >>>> Source) >>>> >>>> at >>>> org.apache.catalina.core.StandardContext.loadOnStartup(Unknown >>>> Source) >>>> >>>> at org.apache.catalina.core.StandardContext.start(Unknown >>>> Source) >>>> >>>> at >>> org.apache.catalina.core.ContainerBase.addChildInternal(Unknown >>>> Source) >>>> >>>> at org.apache.catalina.core.ContainerBase.addChild(Unknown >>> Source) >>>> >>>> at org.apache.catalina.core.StandardHost.addChild(Unknown >>>> Source) >>>> >>>> at >>> org.apache.catalina.startup.HostConfig.deployDescriptor(Unknown >>>> Source) >>>> >>>> at >>> org.apache.catalina.startup.HostConfig.deployDescriptors(Unknown >>>> Source) >>>> >>>> at org.apache.catalina.startup.HostConfig.deployApps(Unknown >>>> Source) >>>> >>>> at org.apache.catalina.startup.HostConfig.check(Unknown >>>> Source) >>>> >>>> at >>>> org.apache.catalina.startup.HostConfig.lifecycleEvent(Unknown >>>> Source) >>>> >>>> at >>>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknow >>>> n >>>> Source) >>>> >>>> at >>> org.apache.catalina.core.ContainerBase.backgroundProcess(Unknown >>>> Source) >>>> >>>> at >>>> >>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>> p >>> r >>> ocessC >>>> hildren(Unknown Source) >>>> >>>> at >>>> >>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>> p >>> r >>> ocessC >>>> hildren(Unknown Source) >>>> >>>> at >>>> >>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>> r >>> u >>> n(Unkn >>>> own Source) >>>> >>>> at java.lang.Thread.run(Thread.java:619) >>>> >>>> >>>> >>>> Even in a new project I've created to see if anything is >>>> interfering with Errai somehow. Trying TomcatCometServlet or >>>> ErraiAutoServlet also yields the same results as before in both >>>> cases. Using the listener/Guice >>> filter >>>> works. I've also gotten it so a callback works in my new minimal >>> project. >>>> So now I'm wondering if something else is interfering with it. >>>> I've got Spring Security protecting pretty much everything, >>>> although I think I've tried taking that out before and had the same effect. >>>> I've also got GXT >>>> (http://www.extjs.com/products/gxt/) in there. Along with Mule and >>>> SOAFaces, although SOAFaces can probably go away since I'll be >>>> communicating to Mule via Errai when that works so I can have >>>> better asynchronous communication and also push communication. I >>>> suppose what I'll try first is ripping out GXT since that's >>>> probably the most likely culprit in my mind. >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Thursday, January 14, 2010 12:12 PM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> We will actually be removing the Guice filter as it's created >>>> problems >>> for >>>> deploying on some appservers. We're falling back on directly declaring >>>> the >>>> servlet. So you might want to switch to directly declaring the >>>> DefaultBlockingServlet like so: >>>> >>>> >>>> >>>> <servlet> >>>> >>>> <servlet-name>ErraiServlet</servlet-name> >>>> >>>> >>>> >>> <servlet-class>org.jboss.errai.bus.server.servlet.DefaultBlockingSer >>> v >>> l >>> et</se >>>> rvlet-class> >>>> >>>> <load-on-startup>1</load-on-startup> >>>> >>>> </servlet> >>>> >>>> >>>> >>>> <servlet-mapping> >>>> >>>> <servlet-name>ErraiServlet</servlet-name> >>>> >>>> <url-pattern>*.erraiBus</url-pattern> >>>> >>>> </servlet-mapping> >>>> >>>> >>>> >>>> . >>>> >>>> >>>> >>>> On 2010-01-14, at 12:45 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> Yes. It's still working the way it was before where I have to >>>> submit >>> more >>>> than once and the response comes back on the POST but the callback >>> doesn't >>>> get called. >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Thursday, January 14, 2010 11:44 AM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> Are you still losing messages? >>>> >>>> >>>> >>>> On 2010-01-14, at 12:31 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Switching it back to the listener config seems to make it work >>>> again through the DefaultBlockingServlet. >>>> >>>> >>>> >>>> From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] >>>> Sent: Thursday, January 14, 2010 11:22 AM >>>> To: 'Mike Brock' >>>> Cc: &#39;errai-users(a)lists.jboss.org&#39; >>>> Subject: RE: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> Yeah, I'm using the NIO connector. And actually if I configure the >>>> TomcatCometServlet manually I get the same error again. I know >>>> that used to happen when I was accessing it through my AJP >>>> connected Apache instance, but now I'm accessing it directly >>>> through port 8443 on Tomcat. >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Thursday, January 14, 2010 10:55 AM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> Are you using the NIO connector in Tomcat? Errai by default will >>>> try to use Tomcat's AIO system, which requires that the NIO or APR >>>> connecter be >>> used. >>>> >>>> >>>> >>>> On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> I tried the AutoServlet and it seems to pick the TomcatCometServlet >>>> which makes it spin over and over on this message every time it >>>> tries to access >>>> it: >>>> >>>> >>> ******************************************************************** >>> * >>> * >>> ****** >>>> ********************* >>>> >>>> ** PROBLEM! >>>> >>>> ** It appears something has been incorrectly configured. In order >>>> to use ErraiBus >>>> >>>> ** on Tomcat, you must ensure that you are using the NIO or APR >>> connector. >>>> Also >>>> >>>> ** make sure that you have added these lines to your >>>> WEB-INF/web.xml >>> file: >>>> >>>> ** --- >>>> >>>> ** <servlet> >>>> >>>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>>> >>>> ** >>>> >>> <servlet-class>org.jboss.errai.bus.server.servlet.TomcatCometServlet >>> < >>> / >>> servle >>>> t-class> >>>> >>>> ** <load-on-startup>1</load-on-startup> >>>> >>>> ** </servlet> >>>> >>>> ** >>>> >>>> ** <servlet-mapping> >>>> >>>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>>> >>>> ** <url-pattern>*.erraiBus</url-pattern> >>>> >>>> ** </servlet-mapping> >>>> >>>> ** --- >>>> >>>> ** If you have the following lines in your WEB-INF/web.xml, you >>>> must comment or remove them: >>>> >>>> ** --- >>>> >>>> ** <listener> >>>> >>>> ** >>>> >>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</liste >>> n >>> e >>> r-clas >>>> s> >>>> >>>> ** </listener> >>>> >>>> >>> ******************************************************************** >>> * >>> * >>> ****** >>>> ********************* >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Thursday, January 14, 2010 10:06 AM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> By the way, if you want, we're on IRC on irc.freenode.net in >>>> channel >>> #errai >>>> -- I'm "cbrock" on there if you want help troubleshooting directly. >>>> >>>> >>>> >>>> On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, and >>>> IE on Windows 7. I'm using Tomcat. >>>> >>>> >>>> >>>> I'll try the AutoServlet to see if it makes a difference. >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Wednesday, January 13, 2010 8:35 PM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> If you update to the latest version of trunk, simply get rid of the >>>> listener and replace your web.xml config with this: >>>> >>>> >>>> >>>> <servlet> >>>> >>>> <servlet-name>ErraiAutoServlet</servlet-name> >>>> >>>> >>>> >>> <servlet-class>org.jboss.errai.bus.server.servlet.ErraiAutoServlet</ >>> s >>> e >>> rvlet- >>>> class> >>>> >>>> <load-on-startup>1</load-on-startup> >>>> >>>> </servlet> >>>> >>>> >>>> >>>> <servlet-mapping> >>>> >>>> <servlet-name>ErraiAutoServlet</servlet-name> >>>> >>>> <url-pattern>*.erraiBus</url-pattern> >>>> >>>> </servlet-mapping> >>>> >>>> >>>> >>>> This problem you're having is curious, though. We haven't seen it >>>> in our internal testing. Can you tell me what browser, what >>>> appserver, and what OS you're on? >>>> >>>> >>>> >>>> On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> I'm using the following on the client side: >>>> >>>> bus.subscribe("ItemFound", new MessageCallback() { >>>> >>>> >>>> >>>> @Override >>>> >>>> public void callback(Message message) { >>>> >>>> //throw new >>>> UnsupportedOperationException("Not supported yet."); >>>> >>>> MessageBox.alert("Success", "In >>> Callback", >>>> null); >>>> >>>> /*Map<String,Object> parts = >>>> message.getParts(); >>>> >>>> Set<String> keys = parts.keySet(); >>>> >>>> for (String key : keys) { >>>> >>>> MessageBox.alert("Key",key,null); >>>> >>>> }*/ >>>> >>>> //Item item = message.get(Item.class, >>>> "Item"); >>>> >>>> //MessageBox.alert("Return", >>>> item.getSerialNumber().toString(), null); >>>> >>>> } >>>> >>>> }); >>>> >>>> >>>> >>> MessageBuilder.createMessage().toSubject("Items").signalling().with( >>> M >>> e >>> ssageP >>>> arts.ReplyTo, "ItemFound").with("SerialNumber", >>>> serialInput.getValue().toString()).errorsHandledBy(new >>>> ErrorCallback() { >>>> >>>> >>>> >>>> @Override >>>> >>>> public boolean error(Message message, >>> Throwable >>>> throwable) { >>>> >>>> //throw new >>>> UnsupportedOperationException("Not supported yet."); >>>> >>>> MessageBox.alert("Error", >>>> throwable.getMessage(), null); >>>> >>>> return true; >>>> >>>> } >>>> >>>> }).sendNowWith(bus); >>>> >>>> >>>> >>>> Which sends: >>>> >>>> {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489" >>>> } >>>> >>>> >>>> >>>> Although I've now noticed that it takes 2 tries to get it to send >>>> that >>> and >>>> a >>>> 3rd one to get the response back for the first one. >>>> >>>> >>>> >>>> Server portion looks like: >>>> >>>> @Service("Items") >>>> >>>> public class Items implements MessageCallback { >>>> >>>> private MessageBus bus; >>>> >>>> >>>> >>>> @Inject >>>> >>>> public Items(MessageBus bus) { >>>> >>>> this.bus = bus; >>>> >>>> System.out.println("Got a bus..."); >>>> >>>> } >>>> >>>> >>>> >>>> @Override >>>> >>>> public void callback(Message message) { >>>> >>>> //throw new UnsupportedOperationException("Not supported >>> yet."); >>>> >>>> System.out.println("Incoming message..."); >>>> >>>> String serialNum = message.get(String.class, >>>> "SerialNumber"); >>>> >>>> System.out.println(serialNum); >>>> >>>> Item item = new Item(); >>>> >>>> item.setSerialNumber(Long.parseLong(serialNum)); >>>> >>>> >>>> >>> MessageBuilder.createConversation(message).subjectProvided().signall >>> i >>> n >>> g().wi >>>> th("Item", item).errorsHandledBy(new ErrorCallback() { >>>> >>>> >>>> >>>> @Override >>>> >>>> public boolean error(Message message, Throwable >>> throwable) >>>> { >>>> >>>> //throw new UnsupportedOperationException("Not >>>> supported yet."); >>>> >>>> throwable.printStackTrace(); >>>> >>>> return true; >>>> >>>> } >>>> >>>> }).sendNowWith(bus); >>>> >>>> } >>>> >>>> } >>>> >>>> >>>> >>>> Response on the second POST is: >>>> >>>> >>> [{"ItemFound":{"Item":{__EncodedType:'com.xteconline.system.Item',id: >>> n >>> ull,se >>>> >>> >> > rialNumber:1201489,part:null,storageLocation:null,storageUnit:null,customer: >>>> >>> null,oemSerial:null,manufacturer:null,status:null,itemInfos:null},"T >>> o >>> S >>> ubject >>>> ":"ItemFound"}}] >>>> >>>> >>>> >>>> All others seem to get: >>>> >>>> [{"HeartBeat":null}] >>>> >>>> >>>> >>>> And on the first time I try to submit, it still seems to be kind of >>> setting >>>> up stuff since it sends: >>>> >>>> >>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>> S >>> e >>> rverBu >>>> >>> >> > s","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":" >>>> >>> ServerBus","Subject":"AuthorizationService","PriorityProcessing":"1" >>> } >>> | >>> |{"Com >>>> >>> mandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Clien >>> t >>> N >>> egotia >>>> >>> tionService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscr >>> i >>> b >>> e","To >>>> >>> Subject":"ServerBus","Subject":"ServerEchoService","PriorityProcessi >>> n >>> g >>> ":"1"} >>>> >>> ||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>> ||Cl >>> ||ient >>>> >>> Bus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Sub >>> j >>> e >>> ct":"C >>>> >>> >> > lientBusErrors"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus"," >>>> >>> Subject":"Items"}||{"CommandType":"RemoteSubscribe","ToSubject":"Ser >>> v >>> e >>> rBus", >>>> >>> "Subject":"ServerBus"}||{"CommandType":"RemoteSubscribe","ToSubject":" >>> Server >>>> >>> Bus","Subject":"AuthorizationService"}||{"CommandType":"RemoteSubscr >>> i >>> b >>> e","To >>>> >>> >> > Subject":"ServerBus","Subject":"ClientNegotiationService"}||{"CommandType":" >>>> RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService" >>>> } >>>> >>>> >>>> >>>> And >>>> >>>> >>>> >>>> >>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>> I >>> t >>> emFoun >>>> d","PriorityProcessing":"1"} >>>> >>>> >>>> >>>> But doesn't send my stuff until I submit again. >>>> >>>> >>>> >>>> And about the only other relevant thing I can think of for Errai is >>>> the servlet config: >>>> >>>> <listener> >>>> >>>> >>>> >>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</liste >>> n >>> e >>> r-clas >>>> s> >>>> >>>> </listener> >>>> >>>> >>>> >>>> Which I believe sets up the DefaultBlockingServlet. >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Tuesday, January 12, 2010 11:48 AM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> We have a fairly significant application that makes extensive use >>>> of >>> this >>>> type of paradigm and we haven't ever experienced any dropped messages. >>> Can >>>> you provide me some examples of your code so we can troubleshoot >>>> what's going on? >>>> >>>> >>>> >>>> On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> The MessageParts.ReplyTo was what I was missing in there. However, >>>> my callback doesn't seem to be called. I get something back when >>>> my request is POSTed, but it never seems to call my callback. They >>>> do seem to work sometimes though. I had accidentally named my >>>> callback subject and the server subject the same and when I created >>>> a message to that subject, >>> both >>>> the client callback and the server callback were called correctly. >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Tuesday, January 12, 2010 9:07 AM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> The sender needs to create a listening service that can be replied to. >>> The >>>> best way to do this is like so: >>>> >>>> >>>> >>>> >>>> >>>> //client-side code >>>> >>>> bus.subscribe("MyResponseSvc", >>>> >>>> new MessageCallback() { >>>> >>>> public void callback(Message msg) { >>>> >>>> ... >>>> >>>> } >>>> >>>> } >>>> >>>> ); >>>> >>>> >>>> >>>> >>> MessageBuilder.createMessage().toSubject("ConversationalService").si >>> g >>> n >>> alling >>>> () >>>> >>>> .with(MessageParts.ReplyTo, "MyResponseSvc") >>>> >>>> .with("SomeMessagePart", "Foo") >>>> >>>> .noErrorHandling() >>>> >>>> .sendNowWith(bus); >>>> >>>> >>>> >>>> ... >>>> >>>> //server-side code >>>> >>>> >>>> >>>> MessageBuilder.createConversation(message) >>>> >>>> .subjectProvided().signalling() >>>> >>>> .with("MyResponseData", "Bar") >>>> >>>> .noErrorHandling() >>>> >>>> .sendNowWith(bus); >>>> >>>> >>>> >>>> ... >>>> >>>> >>>> >>>> Note: we may make this more straight forward in the future, such as >>>> with the RPC API. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> I won't be able to use the Swing monitor on the server I'm >>>> deploying to since it has no interface. However, I did start >>>> enabling logging in various places and it does seem that my >>>> services weren't getting started. I was lacking an >>>> ErraiApp.properties which I guess is used as the root for >>> where >>>> it should start looking for services. After adding that, they >>>> started >>> and >>>> stuff started to go through. Does the client keep a record of >>>> services >>> or >>>> something then? Why wouldn't it try to contact the service and >>>> then fail that it couldn't find it? >>>> >>>> >>>> >>>> Also, looking at the revised Message API, how do you listen for the >>>> reply in a conversation? Do I need to create a separate listener? >>>> Before you >>> could >>>> specify a MessageCallback to get the response in the conversation, >>>> but I can't find anywhere in the call chain to do that and it's not >>>> covered in the SVN book. >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Monday, January 11, 2010 3:16 PM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> Kevin, >>>> >>>> >>>> >>>> I'm not sure how you're launching your app, but can you provide >>>> this command line option which will bring up the bus monitor, and >>>> at least tell me if you've probably deployed your services: >>>> -Derrai.bus.showmonitor=true >>>> >>>> >>>> >>>> Also, can you email me the log output from when your startup the >>>> application? >>>> >>>> >>>> >>>> On 2010-01-11, at 3:35 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Changing to a createCall and making a @Endpoint annotated method on >>>> the server seems to make it send something again: >>>> >>>> >>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>> I >>> t >>> ems.ge >>>> tItem:RespondTo:1","PriorityProcessing":"1"} >>>> >>>> >>>> >>>> With a response of: >>>> >>>> [{"HeartBeat":null}] >>>> >>>> >>>> >>>> However, I still so nowhere where it passes the parameter I give it > with: >>>> >>>> MessageBuilder.createCall().call("Items").endpoint("getItem", >>>> serialInput.getValue()).respondTo(Item.class, new >>>> RemoteCallback<Item>() >>> { >>>> >>>> >>>> >>>> @Override >>>> >>>> public void callback(Item response) { >>>> >>>> //throw new >>>> UnsupportedOperationException("Not supported yet."); >>>> >>>> >>>> MessageBox.alert("Return",item.getSerialNumber().toString(),null); >>>> >>>> } >>>> >>>> >>>> >>>> }).noErrorHandling().sendNowWith(bus); >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> From: errai-users-bounces(a)lists.jboss.org >>>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>>> Jordan >>>> Sent: Monday, January 11, 2010 1:46 PM >>>> To: 'Mike Brock' >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> Made the changes specified in the userguide, but now it doesn't >>>> send anything. I'm using the following: >>>> >>>> >>> MessageBuilder.createMessage().toSubject("Items").signalling().with(" >>> S >>> erialN >>>> umber", "Test").noErrorHandling().sendNowWith(bus); >>>> >>>> >>>> >>>> It still seems to be set up just fine since the in.erraiBus servlet >>>> is created and the client long polls it, but the code above doesn't >>>> seem to send anything. I'm using the following way to make it for >>>> the >>>> DefaultBlockingServlet: >>>> >>>> <listener> >>>> >>>> >>>> >>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</liste >>> n >>> e >>> r-clas >>>> s> >>>> >>>> </listener> >>>> >>>> >>>> >>>> Should I be using that? I figure it shouldn't affect the client >>>> any >>> though >>>> unless the servlet is incorrectly set up as a consequence, which it >>> doesn't >>>> seem to be since they communicate just fine for the initial setup. >>>> What should I look at to see why it's not sending? >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Monday, January 11, 2010 12:43 PM >>>> To: Kevin Jordan >>>> Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> You should be aware we have made changes and are retiring the use >>>> of the CommandMessage API. Be sure to read the documentation in >>>> the userguide/src/main/docbook/en/master.xml file. You can use: >>>> mvn jdocbook:generate to create an HTML file from the userguide/ directory. >>>> >>>> >>>> >>>> On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Friday, January 08, 2010 2:56 PM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> I will check into this. We're still working on getting the AIO >>>> stuff >>>> sorted>Monday, January 11, 2010 8:59 AM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> >>>> >>>> Hi Kevin, the compilation problems should be fixed already. >>>> >>>> >>>> >>>> >>>> >>>> On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Yes, I am using trunk. Is there a more stable branch/version I >>>> should be using? I had updated again hoping it was just something >>>> with the time I checked out and then ran into the problems Heiko >>>> Braun ran into compiling it. >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Friday, January 08, 2010 8:52 PM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> What version of ErraiBus are you using? Are you getting it from trunk? >>>> >>>> >>>> >>>> On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> DefaultBlockingServlet seems to have the same effect. >>>> >>>> >>>> >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Friday, January 08, 2010 2:56 PM >>>> To: Kevin Jordan >>>> Cc: errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> >>>> >>>> I will check into this. We're still working on getting the AIO >>>> stuff sorted, and I wouldn't consider the Tomcat or JBoss adapters >>>> to be production ready. You're best to use the >>>> DefaultBlockingServlet -- which will provide adequate performance >>>> for development while we get the AIO adapters squared away over the >>>> next > few days. >>>> >>>> >>>> >>>> On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> I'm having trouble getting a message to go through using ErraiBus. >>>> I'm using this on the client side: >>>> >>>> CommandMessage msg = (CommandMessage) >>>> CommandMessage.create().toSubject("Items").set("SerialNumber", >>>> serialInput.getValue()); >>>> >>>> bus.conversationWith(msg, new MessageCallback() { >>>> >>>> >>>> >>>> @Override >>>> >>>> public void callback(Message message) { >>>> >>>> //throw new >>>> UnsupportedOperationException("Not supported yet."); >>>> >>>> Item item = message.get(Item.class, >>>> "Item"); >>>> >>>> MessageBox.alert("Errai", >>>> item.getSerialNumber().toString(), null); >>>> >>>> } >>>> >>>> }); >>>> >>>> >>>> >>>> With this on the server side: >>>> >>>> @Service("Items") >>>> >>>> public class Items implements MessageCallback { >>>> >>>> private MessageBus bus; >>>> >>>> >>>> >>>> @Inject >>>> >>>> public Items(MessageBus bus) { >>>> >>>> this.bus = bus; >>>> >>>> System.out.println("Got a bus..."); >>>> >>>> } >>>> >>>> >>>> >>>> @Override >>>> >>>> public void callback(Message message) { >>>> >>>> //throw new UnsupportedOperationException("Not supported >>> yet."); >>>> >>>> System.out.println("Incoming message..."); >>>> >>>> Long serialNum = message.get(Long.class, "SerialNumber"); >>>> >>>> System.out.println(serialNum); >>>> >>>> Item item = new Item(); >>>> >>>> item.setSerialNumber(serialNum); >>>> >>>> >>>> ConversationMessage.create(message).set("Item",item).sendNowWith(bu >>>> s >>>> ) >>>> ; >>>> >>>> } >>>> >>>> >>>> >>>> } >>>> >>>> >>>> >>>> However, all it seems to send is: >>>> >>>> >>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>> t >>> e >>> mp:Con >>>> versation:2","PriorityProcessing":"1"} >>>> >>>> >>>> >>>> I don't see where it actually sends my body or the subject that I >>>> fill >>> out >>>> in my message. Nothing also gets to the Service class. Am I doing >>>> something wrong? I have Tomcat running NIO and everything else >>>> seems set up correctly. It will keep a GET connection open and do >>>> the POST of the >>> JSON >>>> above, but nowhere does it seem to send what I want it to. I also >>>> seem >>> to >>>> be getting these occasionally, usually on some of the first >>>> requests to >>>> in.erraiBus: >>>> >>>> java.lang.NullPointerException >>>> >>>> at >>>> >>> org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(TomcatCo >>> m >>> e >>> tServl >>>> et.java:105) >>>> >>>> at >>>> >>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEven >>> t >>> ( >>> Unknow >>>> n Source) >>>> >>>> at >>>> org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unkno >>>> w >>>> n >>>> Source) >>>> >>>> at org.apache.catalina.core.StandardWrapperValve.event(Unknown >>>> Source) >>>> >>>> at org.apache.catalina.core.StandardContextValve.event(Unknown >>>> Source) >>>> >>>> at org.apache.catalina.core.StandardHostValve.event(Unknown >>> Source) >>>> >>>> at org.apache.catalina.valves.ValveBase.event(Unknown Source) >>>> >>>> at org.apache.catalina.core.StandardEngineValve.event(Unknown >>>> Source) >>>> >>>> at org.apache.catalina.connector.CoyoteAdapter.event(Unknown >>>> Source) >>>> >>>> at org.apache.coyote.http11.Http11NioProcessor.event(Unknown >>>> Source) >>>> >>>> at >>>> >>> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.e >>> v >>> e >>> nt(Unk >>>> nown Source) >>>> >>>> at >>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknown >>> Source) >>>> >>>> at >>>> >>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExe >>> c >>> u >>> tor.ja >>>> va:886) >>>> >>>> at >>>> >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. >>> java:9 >>>> 08) >>>> >>>> at java.lang.Thread.run(Thread.java:619) >>>> >>>> >>>> >>>> Can anyone point me at what I'm missing? >>>> >>>> _______________________________________________ >>>> errai-users mailing list >>>> errai-users(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> errai-users mailing list >>>> errai-users(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>> >>>> >>>> >>>> _______________________________________________ >>>> errai-users mailing list >>>> errai-users(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> errai-users mailing list >>>> errai-users(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/errai-users >>> >> >> > > _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users

Adding that, I can see it picking up my external jar in the List<File> roots parameter, but it still doesn't manage to find the class after that. I think it's because the location it's in has a space which somehow gets replaced with a %20. This makes it not look for the correct file. -----Original Message----- From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 18, 2010 2:06 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages This means that your module is not in the classpath at compile time, and/or you do not have an ErraiApp.properties inside the JAR you wish to scan. Perhaps this is not documented clearly. Every JAR you want Errai to scan *must* have an ErraiApp.properties in it's root folder. The file can be empty. It doesn't have to contain anything. On 2010-01-18, at 2:29 PM, Kevin Jordan wrote: > Okay, in debug mode I see the logging. It definitely doesn't generate > anything for one in a jar file. > > -----Original Message----- > From: errai-users-bounces(a)lists.jboss.org > [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin Jordan > Sent: Monday, January 18, 2010 1:09 PM > To: 'Mike Brock' > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > Sometimes, although seeing as my application will be secured with > authentication and very soon will depend on it, that may not be an > option for much longer. Usually I just compile and deploy it. There > shouldn't be anything really special about the way it's compiled, > seeing as I can compile it using Hudson as well since Netbeans just uses Ant. > > -----Original Message----- > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Monday, January 18, 2010 1:01 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > I'm not really familiar with NetBeans. > > Are you using the GWT Development Mode for testing? > > On 2010-01-18, at 1:53 PM, Kevin Jordan wrote: > >> Yeah, that's the only stuff that comes out during the compile phase. >> Not sure if I have something misconfigured in my logging, but that's >> the only places that print out. >> >> -----Original Message----- >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Monday, January 18, 2010 10:45 AM >> To: Kevin Jordan >> Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> This is for the compile-phase stuff. If you're running in hosted >> mode, you need to look in the GWT Development Mode logger. >> >> On 2010-01-18, at 11:43 AM, Kevin Jordan wrote: >> >>> Is there any logging I have to set up for a particular class or >>> package or any configuration I have to do for that? Normally, even >>> when it works, the only output I see from Errai while compiling is: >>> 0 [main] INFO Configuration - configuration scan targets >>> 0 [main] INFO Configuration - -> >>> >> > C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-persistence-1. >>> 0-SNAPSHOT.jar >>> 0 [main] INFO Configuration - -> >>> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\src\java >>> 0 [main] INFO Configuration - -> >>> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB-IN >>> F >>> \ >>> classe >>> s >>> 63 [main] INFO Configuration - caching context >>> 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-persi >>> s >>> t >>> ence-1 >>> .0-SNAPSHOT.jar:*' >>> 188 [main] INFO Configuration - caching context >>> 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB-I >>> N >>> F >>> \class >>> es' >>> >>> And I'm not even really using persistence (i.e. it's not inherited >>> in my .gwt.xml, but somehow it's getting run anyways either via >>> ErraiBus or ErraiCommons). >>> -----Original Message----- >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Monday, January 18, 2010 10:39 AM >>> To: Kevin Jordan >>> Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> This is an interesting theory. You should be able to determine >>> whether the stub is generated or not since at compile-time the Errai >>> generators show log output for each stub. >>> >>> You should see a log output that says: "Generated >>> marshaller/demarshaller >>> for: <classname>" for each entity you've annotated. >>> >>> On 2010-01-18, at 11:32 AM, Kevin Jordan wrote: >>> >>>> Not sure what you mean by that, but I'm using Netbeans and my >>>> domain POJOs >>> are in a separate project which gets included by my web project. >>> The projects compile file and I've used my domain POJOs via >>> SOAFace's UniversalClient and regular GWT-RPC before without issues. >>> And they get put across the wire with Errai, it's just when the >>> class is in a separate project that there seems to be a problem and >>> my callback isn't called. So I'm wondering if it's an issue with >>> the stub getting >> generated or something. >>> >>>> >>>> -----Original Message----- >>>> From: Thomas SEGISMONT [mailto:tsegismont@gmail.com] >>>> Sent: Monday, January 18, 2010 10:12 AM >>>> To: Kevin Jordan >>>> Cc: Mike Brock; errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> Have you tried to include your project/jar source code in your >>>> launch >>> configuration ? >>>> >>>> It sounds more like a GWT configuration problem than an Errai one. >>>> >>>> If you're using Maven to build your project, you can read this : >>>> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/multiproject.h >>>> t >>>> m >>>> l >>>> >>>> Thomas >>>> >>>> On Mon, 18 Jan 2010 09:50:40 -0600, "Kevin Jordan" >>>> <kevin.jordan(a)xteconline.com&gt; wrote: >>>>> I think I've found out one problem. Somehow Errai has trouble if >>>>> your >>>> POJO >>>>> is in an external jar, or in my case another Netbeans project. >>>>> GWT will compile my project just fine, but it at least seems to be >>>>> that once I go >>>> to >>>>> another project/jar for my POJO it fails to get to my callback and >>>>> does >>>> the >>>>> behavior I've previously described. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Friday, January 15, 2010 4:20 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Yes, that will work, of course. >>>>> >>>>> >>>>> >>>>> On 2010-01-15, at 4:59 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I haven't yet. But I'll try it and let you know if it works. >>>>> >>>>> >>>>> >>>>> So the default constructor provided by the JVM if you don't >>>>> specify one won't work? >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Friday, January 15, 2010 3:55 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Have you updated to trunk -- I think that will fix the >>>>> InstantiationException? Any serializable class *must* have a >>>>> default constructor. >>>>> >>>>> >>>>> >>>>> On 2010-01-15, at 4:48 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Well, I think I've figured it out on my callback problems. I went >>>>> back >>>> to >>>>> just passing a string back and forth and that worked. I then made >>>>> a simpler POJO to pass back and forth with just implementing >>>>> Serializable which didn't work (no callback call). I then added >>>>> the annotation that I just saw in the docs and that didn't work >>>>> (no callback call). I then removed >>>> Serializable >>>>> and the callback gets called, but it gets an error when it tries >>>>> to get >>>> the >>>>> POJO out of the message. >>>>> >>>>> >>>>> >>>>> Is there anything extra I need to do for POJOs? >>>>> >>>>> >>>>> >>>>> From: errai-users-bounces(a)lists.jboss.org >>>>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>>>> Jordan >>>>> Sent: Thursday, January 14, 2010 4:21 PM >>>>> To: 'Mike Brock' >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Whenever I do that, I seem to get: >>>>> >>>>> java.lang.InstantiationException: >>>>> org.jboss.errai.bus.server.servlet.DefaultBlockingServlet >>>>> >>>>> at java.lang.Class.newInstance0(Class.java:340) >>>>> >>>>> at java.lang.Class.newInstance(Class.java:308) >>>>> >>>>> at >>>>> org.apache.catalina.core.StandardWrapper.loadServlet(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardWrapper.load(Unknown >>>>> Source) >>>>> >>>>> at >>>>> org.apache.catalina.core.StandardContext.loadOnStartup(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardContext.start(Unknown >>>>> Source) >>>>> >>>>> at >>>> org.apache.catalina.core.ContainerBase.addChildInternal(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.ContainerBase.addChild(Unknown >>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardHost.addChild(Unknown >>>>> Source) >>>>> >>>>> at >>>> org.apache.catalina.startup.HostConfig.deployDescriptor(Unknown >>>>> Source) >>>>> >>>>> at >>>> org.apache.catalina.startup.HostConfig.deployDescriptors(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.startup.HostConfig.deployApps(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.startup.HostConfig.check(Unknown >>>>> Source) >>>>> >>>>> at >>>>> org.apache.catalina.startup.HostConfig.lifecycleEvent(Unknown >>>>> Source) >>>>> >>>>> at >>>>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unkno >>>>> w >>>>> n >>>>> Source) >>>>> >>>>> at >>>> org.apache.catalina.core.ContainerBase.backgroundProcess(Unknown >>>>> Source) >>>>> >>>>> at >>>>> >>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>> p >>>> r >>>> ocessC >>>>> hildren(Unknown Source) >>>>> >>>>> at >>>>> >>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>> p >>>> r >>>> ocessC >>>>> hildren(Unknown Source) >>>>> >>>>> at >>>>> >>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>> r >>>> u >>>> n(Unkn >>>>> own Source) >>>>> >>>>> at java.lang.Thread.run(Thread.java:619) >>>>> >>>>> >>>>> >>>>> Even in a new project I've created to see if anything is >>>>> interfering with Errai somehow. Trying TomcatCometServlet or >>>>> ErraiAutoServlet also yields the same results as before in both >>>>> cases. Using the listener/Guice >>>> filter >>>>> works. I've also gotten it so a callback works in my new minimal >>>> project. >>>>> So now I'm wondering if something else is interfering with it. >>>>> I've got Spring Security protecting pretty much everything, >>>>> although I think I've tried taking that out before and had the >>>>> same > effect. >>>>> I've also got GXT >>>>> (http://www.extjs.com/products/gxt/) in there. Along with Mule >>>>> and SOAFaces, although SOAFaces can probably go away since I'll be >>>>> communicating to Mule via Errai when that works so I can have >>>>> better asynchronous communication and also push communication. I >>>>> suppose what I'll try first is ripping out GXT since that's >>>>> probably the most likely culprit in my mind. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Thursday, January 14, 2010 12:12 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> We will actually be removing the Guice filter as it's created >>>>> problems >>>> for >>>>> deploying on some appservers. We're falling back on directly > declaring >>>>> the >>>>> servlet. So you might want to switch to directly declaring the >>>>> DefaultBlockingServlet like so: >>>>> >>>>> >>>>> >>>>> <servlet> >>>>> >>>>> <servlet-name>ErraiServlet</servlet-name> >>>>> >>>>> >>>>> >>>> <servlet-class>org.jboss.errai.bus.server.servlet.DefaultBlockingSe >>>> r >>>> v >>>> l >>>> et</se >>>>> rvlet-class> >>>>> >>>>> <load-on-startup>1</load-on-startup> >>>>> >>>>> </servlet> >>>>> >>>>> >>>>> >>>>> <servlet-mapping> >>>>> >>>>> <servlet-name>ErraiServlet</servlet-name> >>>>> >>>>> <url-pattern>*.erraiBus</url-pattern> >>>>> >>>>> </servlet-mapping> >>>>> >>>>> >>>>> >>>>> . >>>>> >>>>> >>>>> >>>>> On 2010-01-14, at 12:45 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> Yes. It's still working the way it was before where I have to >>>>> submit >>>> more >>>>> than once and the response comes back on the POST but the callback >>>> doesn't >>>>> get called. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Thursday, January 14, 2010 11:44 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Are you still losing messages? >>>>> >>>>> >>>>> >>>>> On 2010-01-14, at 12:31 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Switching it back to the listener config seems to make it work >>>>> again through the DefaultBlockingServlet. >>>>> >>>>> >>>>> >>>>> From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] >>>>> Sent: Thursday, January 14, 2010 11:22 AM >>>>> To: 'Mike Brock' >>>>> Cc: &#39;errai-users(a)lists.jboss.org&#39; >>>>> Subject: RE: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Yeah, I'm using the NIO connector. And actually if I configure >>>>> the TomcatCometServlet manually I get the same error again. I >>>>> know that used to happen when I was accessing it through my AJP >>>>> connected Apache instance, but now I'm accessing it directly >>>>> through port 8443 on Tomcat. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Thursday, January 14, 2010 10:55 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Are you using the NIO connector in Tomcat? Errai by default will >>>>> try to use Tomcat's AIO system, which requires that the NIO or APR >>>>> connecter be >>>> used. >>>>> >>>>> >>>>> >>>>> On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> I tried the AutoServlet and it seems to pick the >>>>> TomcatCometServlet which makes it spin over and over on this >>>>> message every time it tries to access >>>>> it: >>>>> >>>>> >>>> ******************************************************************* >>>> * >>>> * >>>> * >>>> ****** >>>>> ********************* >>>>> >>>>> ** PROBLEM! >>>>> >>>>> ** It appears something has been incorrectly configured. In order >>>>> to use ErraiBus >>>>> >>>>> ** on Tomcat, you must ensure that you are using the NIO or APR >>>> connector. >>>>> Also >>>>> >>>>> ** make sure that you have added these lines to your >>>>> WEB-INF/web.xml >>>> file: >>>>> >>>>> ** --- >>>>> >>>>> ** <servlet> >>>>> >>>>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>>>> >>>>> ** >>>>> >>>> <servlet-class>org.jboss.errai.bus.server.servlet.TomcatCometServle >>>> t >>>> < >>>> / >>>> servle >>>>> t-class> >>>>> >>>>> ** <load-on-startup>1</load-on-startup> >>>>> >>>>> ** </servlet> >>>>> >>>>> ** >>>>> >>>>> ** <servlet-mapping> >>>>> >>>>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>>>> >>>>> ** <url-pattern>*.erraiBus</url-pattern> >>>>> >>>>> ** </servlet-mapping> >>>>> >>>>> ** --- >>>>> >>>>> ** If you have the following lines in your WEB-INF/web.xml, you >>>>> must comment or remove them: >>>>> >>>>> ** --- >>>>> >>>>> ** <listener> >>>>> >>>>> ** >>>>> >>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</list >>>> e >>>> n >>>> e >>>> r-clas >>>>> s> >>>>> >>>>> ** </listener> >>>>> >>>>> >>>> ******************************************************************* >>>> * >>>> * >>>> * >>>> ****** >>>>> ********************* >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Thursday, January 14, 2010 10:06 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> By the way, if you want, we're on IRC on irc.freenode.net in >>>>> channel >>>> #errai >>>>> -- I'm "cbrock" on there if you want help troubleshooting directly. >>>>> >>>>> >>>>> >>>>> On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, and >>>>> IE on Windows 7. I'm using Tomcat. >>>>> >>>>> >>>>> >>>>> I'll try the AutoServlet to see if it makes a difference. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Wednesday, January 13, 2010 8:35 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> If you update to the latest version of trunk, simply get rid of >>>>> the listener and replace your web.xml config with this: >>>>> >>>>> >>>>> >>>>> <servlet> >>>>> >>>>> <servlet-name>ErraiAutoServlet</servlet-name> >>>>> >>>>> >>>>> >>>> <servlet-class>org.jboss.errai.bus.server.servlet.ErraiAutoServlet< >>>> / >>>> s >>>> e >>>> rvlet- >>>>> class> >>>>> >>>>> <load-on-startup>1</load-on-startup> >>>>> >>>>> </servlet> >>>>> >>>>> >>>>> >>>>> <servlet-mapping> >>>>> >>>>> <servlet-name>ErraiAutoServlet</servlet-name> >>>>> >>>>> <url-pattern>*.erraiBus</url-pattern> >>>>> >>>>> </servlet-mapping> >>>>> >>>>> >>>>> >>>>> This problem you're having is curious, though. We haven't seen it >>>>> in our internal testing. Can you tell me what browser, what >>>>> appserver, and what OS you're on? >>>>> >>>>> >>>>> >>>>> On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I'm using the following on the client side: >>>>> >>>>> bus.subscribe("ItemFound", new MessageCallback() { >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public void callback(Message message) { >>>>> >>>>> //throw new >>>>> UnsupportedOperationException("Not supported yet."); >>>>> >>>>> MessageBox.alert("Success", "In >>>> Callback", >>>>> null); >>>>> >>>>> /*Map<String,Object> parts = >>>>> message.getParts(); >>>>> >>>>> Set<String> keys = parts.keySet(); >>>>> >>>>> for (String key : keys) { >>>>> >>>>> MessageBox.alert("Key",key,null); >>>>> >>>>> }*/ >>>>> >>>>> //Item item = message.get(Item.class, >>>>> "Item"); >>>>> >>>>> //MessageBox.alert("Return", >>>>> item.getSerialNumber().toString(), null); >>>>> >>>>> } >>>>> >>>>> }); >>>>> >>>>> >>>>> >>>> MessageBuilder.createMessage().toSubject("Items").signalling().with >>>> ( >>>> M >>>> e >>>> ssageP >>>>> arts.ReplyTo, "ItemFound").with("SerialNumber", >>>>> serialInput.getValue().toString()).errorsHandledBy(new >>>>> ErrorCallback() { >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public boolean error(Message message, >>>> Throwable >>>>> throwable) { >>>>> >>>>> //throw new >>>>> UnsupportedOperationException("Not supported yet."); >>>>> >>>>> MessageBox.alert("Error", >>>>> throwable.getMessage(), null); >>>>> >>>>> return true; >>>>> >>>>> } >>>>> >>>>> }).sendNowWith(bus); >>>>> >>>>> >>>>> >>>>> Which sends: >>>>> >>>>> {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489" >>>>> } >>>>> >>>>> >>>>> >>>>> Although I've now noticed that it takes 2 tries to get it to send >>>>> that >>>> and >>>>> a >>>>> 3rd one to get the response back for the first one. >>>>> >>>>> >>>>> >>>>> Server portion looks like: >>>>> >>>>> @Service("Items") >>>>> >>>>> public class Items implements MessageCallback { >>>>> >>>>> private MessageBus bus; >>>>> >>>>> >>>>> >>>>> @Inject >>>>> >>>>> public Items(MessageBus bus) { >>>>> >>>>> this.bus = bus; >>>>> >>>>> System.out.println("Got a bus..."); >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public void callback(Message message) { >>>>> >>>>> //throw new UnsupportedOperationException("Not supported >>>> yet."); >>>>> >>>>> System.out.println("Incoming message..."); >>>>> >>>>> String serialNum = message.get(String.class, >>>>> "SerialNumber"); >>>>> >>>>> System.out.println(serialNum); >>>>> >>>>> Item item = new Item(); >>>>> >>>>> item.setSerialNumber(Long.parseLong(serialNum)); >>>>> >>>>> >>>>> >>>> MessageBuilder.createConversation(message).subjectProvided().signal >>>> l >>>> i >>>> n >>>> g().wi >>>>> th("Item", item).errorsHandledBy(new ErrorCallback() { >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public boolean error(Message message, Throwable >>>> throwable) >>>>> { >>>>> >>>>> //throw new UnsupportedOperationException("Not >>>>> supported yet."); >>>>> >>>>> throwable.printStackTrace(); >>>>> >>>>> return true; >>>>> >>>>> } >>>>> >>>>> }).sendNowWith(bus); >>>>> >>>>> } >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> Response on the second POST is: >>>>> >>>>> >>>> [{"ItemFound":{"Item":{__EncodedType:'com.xteconline.system.Item',id: >>>> n >>>> ull,se >>>>> >>>> >>> >> > rialNumber:1201489,part:null,storageLocation:null,storageUnit:null,customer: >>>>> >>>> null,oemSerial:null,manufacturer:null,status:null,itemInfos:null}," >>>> T >>>> o >>>> S >>>> ubject >>>>> ":"ItemFound"}}] >>>>> >>>>> >>>>> >>>>> All others seem to get: >>>>> >>>>> [{"HeartBeat":null}] >>>>> >>>>> >>>>> >>>>> And on the first time I try to submit, it still seems to be kind >>>>> of >>>> setting >>>>> up stuff since it sends: >>>>> >>>>> >>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>> S >>>> e >>>> rverBu >>>>> >>>> >>> >> > s","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":" >>>>> >>>> ServerBus","Subject":"AuthorizationService","PriorityProcessing":"1" >>>> } >>>> | >>>> |{"Com >>>>> >>>> mandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Clie >>>> n >>>> t >>>> N >>>> egotia >>>>> >>>> tionService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubsc >>>> r >>>> i >>>> b >>>> e","To >>>>> >>>> Subject":"ServerBus","Subject":"ServerEchoService","PriorityProcess >>>> i >>>> n >>>> g >>>> ":"1"} >>>>> >>>> ||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>> ||Cl >>>> ||ient >>>>> >>>> Bus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Su >>>> b >>>> j >>>> e >>>> ct":"C >>>>> >>>> >>> >> > lientBusErrors"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus"," >>>>> >>>> Subject":"Items"}||{"CommandType":"RemoteSubscribe","ToSubject":"Se >>>> r >>>> v >>>> e >>>> rBus", >>>>> >>>> "Subject":"ServerBus"}||{"CommandType":"RemoteSubscribe","ToSubject":" >>>> Server >>>>> >>>> Bus","Subject":"AuthorizationService"}||{"CommandType":"RemoteSubsc >>>> r >>>> i >>>> b >>>> e","To >>>>> >>>> >>> >> > Subject":"ServerBus","Subject":"ClientNegotiationService"}||{"CommandType":" >>>>> RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService" >>>>> } >>>>> >>>>> >>>>> >>>>> And >>>>> >>>>> >>>>> >>>>> >>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>> I >>>> t >>>> emFoun >>>>> d","PriorityProcessing":"1"} >>>>> >>>>> >>>>> >>>>> But doesn't send my stuff until I submit again. >>>>> >>>>> >>>>> >>>>> And about the only other relevant thing I can think of for Errai >>>>> is the servlet config: >>>>> >>>>> <listener> >>>>> >>>>> >>>>> >>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</list >>>> e >>>> n >>>> e >>>> r-clas >>>>> s> >>>>> >>>>> </listener> >>>>> >>>>> >>>>> >>>>> Which I believe sets up the DefaultBlockingServlet. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Tuesday, January 12, 2010 11:48 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> We have a fairly significant application that makes extensive use >>>>> of >>>> this >>>>> type of paradigm and we haven't ever experienced any dropped messages. >>>> Can >>>>> you provide me some examples of your code so we can troubleshoot >>>>> what's going on? >>>>> >>>>> >>>>> >>>>> On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> The MessageParts.ReplyTo was what I was missing in there. >>>>> However, my callback doesn't seem to be called. I get something >>>>> back when my request is POSTed, but it never seems to call my >>>>> callback. They do seem to work sometimes though. I had >>>>> accidentally named my callback subject and the server subject the >>>>> same and when I created a message to that subject, >>>> both >>>>> the client callback and the server callback were called correctly. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Tuesday, January 12, 2010 9:07 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> The sender needs to create a listening service that can be replied to. >>>> The >>>>> best way to do this is like so: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> //client-side code >>>>> >>>>> bus.subscribe("MyResponseSvc", >>>>> >>>>> new MessageCallback() { >>>>> >>>>> public void callback(Message msg) { >>>>> >>>>> ... >>>>> >>>>> } >>>>> >>>>> } >>>>> >>>>> ); >>>>> >>>>> >>>>> >>>>> >>>> MessageBuilder.createMessage().toSubject("ConversationalService").s >>>> i >>>> g >>>> n >>>> alling >>>>> () >>>>> >>>>> .with(MessageParts.ReplyTo, "MyResponseSvc") >>>>> >>>>> .with("SomeMessagePart", "Foo") >>>>> >>>>> .noErrorHandling() >>>>> >>>>> .sendNowWith(bus); >>>>> >>>>> >>>>> >>>>> ... >>>>> >>>>> //server-side code >>>>> >>>>> >>>>> >>>>> MessageBuilder.createConversation(message) >>>>> >>>>> .subjectProvided().signalling() >>>>> >>>>> .with("MyResponseData", "Bar") >>>>> >>>>> .noErrorHandling() >>>>> >>>>> .sendNowWith(bus); >>>>> >>>>> >>>>> >>>>> ... >>>>> >>>>> >>>>> >>>>> Note: we may make this more straight forward in the future, such >>>>> as with the RPC API. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I won't be able to use the Swing monitor on the server I'm >>>>> deploying to since it has no interface. However, I did start >>>>> enabling logging in various places and it does seem that my >>>>> services weren't getting started. I was lacking an >>>>> ErraiApp.properties which I guess is used as the root for >>>> where >>>>> it should start looking for services. After adding that, they >>>>> started >>>> and >>>>> stuff started to go through. Does the client keep a record of >>>>> services >>>> or >>>>> something then? Why wouldn't it try to contact the service and >>>>> then fail that it couldn't find it? >>>>> >>>>> >>>>> >>>>> Also, looking at the revised Message API, how do you listen for >>>>> the reply in a conversation? Do I need to create a separate listener? >>>>> Before you >>>> could >>>>> specify a MessageCallback to get the response in the conversation, >>>>> but I can't find anywhere in the call chain to do that and it's >>>>> not covered in the SVN book. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Monday, January 11, 2010 3:16 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Kevin, >>>>> >>>>> >>>>> >>>>> I'm not sure how you're launching your app, but can you provide >>>>> this command line option which will bring up the bus monitor, and >>>>> at least tell me if you've probably deployed your services: >>>>> -Derrai.bus.showmonitor=true >>>>> >>>>> >>>>> >>>>> Also, can you email me the log output from when your startup the >>>>> application? >>>>> >>>>> >>>>> >>>>> On 2010-01-11, at 3:35 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Changing to a createCall and making a @Endpoint annotated method >>>>> on the server seems to make it send something again: >>>>> >>>>> >>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>> I >>>> t >>>> ems.ge >>>>> tItem:RespondTo:1","PriorityProcessing":"1"} >>>>> >>>>> >>>>> >>>>> With a response of: >>>>> >>>>> [{"HeartBeat":null}] >>>>> >>>>> >>>>> >>>>> However, I still so nowhere where it passes the parameter I give >>>>> it >> with: >>>>> >>>>> MessageBuilder.createCall().call("Items").endpoint("getItem", >>>>> serialInput.getValue()).respondTo(Item.class, new >>>>> RemoteCallback<Item>() >>>> { >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public void callback(Item response) { >>>>> >>>>> //throw new >>>>> UnsupportedOperationException("Not supported yet."); >>>>> >>>>> >>>>> MessageBox.alert("Return",item.getSerialNumber().toString(),null); >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> }).noErrorHandling().sendNowWith(bus); >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> From: errai-users-bounces(a)lists.jboss.org >>>>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>>>> Jordan >>>>> Sent: Monday, January 11, 2010 1:46 PM >>>>> To: 'Mike Brock' >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Made the changes specified in the userguide, but now it doesn't >>>>> send anything. I'm using the following: >>>>> >>>>> >>>> MessageBuilder.createMessage().toSubject("Items").signalling().with(" >>>> S >>>> erialN >>>>> umber", "Test").noErrorHandling().sendNowWith(bus); >>>>> >>>>> >>>>> >>>>> It still seems to be set up just fine since the in.erraiBus >>>>> servlet is created and the client long polls it, but the code >>>>> above doesn't seem to send anything. I'm using the following way >>>>> to make it for the >>>>> DefaultBlockingServlet: >>>>> >>>>> <listener> >>>>> >>>>> >>>>> >>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</list >>>> e >>>> n >>>> e >>>> r-clas >>>>> s> >>>>> >>>>> </listener> >>>>> >>>>> >>>>> >>>>> Should I be using that? I figure it shouldn't affect the client >>>>> any >>>> though >>>>> unless the servlet is incorrectly set up as a consequence, which >>>>> it >>>> doesn't >>>>> seem to be since they communicate just fine for the initial setup. >>>>> What should I look at to see why it's not sending? >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Monday, January 11, 2010 12:43 PM >>>>> To: Kevin Jordan >>>>> Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> You should be aware we have made changes and are retiring the use >>>>> of the CommandMessage API. Be sure to read the documentation in >>>>> the userguide/src/main/docbook/en/master.xml file. You can use: >>>>> mvn jdocbook:generate to create an HTML file from the userguide/ > directory. >>>>> >>>>> >>>>> >>>>> On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Friday, January 08, 2010 2:56 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> I will check into this. We're still working on getting the AIO >>>>> stuff >>>>> sorted>Monday, January 11, 2010 8:59 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Hi Kevin, the compilation problems should be fixed already. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Yes, I am using trunk. Is there a more stable branch/version I >>>>> should be using? I had updated again hoping it was just something >>>>> with the time I checked out and then ran into the problems Heiko >>>>> Braun ran into compiling it. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Friday, January 08, 2010 8:52 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> What version of ErraiBus are you using? Are you getting it from trunk? >>>>> >>>>> >>>>> >>>>> On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> DefaultBlockingServlet seems to have the same effect. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Friday, January 08, 2010 2:56 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> I will check into this. We're still working on getting the AIO >>>>> stuff sorted, and I wouldn't consider the Tomcat or JBoss adapters >>>>> to be production ready. You're best to use the >>>>> DefaultBlockingServlet -- which will provide adequate performance >>>>> for development while we get the AIO adapters squared away over >>>>> the next >> few days. >>>>> >>>>> >>>>> >>>>> On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I'm having trouble getting a message to go through using ErraiBus. >>>>> I'm using this on the client side: >>>>> >>>>> CommandMessage msg = (CommandMessage) >>>>> CommandMessage.create().toSubject("Items").set("SerialNumber", >>>>> serialInput.getValue()); >>>>> >>>>> bus.conversationWith(msg, new MessageCallback() { >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public void callback(Message message) { >>>>> >>>>> //throw new >>>>> UnsupportedOperationException("Not supported yet."); >>>>> >>>>> Item item = message.get(Item.class, >>>>> "Item"); >>>>> >>>>> MessageBox.alert("Errai", >>>>> item.getSerialNumber().toString(), null); >>>>> >>>>> } >>>>> >>>>> }); >>>>> >>>>> >>>>> >>>>> With this on the server side: >>>>> >>>>> @Service("Items") >>>>> >>>>> public class Items implements MessageCallback { >>>>> >>>>> private MessageBus bus; >>>>> >>>>> >>>>> >>>>> @Inject >>>>> >>>>> public Items(MessageBus bus) { >>>>> >>>>> this.bus = bus; >>>>> >>>>> System.out.println("Got a bus..."); >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public void callback(Message message) { >>>>> >>>>> //throw new UnsupportedOperationException("Not supported >>>> yet."); >>>>> >>>>> System.out.println("Incoming message..."); >>>>> >>>>> Long serialNum = message.get(Long.class, "SerialNumber"); >>>>> >>>>> System.out.println(serialNum); >>>>> >>>>> Item item = new Item(); >>>>> >>>>> item.setSerialNumber(serialNum); >>>>> >>>>> >>>>> ConversationMessage.create(message).set("Item",item).sendNowWith(b >>>>> u >>>>> s >>>>> ) >>>>> ; >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> However, all it seems to send is: >>>>> >>>>> >>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>> t >>>> e >>>> mp:Con >>>>> versation:2","PriorityProcessing":"1"} >>>>> >>>>> >>>>> >>>>> I don't see where it actually sends my body or the subject that I >>>>> fill >>>> out >>>>> in my message. Nothing also gets to the Service class. Am I >>>>> doing something wrong? I have Tomcat running NIO and everything >>>>> else seems set up correctly. It will keep a GET connection open >>>>> and do the POST of the >>>> JSON >>>>> above, but nowhere does it seem to send what I want it to. I also >>>>> seem >>>> to >>>>> be getting these occasionally, usually on some of the first >>>>> requests to >>>>> in.erraiBus: >>>>> >>>>> java.lang.NullPointerException >>>>> >>>>> at >>>>> >>>> org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(TomcatC >>>> o >>>> m >>>> e >>>> tServl >>>>> et.java:105) >>>>> >>>>> at >>>>> >>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEve >>>> n >>>> t >>>> ( >>>> Unknow >>>>> n Source) >>>>> >>>>> at >>>>> org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unkn >>>>> o >>>>> w >>>>> n >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardWrapperValve.event(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardContextValve.event(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardHostValve.event(Unknown >>>> Source) >>>>> >>>>> at org.apache.catalina.valves.ValveBase.event(Unknown Source) >>>>> >>>>> at org.apache.catalina.core.StandardEngineValve.event(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.connector.CoyoteAdapter.event(Unknown >>>>> Source) >>>>> >>>>> at org.apache.coyote.http11.Http11NioProcessor.event(Unknown >>>>> Source) >>>>> >>>>> at >>>>> >>>> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler. >>>> e >>>> v >>>> e >>>> nt(Unk >>>>> nown Source) >>>>> >>>>> at >>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknown >>>> Source) >>>>> >>>>> at >>>>> >>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolEx >>>> e >>>> c >>>> u >>>> tor.ja >>>>> va:886) >>>>> >>>>> at >>>>> >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. >>>> java:9 >>>>> 08) >>>>> >>>>> at java.lang.Thread.run(Thread.java:619) >>>>> >>>>> >>>>> >>>>> Can anyone point me at what I'm missing? >>>>> >>>>> _______________________________________________ >>>>> errai-users mailing list >>>>> errai-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> errai-users mailing list >>>>> errai-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> errai-users mailing list >>>>> errai-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> errai-users mailing list >>>>> errai-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>> >>> >>> >> >> > > > _______________________________________________ > errai-users mailing list > errai-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/errai-users >

Adding that, I can see it picking up my external jar in the List<File> roots parameter, but it still doesn't manage to find the class after that. I think it's because the location it's in has a space which somehow gets replaced with a %20. This makes it not look for the correct

-----Original Message----- From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 18, 2010 2:06 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages This means that your module is not in the classpath at compile time, and/or you do not have an ErraiApp.properties inside the JAR you wish to

Perhaps this is not documented clearly. Every JAR you want Errai to scan *must* have an ErraiApp.properties in it's root folder. The file can be empty. It doesn't have to contain

On 2010-01-18, at 2:29 PM, Kevin Jordan wrote: > Okay, in debug mode I see the logging. It definitely doesn't > generate anything for one in a jar file. > > -----Original Message----- > From: errai-users-bounces(a)lists.jboss.org > [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin > Jordan > Sent: Monday, January 18, 2010 1:09 PM > To: 'Mike Brock' > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > Sometimes, although seeing as my application will be secured with > authentication and very soon will depend on it, that may not be an > option for much longer. Usually I just compile and deploy it. There > shouldn't be anything really special about the way it's compiled, > seeing as I can compile it using Hudson as well since Netbeans just > uses Ant. > > -----Original Message----- > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Monday, January 18, 2010 1:01 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > I'm not really familiar with NetBeans. > > Are you using the GWT Development Mode for testing? > > On 2010-01-18, at 1:53 PM, Kevin Jordan wrote: > >> Yeah, that's the only stuff that comes out during the compile phase. >> Not sure if I have something misconfigured in my logging, but that's >> the only places that print out. >> >> -----Original Message----- >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Monday, January 18, 2010 10:45 AM >> To: Kevin Jordan >> Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> This is for the compile-phase stuff. If you're running in hosted >> mode, you need to look in the GWT Development Mode logger. >> >> On 2010-01-18, at 11:43 AM, Kevin Jordan wrote: >> >>> Is there any logging I have to set up for a particular class or >>> package or any configuration I have to do for that? Normally, even >>> when it works, the only output I see from Errai while compiling is: >>> 0 [main] INFO Configuration - configuration scan targets >>> 0 [main] INFO Configuration - -> >>> >> >

>>> 0-SNAPSHOT.jar >>> 0 [main] INFO Configuration - -> >>> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\src\java >>> 0 [main] INFO Configuration - -> >>> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB-I >>> N >>> F >>> \ >>> classe >>> s >>> 63 [main] INFO Configuration - caching context >>> 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-pers >>> i >>> s >>> t >>> ence-1 >>> .0-SNAPSHOT.jar:*' >>> 188 [main] INFO Configuration - caching context >>> 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB- >>> I >>> N >>> F >>> \class >>> es' >>> >>> And I'm not even really using persistence (i.e. it's not inherited >>> in my .gwt.xml, but somehow it's getting run anyways either via >>> ErraiBus or ErraiCommons). >>> -----Original Message----- >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Monday, January 18, 2010 10:39 AM >>> To: Kevin Jordan >>> Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> This is an interesting theory. You should be able to determine >>> whether the stub is generated or not since at compile-time the >>> Errai generators show log output for each stub. >>> >>> You should see a log output that says: "Generated >>> marshaller/demarshaller >>> for: <classname>" for each entity you've annotated. >>> >>> On 2010-01-18, at 11:32 AM, Kevin Jordan wrote: >>> >>>> Not sure what you mean by that, but I'm using Netbeans and my >>>> domain POJOs >>> are in a separate project which gets included by my web project. >>> The projects compile file and I've used my domain POJOs via >>> SOAFace's UniversalClient and regular GWT-RPC before without issues. >>> And they get put across the wire with Errai, it's just when the >>> class is in a separate project that there seems to be a problem and >>> my callback isn't called. So I'm wondering if it's an issue with >>> the stub getting >> generated or something. >>> >>>> >>>> -----Original Message----- >>>> From: Thomas SEGISMONT [mailto:tsegismont@gmail.com] >>>> Sent: Monday, January 18, 2010 10:12 AM >>>> To: Kevin Jordan >>>> Cc: Mike Brock; errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> Have you tried to include your project/jar source code in your >>>> launch >>> configuration ? >>>> >>>> It sounds more like a GWT configuration problem than an Errai one. >>>> >>>> If you're using Maven to build your project, you can read this : >>>> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/multiproject. >>>> h >>>> t >>>> m >>>> l >>>> >>>> Thomas >>>> >>>> On Mon, 18 Jan 2010 09:50:40 -0600, "Kevin Jordan" >>>> <kevin.jordan(a)xteconline.com&gt; wrote: >>>>> I think I've found out one problem. Somehow Errai has trouble if >>>>> your >>>> POJO >>>>> is in an external jar, or in my case another Netbeans project. >>>>> GWT will compile my project just fine, but it at least seems to >>>>> be that once I go >>>> to >>>>> another project/jar for my POJO it fails to get to my callback >>>>> and does >>>> the >>>>> behavior I've previously described. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Friday, January 15, 2010 4:20 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Yes, that will work, of course. >>>>> >>>>> >>>>> >>>>> On 2010-01-15, at 4:59 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I haven't yet. But I'll try it and let you know if it works. >>>>> >>>>> >>>>> >>>>> So the default constructor provided by the JVM if you don't >>>>> specify one won't work? >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Friday, January 15, 2010 3:55 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Have you updated to trunk -- I think that will fix the >>>>> InstantiationException? Any serializable class *must* have a >>>>> default constructor. >>>>> >>>>> >>>>> >>>>> On 2010-01-15, at 4:48 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Well, I think I've figured it out on my callback problems. I >>>>> went back >>>> to >>>>> just passing a string back and forth and that worked. I then >>>>> made a simpler POJO to pass back and forth with just implementing >>>>> Serializable which didn't work (no callback call). I then added >>>>> the annotation that I just saw in the docs and that didn't work >>>>> (no callback call). I then removed >>>> Serializable >>>>> and the callback gets called, but it gets an error when it tries >>>>> to get >>>> the >>>>> POJO out of the message. >>>>> >>>>> >>>>> >>>>> Is there anything extra I need to do for POJOs? >>>>> >>>>> >>>>> >>>>> From: errai-users-bounces(a)lists.jboss.org >>>>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>>>> Jordan >>>>> Sent: Thursday, January 14, 2010 4:21 PM >>>>> To: 'Mike Brock' >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Whenever I do that, I seem to get: >>>>> >>>>> java.lang.InstantiationException: >>>>> org.jboss.errai.bus.server.servlet.DefaultBlockingServlet >>>>> >>>>> at java.lang.Class.newInstance0(Class.java:340) >>>>> >>>>> at java.lang.Class.newInstance(Class.java:308) >>>>> >>>>> at >>>>> org.apache.catalina.core.StandardWrapper.loadServlet(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardWrapper.load(Unknown >>>>> Source) >>>>> >>>>> at >>>>> org.apache.catalina.core.StandardContext.loadOnStartup(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardContext.start(Unknown >>>>> Source) >>>>> >>>>> at >>>> org.apache.catalina.core.ContainerBase.addChildInternal(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.ContainerBase.addChild(Unknown >>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardHost.addChild(Unknown >>>>> Source) >>>>> >>>>> at >>>> org.apache.catalina.startup.HostConfig.deployDescriptor(Unknown >>>>> Source) >>>>> >>>>> at >>>> org.apache.catalina.startup.HostConfig.deployDescriptors(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.startup.HostConfig.deployApps(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.startup.HostConfig.check(Unknown >>>>> Source) >>>>> >>>>> at >>>>> org.apache.catalina.startup.HostConfig.lifecycleEvent(Unknown >>>>> Source) >>>>> >>>>> at >>>>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unkn >>>>> o >>>>> w >>>>> n >>>>> Source) >>>>> >>>>> at >>>> org.apache.catalina.core.ContainerBase.backgroundProcess(Unknown >>>>> Source) >>>>> >>>>> at >>>>> >>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>> p >>>> r >>>> ocessC >>>>> hildren(Unknown Source) >>>>> >>>>> at >>>>> >>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>> p >>>> r >>>> ocessC >>>>> hildren(Unknown Source) >>>>> >>>>> at >>>>> >>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>> r >>>> u >>>> n(Unkn >>>>> own Source) >>>>> >>>>> at java.lang.Thread.run(Thread.java:619) >>>>> >>>>> >>>>> >>>>> Even in a new project I've created to see if anything is >>>>> interfering with Errai somehow. Trying TomcatCometServlet or >>>>> ErraiAutoServlet also yields the same results as before in both >>>>> cases. Using the listener/Guice >>>> filter >>>>> works. I've also gotten it so a callback works in my new minimal >>>> project. >>>>> So now I'm wondering if something else is interfering with it. >>>>> I've got Spring Security protecting pretty much everything, >>>>> although I think I've tried taking that out before and had the >>>>> same > effect. >>>>> I've also got GXT >>>>> (http://www.extjs.com/products/gxt/) in there. Along with Mule >>>>> and SOAFaces, although SOAFaces can probably go away since I'll >>>>> be communicating to Mule via Errai when that works so I can have >>>>> better asynchronous communication and also push communication. I >>>>> suppose what I'll try first is ripping out GXT since that's >>>>> probably the most likely culprit in my mind. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Thursday, January 14, 2010 12:12 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> We will actually be removing the Guice filter as it's created >>>>> problems >>>> for >>>>> deploying on some appservers. We're falling back on directly > declaring >>>>> the >>>>> servlet. So you might want to switch to directly declaring the >>>>> DefaultBlockingServlet like so: >>>>> >>>>> >>>>> >>>>> <servlet> >>>>> >>>>> <servlet-name>ErraiServlet</servlet-name> >>>>> >>>>> >>>>> >>>> <servlet-class>org.jboss.errai.bus.server.servlet.DefaultBlockingS >>>> e >>>> r >>>> v >>>> l >>>> et</se >>>>> rvlet-class> >>>>> >>>>> <load-on-startup>1</load-on-startup> >>>>> >>>>> </servlet> >>>>> >>>>> >>>>> >>>>> <servlet-mapping> >>>>> >>>>> <servlet-name>ErraiServlet</servlet-name> >>>>> >>>>> <url-pattern>*.erraiBus</url-pattern> >>>>> >>>>> </servlet-mapping> >>>>> >>>>> >>>>> >>>>> . >>>>> >>>>> >>>>> >>>>> On 2010-01-14, at 12:45 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> Yes. It's still working the way it was before where I have to >>>>> submit >>>> more >>>>> than once and the response comes back on the POST but the >>>>> callback >>>> doesn't >>>>> get called. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Thursday, January 14, 2010 11:44 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Are you still losing messages? >>>>> >>>>> >>>>> >>>>> On 2010-01-14, at 12:31 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Switching it back to the listener config seems to make it work >>>>> again through the DefaultBlockingServlet. >>>>> >>>>> >>>>> >>>>> From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] >>>>> Sent: Thursday, January 14, 2010 11:22 AM >>>>> To: 'Mike Brock' >>>>> Cc: &#39;errai-users(a)lists.jboss.org&#39; >>>>> Subject: RE: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Yeah, I'm using the NIO connector. And actually if I configure >>>>> the TomcatCometServlet manually I get the same error again. I >>>>> know that used to happen when I was accessing it through my AJP >>>>> connected Apache instance, but now I'm accessing it directly >>>>> through port 8443 on Tomcat. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Thursday, January 14, 2010 10:55 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Are you using the NIO connector in Tomcat? Errai by default will >>>>> try to use Tomcat's AIO system, which requires that the NIO or >>>>> APR connecter be >>>> used. >>>>> >>>>> >>>>> >>>>> On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> I tried the AutoServlet and it seems to pick the >>>>> TomcatCometServlet which makes it spin over and over on this >>>>> message every time it tries to access >>>>> it: >>>>> >>>>> >>>> ****************************************************************** >>>> * >>>> * >>>> * >>>> * >>>> ****** >>>>> ********************* >>>>> >>>>> ** PROBLEM! >>>>> >>>>> ** It appears something has been incorrectly configured. In order >>>>> to use ErraiBus >>>>> >>>>> ** on Tomcat, you must ensure that you are using the NIO or APR >>>> connector. >>>>> Also >>>>> >>>>> ** make sure that you have added these lines to your >>>>> WEB-INF/web.xml >>>> file: >>>>> >>>>> ** --- >>>>> >>>>> ** <servlet> >>>>> >>>>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>>>> >>>>> ** >>>>> >>>> <servlet-class>org.jboss.errai.bus.server.servlet.TomcatCometServl >>>> e >>>> t >>>> < >>>> / >>>> servle >>>>> t-class> >>>>> >>>>> ** <load-on-startup>1</load-on-startup> >>>>> >>>>> ** </servlet> >>>>> >>>>> ** >>>>> >>>>> ** <servlet-mapping> >>>>> >>>>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>>>> >>>>> ** <url-pattern>*.erraiBus</url-pattern> >>>>> >>>>> ** </servlet-mapping> >>>>> >>>>> ** --- >>>>> >>>>> ** If you have the following lines in your WEB-INF/web.xml, you >>>>> must comment or remove them: >>>>> >>>>> ** --- >>>>> >>>>> ** <listener> >>>>> >>>>> ** >>>>> >>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</lis >>>> t >>>> e >>>> n >>>> e >>>> r-clas >>>>> s> >>>>> >>>>> ** </listener> >>>>> >>>>> >>>> ****************************************************************** >>>> * >>>> * >>>> * >>>> * >>>> ****** >>>>> ********************* >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Thursday, January 14, 2010 10:06 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> By the way, if you want, we're on IRC on irc.freenode.net in >>>>> channel >>>> #errai >>>>> -- I'm "cbrock" on there if you want help troubleshooting directly. >>>>> >>>>> >>>>> >>>>> On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, and >>>>> IE on Windows 7. I'm using Tomcat. >>>>> >>>>> >>>>> >>>>> I'll try the AutoServlet to see if it makes a difference. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Wednesday, January 13, 2010 8:35 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> If you update to the latest version of trunk, simply get rid of >>>>> the listener and replace your web.xml config with this: >>>>> >>>>> >>>>> >>>>> <servlet> >>>>> >>>>> <servlet-name>ErraiAutoServlet</servlet-name> >>>>> >>>>> >>>>> >>>> <servlet-class>org.jboss.errai.bus.server.servlet.ErraiAutoServlet >>>> < >>>> / >>>> s >>>> e >>>> rvlet- >>>>> class> >>>>> >>>>> <load-on-startup>1</load-on-startup> >>>>> >>>>> </servlet> >>>>> >>>>> >>>>> >>>>> <servlet-mapping> >>>>> >>>>> <servlet-name>ErraiAutoServlet</servlet-name> >>>>> >>>>> <url-pattern>*.erraiBus</url-pattern> >>>>> >>>>> </servlet-mapping> >>>>> >>>>> >>>>> >>>>> This problem you're having is curious, though. We haven't seen >>>>> it in our internal testing. Can you tell me what browser, what >>>>> appserver, and what OS you're on? >>>>> >>>>> >>>>> >>>>> On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I'm using the following on the client side: >>>>> >>>>> bus.subscribe("ItemFound", new MessageCallback() { >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public void callback(Message message) { >>>>> >>>>> //throw new >>>>> UnsupportedOperationException("Not supported yet."); >>>>> >>>>> MessageBox.alert("Success", "In >>>> Callback", >>>>> null); >>>>> >>>>> /*Map<String,Object> parts = >>>>> message.getParts(); >>>>> >>>>> Set<String> keys = parts.keySet(); >>>>> >>>>> for (String key : keys) { >>>>> >>>>> MessageBox.alert("Key",key,null); >>>>> >>>>> }*/ >>>>> >>>>> //Item item = message.get(Item.class, >>>>> "Item"); >>>>> >>>>> //MessageBox.alert("Return", >>>>> item.getSerialNumber().toString(), null); >>>>> >>>>> } >>>>> >>>>> }); >>>>> >>>>> >>>>> >>>> MessageBuilder.createMessage().toSubject("Items").signalling().wit >>>> h >>>> ( >>>> M >>>> e >>>> ssageP >>>>> arts.ReplyTo, "ItemFound").with("SerialNumber", >>>>> serialInput.getValue().toString()).errorsHandledBy(new >>>>> ErrorCallback() { >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public boolean error(Message message, >>>> Throwable >>>>> throwable) { >>>>> >>>>> //throw new >>>>> UnsupportedOperationException("Not supported yet."); >>>>> >>>>> MessageBox.alert("Error", >>>>> throwable.getMessage(), null); >>>>> >>>>> return true; >>>>> >>>>> } >>>>> >>>>> }).sendNowWith(bus); >>>>> >>>>> >>>>> >>>>> Which sends: >>>>> >>>>> {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489" >>>>> } >>>>> >>>>> >>>>> >>>>> Although I've now noticed that it takes 2 tries to get it to send >>>>> that >>>> and >>>>> a >>>>> 3rd one to get the response back for the first one. >>>>> >>>>> >>>>> >>>>> Server portion looks like: >>>>> >>>>> @Service("Items") >>>>> >>>>> public class Items implements MessageCallback { >>>>> >>>>> private MessageBus bus; >>>>> >>>>> >>>>> >>>>> @Inject >>>>> >>>>> public Items(MessageBus bus) { >>>>> >>>>> this.bus = bus; >>>>> >>>>> System.out.println("Got a bus..."); >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public void callback(Message message) { >>>>> >>>>> //throw new UnsupportedOperationException("Not supported >>>> yet."); >>>>> >>>>> System.out.println("Incoming message..."); >>>>> >>>>> String serialNum = message.get(String.class, >>>>> "SerialNumber"); >>>>> >>>>> System.out.println(serialNum); >>>>> >>>>> Item item = new Item(); >>>>> >>>>> item.setSerialNumber(Long.parseLong(serialNum)); >>>>> >>>>> >>>>> >>>> MessageBuilder.createConversation(message).subjectProvided().signa >>>> l >>>> l >>>> i >>>> n >>>> g().wi >>>>> th("Item", item).errorsHandledBy(new ErrorCallback() { >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public boolean error(Message message, Throwable >>>> throwable) >>>>> { >>>>> >>>>> //throw new UnsupportedOperationException("Not >>>>> supported yet."); >>>>> >>>>> throwable.printStackTrace(); >>>>> >>>>> return true; >>>>> >>>>> } >>>>> >>>>> }).sendNowWith(bus); >>>>> >>>>> } >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> Response on the second POST is: >>>>> >>>>> >>>> [{"ItemFound":{"Item":{__EncodedType:'com.xteconline.system.Item',id: >>>> n >>>> ull,se >>>>> >>>> >>> >> >

>>>>> >>>> null,oemSerial:null,manufacturer:null,status:null,itemInfos:null}," >>>> T >>>> o >>>> S >>>> ubject >>>>> ":"ItemFound"}}] >>>>> >>>>> >>>>> >>>>> All others seem to get: >>>>> >>>>> [{"HeartBeat":null}] >>>>> >>>>> >>>>> >>>>> And on the first time I try to submit, it still seems to be kind >>>>> of >>>> setting >>>>> up stuff since it sends: >>>>> >>>>> >>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>> S >>>> e >>>> rverBu >>>>> >>>> >>> >> >

>>>>> >>>> ServerBus","Subject":"AuthorizationService","PriorityProcessing":"1" >>>> } >>>> | >>>> |{"Com >>>>> >>>> mandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Cli >>>> e >>>> n >>>> t >>>> N >>>> egotia >>>>> >>>> tionService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubs >>>> c >>>> r >>>> i >>>> b >>>> e","To >>>>> >>>> Subject":"ServerBus","Subject":"ServerEchoService","PriorityProces >>>> s >>>> i >>>> n >>>> g >>>> ":"1"} >>>>> >>>> ||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>> ||Cl >>>> ||ient >>>>> >>>> Bus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","S >>>> u >>>> b >>>> j >>>> e >>>> ct":"C >>>>> >>>> >>> >> >

>>>>> >>>> Subject":"Items"}||{"CommandType":"RemoteSubscribe","ToSubject":"S >>>> e >>>> r >>>> v >>>> e >>>> rBus", >>>>> >>>> "Subject":"ServerBus"}||{"CommandType":"RemoteSubscribe","ToSubject":" >>>> Server >>>>> >>>> Bus","Subject":"AuthorizationService"}||{"CommandType":"RemoteSubs >>>> c >>>> r >>>> i >>>> b >>>> e","To >>>>> >>>> >>> >> >

>>>>>

>>>>> } >>>>> >>>>> >>>>> >>>>> And >>>>> >>>>> >>>>> >>>>> >>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>> I >>>> t >>>> emFoun >>>>> d","PriorityProcessing":"1"} >>>>> >>>>> >>>>> >>>>> But doesn't send my stuff until I submit again. >>>>> >>>>> >>>>> >>>>> And about the only other relevant thing I can think of for Errai >>>>> is the servlet config: >>>>> >>>>> <listener> >>>>> >>>>> >>>>> >>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</lis >>>> t >>>> e >>>> n >>>> e >>>> r-clas >>>>> s> >>>>> >>>>> </listener> >>>>> >>>>> >>>>> >>>>> Which I believe sets up the DefaultBlockingServlet. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Tuesday, January 12, 2010 11:48 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> We have a fairly significant application that makes extensive >>>>> use of >>>> this >>>>> type of paradigm and we haven't ever experienced any dropped

>>>> Can >>>>> you provide me some examples of your code so we can troubleshoot >>>>> what's going on? >>>>> >>>>> >>>>> >>>>> On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> The MessageParts.ReplyTo was what I was missing in there. >>>>> However, my callback doesn't seem to be called. I get something >>>>> back when my request is POSTed, but it never seems to call my >>>>> callback. They do seem to work sometimes though. I had >>>>> accidentally named my callback subject and the server subject the >>>>> same and when I created a message to that subject, >>>> both >>>>> the client callback and the server callback were called correctly. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Tuesday, January 12, 2010 9:07 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> The sender needs to create a listening service that can be >>>>> replied

>>>> The >>>>> best way to do this is like so: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> //client-side code >>>>> >>>>> bus.subscribe("MyResponseSvc", >>>>> >>>>> new MessageCallback() { >>>>> >>>>> public void callback(Message msg) { >>>>> >>>>> ... >>>>> >>>>> } >>>>> >>>>> } >>>>> >>>>> ); >>>>> >>>>> >>>>> >>>>> >>>> MessageBuilder.createMessage().toSubject("ConversationalService"). >>>> s >>>> i >>>> g >>>> n >>>> alling >>>>> () >>>>> >>>>> .with(MessageParts.ReplyTo, "MyResponseSvc") >>>>> >>>>> .with("SomeMessagePart", "Foo") >>>>> >>>>> .noErrorHandling() >>>>> >>>>> .sendNowWith(bus); >>>>> >>>>> >>>>> >>>>> ... >>>>> >>>>> //server-side code >>>>> >>>>> >>>>> >>>>> MessageBuilder.createConversation(message) >>>>> >>>>> .subjectProvided().signalling() >>>>> >>>>> .with("MyResponseData", "Bar") >>>>> >>>>> .noErrorHandling() >>>>> >>>>> .sendNowWith(bus); >>>>> >>>>> >>>>> >>>>> ... >>>>> >>>>> >>>>> >>>>> Note: we may make this more straight forward in the future, such >>>>> as with the RPC API. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I won't be able to use the Swing monitor on the server I'm >>>>> deploying to since it has no interface. However, I did start >>>>> enabling logging in various places and it does seem that my >>>>> services weren't getting started. I was lacking an >>>>> ErraiApp.properties which I guess is used as the root for >>>> where >>>>> it should start looking for services. After adding that, they >>>>> started >>>> and >>>>> stuff started to go through. Does the client keep a record of >>>>> services >>>> or >>>>> something then? Why wouldn't it try to contact the service and >>>>> then fail that it couldn't find it? >>>>> >>>>> >>>>> >>>>> Also, looking at the revised Message API, how do you listen for >>>>> the reply in a conversation? Do I need to create a separate

>>>>> Before you >>>> could >>>>> specify a MessageCallback to get the response in the >>>>> conversation, but I can't find anywhere in the call chain to do >>>>> that and it's not covered in the SVN book. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Monday, January 11, 2010 3:16 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Kevin, >>>>> >>>>> >>>>> >>>>> I'm not sure how you're launching your app, but can you provide >>>>> this command line option which will bring up the bus monitor, and >>>>> at least tell me if you've probably deployed your services: >>>>> -Derrai.bus.showmonitor=true >>>>> >>>>> >>>>> >>>>> Also, can you email me the log output from when your startup the >>>>> application? >>>>> >>>>> >>>>> >>>>> On 2010-01-11, at 3:35 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Changing to a createCall and making a @Endpoint annotated method >>>>> on the server seems to make it send something again: >>>>> >>>>> >>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>> I >>>> t >>>> ems.ge >>>>> tItem:RespondTo:1","PriorityProcessing":"1"} >>>>> >>>>> >>>>> >>>>> With a response of: >>>>> >>>>> [{"HeartBeat":null}] >>>>> >>>>> >>>>> >>>>> However, I still so nowhere where it passes the parameter I give >>>>> it >> with: >>>>> >>>>> MessageBuilder.createCall().call("Items").endpoint("getItem", >>>>> serialInput.getValue()).respondTo(Item.class, new >>>>> RemoteCallback<Item>() >>>> { >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public void callback(Item response) { >>>>> >>>>> //throw new >>>>> UnsupportedOperationException("Not supported yet."); >>>>> >>>>> >>>>> MessageBox.alert("Return",item.getSerialNumber().toString(),null) >>>>> ; >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> }).noErrorHandling().sendNowWith(bus); >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> From: errai-users-bounces(a)lists.jboss.org >>>>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>>>> Jordan >>>>> Sent: Monday, January 11, 2010 1:46 PM >>>>> To: 'Mike Brock' >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> Made the changes specified in the userguide, but now it doesn't >>>>> send anything. I'm using the following: >>>>> >>>>> >>>> MessageBuilder.createMessage().toSubject("Items").signalling().with(" >>>> S >>>> erialN >>>>> umber", "Test").noErrorHandling().sendNowWith(bus); >>>>> >>>>> >>>>> >>>>> It still seems to be set up just fine since the in.erraiBus >>>>> servlet is created and the client long polls it, but the code >>>>> above doesn't seem to send anything. I'm using the following way >>>>> to make it for the >>>>> DefaultBlockingServlet: >>>>> >>>>> <listener> >>>>> >>>>> >>>>> >>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</lis >>>> t >>>> e >>>> n >>>> e >>>> r-clas >>>>> s> >>>>> >>>>> </listener> >>>>> >>>>> >>>>> >>>>> Should I be using that? I figure it shouldn't affect the client >>>>> any >>>> though >>>>> unless the servlet is incorrectly set up as a consequence, which >>>>> it >>>> doesn't >>>>> seem to be since they communicate just fine for the initial setup. >>>>> What should I look at to see why it's not sending? >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Monday, January 11, 2010 12:43 PM >>>>> To: Kevin Jordan >>>>> Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> You should be aware we have made changes and are retiring the use >>>>> of the CommandMessage API. Be sure to read the documentation in >>>>> the userguide/src/main/docbook/en/master.xml file. You can use: >>>>> mvn jdocbook:generate to create an HTML file from the userguide/ > directory. >>>>> >>>>> >>>>> >>>>> On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Friday, January 08, 2010 2:56 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> I will check into this. We're still working on getting the AIO >>>>> stuff >>>>> sorted>Monday, January 11, 2010 8:59 AM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Hi Kevin, the compilation problems should be fixed already. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Yes, I am using trunk. Is there a more stable branch/version I >>>>> should be using? I had updated again hoping it was just >>>>> something with the time I checked out and then ran into the >>>>> problems Heiko Braun ran into compiling it. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Friday, January 08, 2010 8:52 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> What version of ErraiBus are you using? Are you getting it from

>>>>> >>>>> >>>>> >>>>> On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> DefaultBlockingServlet seems to have the same effect. >>>>> >>>>> >>>>> >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Friday, January 08, 2010 2:56 PM >>>>> To: Kevin Jordan >>>>> Cc: errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> >>>>> >>>>> I will check into this. We're still working on getting the AIO >>>>> stuff sorted, and I wouldn't consider the Tomcat or JBoss >>>>> adapters to be production ready. You're best to use the >>>>> DefaultBlockingServlet -- which will provide adequate performance >>>>> for development while we get the AIO adapters squared away over >>>>> the next >> few days. >>>>> >>>>> >>>>> >>>>> On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I'm having trouble getting a message to go through using ErraiBus. >>>>> I'm using this on the client side: >>>>> >>>>> CommandMessage msg = (CommandMessage) >>>>> CommandMessage.create().toSubject("Items").set("SerialNumber", >>>>> serialInput.getValue()); >>>>> >>>>> bus.conversationWith(msg, new MessageCallback() { >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public void callback(Message message) { >>>>> >>>>> //throw new >>>>> UnsupportedOperationException("Not supported yet."); >>>>> >>>>> Item item = message.get(Item.class, >>>>> "Item"); >>>>> >>>>> MessageBox.alert("Errai", >>>>> item.getSerialNumber().toString(), null); >>>>> >>>>> } >>>>> >>>>> }); >>>>> >>>>> >>>>> >>>>> With this on the server side: >>>>> >>>>> @Service("Items") >>>>> >>>>> public class Items implements MessageCallback { >>>>> >>>>> private MessageBus bus; >>>>> >>>>> >>>>> >>>>> @Inject >>>>> >>>>> public Items(MessageBus bus) { >>>>> >>>>> this.bus = bus; >>>>> >>>>> System.out.println("Got a bus..."); >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> @Override >>>>> >>>>> public void callback(Message message) { >>>>> >>>>> //throw new UnsupportedOperationException("Not supported >>>> yet."); >>>>> >>>>> System.out.println("Incoming message..."); >>>>> >>>>> Long serialNum = message.get(Long.class, "SerialNumber"); >>>>> >>>>> System.out.println(serialNum); >>>>> >>>>> Item item = new Item(); >>>>> >>>>> item.setSerialNumber(serialNum); >>>>> >>>>> >>>>> ConversationMessage.create(message).set("Item",item).sendNowWith( >>>>> b >>>>> u >>>>> s >>>>> ) >>>>> ; >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> } >>>>> >>>>> >>>>> >>>>> However, all it seems to send is: >>>>> >>>>> >>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>> t >>>> e >>>> mp:Con >>>>> versation:2","PriorityProcessing":"1"} >>>>> >>>>> >>>>> >>>>> I don't see where it actually sends my body or the subject that I >>>>> fill >>>> out >>>>> in my message. Nothing also gets to the Service class. Am I >>>>> doing something wrong? I have Tomcat running NIO and everything >>>>> else seems set up correctly. It will keep a GET connection open >>>>> and do the POST of the >>>> JSON >>>>> above, but nowhere does it seem to send what I want it to. I >>>>> also seem >>>> to >>>>> be getting these occasionally, usually on some of the first >>>>> requests to >>>>> in.erraiBus: >>>>> >>>>> java.lang.NullPointerException >>>>> >>>>> at >>>>> >>>> org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(Tomcat >>>> C >>>> o >>>> m >>>> e >>>> tServl >>>>> et.java:105) >>>>> >>>>> at >>>>> >>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEv >>>> e >>>> n >>>> t >>>> ( >>>> Unknow >>>>> n Source) >>>>> >>>>> at >>>>> org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unk >>>>> n >>>>> o >>>>> w >>>>> n >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardWrapperValve.event(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardContextValve.event(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.core.StandardHostValve.event(Unknown >>>> Source) >>>>> >>>>> at org.apache.catalina.valves.ValveBase.event(Unknown Source) >>>>> >>>>> at org.apache.catalina.core.StandardEngineValve.event(Unknown >>>>> Source) >>>>> >>>>> at org.apache.catalina.connector.CoyoteAdapter.event(Unknown >>>>> Source) >>>>> >>>>> at org.apache.coyote.http11.Http11NioProcessor.event(Unknown >>>>> Source) >>>>> >>>>> at >>>>> >>>> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler. >>>> e >>>> v >>>> e >>>> nt(Unk >>>>> nown Source) >>>>> >>>>> at >>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknow >>>>> n >>>> Source) >>>>> >>>>> at >>>>> >>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolE >>>> x >>>> e >>>> c >>>> u >>>> tor.ja >>>>> va:886) >>>>> >>>>> at >>>>> >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. >>>> java:9 >>>>> 08) >>>>> >>>>> at java.lang.Thread.run(Thread.java:619) >>>>> >>>>> >>>>> >>>>> Can anyone point me at what I'm missing? >>>>> >>>>> _______________________________________________ >>>>> errai-users mailing list >>>>> errai-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> errai-users mailing list >>>>> errai-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> errai-users mailing list >>>>> errai-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> errai-users mailing list >>>>> errai-users(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>> >>> >>> >> >> > > > _______________________________________________ > errai-users mailing list > errai-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/errai-users >

Or another option is: Enumeration<URL> t = Test.class.getClassLoader().getResources("ErraiApp.properties"); while (t.hasMoreElements()) { URL element = t.nextElement(); JarURLConnection conn = (JarURLConnection)element.openConnection(); JarFile jar = conn.getJarFile(); File file = new File(jar.getName()); } -----Original Message----- From: errai-users-bounces(a)lists.jboss.org [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin Jordan Sent: Monday, January 18, 2010 4:53 PM To: 'Mike Brock' Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages I think if you determine that the URL has a ! in it, that after you remove that and everything after it, you can recreate a URL to that, then get the URI of that and make a file out of that. This will prevent you from needing to decode everything yourself since the only thing a File won't like from a URI is if it has the ! in it. -----Original Message----- From: errai-users-bounces(a)lists.jboss.org [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin Jordan Sent: Monday, January 18, 2010 4:00 PM To: 'Mike Brock' Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Yes, I can confirm that. Since it comes back from a URL object, the path is encoded, but a File object doesn't decode it. -----Original Message----- From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 18, 2010 3:52 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Can you confirm that? If so, I'll investigate and get it fixed. On 2010-01-18, at 4:38 PM, Kevin Jordan wrote: > Adding that, I can see it picking up my external jar in the List<File> > roots parameter, but it still doesn't manage to find the class after > that. I think it's because the location it's in has a space which > somehow gets replaced with a %20. This makes it not look for the > correct file. > > -----Original Message----- > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Monday, January 18, 2010 2:06 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > This means that your module is not in the classpath at compile time, > and/or you do not have an ErraiApp.properties inside the JAR you wish > to scan. > Perhaps this is not documented clearly. > > Every JAR you want Errai to scan *must* have an ErraiApp.properties in > it's root folder. The file can be empty. It doesn't have to contain anything. > > > On 2010-01-18, at 2:29 PM, Kevin Jordan wrote: > >> Okay, in debug mode I see the logging. It definitely doesn't >> generate anything for one in a jar file. >> >> -----Original Message----- >> From: errai-users-bounces(a)lists.jboss.org >> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >> Jordan >> Sent: Monday, January 18, 2010 1:09 PM >> To: 'Mike Brock' >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> Sometimes, although seeing as my application will be secured with >> authentication and very soon will depend on it, that may not be an >> option for much longer. Usually I just compile and deploy it. There >> shouldn't be anything really special about the way it's compiled, >> seeing as I can compile it using Hudson as well since Netbeans just >> uses > Ant. >> >> -----Original Message----- >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Monday, January 18, 2010 1:01 PM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> I'm not really familiar with NetBeans. >> >> Are you using the GWT Development Mode for testing? >> >> On 2010-01-18, at 1:53 PM, Kevin Jordan wrote: >> >>> Yeah, that's the only stuff that comes out during the compile phase. >>> Not sure if I have something misconfigured in my logging, but that's >>> the only places that print out. >>> >>> -----Original Message----- >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Monday, January 18, 2010 10:45 AM >>> To: Kevin Jordan >>> Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> This is for the compile-phase stuff. If you're running in hosted >>> mode, you need to look in the GWT Development Mode logger. >>> >>> On 2010-01-18, at 11:43 AM, Kevin Jordan wrote: >>> >>>> Is there any logging I have to set up for a particular class or >>>> package or any configuration I have to do for that? Normally, even >>>> when it works, the only output I see from Errai while compiling is: >>>> 0 [main] INFO Configuration - configuration scan targets >>>> 0 [main] INFO Configuration - -> >>>> >>> >> > C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-persistence-1. >>>> 0-SNAPSHOT.jar >>>> 0 [main] INFO Configuration - -> >>>> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\src\java >>>> 0 [main] INFO Configuration - -> >>>> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB-I >>>> N >>>> F >>>> \ >>>> classe >>>> s >>>> 63 [main] INFO Configuration - caching context >>>> 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-pers >>>> i >>>> s >>>> t >>>> ence-1 >>>> .0-SNAPSHOT.jar:*' >>>> 188 [main] INFO Configuration - caching context >>>> 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB- >>>> I >>>> N >>>> F >>>> \class >>>> es' >>>> >>>> And I'm not even really using persistence (i.e. it's not inherited >>>> in my .gwt.xml, but somehow it's getting run anyways either via >>>> ErraiBus or ErraiCommons). >>>> -----Original Message----- >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Monday, January 18, 2010 10:39 AM >>>> To: Kevin Jordan >>>> Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> This is an interesting theory. You should be able to determine >>>> whether the stub is generated or not since at compile-time the >>>> Errai generators show log output for each stub. >>>> >>>> You should see a log output that says: "Generated >>>> marshaller/demarshaller >>>> for: <classname>" for each entity you've annotated. >>>> >>>> On 2010-01-18, at 11:32 AM, Kevin Jordan wrote: >>>> >>>>> Not sure what you mean by that, but I'm using Netbeans and my >>>>> domain POJOs >>>> are in a separate project which gets included by my web project. >>>> The projects compile file and I've used my domain POJOs via >>>> SOAFace's UniversalClient and regular GWT-RPC before without issues. >>>> And they get put across the wire with Errai, it's just when the >>>> class is in a separate project that there seems to be a problem and >>>> my callback isn't called. So I'm wondering if it's an issue with >>>> the stub getting >>> generated or something. >>>> >>>>> >>>>> -----Original Message----- >>>>> From: Thomas SEGISMONT [mailto:tsegismont@gmail.com] >>>>> Sent: Monday, January 18, 2010 10:12 AM >>>>> To: Kevin Jordan >>>>> Cc: Mike Brock; errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> Have you tried to include your project/jar source code in your >>>>> launch >>>> configuration ? >>>>> >>>>> It sounds more like a GWT configuration problem than an Errai one. >>>>> >>>>> If you're using Maven to build your project, you can read this : >>>>> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/multiproject. >>>>> h >>>>> t >>>>> m >>>>> l >>>>> >>>>> Thomas >>>>> >>>>> On Mon, 18 Jan 2010 09:50:40 -0600, "Kevin Jordan" >>>>> <kevin.jordan(a)xteconline.com&gt; wrote: >>>>>> I think I've found out one problem. Somehow Errai has trouble if >>>>>> your >>>>> POJO >>>>>> is in an external jar, or in my case another Netbeans project. >>>>>> GWT will compile my project just fine, but it at least seems to >>>>>> be that once I go >>>>> to >>>>>> another project/jar for my POJO it fails to get to my callback >>>>>> and does >>>>> the >>>>>> behavior I've previously described. >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Friday, January 15, 2010 4:20 PM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> Yes, that will work, of course. >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-15, at 4:59 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> I haven't yet. But I'll try it and let you know if it works. >>>>>> >>>>>> >>>>>> >>>>>> So the default constructor provided by the JVM if you don't >>>>>> specify one won't work? >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Friday, January 15, 2010 3:55 PM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> Have you updated to trunk -- I think that will fix the >>>>>> InstantiationException? Any serializable class *must* have a >>>>>> default constructor. >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-15, at 4:48 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Well, I think I've figured it out on my callback problems. I >>>>>> went back >>>>> to >>>>>> just passing a string back and forth and that worked. I then >>>>>> made a simpler POJO to pass back and forth with just implementing >>>>>> Serializable which didn't work (no callback call). I then added >>>>>> the annotation that I just saw in the docs and that didn't work >>>>>> (no callback call). I then removed >>>>> Serializable >>>>>> and the callback gets called, but it gets an error when it tries >>>>>> to get >>>>> the >>>>>> POJO out of the message. >>>>>> >>>>>> >>>>>> >>>>>> Is there anything extra I need to do for POJOs? >>>>>> >>>>>> >>>>>> >>>>>> From: errai-users-bounces(a)lists.jboss.org >>>>>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>>>>> Jordan >>>>>> Sent: Thursday, January 14, 2010 4:21 PM >>>>>> To: 'Mike Brock' >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> Whenever I do that, I seem to get: >>>>>> >>>>>> java.lang.InstantiationException: >>>>>> org.jboss.errai.bus.server.servlet.DefaultBlockingServlet >>>>>> >>>>>> at java.lang.Class.newInstance0(Class.java:340) >>>>>> >>>>>> at java.lang.Class.newInstance(Class.java:308) >>>>>> >>>>>> at >>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(Unknown >>>>>> Source) >>>>>> >>>>>> at org.apache.catalina.core.StandardWrapper.load(Unknown >>>>>> Source) >>>>>> >>>>>> at >>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(Unknown >>>>>> Source) >>>>>> >>>>>> at org.apache.catalina.core.StandardContext.start(Unknown >>>>>> Source) >>>>>> >>>>>> at >>>>> org.apache.catalina.core.ContainerBase.addChildInternal(Unknown >>>>>> Source) >>>>>> >>>>>> at org.apache.catalina.core.ContainerBase.addChild(Unknown >>>>> Source) >>>>>> >>>>>> at org.apache.catalina.core.StandardHost.addChild(Unknown >>>>>> Source) >>>>>> >>>>>> at >>>>> org.apache.catalina.startup.HostConfig.deployDescriptor(Unknown >>>>>> Source) >>>>>> >>>>>> at >>>>> org.apache.catalina.startup.HostConfig.deployDescriptors(Unknown >>>>>> Source) >>>>>> >>>>>> at org.apache.catalina.startup.HostConfig.deployApps(Unknown >>>>>> Source) >>>>>> >>>>>> at org.apache.catalina.startup.HostConfig.check(Unknown >>>>>> Source) >>>>>> >>>>>> at >>>>>> org.apache.catalina.startup.HostConfig.lifecycleEvent(Unknown >>>>>> Source) >>>>>> >>>>>> at >>>>>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unkn >>>>>> o >>>>>> w >>>>>> n >>>>>> Source) >>>>>> >>>>>> at >>>>> org.apache.catalina.core.ContainerBase.backgroundProcess(Unknown >>>>>> Source) >>>>>> >>>>>> at >>>>>> >>>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>>> p >>>>> r >>>>> ocessC >>>>>> hildren(Unknown Source) >>>>>> >>>>>> at >>>>>> >>>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>>> p >>>>> r >>>>> ocessC >>>>>> hildren(Unknown Source) >>>>>> >>>>>> at >>>>>> >>>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>>> r >>>>> u >>>>> n(Unkn >>>>>> own Source) >>>>>> >>>>>> at java.lang.Thread.run(Thread.java:619) >>>>>> >>>>>> >>>>>> >>>>>> Even in a new project I've created to see if anything is >>>>>> interfering with Errai somehow. Trying TomcatCometServlet or >>>>>> ErraiAutoServlet also yields the same results as before in both >>>>>> cases. Using the listener/Guice >>>>> filter >>>>>> works. I've also gotten it so a callback works in my new minimal >>>>> project. >>>>>> So now I'm wondering if something else is interfering with it. >>>>>> I've got Spring Security protecting pretty much everything, >>>>>> although I think I've tried taking that out before and had the >>>>>> same >> effect. >>>>>> I've also got GXT >>>>>> (http://www.extjs.com/products/gxt/) in there. Along with Mule >>>>>> and SOAFaces, although SOAFaces can probably go away since I'll >>>>>> be communicating to Mule via Errai when that works so I can have >>>>>> better asynchronous communication and also push communication. I >>>>>> suppose what I'll try first is ripping out GXT since that's >>>>>> probably the most likely culprit in my mind. >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Thursday, January 14, 2010 12:12 PM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> We will actually be removing the Guice filter as it's created >>>>>> problems >>>>> for >>>>>> deploying on some appservers. We're falling back on directly >> declaring >>>>>> the >>>>>> servlet. So you might want to switch to directly declaring the >>>>>> DefaultBlockingServlet like so: >>>>>> >>>>>> >>>>>> >>>>>> <servlet> >>>>>> >>>>>> <servlet-name>ErraiServlet</servlet-name> >>>>>> >>>>>> >>>>>> >>>>> <servlet-class>org.jboss.errai.bus.server.servlet.DefaultBlockingS >>>>> e >>>>> r >>>>> v >>>>> l >>>>> et</se >>>>>> rvlet-class> >>>>>> >>>>>> <load-on-startup>1</load-on-startup> >>>>>> >>>>>> </servlet> >>>>>> >>>>>> >>>>>> >>>>>> <servlet-mapping> >>>>>> >>>>>> <servlet-name>ErraiServlet</servlet-name> >>>>>> >>>>>> <url-pattern>*.erraiBus</url-pattern> >>>>>> >>>>>> </servlet-mapping> >>>>>> >>>>>> >>>>>> >>>>>> . >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-14, at 12:45 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> Yes. It's still working the way it was before where I have to >>>>>> submit >>>>> more >>>>>> than once and the response comes back on the POST but the >>>>>> callback >>>>> doesn't >>>>>> get called. >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Thursday, January 14, 2010 11:44 AM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> Are you still losing messages? >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-14, at 12:31 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Switching it back to the listener config seems to make it work >>>>>> again through the DefaultBlockingServlet. >>>>>> >>>>>> >>>>>> >>>>>> From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] >>>>>> Sent: Thursday, January 14, 2010 11:22 AM >>>>>> To: 'Mike Brock' >>>>>> Cc: &#39;errai-users(a)lists.jboss.org&#39; >>>>>> Subject: RE: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> Yeah, I'm using the NIO connector. And actually if I configure >>>>>> the TomcatCometServlet manually I get the same error again. I >>>>>> know that used to happen when I was accessing it through my AJP >>>>>> connected Apache instance, but now I'm accessing it directly >>>>>> through port 8443 on Tomcat. >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Thursday, January 14, 2010 10:55 AM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> Are you using the NIO connector in Tomcat? Errai by default will >>>>>> try to use Tomcat's AIO system, which requires that the NIO or >>>>>> APR connecter be >>>>> used. >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> I tried the AutoServlet and it seems to pick the >>>>>> TomcatCometServlet which makes it spin over and over on this >>>>>> message every time it tries to access >>>>>> it: >>>>>> >>>>>> >>>>> ****************************************************************** >>>>> * >>>>> * >>>>> * >>>>> * >>>>> ****** >>>>>> ********************* >>>>>> >>>>>> ** PROBLEM! >>>>>> >>>>>> ** It appears something has been incorrectly configured. In order >>>>>> to use ErraiBus >>>>>> >>>>>> ** on Tomcat, you must ensure that you are using the NIO or APR >>>>> connector. >>>>>> Also >>>>>> >>>>>> ** make sure that you have added these lines to your >>>>>> WEB-INF/web.xml >>>>> file: >>>>>> >>>>>> ** --- >>>>>> >>>>>> ** <servlet> >>>>>> >>>>>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>>>>> >>>>>> ** >>>>>> >>>>> <servlet-class>org.jboss.errai.bus.server.servlet.TomcatCometServl >>>>> e >>>>> t >>>>> < >>>>> / >>>>> servle >>>>>> t-class> >>>>>> >>>>>> ** <load-on-startup>1</load-on-startup> >>>>>> >>>>>> ** </servlet> >>>>>> >>>>>> ** >>>>>> >>>>>> ** <servlet-mapping> >>>>>> >>>>>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>>>>> >>>>>> ** <url-pattern>*.erraiBus</url-pattern> >>>>>> >>>>>> ** </servlet-mapping> >>>>>> >>>>>> ** --- >>>>>> >>>>>> ** If you have the following lines in your WEB-INF/web.xml, you >>>>>> must comment or remove them: >>>>>> >>>>>> ** --- >>>>>> >>>>>> ** <listener> >>>>>> >>>>>> ** >>>>>> >>>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</lis >>>>> t >>>>> e >>>>> n >>>>> e >>>>> r-clas >>>>>> s> >>>>>> >>>>>> ** </listener> >>>>>> >>>>>> >>>>> ****************************************************************** >>>>> * >>>>> * >>>>> * >>>>> * >>>>> ****** >>>>>> ********************* >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Thursday, January 14, 2010 10:06 AM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> By the way, if you want, we're on IRC on irc.freenode.net in >>>>>> channel >>>>> #errai >>>>>> -- I'm "cbrock" on there if you want help troubleshooting directly. >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, and >>>>>> IE on Windows 7. I'm using Tomcat. >>>>>> >>>>>> >>>>>> >>>>>> I'll try the AutoServlet to see if it makes a difference. >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Wednesday, January 13, 2010 8:35 PM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> If you update to the latest version of trunk, simply get rid of >>>>>> the listener and replace your web.xml config with this: >>>>>> >>>>>> >>>>>> >>>>>> <servlet> >>>>>> >>>>>> <servlet-name>ErraiAutoServlet</servlet-name> >>>>>> >>>>>> >>>>>> >>>>> <servlet-class>org.jboss.errai.bus.server.servlet.ErraiAutoServlet >>>>> < >>>>> / >>>>> s >>>>> e >>>>> rvlet- >>>>>> class> >>>>>> >>>>>> <load-on-startup>1</load-on-startup> >>>>>> >>>>>> </servlet> >>>>>> >>>>>> >>>>>> >>>>>> <servlet-mapping> >>>>>> >>>>>> <servlet-name>ErraiAutoServlet</servlet-name> >>>>>> >>>>>> <url-pattern>*.erraiBus</url-pattern> >>>>>> >>>>>> </servlet-mapping> >>>>>> >>>>>> >>>>>> >>>>>> This problem you're having is curious, though. We haven't seen >>>>>> it in our internal testing. Can you tell me what browser, what >>>>>> appserver, and what OS you're on? >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> I'm using the following on the client side: >>>>>> >>>>>> bus.subscribe("ItemFound", new MessageCallback() { >>>>>> >>>>>> >>>>>> >>>>>> @Override >>>>>> >>>>>> public void callback(Message message) { >>>>>> >>>>>> //throw new >>>>>> UnsupportedOperationException("Not supported yet."); >>>>>> >>>>>> MessageBox.alert("Success", "In >>>>> Callback", >>>>>> null); >>>>>> >>>>>> /*Map<String,Object> parts = >>>>>> message.getParts(); >>>>>> >>>>>> Set<String> keys = parts.keySet(); >>>>>> >>>>>> for (String key : keys) { >>>>>> >>>>>> MessageBox.alert("Key",key,null); >>>>>> >>>>>> }*/ >>>>>> >>>>>> //Item item = message.get(Item.class, >>>>>> "Item"); >>>>>> >>>>>> //MessageBox.alert("Return", >>>>>> item.getSerialNumber().toString(), null); >>>>>> >>>>>> } >>>>>> >>>>>> }); >>>>>> >>>>>> >>>>>> >>>>> MessageBuilder.createMessage().toSubject("Items").signalling().wit >>>>> h >>>>> ( >>>>> M >>>>> e >>>>> ssageP >>>>>> arts.ReplyTo, "ItemFound").with("SerialNumber", >>>>>> serialInput.getValue().toString()).errorsHandledBy(new >>>>>> ErrorCallback() { >>>>>> >>>>>> >>>>>> >>>>>> @Override >>>>>> >>>>>> public boolean error(Message message, >>>>> Throwable >>>>>> throwable) { >>>>>> >>>>>> //throw new >>>>>> UnsupportedOperationException("Not supported yet."); >>>>>> >>>>>> MessageBox.alert("Error", >>>>>> throwable.getMessage(), null); >>>>>> >>>>>> return true; >>>>>> >>>>>> } >>>>>> >>>>>> }).sendNowWith(bus); >>>>>> >>>>>> >>>>>> >>>>>> Which sends: >>>>>> >>>>>> {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489" >>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> Although I've now noticed that it takes 2 tries to get it to send >>>>>> that >>>>> and >>>>>> a >>>>>> 3rd one to get the response back for the first one. >>>>>> >>>>>> >>>>>> >>>>>> Server portion looks like: >>>>>> >>>>>> @Service("Items") >>>>>> >>>>>> public class Items implements MessageCallback { >>>>>> >>>>>> private MessageBus bus; >>>>>> >>>>>> >>>>>> >>>>>> @Inject >>>>>> >>>>>> public Items(MessageBus bus) { >>>>>> >>>>>> this.bus = bus; >>>>>> >>>>>> System.out.println("Got a bus..."); >>>>>> >>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> @Override >>>>>> >>>>>> public void callback(Message message) { >>>>>> >>>>>> //throw new UnsupportedOperationException("Not supported >>>>> yet."); >>>>>> >>>>>> System.out.println("Incoming message..."); >>>>>> >>>>>> String serialNum = message.get(String.class, >>>>>> "SerialNumber"); >>>>>> >>>>>> System.out.println(serialNum); >>>>>> >>>>>> Item item = new Item(); >>>>>> >>>>>> item.setSerialNumber(Long.parseLong(serialNum)); >>>>>> >>>>>> >>>>>> >>>>> MessageBuilder.createConversation(message).subjectProvided().signa >>>>> l >>>>> l >>>>> i >>>>> n >>>>> g().wi >>>>>> th("Item", item).errorsHandledBy(new ErrorCallback() { >>>>>> >>>>>> >>>>>> >>>>>> @Override >>>>>> >>>>>> public boolean error(Message message, Throwable >>>>> throwable) >>>>>> { >>>>>> >>>>>> //throw new UnsupportedOperationException("Not >>>>>> supported yet."); >>>>>> >>>>>> throwable.printStackTrace(); >>>>>> >>>>>> return true; >>>>>> >>>>>> } >>>>>> >>>>>> }).sendNowWith(bus); >>>>>> >>>>>> } >>>>>> >>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> Response on the second POST is: >>>>>> >>>>>> >>>>> [{"ItemFound":{"Item":{__EncodedType:'com.xteconline.system.Item',id: >>>>> n >>>>> ull,se >>>>>> >>>>> >>>> >>> >> > rialNumber:1201489,part:null,storageLocation:null,storageUnit:null,customer: >>>>>> >>>>> null,oemSerial:null,manufacturer:null,status:null,itemInfos:null}," >>>>> T >>>>> o >>>>> S >>>>> ubject >>>>>> ":"ItemFound"}}] >>>>>> >>>>>> >>>>>> >>>>>> All others seem to get: >>>>>> >>>>>> [{"HeartBeat":null}] >>>>>> >>>>>> >>>>>> >>>>>> And on the first time I try to submit, it still seems to be kind >>>>>> of >>>>> setting >>>>>> up stuff since it sends: >>>>>> >>>>>> >>>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>>> S >>>>> e >>>>> rverBu >>>>>> >>>>> >>>> >>> >> > s","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":" >>>>>> >>>>> ServerBus","Subject":"AuthorizationService","PriorityProcessing":"1" >>>>> } >>>>> | >>>>> |{"Com >>>>>> >>>>> mandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Cli >>>>> e >>>>> n >>>>> t >>>>> N >>>>> egotia >>>>>> >>>>> tionService","PriorityProcessing":"1"}||{"CommandType":"RemoteSubs >>>>> c >>>>> r >>>>> i >>>>> b >>>>> e","To >>>>>> >>>>> Subject":"ServerBus","Subject":"ServerEchoService","PriorityProces >>>>> s >>>>> i >>>>> n >>>>> g >>>>> ":"1"} >>>>>> >>>>> ||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>>> ||Cl >>>>> ||ient >>>>>> >>>>> Bus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","S >>>>> u >>>>> b >>>>> j >>>>> e >>>>> ct":"C >>>>>> >>>>> >>>> >>> >> > lientBusErrors"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus"," >>>>>> >>>>> Subject":"Items"}||{"CommandType":"RemoteSubscribe","ToSubject":"S >>>>> e >>>>> r >>>>> v >>>>> e >>>>> rBus", >>>>>> >>>>> "Subject":"ServerBus"}||{"CommandType":"RemoteSubscribe","ToSubject":" >>>>> Server >>>>>> >>>>> Bus","Subject":"AuthorizationService"}||{"CommandType":"RemoteSubs >>>>> c >>>>> r >>>>> i >>>>> b >>>>> e","To >>>>>> >>>>> >>>> >>> >> > Subject":"ServerBus","Subject":"ClientNegotiationService"}||{"CommandType":" >>>>>> RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService" >>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> And >>>>>> >>>>>> >>>>>> >>>>>> >>>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>>> I >>>>> t >>>>> emFoun >>>>>> d","PriorityProcessing":"1"} >>>>>> >>>>>> >>>>>> >>>>>> But doesn't send my stuff until I submit again. >>>>>> >>>>>> >>>>>> >>>>>> And about the only other relevant thing I can think of for Errai >>>>>> is the servlet config: >>>>>> >>>>>> <listener> >>>>>> >>>>>> >>>>>> >>>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</lis >>>>> t >>>>> e >>>>> n >>>>> e >>>>> r-clas >>>>>> s> >>>>>> >>>>>> </listener> >>>>>> >>>>>> >>>>>> >>>>>> Which I believe sets up the DefaultBlockingServlet. >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Tuesday, January 12, 2010 11:48 AM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> We have a fairly significant application that makes extensive >>>>>> use of >>>>> this >>>>>> type of paradigm and we haven't ever experienced any dropped messages. > >>>>> Can >>>>>> you provide me some examples of your code so we can troubleshoot >>>>>> what's going on? >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> The MessageParts.ReplyTo was what I was missing in there. >>>>>> However, my callback doesn't seem to be called. I get something >>>>>> back when my request is POSTed, but it never seems to call my >>>>>> callback. They do seem to work sometimes though. I had >>>>>> accidentally named my callback subject and the server subject the >>>>>> same and when I created a message to that subject, >>>>> both >>>>>> the client callback and the server callback were called correctly. >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Tuesday, January 12, 2010 9:07 AM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> The sender needs to create a listening service that can be >>>>>> replied to. > >>>>> The >>>>>> best way to do this is like so: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> //client-side code >>>>>> >>>>>> bus.subscribe("MyResponseSvc", >>>>>> >>>>>> new MessageCallback() { >>>>>> >>>>>> public void callback(Message msg) { >>>>>> >>>>>> ... >>>>>> >>>>>> } >>>>>> >>>>>> } >>>>>> >>>>>> ); >>>>>> >>>>>> >>>>>> >>>>>> >>>>> MessageBuilder.createMessage().toSubject("ConversationalService"). >>>>> s >>>>> i >>>>> g >>>>> n >>>>> alling >>>>>> () >>>>>> >>>>>> .with(MessageParts.ReplyTo, "MyResponseSvc") >>>>>> >>>>>> .with("SomeMessagePart", "Foo") >>>>>> >>>>>> .noErrorHandling() >>>>>> >>>>>> .sendNowWith(bus); >>>>>> >>>>>> >>>>>> >>>>>> ... >>>>>> >>>>>> //server-side code >>>>>> >>>>>> >>>>>> >>>>>> MessageBuilder.createConversation(message) >>>>>> >>>>>> .subjectProvided().signalling() >>>>>> >>>>>> .with("MyResponseData", "Bar") >>>>>> >>>>>> .noErrorHandling() >>>>>> >>>>>> .sendNowWith(bus); >>>>>> >>>>>> >>>>>> >>>>>> ... >>>>>> >>>>>> >>>>>> >>>>>> Note: we may make this more straight forward in the future, such >>>>>> as with the RPC API. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> I won't be able to use the Swing monitor on the server I'm >>>>>> deploying to since it has no interface. However, I did start >>>>>> enabling logging in various places and it does seem that my >>>>>> services weren't getting started. I was lacking an >>>>>> ErraiApp.properties which I guess is used as the root for >>>>> where >>>>>> it should start looking for services. After adding that, they >>>>>> started >>>>> and >>>>>> stuff started to go through. Does the client keep a record of >>>>>> services >>>>> or >>>>>> something then? Why wouldn't it try to contact the service and >>>>>> then fail that it couldn't find it? >>>>>> >>>>>> >>>>>> >>>>>> Also, looking at the revised Message API, how do you listen for >>>>>> the reply in a conversation? Do I need to create a separate listener? >>>>>> Before you >>>>> could >>>>>> specify a MessageCallback to get the response in the >>>>>> conversation, but I can't find anywhere in the call chain to do >>>>>> that and it's not covered in the SVN book. >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Monday, January 11, 2010 3:16 PM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> Kevin, >>>>>> >>>>>> >>>>>> >>>>>> I'm not sure how you're launching your app, but can you provide >>>>>> this command line option which will bring up the bus monitor, and >>>>>> at least tell me if you've probably deployed your services: >>>>>> -Derrai.bus.showmonitor=true >>>>>> >>>>>> >>>>>> >>>>>> Also, can you email me the log output from when your startup the >>>>>> application? >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-11, at 3:35 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Changing to a createCall and making a @Endpoint annotated method >>>>>> on the server seems to make it send something again: >>>>>> >>>>>> >>>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>>> I >>>>> t >>>>> ems.ge >>>>>> tItem:RespondTo:1","PriorityProcessing":"1"} >>>>>> >>>>>> >>>>>> >>>>>> With a response of: >>>>>> >>>>>> [{"HeartBeat":null}] >>>>>> >>>>>> >>>>>> >>>>>> However, I still so nowhere where it passes the parameter I give >>>>>> it >>> with: >>>>>> >>>>>> MessageBuilder.createCall().call("Items").endpoint("getItem", >>>>>> serialInput.getValue()).respondTo(Item.class, new >>>>>> RemoteCallback<Item>() >>>>> { >>>>>> >>>>>> >>>>>> >>>>>> @Override >>>>>> >>>>>> public void callback(Item response) { >>>>>> >>>>>> //throw new >>>>>> UnsupportedOperationException("Not supported yet."); >>>>>> >>>>>> >>>>>> MessageBox.alert("Return",item.getSerialNumber().toString(),null) >>>>>> ; >>>>>> >>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> }).noErrorHandling().sendNowWith(bus); >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> From: errai-users-bounces(a)lists.jboss.org >>>>>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>>>>> Jordan >>>>>> Sent: Monday, January 11, 2010 1:46 PM >>>>>> To: 'Mike Brock' >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> Made the changes specified in the userguide, but now it doesn't >>>>>> send anything. I'm using the following: >>>>>> >>>>>> >>>>> MessageBuilder.createMessage().toSubject("Items").signalling().with(" >>>>> S >>>>> erialN >>>>>> umber", "Test").noErrorHandling().sendNowWith(bus); >>>>>> >>>>>> >>>>>> >>>>>> It still seems to be set up just fine since the in.erraiBus >>>>>> servlet is created and the client long polls it, but the code >>>>>> above doesn't seem to send anything. I'm using the following way >>>>>> to make it for the >>>>>> DefaultBlockingServlet: >>>>>> >>>>>> <listener> >>>>>> >>>>>> >>>>>> >>>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</lis >>>>> t >>>>> e >>>>> n >>>>> e >>>>> r-clas >>>>>> s> >>>>>> >>>>>> </listener> >>>>>> >>>>>> >>>>>> >>>>>> Should I be using that? I figure it shouldn't affect the client >>>>>> any >>>>> though >>>>>> unless the servlet is incorrectly set up as a consequence, which >>>>>> it >>>>> doesn't >>>>>> seem to be since they communicate just fine for the initial setup. >>>>>> What should I look at to see why it's not sending? >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Monday, January 11, 2010 12:43 PM >>>>>> To: Kevin Jordan >>>>>> Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> You should be aware we have made changes and are retiring the use >>>>>> of the CommandMessage API. Be sure to read the documentation in >>>>>> the userguide/src/main/docbook/en/master.xml file. You can use: >>>>>> mvn jdocbook:generate to create an HTML file from the userguide/ >> directory. >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Friday, January 08, 2010 2:56 PM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> I will check into this. We're still working on getting the AIO >>>>>> stuff >>>>>> sorted>Monday, January 11, 2010 8:59 AM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Hi Kevin, the compilation problems should be fixed already. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Yes, I am using trunk. Is there a more stable branch/version I >>>>>> should be using? I had updated again hoping it was just >>>>>> something with the time I checked out and then ran into the >>>>>> problems Heiko Braun ran into compiling it. >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Friday, January 08, 2010 8:52 PM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> What version of ErraiBus are you using? Are you getting it from trunk? >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> DefaultBlockingServlet seems to have the same effect. >>>>>> >>>>>> >>>>>> >>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>> Sent: Friday, January 08, 2010 2:56 PM >>>>>> To: Kevin Jordan >>>>>> Cc: errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> >>>>>> >>>>>> I will check into this. We're still working on getting the AIO >>>>>> stuff sorted, and I wouldn't consider the Tomcat or JBoss >>>>>> adapters to be production ready. You're best to use the >>>>>> DefaultBlockingServlet -- which will provide adequate performance >>>>>> for development while we get the AIO adapters squared away over >>>>>> the next >>> few days. >>>>>> >>>>>> >>>>>> >>>>>> On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> I'm having trouble getting a message to go through using ErraiBus. >>>>>> I'm using this on the client side: >>>>>> >>>>>> CommandMessage msg = (CommandMessage) >>>>>> CommandMessage.create().toSubject("Items").set("SerialNumber", >>>>>> serialInput.getValue()); >>>>>> >>>>>> bus.conversationWith(msg, new MessageCallback() { >>>>>> >>>>>> >>>>>> >>>>>> @Override >>>>>> >>>>>> public void callback(Message message) { >>>>>> >>>>>> //throw new >>>>>> UnsupportedOperationException("Not supported yet."); >>>>>> >>>>>> Item item = message.get(Item.class, >>>>>> "Item"); >>>>>> >>>>>> MessageBox.alert("Errai", >>>>>> item.getSerialNumber().toString(), null); >>>>>> >>>>>> } >>>>>> >>>>>> }); >>>>>> >>>>>> >>>>>> >>>>>> With this on the server side: >>>>>> >>>>>> @Service("Items") >>>>>> >>>>>> public class Items implements MessageCallback { >>>>>> >>>>>> private MessageBus bus; >>>>>> >>>>>> >>>>>> >>>>>> @Inject >>>>>> >>>>>> public Items(MessageBus bus) { >>>>>> >>>>>> this.bus = bus; >>>>>> >>>>>> System.out.println("Got a bus..."); >>>>>> >>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> @Override >>>>>> >>>>>> public void callback(Message message) { >>>>>> >>>>>> //throw new UnsupportedOperationException("Not supported >>>>> yet."); >>>>>> >>>>>> System.out.println("Incoming message..."); >>>>>> >>>>>> Long serialNum = message.get(Long.class, "SerialNumber"); >>>>>> >>>>>> System.out.println(serialNum); >>>>>> >>>>>> Item item = new Item(); >>>>>> >>>>>> item.setSerialNumber(serialNum); >>>>>> >>>>>> >>>>>> ConversationMessage.create(message).set("Item",item).sendNowWith( >>>>>> b >>>>>> u >>>>>> s >>>>>> ) >>>>>> ; >>>>>> >>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> However, all it seems to send is: >>>>>> >>>>>> >>>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>>> t >>>>> e >>>>> mp:Con >>>>>> versation:2","PriorityProcessing":"1"} >>>>>> >>>>>> >>>>>> >>>>>> I don't see where it actually sends my body or the subject that I >>>>>> fill >>>>> out >>>>>> in my message. Nothing also gets to the Service class. Am I >>>>>> doing something wrong? I have Tomcat running NIO and everything >>>>>> else seems set up correctly. It will keep a GET connection open >>>>>> and do the POST of the >>>>> JSON >>>>>> above, but nowhere does it seem to send what I want it to. I >>>>>> also seem >>>>> to >>>>>> be getting these occasionally, usually on some of the first >>>>>> requests to >>>>>> in.erraiBus: >>>>>> >>>>>> java.lang.NullPointerException >>>>>> >>>>>> at >>>>>> >>>>> org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(Tomcat >>>>> C >>>>> o >>>>> m >>>>> e >>>>> tServl >>>>>> et.java:105) >>>>>> >>>>>> at >>>>>> >>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEv >>>>> e >>>>> n >>>>> t >>>>> ( >>>>> Unknow >>>>>> n Source) >>>>>> >>>>>> at >>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Unk >>>>>> n >>>>>> o >>>>>> w >>>>>> n >>>>>> Source) >>>>>> >>>>>> at org.apache.catalina.core.StandardWrapperValve.event(Unknown >>>>>> Source) >>>>>> >>>>>> at org.apache.catalina.core.StandardContextValve.event(Unknown >>>>>> Source) >>>>>> >>>>>> at org.apache.catalina.core.StandardHostValve.event(Unknown >>>>> Source) >>>>>> >>>>>> at org.apache.catalina.valves.ValveBase.event(Unknown Source) >>>>>> >>>>>> at org.apache.catalina.core.StandardEngineValve.event(Unknown >>>>>> Source) >>>>>> >>>>>> at org.apache.catalina.connector.CoyoteAdapter.event(Unknown >>>>>> Source) >>>>>> >>>>>> at org.apache.coyote.http11.Http11NioProcessor.event(Unknown >>>>>> Source) >>>>>> >>>>>> at >>>>>> >>>>> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler. >>>>> e >>>>> v >>>>> e >>>>> nt(Unk >>>>>> nown Source) >>>>>> >>>>>> at >>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unknow >>>>>> n >>>>> Source) >>>>>> >>>>>> at >>>>>> >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolE >>>>> x >>>>> e >>>>> c >>>>> u >>>>> tor.ja >>>>>> va:886) >>>>>> >>>>>> at >>>>>> >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. >>>>> java:9 >>>>>> 08) >>>>>> >>>>>> at java.lang.Thread.run(Thread.java:619) >>>>>> >>>>>> >>>>>> >>>>>> Can anyone point me at what I'm missing? >>>>>> >>>>>> _______________________________________________ >>>>>> errai-users mailing list >>>>>> errai-users(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> errai-users mailing list >>>>>> errai-users(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> errai-users mailing list >>>>>> errai-users(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> errai-users mailing list >>>>>> errai-users(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>> >>>> >>>> >>> >>> >> >> >> _______________________________________________ >> errai-users mailing list >> errai-users(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/errai-users >> > > _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users _______________________________________________ errai-users mailing list errai-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/errai-users

That works. I can now get it to find that class and my MessageBus works now. Thanks! -----Original Message----- From: Mike Brock [mailto:cbrock@redhat.com] Sent: Monday, January 18, 2010 7:30 PM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages It's now fixed in trunk. On 2010-01-18, at 5:58 PM, Kevin Jordan wrote: > Or another option is: > Enumeration<URL> t = > Test.class.getClassLoader().getResources("ErraiApp.properties"); > while (t.hasMoreElements()) { > URL element = t.nextElement(); > JarURLConnection conn = (JarURLConnection)element.openConnection(); > JarFile jar = conn.getJarFile(); > File file = new File(jar.getName()); > } > > -----Original Message----- > From: errai-users-bounces(a)lists.jboss.org > [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin Jordan > Sent: Monday, January 18, 2010 4:53 PM > To: 'Mike Brock' > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > I think if you determine that the URL has a ! in it, that after you > remove that and everything after it, you can recreate a URL to that, > then get the URI of that and make a file out of that. This will > prevent you from needing to decode everything yourself since the only > thing a File won't like from a URI is if it has the ! in it. > > -----Original Message----- > From: errai-users-bounces(a)lists.jboss.org > [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin Jordan > Sent: Monday, January 18, 2010 4:00 PM > To: 'Mike Brock' > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > Yes, I can confirm that. Since it comes back from a URL object, the > path is encoded, but a File object doesn't decode it. > > -----Original Message----- > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Monday, January 18, 2010 3:52 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > Can you confirm that? If so, I'll investigate and get it fixed. > > On 2010-01-18, at 4:38 PM, Kevin Jordan wrote: > >> Adding that, I can see it picking up my external jar in the >> List<File> roots parameter, but it still doesn't manage to find the >> class after that. I think it's because the location it's in has a >> space which somehow gets replaced with a %20. This makes it not look >> for the correct > file. >> >> -----Original Message----- >> From: Mike Brock [mailto:cbrock@redhat.com] >> Sent: Monday, January 18, 2010 2:06 PM >> To: Kevin Jordan >> Cc: errai-users(a)lists.jboss.org >> Subject: Re: [errai-users] Trouble sending messages >> >> This means that your module is not in the classpath at compile time, >> and/or you do not have an ErraiApp.properties inside the JAR you wish >> to > scan. >> Perhaps this is not documented clearly. >> >> Every JAR you want Errai to scan *must* have an ErraiApp.properties >> in it's root folder. The file can be empty. It doesn't have to >> contain > anything. >> >> >> On 2010-01-18, at 2:29 PM, Kevin Jordan wrote: >> >>> Okay, in debug mode I see the logging. It definitely doesn't >>> generate anything for one in a jar file. >>> >>> -----Original Message----- >>> From: errai-users-bounces(a)lists.jboss.org >>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>> Jordan >>> Sent: Monday, January 18, 2010 1:09 PM >>> To: 'Mike Brock' >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> Sometimes, although seeing as my application will be secured with >>> authentication and very soon will depend on it, that may not be an >>> option for much longer. Usually I just compile and deploy it. >>> There shouldn't be anything really special about the way it's >>> compiled, seeing as I can compile it using Hudson as well since >>> Netbeans just uses >> Ant. >>> >>> -----Original Message----- >>> From: Mike Brock [mailto:cbrock@redhat.com] >>> Sent: Monday, January 18, 2010 1:01 PM >>> To: Kevin Jordan >>> Cc: errai-users(a)lists.jboss.org >>> Subject: Re: [errai-users] Trouble sending messages >>> >>> I'm not really familiar with NetBeans. >>> >>> Are you using the GWT Development Mode for testing? >>> >>> On 2010-01-18, at 1:53 PM, Kevin Jordan wrote: >>> >>>> Yeah, that's the only stuff that comes out during the compile phase. >>>> Not sure if I have something misconfigured in my logging, but >>>> that's the only places that print out. >>>> >>>> -----Original Message----- >>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>> Sent: Monday, January 18, 2010 10:45 AM >>>> To: Kevin Jordan >>>> Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org >>>> Subject: Re: [errai-users] Trouble sending messages >>>> >>>> This is for the compile-phase stuff. If you're running in hosted >>>> mode, you need to look in the GWT Development Mode logger. >>>> >>>> On 2010-01-18, at 11:43 AM, Kevin Jordan wrote: >>>> >>>>> Is there any logging I have to set up for a particular class or >>>>> package or any configuration I have to do for that? Normally, >>>>> even when it works, the only output I see from Errai while compiling is: >>>>> 0 [main] INFO Configuration - configuration scan targets >>>>> 0 [main] INFO Configuration - -> >>>>> >>>> >>> >> > C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-persistence-1. >>>>> 0-SNAPSHOT.jar >>>>> 0 [main] INFO Configuration - -> >>>>> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\src\java >>>>> 0 [main] INFO Configuration - -> >>>>> C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB- >>>>> I >>>>> N >>>>> F >>>>> \ >>>>> classe >>>>> s >>>>> 63 [main] INFO Configuration - caching context >>>>> 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\lib\errai-per >>>>> s >>>>> i >>>>> s >>>>> t >>>>> ence-1 >>>>> .0-SNAPSHOT.jar:*' >>>>> 188 [main] INFO Configuration - caching context >>>>> 'C:\Users\kjordan\Documents\NetBeansProjects\Desktop\build\web\WEB >>>>> - >>>>> I >>>>> N >>>>> F >>>>> \class >>>>> es' >>>>> >>>>> And I'm not even really using persistence (i.e. it's not inherited >>>>> in my .gwt.xml, but somehow it's getting run anyways either via >>>>> ErraiBus or ErraiCommons). >>>>> -----Original Message----- >>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>> Sent: Monday, January 18, 2010 10:39 AM >>>>> To: Kevin Jordan >>>>> Cc: 'Thomas SEGISMONT'; errai-users(a)lists.jboss.org >>>>> Subject: Re: [errai-users] Trouble sending messages >>>>> >>>>> This is an interesting theory. You should be able to determine >>>>> whether the stub is generated or not since at compile-time the >>>>> Errai generators show log output for each stub. >>>>> >>>>> You should see a log output that says: "Generated >>>>> marshaller/demarshaller >>>>> for: <classname>" for each entity you've annotated. >>>>> >>>>> On 2010-01-18, at 11:32 AM, Kevin Jordan wrote: >>>>> >>>>>> Not sure what you mean by that, but I'm using Netbeans and my >>>>>> domain POJOs >>>>> are in a separate project which gets included by my web project. >>>>> The projects compile file and I've used my domain POJOs via >>>>> SOAFace's UniversalClient and regular GWT-RPC before without issues. >>>>> And they get put across the wire with Errai, it's just when the >>>>> class is in a separate project that there seems to be a problem >>>>> and my callback isn't called. So I'm wondering if it's an issue >>>>> with the stub getting >>>> generated or something. >>>>> >>>>>> >>>>>> -----Original Message----- >>>>>> From: Thomas SEGISMONT [mailto:tsegismont@gmail.com] >>>>>> Sent: Monday, January 18, 2010 10:12 AM >>>>>> To: Kevin Jordan >>>>>> Cc: Mike Brock; errai-users(a)lists.jboss.org >>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>> >>>>>> Have you tried to include your project/jar source code in your >>>>>> launch >>>>> configuration ? >>>>>> >>>>>> It sounds more like a GWT configuration problem than an Errai one. >>>>>> >>>>>> If you're using Maven to build your project, you can read this : >>>>>> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/multiproject. >>>>>> h >>>>>> t >>>>>> m >>>>>> l >>>>>> >>>>>> Thomas >>>>>> >>>>>> On Mon, 18 Jan 2010 09:50:40 -0600, "Kevin Jordan" >>>>>> <kevin.jordan(a)xteconline.com&gt; wrote: >>>>>>> I think I've found out one problem. Somehow Errai has trouble >>>>>>> if your >>>>>> POJO >>>>>>> is in an external jar, or in my case another Netbeans project. >>>>>>> GWT will compile my project just fine, but it at least seems to >>>>>>> be that once I go >>>>>> to >>>>>>> another project/jar for my POJO it fails to get to my callback >>>>>>> and does >>>>>> the >>>>>>> behavior I've previously described. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Friday, January 15, 2010 4:20 PM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> Yes, that will work, of course. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-15, at 4:59 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> I haven't yet. But I'll try it and let you know if it works. >>>>>>> >>>>>>> >>>>>>> >>>>>>> So the default constructor provided by the JVM if you don't >>>>>>> specify one won't work? >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Friday, January 15, 2010 3:55 PM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> Have you updated to trunk -- I think that will fix the >>>>>>> InstantiationException? Any serializable class *must* have a >>>>>>> default constructor. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-15, at 4:48 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Well, I think I've figured it out on my callback problems. I >>>>>>> went back >>>>>> to >>>>>>> just passing a string back and forth and that worked. I then >>>>>>> made a simpler POJO to pass back and forth with just >>>>>>> implementing Serializable which didn't work (no callback call). >>>>>>> I then added the annotation that I just saw in the docs and that >>>>>>> didn't work (no callback call). I then removed >>>>>> Serializable >>>>>>> and the callback gets called, but it gets an error when it tries >>>>>>> to get >>>>>> the >>>>>>> POJO out of the message. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Is there anything extra I need to do for POJOs? >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: errai-users-bounces(a)lists.jboss.org >>>>>>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>>>>>> Jordan >>>>>>> Sent: Thursday, January 14, 2010 4:21 PM >>>>>>> To: 'Mike Brock' >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> Whenever I do that, I seem to get: >>>>>>> >>>>>>> java.lang.InstantiationException: >>>>>>> org.jboss.errai.bus.server.servlet.DefaultBlockingServlet >>>>>>> >>>>>>> at java.lang.Class.newInstance0(Class.java:340) >>>>>>> >>>>>>> at java.lang.Class.newInstance(Class.java:308) >>>>>>> >>>>>>> at >>>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.core.StandardWrapper.load(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at >>>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.core.StandardContext.start(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at >>>>>> org.apache.catalina.core.ContainerBase.addChildInternal(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.core.ContainerBase.addChild(Unknown >>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.core.StandardHost.addChild(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at >>>>>> org.apache.catalina.startup.HostConfig.deployDescriptor(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at >>>>>> org.apache.catalina.startup.HostConfig.deployDescriptors(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.startup.HostConfig.deployApps(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.startup.HostConfig.check(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at >>>>>>> org.apache.catalina.startup.HostConfig.lifecycleEvent(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at >>>>>>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unk >>>>>>> n >>>>>>> o >>>>>>> w >>>>>>> n >>>>>>> Source) >>>>>>> >>>>>>> at >>>>>> org.apache.catalina.core.ContainerBase.backgroundProcess(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at >>>>>>> >>>>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>>>> p >>>>>> r >>>>>> ocessC >>>>>>> hildren(Unknown Source) >>>>>>> >>>>>>> at >>>>>>> >>>>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>>>> p >>>>>> r >>>>>> ocessC >>>>>>> hildren(Unknown Source) >>>>>>> >>>>>>> at >>>>>>> >>>>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor. >>>>>> r >>>>>> u >>>>>> n(Unkn >>>>>>> own Source) >>>>>>> >>>>>>> at java.lang.Thread.run(Thread.java:619) >>>>>>> >>>>>>> >>>>>>> >>>>>>> Even in a new project I've created to see if anything is >>>>>>> interfering with Errai somehow. Trying TomcatCometServlet or >>>>>>> ErraiAutoServlet also yields the same results as before in both >>>>>>> cases. Using the listener/Guice >>>>>> filter >>>>>>> works. I've also gotten it so a callback works in my new >>>>>>> minimal >>>>>> project. >>>>>>> So now I'm wondering if something else is interfering with it. >>>>>>> I've got Spring Security protecting pretty much everything, >>>>>>> although I think I've tried taking that out before and had the >>>>>>> same >>> effect. >>>>>>> I've also got GXT >>>>>>> (http://www.extjs.com/products/gxt/) in there. Along with Mule >>>>>>> and SOAFaces, although SOAFaces can probably go away since I'll >>>>>>> be communicating to Mule via Errai when that works so I can have >>>>>>> better asynchronous communication and also push communication. >>>>>>> I suppose what I'll try first is ripping out GXT since that's >>>>>>> probably the most likely culprit in my mind. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Thursday, January 14, 2010 12:12 PM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> We will actually be removing the Guice filter as it's created >>>>>>> problems >>>>>> for >>>>>>> deploying on some appservers. We're falling back on directly >>> declaring >>>>>>> the >>>>>>> servlet. So you might want to switch to directly declaring the >>>>>>> DefaultBlockingServlet like so: >>>>>>> >>>>>>> >>>>>>> >>>>>>> <servlet> >>>>>>> >>>>>>> <servlet-name>ErraiServlet</servlet-name> >>>>>>> >>>>>>> >>>>>>> >>>>>> <servlet-class>org.jboss.errai.bus.server.servlet.DefaultBlocking >>>>>> S >>>>>> e >>>>>> r >>>>>> v >>>>>> l >>>>>> et</se >>>>>>> rvlet-class> >>>>>>> >>>>>>> <load-on-startup>1</load-on-startup> >>>>>>> >>>>>>> </servlet> >>>>>>> >>>>>>> >>>>>>> >>>>>>> <servlet-mapping> >>>>>>> >>>>>>> <servlet-name>ErraiServlet</servlet-name> >>>>>>> >>>>>>> <url-pattern>*.erraiBus</url-pattern> >>>>>>> >>>>>>> </servlet-mapping> >>>>>>> >>>>>>> >>>>>>> >>>>>>> . >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-14, at 12:45 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> Yes. It's still working the way it was before where I have to >>>>>>> submit >>>>>> more >>>>>>> than once and the response comes back on the POST but the >>>>>>> callback >>>>>> doesn't >>>>>>> get called. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Thursday, January 14, 2010 11:44 AM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> Are you still losing messages? >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-14, at 12:31 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Switching it back to the listener config seems to make it work >>>>>>> again through the DefaultBlockingServlet. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Kevin Jordan [mailto:kevin.jordan@xteconline.com] >>>>>>> Sent: Thursday, January 14, 2010 11:22 AM >>>>>>> To: 'Mike Brock' >>>>>>> Cc: &#39;errai-users(a)lists.jboss.org&#39; >>>>>>> Subject: RE: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> Yeah, I'm using the NIO connector. And actually if I configure >>>>>>> the TomcatCometServlet manually I get the same error again. I >>>>>>> know that used to happen when I was accessing it through my AJP >>>>>>> connected Apache instance, but now I'm accessing it directly >>>>>>> through port 8443 on Tomcat. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Thursday, January 14, 2010 10:55 AM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> Are you using the NIO connector in Tomcat? Errai by default >>>>>>> will try to use Tomcat's AIO system, which requires that the NIO >>>>>>> or APR connecter be >>>>>> used. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-14, at 11:47 AM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> I tried the AutoServlet and it seems to pick the >>>>>>> TomcatCometServlet which makes it spin over and over on this >>>>>>> message every time it tries to access >>>>>>> it: >>>>>>> >>>>>>> >>>>>> ***************************************************************** >>>>>> * >>>>>> * >>>>>> * >>>>>> * >>>>>> * >>>>>> ****** >>>>>>> ********************* >>>>>>> >>>>>>> ** PROBLEM! >>>>>>> >>>>>>> ** It appears something has been incorrectly configured. In >>>>>>> order to use ErraiBus >>>>>>> >>>>>>> ** on Tomcat, you must ensure that you are using the NIO or APR >>>>>> connector. >>>>>>> Also >>>>>>> >>>>>>> ** make sure that you have added these lines to your >>>>>>> WEB-INF/web.xml >>>>>> file: >>>>>>> >>>>>>> ** --- >>>>>>> >>>>>>> ** <servlet> >>>>>>> >>>>>>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>>>>>> >>>>>>> ** >>>>>>> >>>>>> <servlet-class>org.jboss.errai.bus.server.servlet.TomcatCometServ >>>>>> l >>>>>> e >>>>>> t >>>>>> < >>>>>> / >>>>>> servle >>>>>>> t-class> >>>>>>> >>>>>>> ** <load-on-startup>1</load-on-startup> >>>>>>> >>>>>>> ** </servlet> >>>>>>> >>>>>>> ** >>>>>>> >>>>>>> ** <servlet-mapping> >>>>>>> >>>>>>> ** <servlet-name>TomcatErraiServlet</servlet-name> >>>>>>> >>>>>>> ** <url-pattern>*.erraiBus</url-pattern> >>>>>>> >>>>>>> ** </servlet-mapping> >>>>>>> >>>>>>> ** --- >>>>>>> >>>>>>> ** If you have the following lines in your WEB-INF/web.xml, you >>>>>>> must comment or remove them: >>>>>>> >>>>>>> ** --- >>>>>>> >>>>>>> ** <listener> >>>>>>> >>>>>>> ** >>>>>>> >>>>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</li >>>>>> s >>>>>> t >>>>>> e >>>>>> n >>>>>> e >>>>>> r-clas >>>>>>> s> >>>>>>> >>>>>>> ** </listener> >>>>>>> >>>>>>> >>>>>> ***************************************************************** >>>>>> * >>>>>> * >>>>>> * >>>>>> * >>>>>> * >>>>>> ****** >>>>>>> ********************* >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Thursday, January 14, 2010 10:06 AM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> By the way, if you want, we're on IRC on irc.freenode.net in >>>>>>> channel >>>>>> #errai >>>>>>> -- I'm "cbrock" on there if you want help troubleshooting directly. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-14, at 9:44 AM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> It happens in all browsers, Firefox 3.5, Firefox 3.6, Chrome, >>>>>>> and IE on Windows 7. I'm using Tomcat. >>>>>>> >>>>>>> >>>>>>> >>>>>>> I'll try the AutoServlet to see if it makes a difference. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Wednesday, January 13, 2010 8:35 PM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> If you update to the latest version of trunk, simply get rid of >>>>>>> the listener and replace your web.xml config with this: >>>>>>> >>>>>>> >>>>>>> >>>>>>> <servlet> >>>>>>> >>>>>>> <servlet-name>ErraiAutoServlet</servlet-name> >>>>>>> >>>>>>> >>>>>>> >>>>>> <servlet-class>org.jboss.errai.bus.server.servlet.ErraiAutoServle >>>>>> t >>>>>> < >>>>>> / >>>>>> s >>>>>> e >>>>>> rvlet- >>>>>>> class> >>>>>>> >>>>>>> <load-on-startup>1</load-on-startup> >>>>>>> >>>>>>> </servlet> >>>>>>> >>>>>>> >>>>>>> >>>>>>> <servlet-mapping> >>>>>>> >>>>>>> <servlet-name>ErraiAutoServlet</servlet-name> >>>>>>> >>>>>>> <url-pattern>*.erraiBus</url-pattern> >>>>>>> >>>>>>> </servlet-mapping> >>>>>>> >>>>>>> >>>>>>> >>>>>>> This problem you're having is curious, though. We haven't seen >>>>>>> it in our internal testing. Can you tell me what browser, what >>>>>>> appserver, and what OS you're on? >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-13, at 5:08 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> I'm using the following on the client side: >>>>>>> >>>>>>> bus.subscribe("ItemFound", new MessageCallback() { >>>>>>> >>>>>>> >>>>>>> >>>>>>> @Override >>>>>>> >>>>>>> public void callback(Message message) { >>>>>>> >>>>>>> //throw new >>>>>>> UnsupportedOperationException("Not supported yet."); >>>>>>> >>>>>>> MessageBox.alert("Success", "In >>>>>> Callback", >>>>>>> null); >>>>>>> >>>>>>> /*Map<String,Object> parts = >>>>>>> message.getParts(); >>>>>>> >>>>>>> Set<String> keys = parts.keySet(); >>>>>>> >>>>>>> for (String key : keys) { >>>>>>> >>>>>>> MessageBox.alert("Key",key,null); >>>>>>> >>>>>>> }*/ >>>>>>> >>>>>>> //Item item = message.get(Item.class, >>>>>>> "Item"); >>>>>>> >>>>>>> //MessageBox.alert("Return", >>>>>>> item.getSerialNumber().toString(), null); >>>>>>> >>>>>>> } >>>>>>> >>>>>>> }); >>>>>>> >>>>>>> >>>>>>> >>>>>> MessageBuilder.createMessage().toSubject("Items").signalling().wi >>>>>> t >>>>>> h >>>>>> ( >>>>>> M >>>>>> e >>>>>> ssageP >>>>>>> arts.ReplyTo, "ItemFound").with("SerialNumber", >>>>>>> serialInput.getValue().toString()).errorsHandledBy(new >>>>>>> ErrorCallback() { >>>>>>> >>>>>>> >>>>>>> >>>>>>> @Override >>>>>>> >>>>>>> public boolean error(Message message, >>>>>> Throwable >>>>>>> throwable) { >>>>>>> >>>>>>> //throw new >>>>>>> UnsupportedOperationException("Not supported yet."); >>>>>>> >>>>>>> MessageBox.alert("Error", >>>>>>> throwable.getMessage(), null); >>>>>>> >>>>>>> return true; >>>>>>> >>>>>>> } >>>>>>> >>>>>>> }).sendNowWith(bus); >>>>>>> >>>>>>> >>>>>>> >>>>>>> Which sends: >>>>>>> >>>>>>> {"ToSubject":"Items","ReplyTo":"ItemFound","SerialNumber":"1201489" >>>>>>> } >>>>>>> >>>>>>> >>>>>>> >>>>>>> Although I've now noticed that it takes 2 tries to get it to >>>>>>> send that >>>>>> and >>>>>>> a >>>>>>> 3rd one to get the response back for the first one. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Server portion looks like: >>>>>>> >>>>>>> @Service("Items") >>>>>>> >>>>>>> public class Items implements MessageCallback { >>>>>>> >>>>>>> private MessageBus bus; >>>>>>> >>>>>>> >>>>>>> >>>>>>> @Inject >>>>>>> >>>>>>> public Items(MessageBus bus) { >>>>>>> >>>>>>> this.bus = bus; >>>>>>> >>>>>>> System.out.println("Got a bus..."); >>>>>>> >>>>>>> } >>>>>>> >>>>>>> >>>>>>> >>>>>>> @Override >>>>>>> >>>>>>> public void callback(Message message) { >>>>>>> >>>>>>> //throw new UnsupportedOperationException("Not supported >>>>>> yet."); >>>>>>> >>>>>>> System.out.println("Incoming message..."); >>>>>>> >>>>>>> String serialNum = message.get(String.class, >>>>>>> "SerialNumber"); >>>>>>> >>>>>>> System.out.println(serialNum); >>>>>>> >>>>>>> Item item = new Item(); >>>>>>> >>>>>>> item.setSerialNumber(Long.parseLong(serialNum)); >>>>>>> >>>>>>> >>>>>>> >>>>>> MessageBuilder.createConversation(message).subjectProvided().sign >>>>>> a >>>>>> l >>>>>> l >>>>>> i >>>>>> n >>>>>> g().wi >>>>>>> th("Item", item).errorsHandledBy(new ErrorCallback() { >>>>>>> >>>>>>> >>>>>>> >>>>>>> @Override >>>>>>> >>>>>>> public boolean error(Message message, Throwable >>>>>> throwable) >>>>>>> { >>>>>>> >>>>>>> //throw new UnsupportedOperationException("Not >>>>>>> supported yet."); >>>>>>> >>>>>>> throwable.printStackTrace(); >>>>>>> >>>>>>> return true; >>>>>>> >>>>>>> } >>>>>>> >>>>>>> }).sendNowWith(bus); >>>>>>> >>>>>>> } >>>>>>> >>>>>>> } >>>>>>> >>>>>>> >>>>>>> >>>>>>> Response on the second POST is: >>>>>>> >>>>>>> >>>>>> [{"ItemFound":{"Item":{__EncodedType:'com.xteconline.system.Item',id: >>>>>> n >>>>>> ull,se >>>>>>> >>>>>> >>>>> >>>> >>> >> > rialNumber:1201489,part:null,storageLocation:null,storageUnit:null,customer: >>>>>>> >>>>>> null,oemSerial:null,manufacturer:null,status:null,itemInfos:null}," >>>>>> T >>>>>> o >>>>>> S >>>>>> ubject >>>>>>> ":"ItemFound"}}] >>>>>>> >>>>>>> >>>>>>> >>>>>>> All others seem to get: >>>>>>> >>>>>>> [{"HeartBeat":null}] >>>>>>> >>>>>>> >>>>>>> >>>>>>> And on the first time I try to submit, it still seems to be kind >>>>>>> of >>>>>> setting >>>>>>> up stuff since it sends: >>>>>>> >>>>>>> >>>>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>>>> S >>>>>> e >>>>>> rverBu >>>>>>> >>>>>> >>>>> >>>> >>> >> > s","PriorityProcessing":"1"}||{"CommandType":"RemoteSubscribe","ToSubject":" >>>>>>> >>>>>> ServerBus","Subject":"AuthorizationService","PriorityProcessing":"1" >>>>>> } >>>>>> | >>>>>> |{"Com >>>>>>> >>>>>> mandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":"Cl >>>>>> i >>>>>> e >>>>>> n >>>>>> t >>>>>> N >>>>>> egotia >>>>>>> >>>>>> tionService","PriorityProcessing":"1"}||{"CommandType":"RemoteSub >>>>>> s >>>>>> c >>>>>> r >>>>>> i >>>>>> b >>>>>> e","To >>>>>>> >>>>>> Subject":"ServerBus","Subject":"ServerEchoService","PriorityProce >>>>>> s >>>>>> s >>>>>> i >>>>>> n >>>>>> g >>>>>> ":"1"} >>>>>>> >>>>>> ||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>>>> ||Cl >>>>>> ||ient >>>>>>> >>>>>> Bus"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus"," >>>>>> S >>>>>> u >>>>>> b >>>>>> j >>>>>> e >>>>>> ct":"C >>>>>>> >>>>>> >>>>> >>>> >>> >> > lientBusErrors"}||{"CommandType":"RemoteSubscribe","ToSubject":"ServerBus"," >>>>>>> >>>>>> Subject":"Items"}||{"CommandType":"RemoteSubscribe","ToSubject":" >>>>>> S >>>>>> e >>>>>> r >>>>>> v >>>>>> e >>>>>> rBus", >>>>>>> >>>>>> "Subject":"ServerBus"}||{"CommandType":"RemoteSubscribe","ToSubject":" >>>>>> Server >>>>>>> >>>>>> Bus","Subject":"AuthorizationService"}||{"CommandType":"RemoteSub >>>>>> s >>>>>> c >>>>>> r >>>>>> i >>>>>> b >>>>>> e","To >>>>>>> >>>>>> >>>>> >>>> >>> >> > Subject":"ServerBus","Subject":"ClientNegotiationService"}||{"CommandType":" >>>>>>> > RemoteSubscribe","ToSubject":"ServerBus","Subject":"ServerEchoService" >>>>>>> } >>>>>>> >>>>>>> >>>>>>> >>>>>>> And >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>>>> I >>>>>> t >>>>>> emFoun >>>>>>> d","PriorityProcessing":"1"} >>>>>>> >>>>>>> >>>>>>> >>>>>>> But doesn't send my stuff until I submit again. >>>>>>> >>>>>>> >>>>>>> >>>>>>> And about the only other relevant thing I can think of for Errai >>>>>>> is the servlet config: >>>>>>> >>>>>>> <listener> >>>>>>> >>>>>>> >>>>>>> >>>>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</li >>>>>> s >>>>>> t >>>>>> e >>>>>> n >>>>>> e >>>>>> r-clas >>>>>>> s> >>>>>>> >>>>>>> </listener> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Which I believe sets up the DefaultBlockingServlet. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Tuesday, January 12, 2010 11:48 AM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> We have a fairly significant application that makes extensive >>>>>>> use of >>>>>> this >>>>>>> type of paradigm and we haven't ever experienced any dropped > messages. >> >>>>>> Can >>>>>>> you provide me some examples of your code so we can troubleshoot >>>>>>> what's going on? >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-12, at 11:38 AM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> The MessageParts.ReplyTo was what I was missing in there. >>>>>>> However, my callback doesn't seem to be called. I get something >>>>>>> back when my request is POSTed, but it never seems to call my >>>>>>> callback. They do seem to work sometimes though. I had >>>>>>> accidentally named my callback subject and the server subject >>>>>>> the same and when I created a message to that subject, >>>>>> both >>>>>>> the client callback and the server callback were called correctly. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Tuesday, January 12, 2010 9:07 AM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> The sender needs to create a listening service that can be >>>>>>> replied > to. >> >>>>>> The >>>>>>> best way to do this is like so: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> //client-side code >>>>>>> >>>>>>> bus.subscribe("MyResponseSvc", >>>>>>> >>>>>>> new MessageCallback() { >>>>>>> >>>>>>> public void callback(Message msg) { >>>>>>> >>>>>>> ... >>>>>>> >>>>>>> } >>>>>>> >>>>>>> } >>>>>>> >>>>>>> ); >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> MessageBuilder.createMessage().toSubject("ConversationalService"). >>>>>> s >>>>>> i >>>>>> g >>>>>> n >>>>>> alling >>>>>>> () >>>>>>> >>>>>>> .with(MessageParts.ReplyTo, "MyResponseSvc") >>>>>>> >>>>>>> .with("SomeMessagePart", "Foo") >>>>>>> >>>>>>> .noErrorHandling() >>>>>>> >>>>>>> .sendNowWith(bus); >>>>>>> >>>>>>> >>>>>>> >>>>>>> ... >>>>>>> >>>>>>> //server-side code >>>>>>> >>>>>>> >>>>>>> >>>>>>> MessageBuilder.createConversation(message) >>>>>>> >>>>>>> .subjectProvided().signalling() >>>>>>> >>>>>>> .with("MyResponseData", "Bar") >>>>>>> >>>>>>> .noErrorHandling() >>>>>>> >>>>>>> .sendNowWith(bus); >>>>>>> >>>>>>> >>>>>>> >>>>>>> ... >>>>>>> >>>>>>> >>>>>>> >>>>>>> Note: we may make this more straight forward in the future, such >>>>>>> as with the RPC API. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-11, at 5:14 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> I won't be able to use the Swing monitor on the server I'm >>>>>>> deploying to since it has no interface. However, I did start >>>>>>> enabling logging in various places and it does seem that my >>>>>>> services weren't getting started. I was lacking an >>>>>>> ErraiApp.properties which I guess is used as the root for >>>>>> where >>>>>>> it should start looking for services. After adding that, they >>>>>>> started >>>>>> and >>>>>>> stuff started to go through. Does the client keep a record of >>>>>>> services >>>>>> or >>>>>>> something then? Why wouldn't it try to contact the service and >>>>>>> then fail that it couldn't find it? >>>>>>> >>>>>>> >>>>>>> >>>>>>> Also, looking at the revised Message API, how do you listen for >>>>>>> the reply in a conversation? Do I need to create a separate > listener? >>>>>>> Before you >>>>>> could >>>>>>> specify a MessageCallback to get the response in the >>>>>>> conversation, but I can't find anywhere in the call chain to do >>>>>>> that and it's not covered in the SVN book. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Monday, January 11, 2010 3:16 PM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> Kevin, >>>>>>> >>>>>>> >>>>>>> >>>>>>> I'm not sure how you're launching your app, but can you provide >>>>>>> this command line option which will bring up the bus monitor, >>>>>>> and at least tell me if you've probably deployed your services: >>>>>>> -Derrai.bus.showmonitor=true >>>>>>> >>>>>>> >>>>>>> >>>>>>> Also, can you email me the log output from when your startup the >>>>>>> application? >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-11, at 3:35 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Changing to a createCall and making a @Endpoint annotated method >>>>>>> on the server seems to make it send something again: >>>>>>> >>>>>>> >>>>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>>>> I >>>>>> t >>>>>> ems.ge >>>>>>> tItem:RespondTo:1","PriorityProcessing":"1"} >>>>>>> >>>>>>> >>>>>>> >>>>>>> With a response of: >>>>>>> >>>>>>> [{"HeartBeat":null}] >>>>>>> >>>>>>> >>>>>>> >>>>>>> However, I still so nowhere where it passes the parameter I give >>>>>>> it >>>> with: >>>>>>> >>>>>>> MessageBuilder.createCall().call("Items").endpoint("getItem", >>>>>>> serialInput.getValue()).respondTo(Item.class, new >>>>>>> RemoteCallback<Item>() >>>>>> { >>>>>>> >>>>>>> >>>>>>> >>>>>>> @Override >>>>>>> >>>>>>> public void callback(Item response) { >>>>>>> >>>>>>> //throw new >>>>>>> UnsupportedOperationException("Not supported yet."); >>>>>>> >>>>>>> >>>>>>> MessageBox.alert("Return",item.getSerialNumber().toString(),null >>>>>>> ) >>>>>>> ; >>>>>>> >>>>>>> } >>>>>>> >>>>>>> >>>>>>> >>>>>>> }).noErrorHandling().sendNowWith(bus); >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: errai-users-bounces(a)lists.jboss.org >>>>>>> [mailto:errai-users-bounces@lists.jboss.org] On Behalf Of Kevin >>>>>>> Jordan >>>>>>> Sent: Monday, January 11, 2010 1:46 PM >>>>>>> To: 'Mike Brock' >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> Made the changes specified in the userguide, but now it doesn't >>>>>>> send anything. I'm using the following: >>>>>>> >>>>>>> >>>>>> MessageBuilder.createMessage().toSubject("Items").signalling().with(" >>>>>> S >>>>>> erialN >>>>>>> umber", "Test").noErrorHandling().sendNowWith(bus); >>>>>>> >>>>>>> >>>>>>> >>>>>>> It still seems to be set up just fine since the in.erraiBus >>>>>>> servlet is created and the client long polls it, but the code >>>>>>> above doesn't seem to send anything. I'm using the following >>>>>>> way to make it for the >>>>>>> DefaultBlockingServlet: >>>>>>> >>>>>>> <listener> >>>>>>> >>>>>>> >>>>>>> >>>>>> <listener-class>org.jboss.errai.bus.server.ErraiServletConfig</li >>>>>> s >>>>>> t >>>>>> e >>>>>> n >>>>>> e >>>>>> r-clas >>>>>>> s> >>>>>>> >>>>>>> </listener> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Should I be using that? I figure it shouldn't affect the client >>>>>>> any >>>>>> though >>>>>>> unless the servlet is incorrectly set up as a consequence, which >>>>>>> it >>>>>> doesn't >>>>>>> seem to be since they communicate just fine for the initial setup. >>>>>>> What should I look at to see why it's not sending? >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Monday, January 11, 2010 12:43 PM >>>>>>> To: Kevin Jordan >>>>>>> Cc: 'Heiko Braun'; errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> You should be aware we have made changes and are retiring the >>>>>>> use of the CommandMessage API. Be sure to read the >>>>>>> documentation in the userguide/src/main/docbook/en/master.xml file. You can use: >>>>>>> mvn jdocbook:generate to create an HTML file from the userguide/ >>> directory. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-11, at 1:09 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Friday, January 08, 2010 2:56 PM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> I will check into this. We're still working on getting the AIO >>>>>>> stuff >>>>>>> sorted>Monday, January 11, 2010 8:59 AM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Hi Kevin, the compilation problems should be fixed already. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Jan 11, 2010, at 3:36 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Yes, I am using trunk. Is there a more stable branch/version I >>>>>>> should be using? I had updated again hoping it was just >>>>>>> something with the time I checked out and then ran into the >>>>>>> problems Heiko Braun ran into compiling it. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Friday, January 08, 2010 8:52 PM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> What version of ErraiBus are you using? Are you getting it from > trunk? >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-08, at 5:37 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> DefaultBlockingServlet seems to have the same effect. >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Mike Brock [mailto:cbrock@redhat.com] >>>>>>> Sent: Friday, January 08, 2010 2:56 PM >>>>>>> To: Kevin Jordan >>>>>>> Cc: errai-users(a)lists.jboss.org >>>>>>> Subject: Re: [errai-users] Trouble sending messages >>>>>>> >>>>>>> >>>>>>> >>>>>>> I will check into this. We're still working on getting the AIO >>>>>>> stuff sorted, and I wouldn't consider the Tomcat or JBoss >>>>>>> adapters to be production ready. You're best to use the >>>>>>> DefaultBlockingServlet -- which will provide adequate >>>>>>> performance for development while we get the AIO adapters >>>>>>> squared away over the next >>>> few days. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2010-01-08, at 2:34 PM, Kevin Jordan wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> I'm having trouble getting a message to go through using ErraiBus. >>>>>>> I'm using this on the client side: >>>>>>> >>>>>>> CommandMessage msg = (CommandMessage) >>>>>>> CommandMessage.create().toSubject("Items").set("SerialNumber", >>>>>>> serialInput.getValue()); >>>>>>> >>>>>>> bus.conversationWith(msg, new MessageCallback() { >>>>>>> >>>>>>> >>>>>>> >>>>>>> @Override >>>>>>> >>>>>>> public void callback(Message message) { >>>>>>> >>>>>>> //throw new >>>>>>> UnsupportedOperationException("Not supported yet."); >>>>>>> >>>>>>> Item item = message.get(Item.class, >>>>>>> "Item"); >>>>>>> >>>>>>> MessageBox.alert("Errai", >>>>>>> item.getSerialNumber().toString(), null); >>>>>>> >>>>>>> } >>>>>>> >>>>>>> }); >>>>>>> >>>>>>> >>>>>>> >>>>>>> With this on the server side: >>>>>>> >>>>>>> @Service("Items") >>>>>>> >>>>>>> public class Items implements MessageCallback { >>>>>>> >>>>>>> private MessageBus bus; >>>>>>> >>>>>>> >>>>>>> >>>>>>> @Inject >>>>>>> >>>>>>> public Items(MessageBus bus) { >>>>>>> >>>>>>> this.bus = bus; >>>>>>> >>>>>>> System.out.println("Got a bus..."); >>>>>>> >>>>>>> } >>>>>>> >>>>>>> >>>>>>> >>>>>>> @Override >>>>>>> >>>>>>> public void callback(Message message) { >>>>>>> >>>>>>> //throw new UnsupportedOperationException("Not supported >>>>>> yet."); >>>>>>> >>>>>>> System.out.println("Incoming message..."); >>>>>>> >>>>>>> Long serialNum = message.get(Long.class, "SerialNumber"); >>>>>>> >>>>>>> System.out.println(serialNum); >>>>>>> >>>>>>> Item item = new Item(); >>>>>>> >>>>>>> item.setSerialNumber(serialNum); >>>>>>> >>>>>>> >>>>>>> ConversationMessage.create(message).set("Item",item).sendNowWith >>>>>>> ( >>>>>>> b >>>>>>> u >>>>>>> s >>>>>>> ) >>>>>>> ; >>>>>>> >>>>>>> } >>>>>>> >>>>>>> >>>>>>> >>>>>>> } >>>>>>> >>>>>>> >>>>>>> >>>>>>> However, all it seems to send is: >>>>>>> >>>>>>> >>>>>> {"CommandType":"RemoteSubscribe","ToSubject":"ServerBus","Subject":" >>>>>> t >>>>>> e >>>>>> mp:Con >>>>>>> versation:2","PriorityProcessing":"1"} >>>>>>> >>>>>>> >>>>>>> >>>>>>> I don't see where it actually sends my body or the subject that >>>>>>> I fill >>>>>> out >>>>>>> in my message. Nothing also gets to the Service class. Am I >>>>>>> doing something wrong? I have Tomcat running NIO and everything >>>>>>> else seems set up correctly. It will keep a GET connection open >>>>>>> and do the POST of the >>>>>> JSON >>>>>>> above, but nowhere does it seem to send what I want it to. I >>>>>>> also seem >>>>>> to >>>>>>> be getting these occasionally, usually on some of the first >>>>>>> requests to >>>>>>> in.erraiBus: >>>>>>> >>>>>>> java.lang.NullPointerException >>>>>>> >>>>>>> at >>>>>>> >>>>>> org.jboss.errai.bus.server.servlet.TomcatCometServlet.event(Tomca >>>>>> t >>>>>> C >>>>>> o >>>>>> m >>>>>> e >>>>>> tServl >>>>>>> et.java:105) >>>>>>> >>>>>>> at >>>>>>> >>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilterE >>>>>> v >>>>>> e >>>>>> n >>>>>> t >>>>>> ( >>>>>> Unknow >>>>>>> n Source) >>>>>>> >>>>>>> at >>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(Un >>>>>>> k >>>>>>> n >>>>>>> o >>>>>>> w >>>>>>> n >>>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.core.StandardWrapperValve.event(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.core.StandardContextValve.event(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.core.StandardHostValve.event(Unknown >>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.valves.ValveBase.event(Unknown Source) >>>>>>> >>>>>>> at org.apache.catalina.core.StandardEngineValve.event(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at org.apache.catalina.connector.CoyoteAdapter.event(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at org.apache.coyote.http11.Http11NioProcessor.event(Unknown >>>>>>> Source) >>>>>>> >>>>>>> at >>>>>>> >>>>>> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler. >>>>>> e >>>>>> v >>>>>> e >>>>>> nt(Unk >>>>>>> nown Source) >>>>>>> >>>>>>> at >>>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(Unkno >>>>>>> w >>>>>>> n >>>>>> Source) >>>>>>> >>>>>>> at >>>>>>> >>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPool >>>>>> E >>>>>> x >>>>>> e >>>>>> c >>>>>> u >>>>>> tor.ja >>>>>>> va:886) >>>>>>> >>>>>>> at >>>>>>> >>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. >>>>>> java:9 >>>>>>> 08) >>>>>>> >>>>>>> at java.lang.Thread.run(Thread.java:619) >>>>>>> >>>>>>> >>>>>>> >>>>>>> Can anyone point me at what I'm missing? >>>>>>> >>>>>>> _______________________________________________ >>>>>>> errai-users mailing list >>>>>>> errai-users(a)lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> errai-users mailing list >>>>>>> errai-users(a)lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> errai-users mailing list >>>>>>> errai-users(a)lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> errai-users mailing list >>>>>>> errai-users(a)lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/errai-users >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> errai-users mailing list >>> errai-users(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/errai-users >>> >> >> > > > _______________________________________________ > errai-users mailing list > errai-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/errai-users > > _______________________________________________ > errai-users mailing list > errai-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/errai-users >

Do you have any experience running this behind Apache? I'm trying to use it to load balance two Tomcat servers, but it doesn't seem to be working too well. The connections seem to take forever to terminate and when they do they usually get this error back:

bus.server.ServerMessageBusImpl.nextMessage(ServerMessageBusImpl.java: 363)<b r/>org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.pollForMe ssages (DefaultBlockingServlet.java:90)<br/>org.jboss.errai.bus.server.servle t.Defa

http.HttpServlet.service(Unknown Source)<br/>javax.servlet.http.HttpServlet.service(Unknown Source)<br/>org.apache.catalina.core.ApplicationFilterChain.internalDo Filter (Unknown Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter(U nknown Source)<br/>org.springframework.security.util.FilterChainProxy$Virtual Filter Chain.doFilter(FilterChainProxy.java:378)<br/>org.springframework.secu rity.i ntercept.web.FilterSecurityInterceptor.invoke(FilterSecurityIntercepto r.java :109)<br/>org.springframework.security.intercept.web.FilterSecurityInt ercept or.doFilter(FilterSecurityInterceptor.java:83)<br/>org.springframework .secur

390)<br/>org.springframework.security.ui.ExceptionTranslationFilter.do Filter Http(ExceptionTranslationFilter.java:101)<br/>org.springframework.secu rity.u i.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)<br/>org. spring framework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(F ilterC hainProxy.java:390)<br/>org.springframework.security.wrapper.SecurityC ontext HolderAwareRequestFilter.doFilterHttp(SecurityContextHolderAwareReques tFilte r.java:91)<br/>org.springframework.security.ui.SpringSecurityFilter.do Filter (SpringSecurityFilter.java:53)<br/>org.springframework.security.util.F ilterC hainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)<br/>o rg.spr ingframework.security.ui.AbstractProcessingFilter.doFilterHttp(Abstrac tProce ssingFilter.java:278)<br/>org.springframework.security.ui.SpringSecuri tyFilt er.doFilter(SpringSecurityFilter.java:53)<br/>org.springframework.secu rity.u til.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java :390)< br/>org.jasig.cas.client.session.SingleSignOutFilter.doFilter(SingleSi gnOutF ilter.java:106)<br/>org.springframework.security.util.FilterChainProxy $Virtu alFilterChain.doFilter(FilterChainProxy.java:390)<br/>org.springframew ork.se curity.ui.logout.LogoutFilter.doFilterHttp(LogoutFilter.java:89)<br/>o rg.spr

java:53)<br/>org.springframework.security.util.FilterChainProxy$Virtua lFilte

context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionCo ntextI ntegrationFilter.java:235)<br/>org.springframework.security.ui.SpringS ecurit yFilter.doFilter(SpringSecurityFilter.java:53)<br/>org.springframework .secur

springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFi lterPr oxy.java:167)<br/>org.apache.catalina.core.ApplicationFilterChain.inte rnalDo Filter(Unknown Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter(U nknown Source)<br/>com.google.inject.servlet.DefaultFilterPipeline.dispatch(D efault FilterPipeline.java:43)<br/>com.google.inject.servlet.GuiceFilter.doFi lter(G uiceFilter.java:110)<br/>org.apache.catalina.core.ApplicationFilterCha in.int ernalDoFilter(Unknown Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter(U nknown Source)<br/>org.apache.catalina.core.StandardWrapperValve.invoke(Unkno wn Source)<br/>org.apache.catalina.core.StandardContextValve.invoke(Unkno wn Source)<br/>org.apache.catalina.core.StandardHostValve.invoke(Unknown Source)<br/>org.apache.catalina.valves.ErrorReportValve.invoke(Unknown Source)<br/>org.apache.catalina.core.StandardEngineValve.invoke(Unknow n Source)<br/>org.terracotta.modules.tomcat.tomcat_5_5.SessionValve55.tc Invoke (SessionValve55.java:63)<br/>org.terracotta.modules.tomcat.tomcat_5_5. Sessio nValve55.invoke(SessionValve55.java:50)<br/>org.apache.catalina.connec tor.Co yoteAdapter.service(Unknown Source)<br/>org.apache.coyote.http11.Http11NioProcessor.process(Unknow n Source)<br/>org.apache.coyote.http11.Http11NioProtocol$Http11Connectio nHandl er.process(Unknown Source)<br/>org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run (Unkno wn Source)<br/>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Thr eadPoo lExecutor.java:886)<br/>java.util.concurrent.ThreadPoolExecutor$Worker .run(T hreadPoolExecutor.java:908)<br/>java.lang.Thread.run(Thread.java:619)< br/>"} }] I've got Terracotta running to tie the memory between the two instances together and mod_proxy on Apache going to the HTTPS port. The only change I seem to have to make in Tomcat is the proxyName and proxyPort so redirects are handled correctly. Everything else seems to work fine, except for images loaded later seem to take a while, possibly because of the Comet connections Errai is making. I'm not sure if the issue is with Errai or the request is getting rewritten

If I take away Apache and run it just on a single node, everything works fine.

Some messages go through correctly, like the ones at the beginning.

And if the GET connection times out, it will get a heartbeat json

reply. Although it will usually get one in between with the error json

Regular messages like subscribing and sending a message manually will

take a while (like 30 seconds or longer) and usually come back with

the error json below as well. Even with one connection it seems to block

I'm going to try more configuration parameters on the Apache side to

see if it's something on there, but something is definitely blocking

anything else from going through.

Also, I know we had talked about this before, but will the

conversation messages have a direct callback ability instead of having

another subject that needs to be listened to? I'm creating an Errai

Proxy for loading data for GXT stores which in turn is used by

components to get data, but having a secondary subject to listen

doesn't quite fit into the design of this and I think I'd prefer to

keep it to one method of transport rather than using RPC or SOAFaces

UniversalClient. Not to mention a direct callback seems to fit more

into the conversation design since otherwise data could reach more

than one callback if you had the same component more than once on a

page listening to that reply subject and didn't have an increment counter

-----Original Message-----

From: Mike Brock [mailto:cbrock@redhat.com]

Sent: Wednesday, January 20, 2010 4:27 PM

To: Kevin Jordan

Cc: errai-users(a)lists.jboss.org

Subject: Re: [errai-users] Trouble sending messages

Interesting. Errai is designed to only use a single connection /

single queue by default with the server in order to prevent interfering

loading, etc.

We have not tested Errai in any load balancing scenarios such as with

Terracotta.

You're saying all the actual messages are eventually delivered in both

directions, albeit slowly?

On 2010-01-20, at 1:33 PM, Kevin Jordan wrote:

> Do you have any experience running this behind Apache? I'm trying to

> use it to load balance two Tomcat servers, but it doesn't seem to be

> working too well. The connections seem to take forever to terminate

> and when they do they usually get this error back:

> bus.server.ServerMessageBusImpl.nextMessage(ServerMessageBusImpl.java:

> 363)<b

> r/>org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.pollForM

> e

> ssages

> (DefaultBlockingServlet.java:90)<br/>org.jboss.errai.bus.server.servl

> e

> t.Defa

> http.HttpServlet.service(Unknown

> Source)<br/>javax.servlet.http.HttpServlet.service(Unknown

> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.internalD

> o

> Filter

> (Unknown

> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter(

> U

> nknown

> Source)<br/>org.springframework.security.util.FilterChainProxy$Virtua

> l

> Filter

> Chain.doFilter(FilterChainProxy.java:378)<br/>org.springframework.sec

> u

> rity.i

> ntercept.web.FilterSecurityInterceptor.invoke(FilterSecurityIntercept

> o

> r.java

> :109)<br/>org.springframework.security.intercept.web.FilterSecurityIn

> t

> ercept

> or.doFilter(FilterSecurityInterceptor.java:83)<br/>org.springframewor

> k

> .secur

> 390)<br/>org.springframework.security.ui.ExceptionTranslationFilter.d

> o

> Filter

> Http(ExceptionTranslationFilter.java:101)<br/>org.springframework.sec

> u

> rity.u

> i.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)<br/>org.

> spring

> framework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(

> F

> ilterC

> hainProxy.java:390)<br/>org.springframework.security.wrapper.Security

> C

> ontext

> HolderAwareRequestFilter.doFilterHttp(SecurityContextHolderAwareReque

> s

> tFilte

> r.java:91)<br/>org.springframework.security.ui.SpringSecurityFilter.d

> o

> Filter

> (SpringSecurityFilter.java:53)<br/>org.springframework.security.util.

> F

> ilterC

> o

> rg.spr

> ingframework.security.ui.AbstractProcessingFilter.doFilterHttp(Abstra

> c

> tProce

> ssingFilter.java:278)<br/>org.springframework.security.ui.SpringSecur

> i

> tyFilt

> er.doFilter(SpringSecurityFilter.java:53)<br/>org.springframework.sec

> u

> rity.u

> til.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.jav

> a

> :390)<

> br/>org.jasig.cas.client.session.SingleSignOutFilter.doFilter(SingleS

> i

> gnOutF

> ilter.java:106)<br/>org.springframework.security.util.FilterChainProx

> y

> $Virtu

> alFilterChain.doFilter(FilterChainProxy.java:390)<br/>org.springframe

> w

> ork.se

> o

> rg.spr

> java:53)<br/>org.springframework.security.util.FilterChainProxy$Virtu

> a

> lFilte

> context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionC

> o

> ntextI

> ntegrationFilter.java:235)<br/>org.springframework.security.ui.Spring

> S

> ecurit

> yFilter.doFilter(SpringSecurityFilter.java:53)<br/>org.springframewor

> k

> .secur

> doFilterHttp(ChannelProcessingFilter.java:116)<br/>org.springframewor

> k

> .secur

> ity.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)<br

> /

>> org.s

> pringframework.security.util.FilterChainProxy$VirtualFilterChain.doFi

> l

> ter(Fi

> lterChainProxy.java:390)<br/>org.springframework.security.util.Filter

> C

> hainPr

> oxy.doFilter(FilterChainProxy.java:175)<br/>org.springframework.web.f

> i

> lter.D

> springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingF

> i

> lterPr

> oxy.java:167)<br/>org.apache.catalina.core.ApplicationFilterChain.int

> e

> rnalDo

> Filter(Unknown

> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter(

> U

> nknown

> Source)<br/>com.google.inject.servlet.DefaultFilterPipeline.dispatch(

> D

> efault

> FilterPipeline.java:43)<br/>com.google.inject.servlet.GuiceFilter.doF

> i

> lter(G

> uiceFilter.java:110)<br/>org.apache.catalina.core.ApplicationFilterCh

> a

> in.int

> ernalDoFilter(Unknown

> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter(

> U

> nknown

> Source)<br/>org.apache.catalina.core.StandardWrapperValve.invoke(Unkn

> o

> wn

> Source)<br/>org.apache.catalina.core.StandardContextValve.invoke(Unkn

> o

> wn

> Source)<br/>org.apache.catalina.core.StandardHostValve.invoke(Unknown

> Source)<br/>org.apache.catalina.valves.ErrorReportValve.invoke(Unknow

> n

> Source)<br/>org.apache.catalina.core.StandardEngineValve.invoke(Unkno

> w

> n

> Source)<br/>org.terracotta.modules.tomcat.tomcat_5_5.SessionValve55.t

> c

> Invoke

> (SessionValve55.java:63)<br/>org.terracotta.modules.tomcat.tomcat_5_5.

> Sessio

> nValve55.invoke(SessionValve55.java:50)<br/>org.apache.catalina.conne

> c

> tor.Co

> yoteAdapter.service(Unknown

> Source)<br/>org.apache.coyote.http11.Http11NioProcessor.process(Unkno

> w

> n

> Source)<br/>org.apache.coyote.http11.Http11NioProtocol$Http11Connecti

> o

> nHandl

> er.process(Unknown

> Source)<br/>org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.ru

> n

> (Unkno

> wn

> Source)<br/>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Th

> r

> eadPoo

> lExecutor.java:886)<br/>java.util.concurrent.ThreadPoolExecutor$Worke

> r

> .run(T

> hreadPoolExecutor.java:908)<br/>java.lang.Thread.run(Thread.java:619)

> <

> br/>"}

> }]

> I've got Terracotta running to tie the memory between the two

> instances together and mod_proxy on Apache going to the HTTPS port.

> The only change I seem to have to make in Tomcat is the proxyName and

> proxyPort so redirects are handled correctly. Everything else seems

> to work fine, except for images loaded later seem to take a while,

> possibly because of the Comet connections Errai is making. I'm not

> sure if the issue is with Errai or the request is getting rewritten

incorrectly or something.

> If I take away Apache and run it just on a single node, everything

> works fine.

Yeah, although I get that error about the misconfiguration I posted a while back. I figured out how to get rid of the errors at least, using ProxyPreserveHost On in Apache to pass theHost: line from the incoming request gets rid of any errors, however, it still seems to hit some connection limit. Hopefully that at least helps someone who gets errors from Errai while backended behind Apache. -----Original Message----- From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 21, 2010 9:31 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Have you tried using the TomcatCometServlet, which using non-blocking I/O? On 2010-01-20, at 5:56 PM, Kevin Jordan wrote: > Some messages go through correctly, like the ones at the beginning. > And if the GET connection times out, it will get a heartbeat json > reply. Although it will usually get one in between with the error json below immediately. > Regular messages like subscribing and sending a message manually will > take a while (like 30 seconds or longer) and usually come back with > the error json below as well. Even with one connection it seems to block everything else. > I'm going to try more configuration parameters on the Apache side to > see if it's something on there, but something is definitely blocking > anything else from going through. > > Also, I know we had talked about this before, but will the > conversation messages have a direct callback ability instead of having > another subject that needs to be listened to? I'm creating an Errai > Proxy for loading data for GXT stores which in turn is used by > components to get data, but having a secondary subject to listen > doesn't quite fit into the design of this and I think I'd prefer to > keep it to one method of transport rather than using RPC or SOAFaces > UniversalClient. Not to mention a direct callback seems to fit more > into the conversation design since otherwise data could reach more > than one callback if you had the same component more than once on a > page listening to that reply subject and didn't have an increment counter or something to differentiate them. > > -----Original Message----- > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Wednesday, January 20, 2010 4:27 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > Interesting. Errai is designed to only use a single connection / > single queue by default with the server in order to prevent interfering with image > loading, etc. > > We have not tested Errai in any load balancing scenarios such as with > Terracotta. > > You're saying all the actual messages are eventually delivered in both > directions, albeit slowly? > > On 2010-01-20, at 1:33 PM, Kevin Jordan wrote: > >> Do you have any experience running this behind Apache? I'm trying to >> use it to load balance two Tomcat servers, but it doesn't seem to be >> working too well. The connections seem to take forever to terminate >> and when they do they usually get this error back: >> > [{"ClientBusErrors":{ErrorMessage:"null",AdditionalDetails:"org.jboss.errai. >> bus.server.ServerMessageBusImpl.nextMessage(ServerMessageBusImpl.java: >> 363)<b >> r/>org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.pollForM >> e >> ssages >> (DefaultBlockingServlet.java:90)<br/>org.jboss.errai.bus.server.servl >> e >> t.Defa >> > ultBlockingServlet.doPost(DefaultBlockingServlet.java:84)<br/>javax.servlet. >> http.HttpServlet.service(Unknown >> Source)<br/>javax.servlet.http.HttpServlet.service(Unknown >> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.internalD >> o >> Filter >> (Unknown >> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter( >> U >> nknown >> Source)<br/>org.springframework.security.util.FilterChainProxy$Virtua >> l >> Filter >> Chain.doFilter(FilterChainProxy.java:378)<br/>org.springframework.sec >> u >> rity.i >> ntercept.web.FilterSecurityInterceptor.invoke(FilterSecurityIntercept >> o >> r.java >> :109)<br/>org.springframework.security.intercept.web.FilterSecurityIn >> t >> ercept >> or.doFilter(FilterSecurityInterceptor.java:83)<br/>org.springframewor >> k >> .secur >> > ity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java: >> 390)<br/>org.springframework.security.ui.ExceptionTranslationFilter.d >> o >> Filter >> Http(ExceptionTranslationFilter.java:101)<br/>org.springframework.sec >> u >> rity.u >> i.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)<br/>org. >> spring >> framework.security.util.FilterChainProxy$VirtualFilterChain.doFilter( >> F >> ilterC >> hainProxy.java:390)<br/>org.springframework.security.wrapper.Security >> C >> ontext >> HolderAwareRequestFilter.doFilterHttp(SecurityContextHolderAwareReque >> s >> tFilte >> r.java:91)<br/>org.springframework.security.ui.SpringSecurityFilter.d >> o >> Filter >> (SpringSecurityFilter.java:53)<br/>org.springframework.security.util. >> F >> ilterC >> hainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)<br/> >> o >> rg.spr >> ingframework.security.ui.AbstractProcessingFilter.doFilterHttp(Abstra >> c >> tProce >> ssingFilter.java:278)<br/>org.springframework.security.ui.SpringSecur >> i >> tyFilt >> er.doFilter(SpringSecurityFilter.java:53)<br/>org.springframework.sec >> u >> rity.u >> til.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.jav >> a >> :390)< >> br/>org.jasig.cas.client.session.SingleSignOutFilter.doFilter(SingleS >> i >> gnOutF >> ilter.java:106)<br/>org.springframework.security.util.FilterChainProx >> y >> $Virtu >> alFilterChain.doFilter(FilterChainProxy.java:390)<br/>org.springframe >> w >> ork.se >> curity.ui.logout.LogoutFilter.doFilterHttp(LogoutFilter.java:89)<br/> >> o >> rg.spr >> > ingframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter. >> java:53)<br/>org.springframework.security.util.FilterChainProxy$Virtu >> a >> lFilte >> > rChain.doFilter(FilterChainProxy.java:390)<br/>org.springframework.security. >> context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionC >> o >> ntextI >> ntegrationFilter.java:235)<br/>org.springframework.security.ui.Spring >> S >> ecurit >> yFilter.doFilter(SpringSecurityFilter.java:53)<br/>org.springframewor >> k >> .secur >> > ity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java: >> > 390)<br/>org.springframework.security.securechannel.ChannelProcessingFilter. >> doFilterHttp(ChannelProcessingFilter.java:116)<br/>org.springframewor >> k >> .secur >> ity.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)<br >> / >>> org.s >> pringframework.security.util.FilterChainProxy$VirtualFilterChain.doFi >> l >> ter(Fi >> lterChainProxy.java:390)<br/>org.springframework.security.util.Filter >> C >> hainPr >> oxy.doFilter(FilterChainProxy.java:175)<br/>org.springframework.web.f >> i >> lter.D >> > elegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:236)<br/>org. >> springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingF >> i >> lterPr >> oxy.java:167)<br/>org.apache.catalina.core.ApplicationFilterChain.int >> e >> rnalDo >> Filter(Unknown >> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter( >> U >> nknown >> Source)<br/>com.google.inject.servlet.DefaultFilterPipeline.dispatch( >> D >> efault >> FilterPipeline.java:43)<br/>com.google.inject.servlet.GuiceFilter.doF >> i >> lter(G >> uiceFilter.java:110)<br/>org.apache.catalina.core.ApplicationFilterCh >> a >> in.int >> ernalDoFilter(Unknown >> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter( >> U >> nknown >> Source)<br/>org.apache.catalina.core.StandardWrapperValve.invoke(Unkn >> o >> wn >> Source)<br/>org.apache.catalina.core.StandardContextValve.invoke(Unkn >> o >> wn >> Source)<br/>org.apache.catalina.core.StandardHostValve.invoke(Unknown >> Source)<br/>org.apache.catalina.valves.ErrorReportValve.invoke(Unknow >> n >> Source)<br/>org.apache.catalina.core.StandardEngineValve.invoke(Unkno >> w >> n >> Source)<br/>org.terracotta.modules.tomcat.tomcat_5_5.SessionValve55.t >> c >> Invoke >> (SessionValve55.java:63)<br/>org.terracotta.modules.tomcat.tomcat_5_5. >> Sessio >> nValve55.invoke(SessionValve55.java:50)<br/>org.apache.catalina.conne >> c >> tor.Co >> yoteAdapter.service(Unknown >> Source)<br/>org.apache.coyote.http11.Http11NioProcessor.process(Unkno >> w >> n >> Source)<br/>org.apache.coyote.http11.Http11NioProtocol$Http11Connecti >> o >> nHandl >> er.process(Unknown >> Source)<br/>org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.ru >> n >> (Unkno >> wn >> Source)<br/>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Th >> r >> eadPoo >> lExecutor.java:886)<br/>java.util.concurrent.ThreadPoolExecutor$Worke >> r >> .run(T >> hreadPoolExecutor.java:908)<br/>java.lang.Thread.run(Thread.java:619) >> < >> br/>"} >> }] >> >> I've got Terracotta running to tie the memory between the two >> instances together and mod_proxy on Apache going to the HTTPS port. >> The only change I seem to have to make in Tomcat is the proxyName and >> proxyPort so redirects are handled correctly. Everything else seems >> to work fine, except for images loaded later seem to take a while, >> possibly because of the Comet connections Errai is making. I'm not >> sure if the issue is with Errai or the request is getting rewritten > incorrectly or something. >> >> If I take away Apache and run it just on a single node, everything >> works fine. >> > >

Even just connecting to Tomcat directly, I still seem to get that error. From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 21, 2010 10:06 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages You still get that error? I'm pretty sure I fixed it. On 2010-01-21, at 10:54 AM, Kevin Jordan wrote: Yeah, although I get that error about the misconfiguration I posted a while back. I figured out how to get rid of the errors at least, using ProxyPreserveHost On in Apache to pass theHost: line from the incoming request gets rid of any errors, however, it still seems to hit some connection limit. Hopefully that at least helps someone who gets errors from Errai while backended behind Apache. -----Original Message----- From: Mike Brock [mailto:cbrock@redhat.com] Sent: Thursday, January 21, 2010 9:31 AM To: Kevin Jordan Cc: errai-users(a)lists.jboss.org Subject: Re: [errai-users] Trouble sending messages Have you tried using the TomcatCometServlet, which using non-blocking I/O? On 2010-01-20, at 5:56 PM, Kevin Jordan wrote: > Some messages go through correctly, like the ones at the beginning. > And if the GET connection times out, it will get a heartbeat json > reply. Although it will usually get one in between with the error json below immediately. > Regular messages like subscribing and sending a message manually will > take a while (like 30 seconds or longer) and usually come back with > the error json below as well. Even with one connection it seems to block everything else. > I'm going to try more configuration parameters on the Apache side to > see if it's something on there, but something is definitely blocking > anything else from going through. > > Also, I know we had talked about this before, but will the > conversation messages have a direct callback ability instead of having > another subject that needs to be listened to? I'm creating an Errai > Proxy for loading data for GXT stores which in turn is used by > components to get data, but having a secondary subject to listen > doesn't quite fit into the design of this and I think I'd prefer to > keep it to one method of transport rather than using RPC or SOAFaces > UniversalClient. Not to mention a direct callback seems to fit more > into the conversation design since otherwise data could reach more > than one callback if you had the same component more than once on a > page listening to that reply subject and didn't have an increment counter or something to differentiate them. > > -----Original Message----- > From: Mike Brock [mailto:cbrock@redhat.com] > Sent: Wednesday, January 20, 2010 4:27 PM > To: Kevin Jordan > Cc: errai-users(a)lists.jboss.org > Subject: Re: [errai-users] Trouble sending messages > > Interesting. Errai is designed to only use a single connection / > single queue by default with the server in order to prevent interfering with image > loading, etc. > > We have not tested Errai in any load balancing scenarios such as with > Terracotta. > > You're saying all the actual messages are eventually delivered in both > directions, albeit slowly? > > On 2010-01-20, at 1:33 PM, Kevin Jordan wrote: > >> Do you have any experience running this behind Apache? I'm trying to >> use it to load balance two Tomcat servers, but it doesn't seem to be >> working too well. The connections seem to take forever to terminate >> and when they do they usually get this error back: >> > [{"ClientBusErrors":{ErrorMessage:"null",AdditionalDetails:"org.jboss.errai. >> bus.server.ServerMessageBusImpl.nextMessage(ServerMessageBusImpl.java: >> 363)<b >> r/>org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.pollForM >> e >> ssages >> (DefaultBlockingServlet.java:90)<br/>org.jboss.errai.bus.server.servl >> e >> t.Defa >> > ultBlockingServlet.doPost(DefaultBlockingServlet.java:84)<br/>javax.servlet. >> http.HttpServlet.service(Unknown >> Source)<br/>javax.servlet.http.HttpServlet.service(Unknown >> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.internalD >> o >> Filter >> (Unknown >> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter( >> U >> nknown >> Source)<br/>org.springframework.security.util.FilterChainProxy$Virtua >> l >> Filter >> Chain.doFilter(FilterChainProxy.java:378)<br/>org.springframework.sec >> u >> rity.i >> ntercept.web.FilterSecurityInterceptor.invoke(FilterSecurityIntercept >> o >> r.java >> :109)<br/>org.springframework.security.intercept.web.FilterSecurityIn >> t >> ercept >> or.doFilter(FilterSecurityInterceptor.java:83)<br/>org.springframewor >> k >> .secur >> > ity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java: >> 390)<br/>org.springframework.security.ui.ExceptionTranslationFilter.d >> o >> Filter >> Http(ExceptionTranslationFilter.java:101)<br/>org.springframework.sec >> u >> rity.u >> i.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)<br/>org. >> spring >> framework.security.util.FilterChainProxy$VirtualFilterChain.doFilter( >> F >> ilterC >> hainProxy.java:390)<br/>org.springframework.security.wrapper.Security >> C >> ontext >> HolderAwareRequestFilter.doFilterHttp(SecurityContextHolderAwareReque >> s >> tFilte >> r.java:91)<br/>org.springframework.security.ui.SpringSecurityFilter.d >> o >> Filter >> (SpringSecurityFilter.java:53)<br/>org.springframework.security.util. >> F >> ilterC >> hainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)<br/> >> o >> rg.spr >> ingframework.security.ui.AbstractProcessingFilter.doFilterHttp(Abstra >> c >> tProce >> ssingFilter.java:278)<br/>org.springframework.security.ui.SpringSecur >> i >> tyFilt >> er.doFilter(SpringSecurityFilter.java:53)<br/>org.springframework.sec >> u >> rity.u >> til.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.jav >> a >> :390)< >> br/>org.jasig.cas.client.session.SingleSignOutFilter.doFilter(SingleS >> i >> gnOutF >> ilter.java:106)<br/>org.springframework.security.util.FilterChainProx >> y >> $Virtu >> alFilterChain.doFilter(FilterChainProxy.java:390)<br/>org.springframe >> w >> ork.se >> curity.ui.logout.LogoutFilter.doFilterHttp(LogoutFilter.java:89)<br/> >> o >> rg.spr >> > ingframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter. >> java:53)<br/>org.springframework.security.util.FilterChainProxy$Virtu >> a >> lFilte >> > rChain.doFilter(FilterChainProxy.java:390)<br/>org.springframework.security. >> context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionC >> o >> ntextI >> ntegrationFilter.java:235)<br/>org.springframework.security.ui.Spring >> S >> ecurit >> yFilter.doFilter(SpringSecurityFilter.java:53)<br/>org.springframewor >> k >> .secur >> > ity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java: >> > 390)<br/>org.springframework.security.securechannel.ChannelProcessingFilter. >> doFilterHttp(ChannelProcessingFilter.java:116)<br/>org.springframewor >> k >> .secur >> ity.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)<br >> / >>> org.s >> pringframework.security.util.FilterChainProxy$VirtualFilterChain.doFi >> l >> ter(Fi >> lterChainProxy.java:390)<br/>org.springframework.security.util.Filter >> C >> hainPr >> oxy.doFilter(FilterChainProxy.java:175)<br/>org.springframework.web.f >> i >> lter.D >> > elegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:236)<br/>org. >> springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingF >> i >> lterPr >> oxy.java:167)<br/>org.apache.catalina.core.ApplicationFilterChain.int >> e >> rnalDo >> Filter(Unknown >> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter( >> U >> nknown >> Source)<br/>com.google.inject.servlet.DefaultFilterPipeline.dispatch( >> D >> efault >> FilterPipeline.java:43)<br/>com.google.inject.servlet.GuiceFilter.doF >> i >> lter(G >> uiceFilter.java:110)<br/>org.apache.catalina.core.ApplicationFilterCh >> a >> in.int >> ernalDoFilter(Unknown >> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter( >> U >> nknown >> Source)<br/>org.apache.catalina.core.StandardWrapperValve.invoke(Unkn >> o >> wn >> Source)<br/>org.apache.catalina.core.StandardContextValve.invoke(Unkn >> o >> wn >> Source)<br/>org.apache.catalina.core.StandardHostValve.invoke(Unknown >> Source)<br/>org.apache.catalina.valves.ErrorReportValve.invoke(Unknow >> n >> Source)<br/>org.apache.catalina.core.StandardEngineValve.invoke(Unkno >> w >> n >> Source)<br/>org.terracotta.modules.tomcat.tomcat_5_5.SessionValve55.t >> c >> Invoke >> (SessionValve55.java:63)<br/>org.terracotta.modules.tomcat.tomcat_5_5. >> Sessio >> nValve55.invoke(SessionValve55.java:50)<br/>org.apache.catalina.conne >> c >> tor.Co >> yoteAdapter.service(Unknown >> Source)<br/>org.apache.coyote.http11.Http11NioProcessor.process(Unkno >> w >> n >> Source)<br/>org.apache.coyote.http11.Http11NioProtocol$Http11Connecti >> o >> nHandl >> er.process(Unknown >> Source)<br/>org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.ru >> n >> (Unkno >> wn >> Source)<br/>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Th >> r >> eadPoo >> lExecutor.java:886)<br/>java.util.concurrent.ThreadPoolExecutor$Worke >> r >> .run(T >> hreadPoolExecutor.java:908)<br/>java.lang.Thread.run(Thread.java:619) >> < >> br/>"} >> }] >> >> I've got Terracotta running to tie the memory between the two >> instances together and mod_proxy on Apache going to the HTTPS port. >> The only change I seem to have to make in Tomcat is the proxyName and >> proxyPort so redirects are handled correctly. Everything else seems >> to work fine, except for images loaded later seem to take a while, >> possibly because of the Comet connections Errai is making. I'm not >> sure if the issue is with Errai or the request is getting rewritten > incorrectly or something. >> >> If I take away Apache and run it just on a single node, everything >> works fine. >> > >

Some messages go through correctly, like the ones at the beginning.

And if the GET connection times out, it will get a heartbeat json

reply. Although it will usually get one in between with the error json

Regular messages like subscribing and sending a message manually will

take a while (like 30 seconds or longer) and usually come back with

the error json below as well. Even with one connection it seems to block

I'm going to try more configuration parameters on the Apache side to

see if it's something on there, but something is definitely blocking

anything else from going through.

Also, I know we had talked about this before, but will the

conversation messages have a direct callback ability instead of having

another subject that needs to be listened to? I'm creating an Errai

Proxy for loading data for GXT stores which in turn is used by

components to get data, but having a secondary subject to listen

doesn't quite fit into the design of this and I think I'd prefer to

keep it to one method of transport rather than using RPC or SOAFaces

UniversalClient. Not to mention a direct callback seems to fit more

into the conversation design since otherwise data could reach more

than one callback if you had the same component more than once on a

page listening to that reply subject and didn't have an increment counter

-----Original Message-----

From: Mike Brock [mailto:cbrock@redhat.com]

Sent: Wednesday, January 20, 2010 4:27 PM

To: Kevin Jordan

Cc: errai-users(a)lists.jboss.org

Subject: Re: [errai-users] Trouble sending messages

Interesting. Errai is designed to only use a single connection /

single queue by default with the server in order to prevent interfering

loading, etc.

We have not tested Errai in any load balancing scenarios such as with

Terracotta.

You're saying all the actual messages are eventually delivered in both

directions, albeit slowly?

On 2010-01-20, at 1:33 PM, Kevin Jordan wrote:

> Do you have any experience running this behind Apache? I'm trying to

> use it to load balance two Tomcat servers, but it doesn't seem to be

> working too well. The connections seem to take forever to terminate

> and when they do they usually get this error back:

> bus.server.ServerMessageBusImpl.nextMessage(ServerMessageBusImpl.java:

> 363)<b

> r/>org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.pollForM

> e

> ssages

> (DefaultBlockingServlet.java:90)<br/>org.jboss.errai.bus.server.servl

> e

> t.Defa

> http.HttpServlet.service(Unknown

> Source)<br/>javax.servlet.http.HttpServlet.service(Unknown

> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.internalD

> o

> Filter

> (Unknown

> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter(

> U

> nknown

> Source)<br/>org.springframework.security.util.FilterChainProxy$Virtua

> l

> Filter

> Chain.doFilter(FilterChainProxy.java:378)<br/>org.springframework.sec

> u

> rity.i

> ntercept.web.FilterSecurityInterceptor.invoke(FilterSecurityIntercept

> o

> r.java

> :109)<br/>org.springframework.security.intercept.web.FilterSecurityIn

> t

> ercept

> or.doFilter(FilterSecurityInterceptor.java:83)<br/>org.springframewor

> k

> .secur

> 390)<br/>org.springframework.security.ui.ExceptionTranslationFilter.d

> o

> Filter

> Http(ExceptionTranslationFilter.java:101)<br/>org.springframework.sec

> u

> rity.u

> i.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)<br/>org.

> spring

> framework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(

> F

> ilterC

> hainProxy.java:390)<br/>org.springframework.security.wrapper.Security

> C

> ontext

> HolderAwareRequestFilter.doFilterHttp(SecurityContextHolderAwareReque

> s

> tFilte

> r.java:91)<br/>org.springframework.security.ui.SpringSecurityFilter.d

> o

> Filter

> (SpringSecurityFilter.java:53)<br/>org.springframework.security.util.

> F

> ilterC

> o

> rg.spr

> ingframework.security.ui.AbstractProcessingFilter.doFilterHttp(Abstra

> c

> tProce

> ssingFilter.java:278)<br/>org.springframework.security.ui.SpringSecur

> i

> tyFilt

> er.doFilter(SpringSecurityFilter.java:53)<br/>org.springframework.sec

> u

> rity.u

> til.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.jav

> a

> :390)<

> br/>org.jasig.cas.client.session.SingleSignOutFilter.doFilter(SingleS

> i

> gnOutF

> ilter.java:106)<br/>org.springframework.security.util.FilterChainProx

> y

> $Virtu

> alFilterChain.doFilter(FilterChainProxy.java:390)<br/>org.springframe

> w

> ork.se

> o

> rg.spr

> java:53)<br/>org.springframework.security.util.FilterChainProxy$Virtu

> a

> lFilte

> context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionC

> o

> ntextI

> ntegrationFilter.java:235)<br/>org.springframework.security.ui.Spring

> S

> ecurit

> yFilter.doFilter(SpringSecurityFilter.java:53)<br/>org.springframewor

> k

> .secur

> doFilterHttp(ChannelProcessingFilter.java:116)<br/>org.springframewor

> k

> .secur

> ity.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)<br

> /

>> org.s

> pringframework.security.util.FilterChainProxy$VirtualFilterChain.doFi

> l

> ter(Fi

> lterChainProxy.java:390)<br/>org.springframework.security.util.Filter

> C

> hainPr

> oxy.doFilter(FilterChainProxy.java:175)<br/>org.springframework.web.f

> i

> lter.D

> springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingF

> i

> lterPr

> oxy.java:167)<br/>org.apache.catalina.core.ApplicationFilterChain.int

> e

> rnalDo

> Filter(Unknown

> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter(

> U

> nknown

> Source)<br/>com.google.inject.servlet.DefaultFilterPipeline.dispatch(

> D

> efault

> FilterPipeline.java:43)<br/>com.google.inject.servlet.GuiceFilter.doF

> i

> lter(G

> uiceFilter.java:110)<br/>org.apache.catalina.core.ApplicationFilterCh

> a

> in.int

> ernalDoFilter(Unknown

> Source)<br/>org.apache.catalina.core.ApplicationFilterChain.doFilter(

> U

> nknown

> Source)<br/>org.apache.catalina.core.StandardWrapperValve.invoke(Unkn

> o

> wn

> Source)<br/>org.apache.catalina.core.StandardContextValve.invoke(Unkn

> o

> wn

> Source)<br/>org.apache.catalina.core.StandardHostValve.invoke(Unknown

> Source)<br/>org.apache.catalina.valves.ErrorReportValve.invoke(Unknow

> n

> Source)<br/>org.apache.catalina.core.StandardEngineValve.invoke(Unkno

> w

> n

> Source)<br/>org.terracotta.modules.tomcat.tomcat_5_5.SessionValve55.t

> c

> Invoke

> (SessionValve55.java:63)<br/>org.terracotta.modules.tomcat.tomcat_5_5.

> Sessio

> nValve55.invoke(SessionValve55.java:50)<br/>org.apache.catalina.conne

> c

> tor.Co

> yoteAdapter.service(Unknown

> Source)<br/>org.apache.coyote.http11.Http11NioProcessor.process(Unkno

> w

> n

> Source)<br/>org.apache.coyote.http11.Http11NioProtocol$Http11Connecti

> o

> nHandl

> er.process(Unknown

> Source)<br/>org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.ru

> n

> (Unkno

> wn

> Source)<br/>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Th

> r

> eadPoo

> lExecutor.java:886)<br/>java.util.concurrent.ThreadPoolExecutor$Worke

> r

> .run(T

> hreadPoolExecutor.java:908)<br/>java.lang.Thread.run(Thread.java:619)

> <

> br/>"}

> }]

> I've got Terracotta running to tie the memory between the two

> instances together and mod_proxy on Apache going to the HTTPS port.

> The only change I seem to have to make in Tomcat is the proxyName and

> proxyPort so redirects are handled correctly. Everything else seems

> to work fine, except for images loaded later seem to take a while,

> possibly because of the Comet connections Errai is making. I'm not

> sure if the issue is with Errai or the request is getting rewritten

incorrectly or something.

> If I take away Apache and run it just on a single node, everything

> works fine.