Add new registration not working

After manual “Add new registration” got message “Registration successfully updated.” but no registration in list appears.

And no records in the table “gatewayRegistration” on my MS SQL server appears too.

Error log afte adding new registration:

2007.01.15 14:32:02 [org.jivesoftware.wildfire.gateway.Registration.

What do I do incorrectly?

What version are you running? This issue was, in theory, supposed to be resolved in 0.6b.

I’'m using :

Microsoft Windows Server 2003 Enterprise Edition (SP1)

Microsoft SQL Server 2000 Enterprise Edition (SP3)

version of WildFire is 3.1.1

version of IM Gateway is 1.0 Beta 6b

Message was edited by: IronHIRD

Aaaaaand ?..

GATE-169

The same issue. Integer out of range.

PostgreSQL 8.2, Gateway IM 1.0 beta 6b, Wildfire 3.1.1


8<----


[org.jivesoftware.wildfire.gateway.Registration.(Registration.java:83)

at org.jivesoftware.wildfire.gateway.RegistrationManager.createRegistration(Regist rationManager.java:71)

at org.jivesoftware.wildfire.gateway.BaseTransport.addNewRegistration(BaseTranspor t.java:1257)

at org.jivesoftware.wildfire.plugin.gateway.gateway_002dregistrations_jsp._jspServ ice(gateway_002dregistrations_jsp.java:151)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)

at org.jivesoftware.wildfire.container.PluginServlet.handleJSP(PluginServlet.java: 234)

at org.jivesoftware.wildfire.container.PluginServlet.service(PluginServlet.java:92 )

at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:830)

at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:11 8)

at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.util.LocaleFilter.doFilter(LocaleFilter.java:65)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingF ilter.java:41)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler. java:471)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)

at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)

at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.ja va:633)

at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)

at org.mortbay.http.HttpServer.service(HttpServer.java:909)

at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)

at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)

at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)

at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)

at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)

at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)


8----


GATE-170

I don’‘t know if either if you are willing to try this. If you are, would you mind wiping your db (or setting up a new temporary one) to see if a complete fresh install has this issue? I’'ve asked some of the Jive folk to look into this as I appear to be missing something.

I am having the same issue too.

org.postgresql.util.PSQLException: ERROR: inteiro fora do intervalo (integer out of range)

I’'m using Wildfire 3.1.1 / The last IM Gateway version and Postgres 8.1.6.

PS.: Using portuguese/BR version.

Kleber.

I wished to test preliminary all aspects of the program before using it in our company, so for the first time used an empty new database and I have received this error.

IronHIRD wrote:

I wished to test preliminary all aspects of the program before using it in our company, so for the first time used an empty new database and I have received this error.

Well crap. =) That kills a theory I had. None-the-less, thanks! That’'s quite useful to know!

Hey guys… I succeed. I had to did some manual work… but worked great.

Let me say what i did:

First, at the PSQL interface, i executed this command:

==> insert into gatewayregistration values (01,’‘jid@domain.com’’,’‘msn’’,’‘login@hotmail.com’’,’‘password’’,’‘nickname’’,0,0);

PS: remember to change some informations by your informations, like the JID.

After executed the command above i can see, in the Gateways/Registrations section at the Wildfire Administration Console, my registration. Before a tryed to use the transport at the IM Client i refresh the registration passoword to create a crypted password in the gatewayregistration database table. Finally, a had a logout and a login in my IM client and everything work great.

Despite this, i still can’'t make new registrations throught the Wildfire Admin Console, but i can make new registration manually and delete, throught the Wildfire Console, the registrations created manually.

Sorry if i commited some word mistakes, my writing english is intermediary.

I think that this can help on the developing of new great IM Gateway versions. Thanks a lot.

Kleber.

Just chiming in to say that I’'m getting this, too. CentOS 4.4, PostgreSQL 7.4, Wildfire 3.1.1, Gateway 1.0 Beta 6b. Brand new, fresh install.

Doing the manual SQL entries worked, as mentioned in the last post.

Yeah it’‘s not the SQL that’‘s bad (I’‘m doing the same thing in my code ;D ), but rather the java ODBC functionality is disagreeing with how I’‘m using it and how it’'s set up in the actual database.