[JBoss Web Services] - Re: missing <wsse:Security> tag in WS-Security
by Himaja Thovi
Himaja Thovi [http://community.jboss.org/people/t.himaja] created the discussion
"Re: missing <wsse:Security> tag in WS-Security"
To view the discussion, visit: http://community.jboss.org/message/580453#580453
--------------------------------------------------------------
Hi,
Later i added few jars like jbossws-client.jar, jboss-common.jar, log4j.jar then i got some debug log at client side as follows:
DEBUG [main] (JAXWSClientMetaDataBuilder.java:77) - START buildMetaData: [service={http://com/}ServerService]
DEBUG [main] (WSDLDefinitionsFactory.java:102) - parse: http://127.0.0.1:9898/JbossWS/Server?wsdl
DEBUG [main] (JavaToXSD.java:175) - Load schema: http://com/=file:/tmp/JBossWS_com_5071302848578309750.xsd
DEBUG [main] (JBossWSEntityResolver.java:64) - resolveEntity: [pub=null,sysid=file:/tmp/JBossWS_com_5071302848578309750.xsd]
DEBUG [main] (JBossWSEntityResolver.java:64) - resolveEntity: [pub=http://schemas.xmlsoap.org/soap/encoding/,sysid=null]
DEBUG [main] (EndpointMetaData.java:311) - Using default parameter style: WRAPPED
DEBUG [main] (JAXWSClientMetaDataBuilder.java:102) - END buildMetaData:
UnifiedMetaData:
implementation: jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
deploymentName: null
securityDomain: null
ServiceMetaData:
qname={http://com/}ServerService
refName=null
wsdName=null
wsdlFile=null
wsdlLocation=http://127.0.0.1:9898/JbossWS/Server?wsdl
jaxrpcMapping=null
publishLocation=null
securityConfig=null
properties=null
TypesMetaData:
<schema targetNamespace='http://com/' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:tns='http://com/' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<complexType name='message'/>
<complexType name='messageResponse'>
<sequence>
<element maxOccurs='1' minOccurs='0' name='return' type='string'/>
</sequence>
</complexType>
<element name='message' type='tns:message'/>
<element name='messageResponse' type='tns:messageResponse'/>
</schema>
ClientEndpointMetaData:
type=JAXWS
qname={http://com/}ServerPort
address=http://127.0.0.1:9898/JbossWS/Server
binding=http://schemas.xmlsoap.org/wsdl/soap/http
seiName=null
configFile=META-INF/standard-jaxws-client-config.xml
configName=Standard Client(Doubt At This Point)
authMethod=null
properties={}
OperationMetaData:
qname={http://com/}message
javaName={http://com/}message
style=document/literal/WRAPPED
oneWay=false
soapAction=
DEBUG [main] (JAXWSClientMetaDataBuilder.java:276) - START: rebuildMetaData
DEBUG [main] (EndpointMetaData.java:321) - setParameterStyle: null
DEBUG [main] (EndpointMetaData.java:812) - Create new config [name=Standard Client,file=META-INF/standard-jaxws-client-config.xml]
DEBUG [main] (JBossWSConfigFactory.java:125) - getConfig: [name=Standard Client,url=META-INF/standard-jaxws-client-config.xml]
DEBUG [main] (JBossWSConfigFactory.java:71) - parse: jar:file:/home/himaja/NetBeansProjects/JbossWSClient/lib/jbossws-client.jar!/META-INF/standard-jaxws-client-config.xml
DEBUG [main] (SaxJBossXBParser.java:241) - Created parser: org.apache.xerces.jaxp.SAXParserImpl@15aed57, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
DEBUG [main] (SaxJBossXBParser.java:157) - http://xml.org/sax/features/validation set to: true
DEBUG [main] (SaxJBossXBParser.java:157) - http://xml.org/sax/features/namespaces set to: true
DEBUG [main] (SaxJBossXBParser.java:157) - http://apache.org/xml/features/validation/dynamic set to: true
DEBUG [main] (SaxJBossXBParser.java:157) - http://xml.org/sax/features/validation set to: true
DEBUG [main] (SaxJBossXBParser.java:157) - http://apache.org/xml/features/validation/schema set to: true
DEBUG [main] (SaxJBossXBParser.java:241) - Created parser: org.apache.xerces.jaxp.SAXParserImpl@15aed57, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
DEBUG [main] (EndpointMetaData.java:867) - Configure EndpointMetaData
DEBUG [main] (EndpointMetaData.java:879) - Added 0 PRE handlers
DEBUG [main] (EndpointMetaData.java:880) - Added 0 ENDPOINT handlers
DEBUG [main] (EndpointMetaData.java:881) - Added 0 POST handlers
DEBUG [main] (EndpointMetaData.java:321) - setParameterStyle: WRAPPED
DEBUG [main] (JAXWSMetaDataBuilder.java:938) - JAXBContext [types=[class com.Message, class com.MessageResponse],tns=http://com/]
DEBUG [main] (OperationMetaData.java:208) - Found best matching java method: public abstract java.lang.String com.Server.message()
DEBUG [main] (JAXWSClientMetaDataBuilder.java:322) - END: rebuildMetaData
ServiceMetaData:
qname={http://com/}ServerService
refName=null
wsdName=null
wsdlFile=null
wsdlLocation=http://127.0.0.1:9898/JbossWS/Server?wsdl
jaxrpcMapping=null
publishLocation=null
securityConfig=null
properties=null
TypesMetaData:
[complexType={http://com/}message,javaType=com.Message]
[complexType={http://com/}messageResponse,javaType=com.MessageResponse]
<schema targetNamespace='http://com/' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:tns='http://com/' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<complexType name='message'/>
<complexType name='messageResponse'>
<sequence>
<element maxOccurs='1' minOccurs='0' name='return' type='string'/>
</sequence>
</complexType>
<element name='message' type='tns:message'/>
<element name='messageResponse' type='tns:messageResponse'/>
</schema>
ClientEndpointMetaData:
type=JAXWS
qname={http://com/}ServerPort
address=http://127.0.0.1:9898/JbossWS/Server
binding=http://schemas.xmlsoap.org/wsdl/soap/http
seiName=com.Server
configFile=META-INF/standard-jaxws-client-config.xml
configName=Standard Client
authMethod=null
properties={}
OperationMetaData:
qname={http://com/}message
javaName=message
style=document/literal/WRAPPED
oneWay=false
soapAction=
ParameterMetaData:
xmlName={http://com/}message
partName=message
xmlType={http://com/}message
javaType=com.Message
mode=IN
inHeader=false
index=0
wrappedParameters=[]
ReturnMetaData:
xmlName={http://com/}messageResponse
partName=messageResponse
xmlType={http://com/}messageResponse
javaType=com.MessageResponse
mode=OUT
inHeader=false
index=-1
wrappedParameters=[[name = return, type = java.lang.String, typeArgs = null, variable = return, index = -1]]
DEBUG [main] (EndpointMetaData.java:732) - Configure SOAPBinding
DEBUG [main] (HandlerResolverImpl.java:125) - initHandlerChain: PRE
DEBUG [main] (HandlerResolverImpl.java:125) - initHandlerChain: ENDPOINT
DEBUG [main] (HandlerResolverImpl.java:125) - initHandlerChain: POST
DEBUG [main] (HandlerResolverImpl.java:99) - getHandlerChain: [type=PRE,info=[service={http://com/}ServerService,port={http://com/}Serve...]
DEBUG [main] (HandlerResolverImpl.java:99) - getHandlerChain: [type=POST,info=[service={http://com/}ServerService,port={http://com/}Serv...]
DEBUG [main] (HandlerResolverImpl.java:99) - getHandlerChain: [type=ENDPOINT,info=[service={http://com/}ServerService,port={http://com/}...]
DEBUG [main] (BindingImpl.java:94) - setHandlerChain: []
DEBUG [main] (ServiceDelegateImpl.java:434) - No port configuration for: {http://com/}ServerPort
DEBUG [main] (MessageContextAssociation.java:46) - pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@afae4a (Thread main)
DEBUG [main] (ParameterWrapping.java:109) - wrapRequestParameters: com.Message
DEBUG [main] (EndpointInvocation.java:103) - setRequestParamValue: [name={http://com/}message,value=com.Message]
DEBUG [main] (CommonSOAPBinding.java:144) - bindRequestMessage: {http://com/}message
DEBUG [main] (EndpointInvocation.java:110) - getRequestParamValue: {http://com/}message
DEBUG [main] (EndpointInvocation.java:268) - transformPayloadValue: com.Message -> com.Message
DEBUG [main] (HandlerChainExecutor.java:84) - Create a handler executor: []
DEBUG [main] (HandlerChainExecutor.java:84) - Create a handler executor: []
DEBUG [main] (HandlerChainExecutor.java:84) - Create a handler executor: []
DEBUG [main] (HTTPRemotingConnection.java:176) - Get locator for: [addr=http://127.0.0.1:9898/JbossWS/Server,props={javax.xml.ws.service.endpoint.address=http://127.0.0.1:9898/JbossWS/Server}]
DEBUG [main] (MicroRemoteClientInvoker.java:298) - org.jboss.remoting.transport.http.HTTPClientInvoker@15b0e2c connecting
DEBUG [main] (MicroRemoteClientInvoker.java:312) - org.jboss.remoting.transport.http.HTTPClientInvoker@15b0e2c connected
DEBUG [main] (HTTPRemotingConnection.java:220) - Remoting metadata: {NoThrowOnError=true, HEADER={SOAPAction="", Content-Type=text/xml; charset=UTF-8}}
DEBUG [main] (HTTPClientInvoker.java:313) - Setting request header with SOAPAction : ""
DEBUG [main] (HTTPClientInvoker.java:313) - Setting request header with Content-Type : text/xml; charset=UTF-8
DEBUG [main] (SOAPContentElement.java:137) - -----------------------------------
DEBUG [main] (SOAPContentElement.java:138) - Transitioning from OBJECT_VALID to XML_VALID
DEBUG [main] (ObjectContent.java:135) - getXMLFragment from Object [xmlType={http://com/}message,javaType=class com.Message]
DEBUG [main] (JAXBSerializer.java:61) - serialize: [xmlName={http://com/}message,xmlType={http://com/}message]
DEBUG [main] (JAXBSerializer.java:83) - serialized: <ns1:message xmlns:ns1="http://com/"/>
DEBUG [main] (ObjectContent.java:162) - xmlFragment: [source=<ns1:message xmlns:ns1="http://com/"/>]
DEBUG [main] (SOAPContentElement.java:144) - -----------------------------------
DEBUG [main] (SOAPMessageUnMarshallerHTTP.java:123) - getMimeHeaders from: {Date=[Thu, 13 Jan 2011 05:18:34 GMT], Transfer-Encoding=[chunked], NoThrowOnError=true, HEADER={SOAPAction="", Content-Type=text/xml; charset=UTF-8}, ResponseCode=500, ResponseCodeMessage=Internal Server Error, ResponseHeaders={null=[HTTP/1.1 500 Internal Server Error], Transfer-Encoding=[chunked], Date=[Thu, 13 Jan 2011 05:18:34 GMT], Content-Type=[text/xml;charset=UTF-8], Connection=[close], Server=[Apache-Coyote/1.1], X-Powered-By=[Servlet 2.5; JBoss-5.0/JBossWeb-2.1]}, Connection=[close], Content-Type=[text/xml;charset=UTF-8], X-Powered-By=[Servlet 2.5; JBoss-5.0/JBossWeb-2.1], Server=[Apache-Coyote/1.1]}
DEBUG [main] (MessageFactoryImpl.java:215) - createMessage: [contentType=text/xml; charset=UTF-8]
DEBUG [main] (InvokerRegistry.java:631) - removed org.jboss.remoting.transport.http.HTTPClientInvoker@15b0e2c from registry
DEBUG [main] (MessageContextJAXWS.java:105) - Begin response processing
DEBUG [main] (MessageContextAssociation.java:75) - popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@afae4a (Thread main)
DEBUG [main] (MessageContextAssociation.java:46) - pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@61cd2 (Thread main)
DEBUG [main] (CommonSOAPBinding.java:542) - unbindResponseMessage: {http://com/}message
DEBUG [main] (SOAPContentElement.java:137) - -----------------------------------
DEBUG [main] (SOAPContentElement.java:138) - Transitioning from XML_VALID to DOM_VALID
DEBUG [main] (SOAPContentElement.java:144) - -----------------------------------
DEBUG [main] (HandlerChainExecutor.java:96) - close
DEBUG [main] (HandlerChainExecutor.java:96) - close
DEBUG [main] (HandlerChainExecutor.java:96) - close
DEBUG [main] (MessageContextAssociation.java:75) - popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@61cd2 (Thread main)
javax.xml.ws.soap.SOAPFaultException: This service requires <wsse:Security>, which is missing.
at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:72)
at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109)
at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
at $Proxy15.message(Unknown Source)
at jbosswsclient.Main.main(Main.java:16)
BUILD SUCCESSFUL (total time: 2 seconds)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/580453#580453]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[jBPM] - Unable to assign a task to Group
by shashi mhatre
shashi mhatre [http://community.jboss.org/people/khalipili] created the discussion
"Unable to assign a task to Group"
To view the discussion, visit: http://community.jboss.org/message/581708#581708
--------------------------------------------------------------
I am using sample BPMN process (Evaluation process) provided in jbpm-installer in this my test. I have changed to first human task node (Self evaluation) in process by removing the actor id #{employee} and added the entry to group id as "Employees". I have changed the roles.properties file in jboss/default/conf/props folder and added the "Employees" role to krisv and few other users.
Now when i run my process, it runs successfully till self evaluation human task node and waits there for task completion signal. now when i login to jbpm-console as "krisv", I did not get any task in "Personal" or "Group" task view.
I did verified the jboss console, it throws below error message
16:20:50,484 INFO [STDOUT] [2011:01:18 16:01:484:debug] Arguments : [[]]
16:49:36,109 INFO [STDOUT] No properties file: roles.properties found
16:49:36,125 INFO [STDOUT] [2011:01:18 16:01:109:debug] Message receieved on client : QueryTaskSummaryResponse
16:49:36,125 INFO [STDOUT] [2011:01:18 16:01:125:debug] Arguments : [[]]
Not quite sure where i am missing, whether its jboss configuration issue or jbpm-console-server issue?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/581708#581708]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[Beginner's Corner] - Getting OutOfMemoryError:Java heap space error
by Mitesh Kothari
Mitesh Kothari [http://community.jboss.org/people/mkothari] created the discussion
"Getting OutOfMemoryError:Java heap space error"
To view the discussion, visit: http://community.jboss.org/message/580176#580176
--------------------------------------------------------------
java.lang.OutOfMemoryError:Java heap space
at java.util.HashMap.addEntry(HashMap.java:797)
at java.util.HashMap.put(HashMap.java:431)
at com.documentum.fc.client.impl.typeddata.AggregateLiteType.addAttrInternal(AggregateLiteType.java:430)
atcom.documentum.fc.client.impl.typeddata.AggregateLiteType.addAttrInternal(AggregateLiteType.java:423)
at com.documentum.fc.client.impl.typeddata.AggregateLiteType.buildMapping(AggregateLiteType.java:344)
atcom.documentum.fc.client.impl.typeddata.AggregateLiteType.<init>(AggregateLiteType.java:35)
at com.documentum.fc.client.impl.typeddata.AggregateLiteType.getUnextendedType(AggregateLiteType.java:103)
atcom.documentum.fc.client.impl.connection.LiteTypeManager.extractAspectTypeNames(LiteTypeManager.java:328)
at com.documentum.fc.client.impl.connection.LiteTypeManager.refreshTypeIfNeeded(LiteTypeManager.java:303)
atcom.documentum.fc.client.impl.objectprotocol.ObjectProtocolV1.deserializeObject(ObjectProtocolV1.java:91)
atcom.documentum.fc.client.impl.objectprotocol.ObjectProtocolV1.deserializeObjectWithPossiblyExtendedType(ObjectProtocolV1.java:203)
atcom.documentum.fc.client.impl.objectprotocol.ObjectProtocolV1.deserializeObjectWithPreamble(ObjectProtocolV1.java:309)
at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.applyForObject(NetwiseDocbaseRpcClient.java:663)
atcom.documentum.fc.client.impl.connection.docbase.DocbaseConnection$8.evaluate(DocbaseConnection.java:1246)
at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.evaluateRpc(DocbaseConnection.java:1014)
atcom.documentum.fc.client.impl.connection.docbase.DocbaseConnection.applyForObject(DocbaseConnection.java:1238)
at com.documentum.fc.client.impl.docbase.DocbaseApi.parameterizedFetch(DocbaseApi.java:106)
atcom.documentum.fc.client.impl.objectmanager.PersistentDataManager.fetchFromServer(PersistentDataManager.java:194)
atcom.documentum.fc.client.impl.objectmanager.PersistentDataManager.getData(PersistentDataManager.java:92)
atcom.documentum.fc.client.impl.objectmanager.PersistentObjectManager.getObjectFromServer(PersistentObjectManager.java:355)
atcom.documentum.fc.client.impl.objectmanager.PersistentObjectManager.getObject(PersistentObjectManager.java:311)
at com.documentum.fc.client.impl.session.Session.getObject(Session.java:834)
atcom.documentum.fc.client.impl.session.SessionHandle.getObject(SessionHandle.java:580)
at com.bureauveritas.documentum.common.dql.ExecDQL.queryForList(Unknown Source)
at com.bureauveritas.documentum.common.dql.ExecDQL.queryForList(Unknown Source)
atcom.bureauveritas.documentum.ismt.alertnotification.BvAlertNotificationJob.getExceededDueDate(UnknownSource)
atcom.bureauveritas.documentum.ismt.alertnotification.BvAlertNotificationJob.performJob(UnknownSource)
at com.bureauveritas.documentum.common.job.ABvCommonJob.performMethod(UnknownSource)
at com.bureauveritas.documentum.common.method.ABvCommonMethod.perform(UnknownSource)
at com.bureauveritas.documentum.common.method.ABvCommonMethod.execute(UnknownSource)
at com.documentum.mthdservlet.DfMethodRunner.runIt(Unknown Source)
at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)
06:12:38,598ERROR [http-0.0.0.0-9080-1] com.documentum.mthdservlet.DoMethod - Exceptioninvoking bv_mod_icc_dctm_alertnotification.
ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:319)
at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
atorg.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)
at com.documentum.mthdservlet.MethodOutputStream.flush(Unknown Source)
at com.documentum.mthdservlet.MethodOutputStream.flush(Unknown Source)
at com.documentum.mthdservlet.MethodOutputStream.methodClose(Unknown Source)
at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)
at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)
at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
atorg.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
atorg.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
atorg.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
atorg.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
atorg.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
atorg.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
atorg.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Causedby: java.net.SocketException: Software caused connection abort: socket writeerror
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
atorg.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
atorg.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:299)
at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:963)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314)
... 28 more
06:12:38,598ERROR [http-0.0.0.0-9080-1]org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/DmMethods].[DoMethod]- Servlet.service() for servlet DoMethod threw exception
javax.servlet.ServletException:ClientAbortException: java.net.SocketException: Software causedconnection abort: socket write error
at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)
at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
atorg.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
atorg.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
atorg.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
atorg.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
atorg.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
atorg.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/580176#580176]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[JBoss Portal] - Performance problems due to too many users registered?
by marco angheben
marco angheben [http://community.jboss.org/people/marco.angheben.2] created the discussion
"Performance problems due to too many users registered?"
To view the discussion, visit: http://community.jboss.org/message/581833#581833
--------------------------------------------------------------
Hi all.
We are running a JBoss Portal 2.6.4 instance on an Oracle 10g database, and we are experiencing a lot of performance problems related to OutOfMemoryError and CPU saturation; in addition to this, the system is extremely slow when accessing the pages for user management in the Admin portal.
Looking at the JBPM tables i found out that for each user registered existed a record in the JBPM_PROCESSINSTANCE table, with the END_field filled with the time the user had became active on the Portal.
As extreme try to solve our problems we deleted all the ended process instances associated to the jbp_identity_validation_approval_workflow using the JBPM API to avoid encountering problems on the database constraints. This cleaning operation seems to solve all the problems we had, as you can see looking the image attached.
Has anyone experienced a problem like this? Does anyone think a clean-up procedure like the one described above will be effective and harmless?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/581833#581833]
Start a new discussion in JBoss Portal at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[jBPM] - jBPM5 Persistance issue creating multiple human task
by shashi mhatre
shashi mhatre [http://community.jboss.org/people/khalipili] created the discussion
"jBPM5 Persistance issue creating multiple human task"
To view the discussion, visit: http://community.jboss.org/message/580756#580756
--------------------------------------------------------------
I have created a simple workflow, it contains first 2 action event, 1 rule task then a human task and again an action task. I have configure JBPM to persist the session/process in mysql. now when i start the process everything works file till human task. jbpm persist the process, signal to task service and wait for response from task service. i am able to view the human task in jbpm console too.
now i closed my current running program/process; as this process has already initiated human task, transaction manager has persisted the state in DB. if i view in the mysql db, i am getting only one task and one entry in "eventtypes" table (Entry for ruleflow - this event has already completed before human task - not quite sure why its still there).
Later I restarted the process; process started successfully and processed till human task. Now if we look into jbpm console for human task,it shows 3 (three) human task 1) 1 from current process and 2) 2 from prior process which i closed abruptly.
As my first process runtime was already persisted and human task was created for same, why jbpm is creating human task again.
i think due to eventytype entry of ruleflow task, which was already completed and not removed by jbpm session. jbpm session is putting duplicate entry in workitems table. this seems to be an issue in jbpm process persistence.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/580756#580756]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[JBoss Messaging] - Error: relation "jbm_dual" already exists
by tim＠nwresearch.com
tim(a)nwresearch.com [http://community.jboss.org/people/tim%40nwresearch.com] created the discussion
"Error: relation "jbm_dual" already exists"
To view the discussion, visit: http://community.jboss.org/message/581729#581729
--------------------------------------------------------------
I've set up jboss messaging in a 2 node Jboss 4.2.3 cluster with a postgresql database for shared jboss messaging datastore. When the second node is started, I see errors in the log like the second node is trying to recreate the messaging database tables.
2011-01-18 18:04:55,891 DEBUG [org.jboss.messaging.core.impl.JDBCSupport] Failed to execute: CREATE TABLE JBM
_DUAL (DUMMY INTEGER, PRIMARY KEY (DUMMY))
org.postgresql.util.PSQLException: ERROR: relation "jbm_dual" already exists
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:353)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:299)
at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:249)
at org.jboss.messaging.core.impl.JDBCSupport.createSchema(JDBCSupport.java:301)
at org.jboss.messaging.core.impl.JDBCSupport.start(JDBCSupport.java:167)
at org.jboss.messaging.core.impl.JDBCPersistenceManager.start(JDBCPersistenceManager.java:149)
at org.jboss.messaging.core.jmx.JDBCPersistenceManagerService.startService(JDBCPersistenceManagerServ
ice.java:100)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java
:142)
....
Similar errors are repeated for all the tables and user inserts.
This seems to me like a problem, but as near as I can tell things seem to be working dispite the errors. Is this error something to worry about? Is there a configuration which will prevent the second node from trying to recreate the tables which already exist?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/581729#581729]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months