[JBoss Web Services Development] - Basic Authentication with SOAPProxy or SOAPClient or HTTPRouter
by Juan Rios
Juan Rios [https://community.jboss.org/people/jark1982] created the discussion
"Basic Authentication with SOAPProxy or SOAPClient or HTTPRouter"
To view the discussion, visit: https://community.jboss.org/message/779999#779999
--------------------------------------------------------------
Hello I am new to JBoss ESB, I've been trying to consume a web service with three Apis, first with HttpRouter, then with SoapClient and finally SOAPProxy and in all these cases the response was the same.
h2. Error 401--Unauthorized
| h3. From RFC 2068 +Hypertext Transfer Protocol -- HTTP/1.1+:
h4. 10.4.2 401 Unauthorized
The request requires user authentication. The response MUST include a WWW-Authentic ate header field (section 14.46) containing a challenge applicable to the requested resource. The client MAY repeat th e request with a suitable Authorization header field (section 14.8). If the request already included Authorization cre dentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 respon se contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity MAY include rele vant diagnostic information. HTTP access authentication is explained in section 11.
|
I consulted on almost every forum and many solutions presented when applying but not any.
This is a picture of the work environment.
https://community.jboss.org/servlet/JiveServlet/downloadImage/2-779999-19... (https://community.jboss.org/servlet/JiveServlet/showImage/2-779999-19963/...)
This is my xml
** *<?*
*xml* version=++"1.0"++*?>**<*
*jbossesb*
*xmlns=+*+" http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."+*
+*
*xmlns:xsi=+*+" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance"+*+** xsi:schemaLocation=+*+" http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."+*+**>*
*<globals>
*
*<war-security domain=+*+"other"+*+** method=+*+"BASIC"+*+**/>*
*</globals>
*
*<providers>
*
*<fs-provider name=+*+"InputFile"+*+**>*
*<fs-bus busid=+*+"inputFile"+*+**>*
*<fs-message-filter directory=+*+"/tmp"+*+** input-suffix=+*+"esbfile"+*+**/>*
*</fs-bus>
*
*</fs-provider>
*
*</providers>
*
*<services>
*
*<service category=+*+"consume"+*+** description=+*+"Consume un servicio web"+*
+*
*invmScope=+*+"GLOBAL"+*+** name=+*+"ConsumeServicio"+*+**>*
*<listeners>
*
*<fs-listener busidref=+*+"inputFile"+*+** is-gateway=+*+"true"+*+** name=+*+"ListennerInputFile"+*+**/>*
*</listeners>
*
*<actions mep=+*+"RequestResponse"+*+**>*
*<action class=+*+"action.GetFile"+*+** name=+*+"getFile"+*+** process=+*+"process"+*+**/>*
*<action class=+*+"org.jboss.soa.esb.actions.SystemPrintln"+*+** name=+*+"showMessageBefore"+*+**>*
*<property name=+*+"message"+*+** value=+*+"ConsumeServicio->Actions->showMessageBefore"+*+**/>*
*<property name=+*+"printfull"+*+** value=+*+"true"+*+**/>*
*</action>
*
*<action class=+*+"org.jboss.soa.esb.actions.routing.http.HttpRouter"+*+** name=+*+"consumeServicioSII"+*+**>*
*<property name=+*+"method"+*+** value=+*+"POST"+*+**/>*
*<property name=+*+"endpointUrl"+*+** value=+*+" https://test.pisee.cl/SIIDireccionContribuyenteProxy https://test.pisee.cl/SIIDireccionContribuyenteProxy"+*+**>*
*<http-client-property name=+*+"username"+*+** value=+*+"HACIENDA"+*+**/>*
*<http-client-property name=+*+"password"+*+** value=+*+"fWQ5DK8z"+*+**/>*
*<http-client-property name=+*+"file"+*+** value=+*+"/HttpRouter-localhost-https-9433.properties"+*+**/>*
*</property>
*
*</action>
*
*<action class=+*+"org.jboss.soa.esb.actions.SystemPrintln"+*+** name=+*+"showMessageAfter"+*+**>*
*<property name=+*+"message"+*+** value=+*+"ConsumeServicio->Actions->showMessageAfter"+*+**/>*
*</action>
*
*<action class=+*+"org.jboss.soa.esb.actions.SyncServiceInvoker"+*+** name=+*+"enviaAConsumeWSClient"+*+**>*
*<property name=+*+"service-category"+*+** value=+*+"consume"+*+**/>*
*<property name=+*+"service-name"+*+** value=+*+"ConsumeSOAPProxy"+*+**/>*
*</action>
*
*</actions>
*
*</service>
*
*<!-- <service category="consume" description="Utiliza SOAPClient" invmScope="GLOBAL"* *name="ConsumeWSClient"> <actions mep="RequestResponse"> <action class="action.GetFile"*
*name="getFile" process="process"/> <action class="org.jboss.soa.esb.actions.SystemPrintln"*
*name="showMessageBefore"> <property name="message" value="Services->Actions->ConsumeWSClient->showMessageBefore"/>*
*<property name="printfull" value="true"/> </action> <action class="org.jboss.soa.esb.actions.soap.SOAPClient"*
*name="consumeWS"> <property name="wsdl" value="https://test.pisee.cl/SIIDireccionContribuyenteProxy?wsdl"/>*
*<property name="SOAPAction" value="getDireccionesCont"/> <property name="endpointUrl"*
*value="https://test.pisee.cl/SIIDireccionContribuyenteProxy"/> <property*
*name="http-client-properties"> <http-client-property name="http.proxyHost"*
*value="localhost"/> <http-client-property name="http.proxyPort" value="8080"/>*
*</property> <property name="password" value="fWQ5DK8z"/> <property name="username"*
*value="HACIENDA"/> </action> <action class="org.jboss.soa.esb.actions.SystemPrintln"*
*name="showMessageAfter"> <property name="message" value="Services->Actions->ConsumeWSClient->showMessageAfter"/>*
*</action> </actions> </service> -->*
*<service category=+*+"consume"+*
+*
*description=+*+"Consume mediante la clae SOAPProxy"+*+** invmScope=+*+"GLOBAL"+*+** name=+*+"ConsumeSOAPProxy"+*+**>*
*<security
*
*callbackHandler=+*+"org.jboss.soa.esb.services.security.auth.login.JBossSTSIssueCallbackHandler"+*+** moduleName=+*+""+*+**>*
*<property name=+*+"password"+*+** value=+*+"fWQ5DK8z"+*+**/>*
*<property name=+*+"username"+*+** value=+*+"HACIENDA"+*+**/>*
*</security>
*
*<property name=+*+"username"+*+** value=+*+"HACIENDA"+*+**/>*
*<property name=+*+"password"+*+** value=+*+"fWQ5DK8z"+*+**/>*
*<actions mep=+*+"RequestResponse"+*+**>*
*<action class=+*+"action.GetFile"+*+** name=+*+"getFile"+*+** process=+*+"process"+*+**/>*
*<action class=+*+"org.jboss.soa.esb.actions.SystemPrintln"+*+** name=+*+"showMessageBefore"+*+**>*
*<property name=+*+"message"+*+** value=+*+"Services->Actions-ConsumeSOAPProxy>showMessageBefore"+*+**/>*
*<property name=+*+"printfull"+*+** value=+*+"true"+*+**/>*
*</action>
*
*<action class=+*+"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"+*+** name=+*+"ConsumeWSSIISOAPProxy"+*+**>*
*<property name=+*+"wsdl"+*+** value=+*+" https://test.pisee.cl/SIIDireccionContribuyenteProxy?wsdl https://test.pisee.cl/SIIDireccionContribuyenteProxy?wsdl"+*+**/>*
*<property name=+*+"file"+*+** value=+*+"/META-INF//httpclient-8443.properties"+*+**/>*
*<!-- <property name="clientCredentialsRequired" value="true"/>-->*
*<property name=+*+"method"+*+** value=+*+"POST"+*+**/>*
*<property name=+*+"endpointUrl"+*+** value=+*+" https://test.pisee.cl/SIIDireccionContribuyenteProxy https://test.pisee.cl/SIIDireccionContribuyenteProxy"+*+**/>*
*<property name=+*+"headers"+*+**>*
*<header name=+*+"username"+*+** value=+*+"HACIENDA"+*+**/>*
*<header name=+*+"password"+*+** value=+*+"fWQ5DK8z"+*+**/>*
*</property>
*
*</action>
*
*<action class=+*+"org.jboss.soa.esb.actions.SystemPrintln"+*+** name=+*+"showMessageAfter"+*+**>*
*<property name=+*+"message"+*+** value=+*+"Services->Actions-ConsumeSOAPProxy>showMessageAfter"+*+**/>*
*</action>
*
*</actions>
*
*</service>
*
*</services**>**</*
*jbossesb>
*
And this is my property file
configurators=AuthBASIC,HttpProtocol
auth-username=HACIENDA
auth-password=fWQ5DK8z
authscope-host=127.0.0.1
authscope-port=8080
protocol-socket-factory=org.apache.commons.httpclient.contrib.ssl.EasySSLProtocolSocketFactory
keystore=/keystore.jks
keystore-passw=hola1982
truststore=/truststore.jks
truststore-passw=hola1982
max-connections-per-host=5
I hope you can help me thanks!
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/779999#779999]
Start a new discussion in JBoss Web Services Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
Re: [jboss-dev-forums] [JBoss AS 7 Development] - Single Installation Patching
by Brian Stansberry
Brian Stansberry [https://community.jboss.org/people/brian.stansberry] commented on the document
"Single Installation Patching"
To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47500#comment-11224
--------------------------------------------------
> Jeff Mesnil wrote:
>
>
>
> My main concern was if we had to generate patches from sources instead of using a binary. As long as patches are generated from binaries, we won't have checksum issues.
>
> This could be a "nice to have" feature but I'd prefer to postpone that when we have deeper insights on how patches are generated and used instead of introducing more complexity from the start.
>
Fair enough; I have no argument with that philosophy at all.
I think a lot of one off patches will be generated from source though. The support people will checkout the code for the version being patched, make whatever changes, and then build. The result of that build will be the --updated-dist used by the patch-gen tool. I could be wrong though; they may build jars and then copy them into a pristine dist and use that as their --updated-dist. Or they could skip the copy, use the dist produced by the build, but use the specified-content approach in the patch-config.xml.
We'll see!
--------------------------------------------------
10 years, 9 months
[JBoss Tools Development] - JBoss Tools Development Environment
by Nick Boldt
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document:
"JBoss Tools Development Environment"
To view the document, visit: https://community.jboss.org/docs/DOC-18124
--------------------------------------------------------------
*
#Tools_and_technologies Tools and technologies
**
#Java Java
**
#Eclipse_PDERCP Eclipse PDE/RCP
**
#SVN SVN
**
#Tips_for_productivity_and_quality Tips for productivity and quality
***
#Install_Code_Recommanders Install Code Recommanders
***
#Static_analysis Static analysis
****
#Enable_all_JDT_warnings Enable all JDT warnings
****
#Install_Findbugs_for_Eclipse Install Findbugs for Eclipse
****
#Install_PMD_for_Eclipse Install PMD for Eclipse
***
#Coverage Coverage
*
#Get_source Get source
**
#To_work_on_a_specific_component To work on a specific component
*
#Set_up_a_target_platform Set up a target platform
**
#Import_target_platforms Import target platforms
**
#Choose_and_use_a_target_platform Choose and use a target platform
*
#Run_JBoss_Tools_and_Tests_from_your_IDE Run JBoss Tools and Tests from your IDE
This article explains the different steps to set up a 1st-class environment when you want to write code for JBoss Tools
h1. Tools and technologies
h2. Java
JBoss Tools requires Java 6. Ensure your JRE and JDK are compatible with Java 6
h2. Eclipse PDE/RCP
JBoss Tools are a set of plugins for Eclipse. Then get your favourite recent version of Eclipse from here: http://eclipse.org/downloads/ http://eclipse.org/downloads/ We recommand you using +Eclipse for RCP and RAP Developers+. But you can also install PDE in any other installation of Eclipse:
https://community.jboss.org/servlet/JiveServlet/showImage/102-18124-5-185... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18124-5...
h2. SVN
You'll need to install a recent version of SVN (1.6 or more recent). Then you should install SVN Tools in Eclipse. You are free to choose your favourite Eclipse plugin and SVN connector by yourself, however, curret author of this page recommands using Subversive (part of the Eclipse latest release site) with SVNKit connector. Feel free to install Subversive extensions for other projects, it's always helpful.
h2. Tips for productivity and quality
Here are some highly recommanded plugins that will make your more efficient when inside the IDE
h3. Install Code Recommanders
Provides additional snippets, templates and smart completion. Not intrusive. You can find it on the "Juno" update-site or the current Eclipse release site.
h3. Static analysis
Static analysis will detect bug very early and will save you minutes of debug every day. Using it will make you and your colleagues happier. It tells you while typing code that you may have a bug. No need to wait for running test or CI reports to detect this.
h4. Enable all JDT warnings
JDT provides very good static analysis, and can prevent you from writing bugs. You simply have to turn all "ignored" advices to "warning" in Window > Preference > Java > Compiler > Errors/Warning.
https://community.jboss.org/servlet/JiveServlet/showImage/102-18124-5-185... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18124-5...
h4. Install Findbugs for Eclipse
http://marketplace.eclipse.org/content/findbugs-eclipse-plugin http://marketplace.eclipse.org/content/findbugs-eclipse-plugin
h4. Install PMD for Eclipse
http://marketplace.eclipse.org/content/pmd-eclipse http://marketplace.eclipse.org/content/pmd-eclipse
h3. Coverage
Coverage answers to the question "What is tested or net?".
JBoss Tools CI builds provide Jacoco reports for coverage by unit tests (file name is jacoco.exec). This file can easily be analyzed inside Eclipse on your Java editor using EclEmma plugin: http://marketplace.eclipse.org/content/eclemma-java-code-coverage http://marketplace.eclipse.org/content/eclemma-java-code-coverage
h1. Get source
Each JBoss Tools component is now its own GitHub repo: https://github.com/jbosstools/ https://github.com/jbosstools/
h2. To work on a specific component
The easiest way to get started is to check out source for only the module you wish to work on, and import Java projects from this part of the source tree.
Example:
* I want to fix a bug in CDI component of JBT: git clone git://github.com/jbosstools/jbosstools-server.git and import plugins and tests projects from plugns/* and tests/*
h1. Set up a target platform
Target platforms (TP) are aimed at specifying what are the dependencies allowed and used to write, compile and execute code. *Target Platform=Build Path + Default Runtime Classpath.* We provide several TP that have different purpose. We do set up some default TP for development, that you should use.
h2. Import target platforms
Import into your Eclipse workspace JBoss Tools target platforms from GitHub:
git clone git://github.com/jbosstools/jbosstools-build.git
You can then build a specific target platform like this:
cd jbosstools-build/target-platforms/jbosstools-JunoSR1a/; mvn clean install
h2. Choose and use a target platform
Then go into Window > Preference > Plug-in development > Target Platform. We recommend you to use *multiple.target* since it will contain all deps allowed from 3rd-party (Eclipse, Google...) *AND SOURCE BUNDLES*. If you don't depend on any other JBoss Tools project, please use *unified.target*.
https://community.jboss.org/servlet/JiveServlet/showImage/102-18124-5-185... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18124-5...
h1. Run JBoss Tools and Tests from your IDE
Once Target Platform is configured, you can easily give a try to your plugins using +Run As > Java Application.+ You can also run automated tests from your IDE using +Run As... > JUnit Plugin Tests+.
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-18124]
Create a new document in JBoss Tools Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
10 years, 9 months
[JBoss AS Development Deployment Framework] - problem in deploying seam application on jboss 7.1
by Gaurav Gupta
Gaurav Gupta [https://community.jboss.org/people/gg.svce] created the discussion
"problem in deploying seam application on jboss 7.1"
To view the discussion, visit: https://community.jboss.org/message/779764#779764
--------------------------------------------------------------
18:39:52,684 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service { http://soap.sforce.com/2005/09/outbound http://soap.sforce.com/2005/09/outbound}CoreWsImplService from class no.messageman.protectoria.core.salesforce.buyfromsalesman.outbound.CoreWsImpl
18:39:53,089 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/app/NotificationPort http://localhost:8080/app/NotificationPort
18:39:53,179 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-3) WSDL published to: file:/D:/MM%20Venus%20Project/JBOSS/jboss-as-7.1.1.Final/standalone/data/wsdl/protectoria.ear/app.jar/CoreWsImplService.wsdl
18:39:53,200 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015539: Starting service jboss.ws.port-component-link
18:39:53,266 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."protectoria.ear"."app.jar".CoreWsImpl
18:39:53,268 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015539: Starting service jboss.ws.endpoint."protectoria.ear"."app.jar".ThickClientSharedSecretEncryptedWS
18:39:53,283 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) register: jboss.ws:context=app,endpoint=CoreWsImpl
18:39:53,291 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-4) register: jboss.ws:context=app,endpoint=ThickClientSharedSecretEncryptedWS
18:39:53,508 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015951: Admin console listening on http://127.0.0.1:9990 http://127.0.0.1:9990
18:39:53,515 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 57864ms - Started 1491 of 1687 services (115 services failed or *missing dependencies, 80 services are passive or on-demand)*
*18:39:53,714 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "protectoria.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"protectoria.ear/app.jar#protectoria\"jboss.naming.context.java.jboss.datasources.MySqlDSMissing[jboss.persistenceunit.\"protectoria.ear/app.jar#protectoria\"jboss.naming.context.java.jboss.datasources.MySqlDS]","jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".notificationSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.notification.mailMissing[jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".notificationSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.notification.mail]","jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".outboundSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.outbound.mailMissing[jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".outboundSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.outbound.mail]"]}*
*18:39:53,824 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015540: Stopping service jboss.ws.endpoint."protectoria.ear"."app.jar".CoreWsImpl*
*18:39:53,824 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."protectoria.ear"."app.jar".ThickClientSharedSecretEncryptedWS*
*18:39:53,837 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) remove: jboss.ws:context=app,endpoint=CoreWsImpl*
*18:39:53,853 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=app,endpoint=ThickClientSharedSecretEncryptedWS*
*18:39:53,978 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015540: Stopping service jboss.ws.port-component-link*
*18:39:54,207 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment app.jar in 492ms*
*18:39:54,260 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment app.war in 545ms*
*18:39:54,372 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment protectoria.ear in 657ms*
*18:39:54,381 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report*
*JBAS014775: New missing/unsatisfied dependencies:*
* service jboss.naming.context.java.comp.protectoria."app.jar".SMTPHandler.env.protectoria.notification.mail (missing) dependents: [service jboss.naming.context.java.comp.protectoria."app.jar".SMTPHandler.env."no.messageman.protectoria.core.smtp.SMTPHandler".notificationSession]*
* service jboss.naming.context.java.comp.protectoria."app.jar".SMTPHandler.env.protectoria.outbound.mail (missing) dependents: [service jboss.naming.context.java.comp.protectoria."app.jar".SMTPHandler.env."no.messageman.protectoria.core.smtp.SMTPHandler".outboundSession]*
* service jboss.naming.context.java.jboss.datasources.MySqlDS (missing) dependents: [service jboss.persistenceunit."protectoria.ear/app.jar#protectoria"]*
*18:39:54,447 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"protectoria.ear/app.jar#protectoria\"jboss.naming.context.java.jboss.datasources.MySqlDSMissing[jboss.persistenceunit.\"protectoria.ear/app.jar#protectoria\"jboss.naming.context.java.jboss.datasources.MySqlDS]","jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".notificationSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.notification.mailMissing[jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".notificationSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.notification.mail]","jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".outboundSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.outbound.mailMissing[jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".outboundSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.outbound.mail]"]}}}*
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/779764#779764]
Start a new discussion in JBoss AS Development Deployment Framework at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 10 months
[jBPM Development] - JPAWorkingMemoryDbLogger issue on server restart
by Proteus Hades
Proteus Hades [https://community.jboss.org/people/proteus] created the discussion
"JPAWorkingMemoryDbLogger issue on server restart"
To view the discussion, visit: https://community.jboss.org/message/778787#778787
--------------------------------------------------------------
Hi,
I'm using jpbm5.2 in my project which involves few User Tasks. I have created different methods to start and load the knowledge session and also to start and complete the user task.
I'm using the JPAWorkingMemoryDbLogger to log the entering and exiting of the nodes in the log tables. The logger is initialized when ever the StatefulKnowledgeSession is created or loaded.
+ //load the knowledge session.+
+ ksession = Configuration.loadKSession(ksessionId,+
+ myJbpm.getMyEmfPersistence(),+
+ myJbpm.getMyKnowledgeBase());+
+
+
+ // Initialize logger to enter values in log table+
+JPAWorkingMemoryDbLogger myJpaLogger = new JPAWorkingMemoryDbLogger(++ksession);+
The knowledge session & process instance id created is stored in project's database, so that whenever a user log in I could get the process info and load it.
Now the problem is whenever the tomcat server restarts and the knowledge session is loaded and the process continued, entries are not made in the log tables, but Task table has proper entries.
When checked at the console for sql queries, whenever the tomcat restarts the 'insert into nodeinstancelog...' statements are missing.
My project's working depends on the data in nodeinstancelog table which I query to check where the process has reached. So although the process has moved forward the nodeinstancelog do not have entries. Thereby crashing the whole application.
This occurs only when the tomcat restarts- which occurs quite a few times where the project is intended to be deployed.
The logger is giving me a hard time... kindly help.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/778787#778787]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 10 months
