[JNDI/Naming/Network] - NamingException:Connection Reset
by sanjeeth
Hello All,
When i try to do a lookup for a Queue/Topic it gives be the following Naming Error
javax.naming.CommunicationException: Failed to retrieve stub from server D1FBMCS:8002 [Root exception is java.net.SocketException: Connection reset]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:263)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(Unknown Source)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at java.io.ObjectInputStream$PeekInputStream.read(Unknown Source)
at java.io.ObjectInputStream$PeekInputStream.readFully(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown Source)
at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
at java.io.ObjectInputStream.(Unknown Source)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:250)
The Main cause of this problem is because of the Connection getting reset. Also This problem does not happen frequently. When i run my application for some long period of time only then this problem is happening and also it happens only few times.
AnyBody know about this problem and when and why this connection will get reset.
Also can the problem be because of the local Port which was in the TIME_WAIT state was used for creation of sockets.
I am using JBoss:JBoss 4.0.4 GA
Os:Windows
8002 is the port where NamingService is running and its RMI port is 8003
Regards
Sanjeeth S
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039775#4039775
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039775
19 years
[JNDI/Naming/Network] - Failure to look up session bean from war in same ear
by sverker
I have an application where a war is packaged in an ear together with an ejb3 jar. The application has worked fine before but suddenly when building a new version it started to cause problems. When trying to look up a session bean from a servlet in the war file I get the following exception:
se.broaden.portal.t2.SubscriptionServiceException: Error performing 'se.broaden.
| portal.t2.SubscriptionService.findSubscriptions(java.lang.String msisdn)' --> ja
| vax.naming.CommunicationException: Receive timed out [Root exception is java.net
| .SocketTimeoutException: Receive timed out]
| ....
|
| Caused by: java.net.SocketTimeoutException: Receive timed out
| at java.net.PlainDatagramSocketImpl.receive0(Native Method)
| at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java
| :136)
| at java.net.DatagramSocket.receive(DatagramSocket.java:712)
| at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:12
| 87)
| at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1446)
| 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 se.broaden.portal.t2.tv.ServiceLocator.get_se_broaden_portal_t2_Subsc
| riptionServiceBean_Remote(ServiceLocator.java:108)
| at se.broaden.portal.t2.SubscriptionServiceDelegate.getSubscriptionServi
| ceRemote(SubscriptionServiceDelegate.java:40)
| at se.broaden.portal.t2.SubscriptionServiceDelegate.findSubscriptions(Su
| bscriptionServiceDelegate.java:196)
| ... 32 more
What happens is that for some reason my web app tries to do a service discovery over multicast instead of using the local server in the same vm.
I've run it with debugger and see that at line 1442 in NamingContext the localServer is null, hence it goes for discovery which doesn't work in my setup as I haven't deployed any HA stuff.
The application is generated with AndroMDA 3.3-SNAPSHOT and obviously that has something to do with it as an older version of the same application which is generated with AndroMDA 3.2-SNAPSHOT works fine when deployed on the same jboss server.
However, I've examined all deployment descriptors generated by AndroMDA and compared them to the ones that actually work and I can't find anything strange and nothing that has to do with naming. There is no jndi.properties or anything like that. I've also checked with the debugger what actually happens in the generated ServiceDelegate which is used to look up the session bean. It creates an InitialContext with null environment, exactly as the working app does, but fails when trying to look up the remote interface.
What could possible cause this behavior when a war in the same ear file starts to try to discover naming service? No clustering what so ever is configured as far as I can see.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039766#4039766
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039766
19 years
[JCA/JBoss] - WrappedResultSet cast excpetion
by mhammam
Hi all;
When i want to cast WrappedResultSet to OracleConnection i have the following error :
-----------------------------------------------------------
java.lang.UnsupportedOperationException: Do not know how to handle method=public abstract long java.sql.Blob.length() throws java.sql.SQLException
at org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService.invoke(WrapperDataSourceService.java:247)
at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)
at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)
at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195)
at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy62.length(Unknown Source)
------------------------------
thank's for your help;
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039765#4039765
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039765
19 years
[JBoss Seam] - Seam, WS and jbpm
by szaccaria
Hello to all!
I've a problem with seam, web service and jbpm... In particular, in my application, I want, from a web service, to register a order ( that i received from ws in xml format ) and start a instance in to jbpm process. I use seam - jbpm for to manage this order ( to check, to reject, to assign to person etc ) with ui interface ( jsf ), but I don't know how to create a instance from ws in the jbpm process.
I read some post like:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104926
where Shane wrote:
Web services support is still under development, in CVS only. I can't really help you with starting a JBPM process because we haven't built support for that yet :)
So I'm in trouble, can somebody give me a idea o a simple example?
Or at best, the ws support is near to out ?
Any help will be appreciated!
Thanks,
Stefano
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039760#4039760
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039760
19 years
[JBoss Portal] - Re: Failing to login using LDAP UserModule
by bdaw
"maph2880" wrote :
| I am using the LDAPUserModuleImpl user module.. For the user module, i have specified the common properties for userCtxDN and uidAttributeID. For the Role and Membership modules, I am using DB.
|
I thing the simple reason is that you are mixing UserModule from LDAP with RoleModule and MembershipModule from DB. HibernateMembershipModuleImpl won't be able to resolve user/role relationship in such scenario and I suspect this is the root of exception during login process.
So simply you cannot mix modules in such way. Only usage of delegating UserProfileModule for DB is allowed - like configured in default ldap config.
Sory if documentation wasn't clear enough about this. I will add a note there.
If you'll have any other issues don't hesitate to ask.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039758#4039758
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039758
19 years