Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NullPointerException in connecting #2

Open
GoogleCodeExporter opened this issue Nov 14, 2015 · 3 comments
Open

NullPointerException in connecting #2

GoogleCodeExporter opened this issue Nov 14, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

con = new Connection("url", 61613, "guest", "guest");
        try {
            System.out.println("Starting connection");
            ErrorMessage errmsg = con.connect();
            if (errmsg != null)
                System.out.println("Error? "+errmsg.getContentAsString());
        } catch (StompJException e) {
            // TODO Auto-generated catch block
            System.out.println("Couldn't connect with Java Stomp thing");
            e.printStackTrace();
        }




/////////////

Here are results :-(

Initializing connection
[INFO] [Launcher:/installer] org.red5.server.service.Installer - Installer 
service created
Starting connection
[ERROR] [Launcher:/app] org.red5.server.Scope - Could not start scope 
[WebScope@55f35e30 Depth = 1, Path = '/default', Name = 'app']. 
java.lang.NullPointerException

Original issue reported on code.google.com by K2xL....@gmail.com on 4 Mar 2011 at 7:13

@GoogleCodeExporter
Copy link
Author

We put another catch for null pointer:

Couldn't connect with Java Stomp thing (NullPointerException)
java.lang.NullPointerException
    at pk.aamir.stompj.internal.FrameReceiver.processERRORFrame(FrameReceiver.java:147)
    at pk.aamir.stompj.internal.FrameReceiver.processFirstResponse(FrameReceiver.java:42)
    at pk.aamir.stompj.internal.StompJSession.connect(StompJSession.java:64)
    at pk.aamir.stompj.Connection.connect(Connection.java:44)

Original comment by K2xL....@gmail.com on 4 Mar 2011 at 7:19

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Have you tried setting the error handler before calling connect?

Original comment by volkov.r...@gmail.com on 30 Aug 2011 at 1:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant