[JNDI and Naming] - InitialContext#lookup does not timeout
by Stian Thorgersen
Stian Thorgersen [http://community.jboss.org/people/stianst] created the discussion
"InitialContext#lookup does not timeout"
To view the discussion, visit: http://community.jboss.org/message/600583#600583
--------------------------------------------------------------
I've got an issue where InitialContext#lookup will hang forever doing a lookup if there is a problem with the network. I appreciate this is the default settings of the TCP sockets to wait forever, so I've tried to configure the timeout using 'jnp.timeout' and 'jnp.sotimeout', but it still waits forever.
Hashtable<String, String> env = new Hashtable<String, String>();
env.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
env.put("java.naming.provider.url", "jnp://10.9.1.11:1099");
env.put("java.naming.factory.url.pkgs", "org.jboss.naming");
env.put("jnp.socketFactor", "org.jnp.interfaces.TimedSocketFactory");
env.put("jnp.timeout", "1000");
env.put("jnp.sotimeout", "1000");
InitialContext ctx = new InitialContext(env);
HelloWorld world = (HelloWorld) ctx.lookup("HelloWorldBean/remote");
world.sayHello("hello");
// disconnect network here
world = (HelloWorld) ctx.lookup("HelloWorldBean/remote");
world.sayHello("hello");
In the above example if the network is disconnected before the first lookup it times out as expected, but if the network is disconnected between the first and the second lookup it doesn't timeout at all (waited 10 min+).
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/600583#600583]
Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 8 months
[jBPM] - problem with jbpm on weblogic
by arash norouz
arash norouz [http://community.jboss.org/people/arashbahal] created the discussion
"problem with jbpm on weblogic"
To view the discussion, visit: http://community.jboss.org/message/569094#569094
--------------------------------------------------------------
hi all
i am new to jbpm.
i am trying to implement some web services based on jbpm. i have implemented my services and test it in stand alone mode and it is ok!
but when i am trying to deploy my services on weblogic server it is thrown by some exceptions!
*org.hibernate.HibernateException: Errors in named queries: findTasks, findMessages, findTimers, findGroupsByUserAndGroupType, findProcessInstanceIds, findJo
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:397)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1327)
at org.jbpm.pvm.internal.wire.descriptor.HibernateSessionFactoryDescriptor.construct(HibernateSessionFactoryDescriptor.java:62)
at org.jbpm.pvm.internal.wire.WireContext.construct(WireContext.java:487)
at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:466)
Truncated. see log file for complete stacktrace*
after searching the internet i have found that adding
*<property name="hibernate.query.factory_class">org.hibernate.hql.classic.ClassicQueryTranslatorFactory</property>*
to hibernate config fix the problem. i have tried the solution and it was successful, but after deploying
when i want to run one of my services it throws another exception
my code snippet is:
*ProcessInstance processInstance = executionService
.startProcessInstanceByKey(processDefinitionId, parameters,
userId + "-" + sequence);*
and the exception is :
*Error invoking com.pardis.notification.core.Services (POJO): org.hibernate.QueryException<ComponentHandler.handleRequest:144>
<WSEE:21>org.hibernate.QueryException: Incorrect query syntax [select new map( idProperty.objectName as objectName, idProperty.deployment.dbid as deploymentDbid )*
*
*
*Caused by: java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:123)
at org.hibernate.hql.classic.SelectParser.token(SelectParser.java:96)
at org.hibernate.hql.classic.ClauseParser.token(ClauseParser.java:109)
at org.hibernate.hql.classic.ClauseParser.end(ClauseParser.java:136)
at org.hibernate.hql.classic.PreprocessingParser.end(PreprocessingParser.java:145)
at org.hibernate.hql.classic.ParserHelper.parse(ParserHelper.java:52)
at org.hibernate.hql.classic.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:239)*
please help me about this situation
thanks in advance
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/569094#569094]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 8 months
[jBPM] - jBPM-console - Oracle - start process
by bpmn2user
bpmn2user [http://community.jboss.org/people/bpmn2user] created the discussion
"jBPM-console - Oracle - start process"
To view the discussion, visit: http://community.jboss.org/message/582637#582637
--------------------------------------------------------------
I get the following error after starting a porcess using jBPM-console with Oracle database(SNAPSHOT code).
Any comments are appreciated
[2011:01:23 22:01:450:exception] Uncaught exception on client
org.apache.mina.filter.codec.ProtocolDecoderException: java.lang.IllegalStateExc
eption: unread block data (Hexdump: 00 00 01 7F AC ED 00 05 73 72 01 00 1D 6F 72
67 2E 6A 62 70 6D 2E 74 61 73 6B 2E 73 65 72 76 69 63 65 2E 43 6F 6D 6D 61 6E 6
.......
at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(Prot
ocolCodecFilter.java:180)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessage
Received(DefaultIoFilterChain.java:414)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(Def
aultIoFilterChain.java:49)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.mes
sageReceived(DefaultIoFilterChain.java:832)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$HeadFilter.mess
ageReceived(DefaultIoFilterChain.java:616)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessage
Received(DefaultIoFilterChain.java:414)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.fireMessageRece
ived(DefaultIoFilterChain.java:408)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(Abstract
PollingIoProcessor.java:578)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(Abstr
actPollingIoProcessor.java:540)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(Abstr
actPollingIoProcessor.java:532)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(Ab
stractPollingIoProcessor.java:58)
at org.apache.mina.core.polling.AbstractPollingIoProcessor$Worker.run(Ab
stractPollingIoProcessor.java:857)
at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnabl
e.java:51)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IllegalStateException: unread block data
at java.io.ObjectInputStream$BlockDataInputStream.setBlockDataMode(Objec
tInputStream.java:2376)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1360)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:19
46)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1
752)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
at org.apache.mina.core.buffer.AbstractIoBuffer.getObject(AbstractIoBuff
er.java:1628)
at org.apache.mina.filter.codec.serialization.ObjectSerializationDecoder
.doDecode(ObjectSerializationDecoder.java:93)
at org.apache.mina.filter.codec.CumulativeProtocolDecoder.decode(Cumulat
iveProtocolDecoder.java:173)
at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(Prot
ocolCodecFilter.java:170)
... 15 more
2011-01-23 22:51:49,356 (LogLevel.java:90) INFO org.apache.mina.filter.logging.
LoggingFilter - IDLE: both idle
java.lang.RuntimeException: Timeout : unable to retrieve results
at org.jbpm.task.service.responsehandlers.BlockingTaskSummaryResponseHan
dler.getResults(BlockingTaskSummaryResponseHandler.java:41)
at org.jbpm.integration.console.TaskManagement.getAssignedTasks(TaskMana
gement.java:132)
at org.jboss.bpm.console.server.TaskListFacade.getTasksForIdRef(TaskList
Facade.java:99)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.
java:117)
at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.
java:260)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232
)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166
)
at org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(Dispatch
erUtilities.java:142)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispa
tcher.java:356)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispa
tcher.java:173)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.servi
ce(HttpServletDispatcher.java:93)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.servi
ce(HttpServletDispatcher.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
at org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilte
r.java:59)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
2011-01-23 22:51:54,435 (LogLevel.java:90) INFO org.apache.mina.filter.logging.
LoggingFilter - IDLE: both idle
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/582637#582637]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 8 months
[JBoss Remoting] - Re: Sockets left in CLOSE_WAIT on server for JMS connections
by Joseph S
Joseph S [http://community.jboss.org/people/jselvin] created the discussion
"Re: Sockets left in CLOSE_WAIT on server for JMS connections"
To view the discussion, visit: http://community.jboss.org/message/596026#596026
--------------------------------------------------------------
Hi Ron,
I am observing similar issue in my application. We are using Jboss 4.2.0.GA, Jboss Remoting 2.5.3.SP1
We have a firewall between our server and client and we followed the forum,
http://blog.akquinet.de/2009/09/30/using-jboss-messaging-in-a-firewalled-... http://blog.akquinet.de/2009/09/30/using-jboss-messaging-in-a-firewalled-...
to set our parameters like below,
+ <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>+
+ <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>+
+ <attribute name="dataType" isParam="true">jms</attribute>+
+ <attribute name="socket.check_connection" isParam="true">true</attribute> +
+ <attribute name="serverBindAddress">${jboss.bind.address}</attribute>+
+ <attribute name="serverBindPort">4457</attribute>+
+ <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>+
+ <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>+
+ <attribute name="numberOfCallRetries" isParam="true">5</attribute>+
+ <attribute name="pingFrequency" isParam="true">5000</attribute>+
+ <attribute name="pingWindowFactor" isParam="true">2</attribute>+
+ <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute> +
+ <attribute name="stopLeaseOnFailure" isParam="true">true</attribute>+
+ <attribute name="clientLeasePeriod" isParam="true">10000</attribute>+
+ <attribute name="validatorPingPeriod" isParam="true">10000</attribute>+
+ <attribute name="validatorPingTimeout" isParam="true">5000</attribute>+
+ <attribute name="failureDisconnectTimeout" isParam="true">0</attribute>+
+ <attribute name="callbackErrorsAllowed">1</attribute>+
+ <attribute name="registerCallbackListener">false</attribute>+
+ <attribute name="useClientConnectionIdentity" isParam="true">true</attribute>+
+ <attribute name="timeout" isParam="true">1800000</attribute>+
+ <attribute name="numberOfRetries" isParam="true">10</attribute>+
+ <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>+
+ <attribute name="callbackTimeout">10000</attribute>+
+ <attribute name="secondaryBindPort">4481</attribute>+
With this implementation, we have mulitple Connections in CLOSE_WAIT state most of them getting cleared and some left behind.
After several days, we loose the JMS communication. We need to restart the application again to get rid off.
Also we observed the below exception multiple times when the issue happens,
Exception:
2011-03-28 11:50:10,271 TRACE [org.jboss.remoting.transport.socket.ServerThread(638)](WorkerThread#4[10.255.254.134:42933]) WorkerThread#4[10.255.254.134:42933] EOFException received. This is likely due to client finishing communication.
java.io.EOFException
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:740)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:586)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)
Kindly share some light to resolve this.
Regards,
Joseph.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/596026#596026]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 8 months