[JBoss Messaging] - Re: JNP message queues through SSH tunnels
by cameronjones
I've investigated a bit more and i think i've found the root of the problem. The lookup to the jnp server is working as expected, returning the correct resource however from the hermes logs it appears that it is then attempting to connect to an internal ip address instead of going through the localhost tunnel. Notice in the logs that it fails while trying to lookup ip address 10.11.64.61
I've tested hermes with jboss messaging on my local machine and everything works well - do you have any ideas on how i can get this to work?
Ovidiu - I'm more than happy to add to the doco :-)
2006-08-24 21:10:38,446 [Hermes ThreadPool-4] ERROR hermes.browser.tasks.HermesBrowserTaskListener - No message, linked exception is : null
hermes.HermesException: No message, linked exception is : null
at hermes.browser.model.tree.ContextTreeNode.setContext(ContextTreeNode.java:174)
at hermes.browser.model.tree.ContextTreeNode.(ContextTreeNode.java:65)
at hermes.browser.model.tree.ContextTreeNode.(ContextTreeNode.java:70)
at hermes.browser.components.ContextTreeModelFactory.create(ContextTreeModelFactory.java:60)
at hermes.browser.tasks.JNDIBrowseTask.invoke(JNDIBrowseTask.java:59)
at hermes.browser.tasks.TaskSupport.run(TaskSupport.java:174)
at hermes.browser.tasks.ThreadPool.run(ThreadPool.java:182)
at java.lang.Thread.run(Thread.java:595)
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 10.11.64.61; nested exception is:
java.net.ConnectException: Connection timed out: connect]
at org.jnp.interfaces.NamingContext.list(NamingContext.java:812)
at org.jnp.interfaces.NamingContext.list(NamingContext.java:786)
at javax.naming.InitialContext.list(InitialContext.java:395)
at hermes.browser.model.tree.ContextTreeNode.setContext(ContextTreeNode.java:101)
at hermes.browser.model.tree.ContextTreeNode.(ContextTreeNode.java:65)
at hermes.browser.model.tree.ContextTreeNode.(ContextTreeNode.java:70)
at hermes.browser.components.ContextTreeModelFactory.create(ContextTreeModelFactory.java:60)
at hermes.browser.tasks.JNDIBrowseTask.invoke(JNDIBrowseTask.java:59)
at hermes.browser.tasks.TaskSupport.run(TaskSupport.java:174)
at hermes.browser.tasks.ThreadPool.run(ThreadPool.java:182)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.rmi.ConnectException: Connection refused to host: 10.11.64.61; nested exception is:
java.net.ConnectException: Connection timed out: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
at org.jnp.server.NamingServer_Stub.list(Unknown Source)
at org.jnp.interfaces.NamingContext.list(NamingContext.java:800)
... 10 more
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:516)
at java.net.Socket.connect(Socket.java:466)
at java.net.Socket.(Socket.java:366)
at java.net.Socket.(Socket.java:179)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
... 15 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967342#3967342
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967342
19 years, 8 months
[JBoss Seam] - Re: Please explain entity Scope
by norman.richards＠jboss.com
Setting the scope to session doesn't mean that all User instances live in the session. It means that there is one seam component type called "user" that seam will manage in the session. Usually this would be to manage the instance of the user that represents the current logged in user. Perhaps it would be clearer if the component name were "currentUser".
Remember, of course, that a EJB3 bean can have multiple roles in Seam. If you used User in another way in the same application, you could give the component another role. (an additional name/scope)
To answer your question, yes it means that the seam-managed "user" component would be stored in the session. The fact that you are accessing from a stateless component is not relevant. Yes, changing it to EVENT would store it in the request. I think entities default to conversation scope if you don't specify otherwise.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967336#3967336
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967336
19 years, 8 months
[JBoss Seam] - Please explain entity Scope
by sjmenden
Can someone explain to me the details of scoping with entity beans. The majority if not all of the examples I've seen show entitiy beans using the session scope. Like in the seam documentation:
| @Name("user")
| @Entity
| @Scope(SESSION)
| public class User {
| ...
| }
|
So what does this exactly mean that the 'user' entity bean lives in the Session scope, does this mean that in Bijection the user bean is literally in the session scope even if the EJB3 accessing the user entity bean is Stateless?
So if I changed the @Scope(SESSION) to @Scope(EVENT) then the user bean would only stay in the EVENT/request scope during bijection?
Help understanding this would be greatly appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967332#3967332
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967332
19 years, 8 months
[JBoss Portal] - Re: File upload problem
by PeterJ
OK, I tried it again with MySQL 5.0. This time the zip file uploaded just find. Well, almost. I did get quite a lot of errors that look like this:
12:18:56,704 ERROR [VersionManager] Error while setting references: javax.jcr.RepositoryException: 6d43a21c-ae9a-44fb-a117-d9f7b96cf2cb: 6d43a21c-ae9a-44fb-a117-d9f7b96cf2cb
But the files appear to be loaded.
Oh, I just realized that I am using a 2.4 portal that I build this morning from source downloaded from CVS. Be back in a second.
Ok, now I am running on 2.4.0GA and MySQL 5.0. Uploaded the 600K zip file and got the same results as indicated above. By the way, this zip file contains over 200 files in various directories, most of the files are HTML.
I then tried to upload a 2MB zip file (containing a single pdf file - the quick start guide) and got an error: Packet for query is too large. Fixed that and tried again. Now the file uploads just fine.
So it looks like the problem is PostgreSQL specific.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967329#3967329
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967329
19 years, 8 months