[Installation, Configuration & DEPLOYMENT] - JBoss Service Doesnt Stop
by raghav8t2
Using Native JBoss i m running my jboss service. but i get the problem when i try to stop the service.. From control panel when i stop the service, it shows it as stopped. but i can stilll access the jboss from the browser.
when i tried using this command:
service stop jbas42svc
this is the error message that is displayed....
Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.Shutdown.main(Shutdown.java:214)
Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 5 more
Caused by: java.net.ConnectException: Connection refused: 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:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.(Socket.java:365)
at java.net.Socket.(Socket.java:265)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
Have i missed out any configurations...???
Thanks,
Raghav
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125368#4125368
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125368
18 years, 2 months
[JBoss Messaging] - Re: Understanding JBoss Messaging and SPOF (Single Point of
by seattle.golfer
"timfox" wrote :
|
| JBossMessaging 2.0, which is what we are currently at work on has major improvements in the area of persistence.
|
| We will support:
|
| 1) Shared JDBC database - like in 1.x
| 2) Unshared JDBC database per node (already working in TRUNK)
| 3) Unshared file based journal per node
|
| For HA we will also support replication between nodes for a "shared nothing" approach.
|
| Also we'll support failover via a shared file sytem (e.g., GFS over a SAN) in the case one is available.
|
| Lots of other great new things in JBM 2.0 including a brand new super fast NIO transport using Apache MINA. (Trustin Lee the author of MINA is now a JBoss employee), and many other features.
Awesome! That sounds like an exhaustive feature set! Now the obvious questions.. any chance some of these features can/will be backported to 1.4.x? Also, in your opinion, is what's in source stable enough to start building a solution? i.e do you think the interfaces and such are pretty well fleshed out at this point?
anonymous wrote :
| Also see JIRA for JBM 2.0 tasks and provisional timescales. We should have a GA released towards the end of the year.
|
| There is also a little bit more info on the jboss labs JBM project page.
|
I spent some time browsing JIRA, but can't seem to find the 2.0 provisional timescale. Any chance you can post a link?
anonymous wrote :
| JBM 2.0 is the subject of my talk at JBoss World in a couple of weeks. Why don't you come along and find out more?
|
I just started a new job this week, and doubt I've earned enough creed to justify a trip out so soon. :) Perhaps next year.
Tim, I really appreciate you taking the time to respond. It's good to see the community alive & well post acquisition.
thanks,
Deepak
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125362#4125362
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125362
18 years, 2 months
[Installation, Configuration & DEPLOYMENT] - Re: JBoss Not Working On IpAddress. Works Only On localhost
by raghav8t2
Hi.. Thanks for the solution. Now my jboss service runs fine.... but i get the problem when i try to stop the service.. From control panel when i stop the service, it shows it as stopped. but i can stilll access the jboss from the browser.
when i tried using this command:
service stop
this is the error message that is displayed....
Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.Shutdown.main(Shutdown.java:214)
Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 5 more
Caused by: java.net.ConnectException: Connection refused: 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:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.(Socket.java:365)
at java.net.Socket.(Socket.java:265)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
Have i missed out any other configurations...???
Thanks,
Raghav
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125361#4125361
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125361
18 years, 2 months
[JBoss Seam] - Re: Exception with basic authentication
by alllle
"shane.bryzak(a)jboss.com" wrote : If you're invoking a restricted method and the credentials are set (which is what the AuthenticationFilter does) then a silent login will automatically occur, with no need to explicitly call Identity.authenticate(). Digest authentication is a special case, with a special type of authenticator. You have to keep in mind that the request may be for an unsecured resource, for which authentication may not be required. If that is the case then you don't want to be prompting the user for their username and password.
I wasn't able to find any code to support your claim so far.
First of all, the AuthenticationFilter is only invoked when its urlPattern matches the requested resource. This is done in the SeamFilter$FilterChainImpl inner class:
| if (filter instanceof AbstractFilter)
| {
| AbstractFilter bf = (AbstractFilter) filter;
|
| if ( bf.isMappedToCurrentRequestPath(request) )
| {
| filter.doFilter(request, response, this);
| }
|
| else
| {
| this.doFilter(request, response);
| }
| }
|
|
Therefore, it will not be used if the resource requested is not a protected one.
Secondly, I'd like to see you pointing out to me where the "silent login" happens. So far with my own research, the JAAS login() is triggered via the Identity.authenticate() call. This is not a automatic process, it needs to be invoked from somewhere and it is not done with the current code if it is BASIC authentication.
I have to question that if you have done any testing on this, or even look it up in your code before making your claim. I have put in the identity fix myself and tried it out before posting my workaround, and my test confirmed that without the 2nd fix I mentioned, the authentication does not "silently" happen. You end up keep getting username/password prompt from the client browser.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125357#4125357
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125357
18 years, 2 months