from:"Gert Vanthienen"

Add an example of  to the archetype's xbean.xml
-

 Key: SM-1025
 URL: https://issues.apache.org/activemq/browse/SM-1025
 Project: ServiceMix
  Issue Type: Improvement
  Components: tooling
Affects Versions: 3.1.1
Reporter: Gert Vanthienen
Priority: Minor


The xbean.xml file generated by the {{servicemix-eip-service-unit}} archetype 
doesn't contain an example for the new 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Default behavior on mvn jbi:projectDeploy

2007-08-08 Thread Gert Vanthienen


L.S.,


By default, this command doesn't seem to update anything that is already 
installed/deployed.  I would have expected that by default for a service 
assembly:
- it installs any dependencies (components and shared libraries) that 
aren't already installed, but doesn't update them

- it deploys the service assembly or updates it if necessary

You can specify -DforceUpdate=true, but this will also update the JBI 
components that were already installed (possibly causing other SA to be 
restarted in the process) while they probably haven't changed if you're 
using a released version of ServiceMix.



Gert

[jira] Resolved: (SM-1024) Archetype generates invalid brokerURL


 [ 
https://issues.apache.org/activemq/browse/SM-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-1024.
-

   Resolution: Fixed
Fix Version/s: 3.2
   3.1.2

The servicemix-jms-consumer-service-unit archetype had the same problem.  Fixed 
in both trunk and the 3.1.2-SNAPSHOT branch
http://svn.apache.org/viewvc?view=rev&revision=564082
http://svn.apache.org/viewvc?view=rev&revision=564083

> Archetype generates invalid brokerURL
> -
>
> Key: SM-1024
> URL: https://issues.apache.org/activemq/browse/SM-1024
> Project: ServiceMix
>  Issue Type: Bug
>  Components: tooling
>Affects Versions: 3.1.1
>Reporter: Gert Vanthienen
>Priority: Trivial
> Fix For: 3.1.2, 3.2
>
>
> The servicemix-jms-provider-service-unit generates an xbean.xml file that 
> contains
> {code:xml}
>  brokerURL="tcp://localhost:61616/" />
> {code}
> When you try to deploy this, you get an exception on the trailing /

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SM-1024) Archetype generates invalid brokerURL

Archetype generates invalid brokerURL
-

 Key: SM-1024
 URL: https://issues.apache.org/activemq/browse/SM-1024
 Project: ServiceMix
  Issue Type: Bug
  Components: tooling
Affects Versions: 3.1.1
Reporter: Gert Vanthienen
Priority: Trivial


The servicemix-jms-provider-service-unit generates an xbean.xml file that 
contains
{code:xml}

{code}

When you try to deploy this, you get an exception on the trailing /

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Getting started: Using the Maven tooling

2007-08-08 Thread Gert Vanthienen


L.S.,

I added a second tutorial to the wiki Sandbox 
(http://cwiki.apache.org/confluence/x/Q94), explaining to a newbie user 
how to leverage the Maven archetypes and tooling for building their own 
service assemblies.  Any comments, corrections, feedback, ... are welcome.


Gert

Re: [jira] Commented: (SM-990) FilePoller with Archiving

2007-08-08 Thread Gert Vanthienen




Guillaume Nodet wrote:

You mean a file based implementation of servicemix-audit ?
See 
http://incubator.apache.org/servicemix/dist/servicemix-3.1-incubating/site/core/servicemix-audit/apidocs/org/apache/servicemix/jbi/audit/AuditorMBean.html
  
Yes, my first comment was exactly that: using an auditor for archiving 
the files.  This isn't the best solution for this particular issue, but 
it still might be a worthwhile addition to ServiceMix.  We still need to 
find a good way to avoid having to load entire messages into memory 
however.  Anybody has any good suggestions for solving that?

I think we should only backport bug fixes, do you ?
But I'm open to discuss that, especially given the long release cycle
we have (we really need to do something about that, btw).
  
That's exactly why I was asking.  I think these branches are great for 
doing bug fixes on an existing release, but I agree we should try to 
avoid it for new features.  What is holding us back to shorten the 
release cycle (or even time-boxing it)?  I'm trying to build a tool to 
regenerate the legal files, so we can already avoid the pain of checking 
those 'manually' every time.  Is there anything else?

[jira] Resolved: (SM-990) FilePoller with Archiving


 [ 
https://issues.apache.org/activemq/browse/SM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-990.


   Resolution: Fixed
Fix Version/s: 3.2

Added {{archive}} attribute to specify the archive directory
http://svn.apache.org/viewvc?view=rev&revision=564081

> FilePoller with Archiving
> -
>
> Key: SM-990
> URL: https://issues.apache.org/activemq/browse/SM-990
> Project: ServiceMix
>  Issue Type: Improvement
>  Components: servicemix-components, servicemix-file
>Affects Versions: 3.1
>Reporter: Juergen Mayrbaeurl
>Priority: Minor
> Fix For: 3.2
>
>
> The various FilePoller implementations should archive the files before 
> deleting them (e.g. by copying them to another directory)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: moving camel-jbi module from Camel to the servicemix-camel module...

2007-08-08 Thread Gert Vanthienen


Sounds like a good idea to me as well.
+1

James Strachan wrote:

In the Camel project we've an EIP implementation which can route any
JBI components (as well as other things)...
http://activemq.apache.org/camel/jbi.html

the current list of EIP patterns implemented is here...
http://activemq.apache.org/camel/enterprise-integration-patterns.html

you can use Java code or XML (spring XML) to implement the routing...
http://activemq.apache.org/camel/spring.html

The current camel-jbi depends on trunk of ServiceMix (as it plugs into
all the nice features in ServiceMix, like dynamic endpoint resolution,
URI syntax and so forth). Given this dependency on the internals of
ServiceMix (and it only really uses the simple public APIs of Camel),
plus I'd like to hopefully unify serviceix-eip with Camel routing
capabilities - I'm gonna move the following modules from Camel into
ServiceMix...

camel/components/camel-jbi
  -> servicemix/deployables/serviceengines/servicemix-camel

camel/tooling/archetypes/camel-jbi-service-unit
  -> servicemix/archetypes/servicemix-camel-service-unit

As usual, any feedback most welcome. We can always move it back if
folks think of a good reason later on (for once, I'm glad all of
apache is a single svn repo ;-).

[jira] Resolved: (SM-1020) Invalid query.xq generated by servicemix-saxon-xquery-service-unit archetype


 [ 
https://issues.apache.org/activemq/browse/SM-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-1020.
-

   Resolution: Fixed
Fix Version/s: 3.2
   3.1.2

Changed the comment syntax in the archetype
http://svn.apache.org/viewvc?view=rev&revision=563873
http://svn.apache.org/viewvc?view=rev&revision=563877


> Invalid query.xq generated by servicemix-saxon-xquery-service-unit archetype
> 
>
> Key: SM-1020
> URL: https://issues.apache.org/activemq/browse/SM-1020
> Project: ServiceMix
>  Issue Type: Bug
>  Components: tooling
>Affects Versions: 3.1.1
>Reporter: Erik Allais
>Assignee: Gert Vanthienen
>Priority: Trivial
> Fix For: 3.1.2, 3.2
>
>
> hi,
> i compile the saxon component and deploy on servicemix-3.1.1
> here the following xbean.xml
> http://servicemix.apache.org/saxon/1.0";
>xmlns:example="http://example.com/exampleService";>
>   
>resource="classpath:query.xq" />
>   
>   
>   
> 
> 
>   for $x in /bookstore/book
>   where $x/price > 30
>   return $x/title
> 
> 
>key="{http://saxon.sf.net/}wrap-result-sequence";>yes
> 
>   
>   
>  
>   
>   
> 
>   
> 
>   
> 
>   
>   
> 
> i dont touch the query.xq (the problem seems to come from this file)
> My error is :
> Error on line 18 column 8
>   XPST0003: XQuery syntax error in #...er the License. -->  {#:
> Unexpected token ">" beyond end of query
> [Fatal Error] :14:47: The element type "titles" must be terminated by the 
> matching end-tag "".
> WARN  - ServiceAssemblyLifeCycle   - Could not parse result exception
> org.xml.sax.SAXParseException: The element type "titles" must be terminated 
> by the matching end-tag "".
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.parse(ServiceAssemblyLifeCycle.java:421)
> at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.getComponentFailure(ServiceAssemblyLifeCycle.java:402)
> at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
> at 
> org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> INFO  - ServiceUnitLifeCycle   - Starting service unit: mc-jsr181-su
> INFO  - ServiceUnitLifeCycle   - Starting service unit: mc-http-su
> INFO  - DeploymentService  - Error in start
> java.lang.Exception: 
> http://java.sun.com/xml/ns/jbi/management-message"; 
> version="1.0">
> 
> 
> 
> 
> start
> FAILED
> ERROR
> 
> 
> 
> 
> servicemix-saxon
> 
> 
> start
> FAILED
> ERROR
> 
> 
> 
> Unable to parse result string
> 
> 
> 
> 1
> 
>  xmlns="http://java.sun.com/xml/ns/jbi/management-message";>
> servicemix-saxon
> 
> 
> start
> FAILED
> ERROR
> 
> Unable to start 
> service unit
> 
> 1
> 
> 
> XQuery syntax error in 
> #...er the License. -->  {#:
> Unexpected token ">" beyond end of query
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>

[jira] Updated: (SM-1020) Invalid query.xq generated by servicemix-saxon-xquery-service-unit archetype


 [ 
https://issues.apache.org/activemq/browse/SM-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SM-1020:


Component/s: (was: servicemix-saxon)
 tooling
Summary: Invalid query.xq generated by 
servicemix-saxon-xquery-service-unit archetype  (was: Problem with the 
saxon-xquery component and the generic query.xq file)

> Invalid query.xq generated by servicemix-saxon-xquery-service-unit archetype
> 
>
> Key: SM-1020
> URL: https://issues.apache.org/activemq/browse/SM-1020
> Project: ServiceMix
>  Issue Type: Bug
>  Components: tooling
>Affects Versions: 3.1.1
>Reporter: Erik Allais
>Assignee: Gert Vanthienen
>Priority: Trivial
>
> hi,
> i compile the saxon component and deploy on servicemix-3.1.1
> here the following xbean.xml
> http://servicemix.apache.org/saxon/1.0";
>xmlns:example="http://example.com/exampleService";>
>   
>resource="classpath:query.xq" />
>   
>   
>   
> 
> 
>   for $x in /bookstore/book
>   where $x/price > 30
>   return $x/title
> 
> 
>key="{http://saxon.sf.net/}wrap-result-sequence";>yes
> 
>   
>   
>  
>   
>   
> 
>   
> 
>   
> 
>   
>   
> 
> i dont touch the query.xq (the problem seems to come from this file)
> My error is :
> Error on line 18 column 8
>   XPST0003: XQuery syntax error in #...er the License. -->  {#:
> Unexpected token ">" beyond end of query
> [Fatal Error] :14:47: The element type "titles" must be terminated by the 
> matching end-tag "".
> WARN  - ServiceAssemblyLifeCycle   - Could not parse result exception
> org.xml.sax.SAXParseException: The element type "titles" must be terminated 
> by the matching end-tag "".
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.parse(ServiceAssemblyLifeCycle.java:421)
> at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.getComponentFailure(ServiceAssemblyLifeCycle.java:402)
> at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
> at 
> org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> INFO  - ServiceUnitLifeCycle   - Starting service unit: mc-jsr181-su
> INFO  - ServiceUnitLifeCycle   - Starting service unit: mc-http-su
> INFO  - DeploymentService  - Error in start
> java.lang.Exception: 
> http://java.sun.com/xml/ns/jbi/management-message"; 
> version="1.0">
> 
> 
> 
> 
> start
> FAILED
> ERROR
> 
> 
> 
> 
> servicemix-saxon
> 
> 
> start
> FAILED
> ERROR
> 
> 
> 
> Unable to parse result string
> 
> 
> 
> 1
> 
>  xmlns="http://java.sun.com/xml/ns/jbi/management-message";>
> servicemix-saxon
> 
> 
> start
> FAILED
> ERROR
> 
> Unable to start 
> service unit
> 
> 1
> 
> 
> XQuery syntax error in 
> #...er the License. -->  {#:
> Unexpected token ">" beyond end of query
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>

[jira] Reopened: (SM-1020) Problem with the saxon-xquery component and the generic query.xq file


 [ 
https://issues.apache.org/activemq/browse/SM-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen reopened SM-1020:
-

  Assignee: Gert Vanthienen

The query.xq Erik refers to is generated by our own 
servicemix-saxon-xquery-service-unit archetype. It would be better to fix the 
archetype to provide the users with a correct query.xq sample file.

> Problem with the saxon-xquery component and the generic query.xq file
> -
>
> Key: SM-1020
> URL: https://issues.apache.org/activemq/browse/SM-1020
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-saxon
>Affects Versions: 3.1.1
>Reporter: Erik Allais
>Assignee: Gert Vanthienen
>Priority: Trivial
>
> hi,
> i compile the saxon component and deploy on servicemix-3.1.1
> here the following xbean.xml
> http://servicemix.apache.org/saxon/1.0";
>xmlns:example="http://example.com/exampleService";>
>   
>resource="classpath:query.xq" />
>   
>   
>   
> 
> 
>   for $x in /bookstore/book
>   where $x/price > 30
>   return $x/title
> 
> 
>key="{http://saxon.sf.net/}wrap-result-sequence";>yes
> 
>   
>   
>  
>   
>   
> 
>   
> 
>   
> 
>   
>   
> 
> i dont touch the query.xq (the problem seems to come from this file)
> My error is :
> Error on line 18 column 8
>   XPST0003: XQuery syntax error in #...er the License. -->  {#:
> Unexpected token ">" beyond end of query
> [Fatal Error] :14:47: The element type "titles" must be terminated by the 
> matching end-tag "".
> WARN  - ServiceAssemblyLifeCycle   - Could not parse result exception
> org.xml.sax.SAXParseException: The element type "titles" must be terminated 
> by the matching end-tag "".
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.parse(ServiceAssemblyLifeCycle.java:421)
> at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.getComponentFailure(ServiceAssemblyLifeCycle.java:402)
> at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
> at 
> org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
> at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> INFO  - ServiceUnitLifeCycle   - Starting service unit: mc-jsr181-su
> INFO  - ServiceUnitLifeCycle   - Starting service unit: mc-http-su
> INFO  - DeploymentService  - Error in start
> java.lang.Exception: 
> http://java.sun.com/xml/ns/jbi/management-message"; 
> version="1.0">
> 
> 
> 
> 
> start
> FAILED
> ERROR
> 
> 
> 
> 
> servicemix-saxon
> 
> 
> start
> FAILED
> ERROR
> 
> 
> 
> Unable to parse result string
> 
> 
> 
> 1
> 
>  xmlns="http://java.sun.com/xml/ns/jbi/management-message";>
> servicemix-saxon
> 
> 
> start
> FAILED
> ERROR
> 
> Unable to start 
> service unit
> 
> 1
> 
> 
> XQuery syntax error in 
> #...er the License. -->  {#:
> Unexpected token ">" beyond end of query
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>

[jira] Commented: (SM-990) FilePoller with Archiving


[ 
https://issues.apache.org/activemq/browse/SM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39880
 ] 

Gert Vanthienen commented on SM-990:


I was thinking about some kind of WireTap (implemented as an Auditor to easily 
apply it to all message), but I suppose you're worrying about the fact that we 
need to ensure re-readability of the stream for this.  Would it be possible to 
'decorate' the NormalizedMessage somehow, so it  can intercept when bytes are 
read from the inputstream by the provider and do the archiving on-the-fly?

> FilePoller with Archiving
> -
>
> Key: SM-990
> URL: https://issues.apache.org/activemq/browse/SM-990
> Project: ServiceMix
>  Issue Type: Improvement
>  Components: servicemix-components, servicemix-file
>Affects Versions: 3.1
>Reporter: Juergen Mayrbaeurl
>Priority: Minor
>
> The various FilePoller implementations should archive the files before 
> deleting them (e.g. by copying them to another directory)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: ActiveMQ Causing OutOfMemoryError After Service Deployment

2007-07-26 Thread Gert Vanthienen

L.S.,

Gert

ArmenH wrote:

FYI.

We did try replacing the ServiceMix ActiveMQ JAR files with the latest
ActiveMQ SNAPSHOT JAR files and the problem was resolved.

We would be very anxious to get the ServiceMix 3.1.2 release with all the
latest bug fixes as soon as it becomes available. This directly affects our
trading application.

Armen H.

Gert Vanthienen wrote:

Armen H.,

In the meantime, could you try replacing the JAR files for ActiveMQ in
your installation with a recent build of ActiveMQ to see if it really
resolves the problems you're experiencing?

Gert

ArmenH wrote:

Hi Gert,

We're using HTTP BC and JSR 181 SEs. We have custom business logic (very
simple) that uses POJOs generated from the JAXB version of the JDK
1.6.0_01.

We are also dependent on JDK 1.6 JAX-WS to generate our service interface
(WSDL).

We will check the number of service endpoints and let you know.

By the way, I have another thread on the ActiveMQ forums and other folks
have experienced very similar issues with ActiveMQ as that causes the
heap
overflow.

The fix for this issue was put on July 24 but it's unclear which version
it
will end up in and also more importantly when would ServiceMix pick up
the
latest 4.1.x SNAPSHOT from ActiveMQ.

Armen H.

Gert Vanthienen wrote:

Armen H.,

What JBI Components (JMS, HTTP, JSR-181, ...) are you using? From your
description, I assume you at least have a few custom built components as
well...

Can you try to use jconsole
(http://incubator.apache.org/servicemix/15-tutorial-using-jmx-to-look-inside-the-esb.html)
to look at the number of service endpoint that are actually registered?
Also, can you take a look at the number of threads that are in use?

What version of Java are you using?

Gert

ArmenH wrote:

Gert,

We use the Windows version for development phase of our services.

We are deploying services by dropping the files in the deploy and
install
directories. We don't use JMX for the development phase.

We're using ServiceMix version 3.1 in stand-alone mode. We deploy SAs
as
well.

Regards,
Armen H.

Gert Vanthienen wrote:

L.S.,

One of my customers is running ServiceMix on Windows as well, but even
with a dozen SA deployed, the memory usage doesn't raise to the
amounts
you mention here, although there are using several types of services
(HTTP, JMS, FTP, File, Saxon, EIP, bean, lwcontainer).

What version of ServiceMix and/or Java are you using? Are you using
ServiceMix in stand-alone or web application 'mode'? What is the type
of
service you are trying to deploy? Can you try to check the number of
threads that are running with a JMX console?

Regards,

Gert

ArmenH wrote:

We have found out that after just one service deployed on Windows
ServiceMix the memory usage jumps to 500 MB and it increases linearly
after each service deployment until ServiceMix dies with an
OutOfMemoryError.

We tried increasing the heap size and it helped up to a certain
number
of
services deployed in the container, after that the Error happened as
expected.

We used jhatfor heap analysis and found out that the following
instance
usage (after just one service deployment):

1673478 instances of class
org.apache.activemq.filter.DestinationMapNode
3001 instances of class
edu.emory.mathcs.backport.java.util.concurrent.locks.ReentrantLock$NonfairSync

This is a critical issue for us. Please advise.

Regards.
Armen H.

Re: Two steps build

2007-07-25 Thread Gert Vanthienen


Guillaume,

What is causing the two step build in the first place?  Shouldn't Maven 
take care of building everything in the right order automatically, based 
on the interdependencies of the subprojects?



Gert

Guillaume Nodet wrote:

I was wondering if someone knows a way to spawn a maven build from
within maven. Maybe this would be a way to remove the two steps build
needed the first time (and when releasing too).

Re: ActiveMQ Causing OutOfMemoryError After Service Deployment

2007-07-25 Thread Gert Vanthienen

Armen H.,

In the meantime, could you try replacing the JAR files for ActiveMQ in
your installation with a recent build of ActiveMQ to see if it really
resolves the problems you're experiencing?

Gert

ArmenH wrote:

Hi Gert,

We're using HTTP BC and JSR 181 SEs. We have custom business logic (very
simple) that uses POJOs generated from the JAXB version of the JDK 1.6.0_01.

We are also dependent on JDK 1.6 JAX-WS to generate our service interface
(WSDL).

We will check the number of service endpoints and let you know.

By the way, I have another thread on the ActiveMQ forums and other folks
have experienced very similar issues with ActiveMQ as that causes the heap
overflow.

The fix for this issue was put on July 24 but it's unclear which version it
will end up in and also more importantly when would ServiceMix pick up the
latest 4.1.x SNAPSHOT from ActiveMQ.

Armen H.

Gert Vanthienen wrote:

Armen H.,

What JBI Components (JMS, HTTP, JSR-181, ...) are you using? From your
description, I assume you at least have a few custom built components as
well...

Can you try to use jconsole
(http://incubator.apache.org/servicemix/15-tutorial-using-jmx-to-look-inside-the-esb.html)
to look at the number of service endpoint that are actually registered?
Also, can you take a look at the number of threads that are in use?

What version of Java are you using?

Gert

ArmenH wrote:

Gert,

We use the Windows version for development phase of our services.

We are deploying services by dropping the files in the deploy and install
directories. We don't use JMX for the development phase.

We're using ServiceMix version 3.1 in stand-alone mode. We deploy SAs as
well.

Regards,
Armen H.

Gert Vanthienen wrote:

L.S.,

One of my customers is running ServiceMix on Windows as well, but even
with a dozen SA deployed, the memory usage doesn't raise to the amounts
you mention here, although there are using several types of services
(HTTP, JMS, FTP, File, Saxon, EIP, bean, lwcontainer).

What version of ServiceMix and/or Java are you using? Are you using
ServiceMix in stand-alone or web application 'mode'? What is the type
of
service you are trying to deploy? Can you try to check the number of
threads that are running with a JMX console?

Regards,

Gert

ArmenH wrote:

We have found out that after just one service deployed on Windows
ServiceMix the memory usage jumps to 500 MB and it increases linearly
after each service deployment until ServiceMix dies with an
OutOfMemoryError.

We tried increasing the heap size and it helped up to a certain number
of
services deployed in the container, after that the Error happened as
expected.

We used jhatfor heap analysis and found out that the following instance
usage (after just one service deployment):

1673478 instances of class
org.apache.activemq.filter.DestinationMapNode
3001 instances of class
edu.emory.mathcs.backport.java.util.concurrent.locks.ReentrantLock$NonfairSync

This is a critical issue for us. Please advise.

Regards.
Armen H.

Re: ActiveMQ Causing OutOfMemoryError After Service Deployment

2007-07-24 Thread Gert Vanthienen

Armen H.,

What JBI Components (JMS, HTTP, JSR-181, ...) are you using? From your
description, I assume you at least have a few custom built components as
well...

Can you try to use jconsole
(http://incubator.apache.org/servicemix/15-tutorial-using-jmx-to-look-inside-the-esb.html)
to look at the number of service endpoint that are actually registered?
Also, can you take a look at the number of threads that are in use?

What version of Java are you using?

Gert

ArmenH wrote:

Gert,

We use the Windows version for development phase of our services.

We are deploying services by dropping the files in the deploy and install
directories. We don't use JMX for the development phase.

We're using ServiceMix version 3.1 in stand-alone mode. We deploy SAs as
well.

Regards,
Armen H.

Gert Vanthienen wrote:

L.S.,

One of my customers is running ServiceMix on Windows as well, but even
with a dozen SA deployed, the memory usage doesn't raise to the amounts
you mention here, although there are using several types of services
(HTTP, JMS, FTP, File, Saxon, EIP, bean, lwcontainer).

What version of ServiceMix and/or Java are you using? Are you using
ServiceMix in stand-alone or web application 'mode'? What is the type of
service you are trying to deploy? Can you try to check the number of
threads that are running with a JMX console?

Regards,

Gert

ArmenH wrote:

We have found out that after just one service deployed on Windows
ServiceMix the memory usage jumps to 500 MB and it increases linearly
after each service deployment until ServiceMix dies with an
OutOfMemoryError.

We tried increasing the heap size and it helped up to a certain number of
services deployed in the container, after that the Error happened as
expected.

We used jhatfor heap analysis and found out that the following instance
usage (after just one service deployment):

1673478 instances of class org.apache.activemq.filter.DestinationMapNode
3001 instances of class
edu.emory.mathcs.backport.java.util.concurrent.locks.ReentrantLock$NonfairSync

This is a critical issue for us. Please advise.

Regards.
Armen H.

[jira] Resolved: (SM-932) Enable PMD/CheckStyle for binding components

2007-07-20 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-932.


   Resolution: Fixed
Fix Version/s: 3.2

Updated the binding components' parent pom.xml
http://svn.apache.org/viewvc?view=rev&revision=557983

> Enable PMD/CheckStyle for binding components
> 
>
> Key: SM-932
> URL: https://issues.apache.org/activemq/browse/SM-932
> Project: ServiceMix
>  Issue Type: Task
>  Components: servicemix-file, servicemix-ftp, servicemix-http, 
> servicemix-jms, servicemix-truezip
>Reporter: Gert Vanthienen
>Priority: Minor
> Fix For: 3.2
>
> Attachments: SM-932-file.patch, SM-932-ftp.patch, 
> SM-932-http-part2.patch, SM-932-http.patch, SM-932-jms.patch, 
> SM-932-truezip.patch, SM-932-xmpp.patch
>
>
> PMD/CheckStyle should be enabled for binding components

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SM-932) Enable PMD/CheckStyle for binding components

2007-07-20 Thread Gert Vanthienen (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39721
 ] 

Gert Vanthienen commented on SM-932:


Fixed for servicemix-ftp
http://svn.apache.org/viewvc?view=rev&revision=557640

Fixed for servicemix-http
http://svn.apache.org/viewvc?view=rev&revision=557757

Fixed for servicemix-jms
http://svn.apache.org/viewvc?view=rev&revision=557769

Fixed for servicemix-truezip
http://svn.apache.org/viewvc?view=rev&revision=557978

Fixed for servicemix-xmpp
http://svn.apache.org/viewvc?view=rev&revision=557981

> Enable PMD/CheckStyle for binding components
> 
>
> Key: SM-932
> URL: https://issues.apache.org/activemq/browse/SM-932
> Project: ServiceMix
>  Issue Type: Task
>  Components: servicemix-file, servicemix-ftp, servicemix-http, 
> servicemix-jms, servicemix-truezip
>Reporter: Gert Vanthienen
>Priority: Minor
> Attachments: SM-932-file.patch, SM-932-ftp.patch, 
> SM-932-http-part2.patch, SM-932-http.patch, SM-932-jms.patch, 
> SM-932-truezip.patch, SM-932-xmpp.patch
>
>
> PMD/CheckStyle should be enabled for binding components

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SM-932) Enable PMD/CheckStyle for binding components

2007-07-19 Thread Gert Vanthienen (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39702
 ] 

Gert Vanthienen commented on SM-932:


Fixed for servicemix-file:
http://svn.apache.org/viewvc?view=rev&revision=557551

> Enable PMD/CheckStyle for binding components
> 
>
> Key: SM-932
> URL: https://issues.apache.org/activemq/browse/SM-932
> Project: ServiceMix
>  Issue Type: Task
>  Components: servicemix-file, servicemix-ftp, servicemix-http, 
> servicemix-jms, servicemix-truezip
>    Reporter: Gert Vanthienen
>Priority: Minor
> Attachments: SM-932-file.patch, SM-932-ftp.patch, 
> SM-932-http-part2.patch, SM-932-http.patch, SM-932-jms.patch, 
> SM-932-truezip.patch, SM-932-xmpp.patch
>
>
> PMD/CheckStyle should be enabled for binding components

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-1006) 0 byte files written when message contains invalid content

2007-07-17 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-1006.
-

   Resolution: Fixed
Fix Version/s: 3.2
   3.1.2

http://svn.apache.org/viewvc?view=rev&revision=557173
http://svn.apache.org/viewvc?view=rev&revision=557174

> 0 byte files written when message contains invalid content
> --
>
> Key: SM-1006
> URL: https://issues.apache.org/activemq/browse/SM-1006
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-file
>Affects Versions: 3.1.1
>Reporter: Gert Vanthienen
> Fix For: 3.1.2, 3.2
>
>
> When a message contains invalid content (e.g. incomplete XML message), a 0 
> byte file is created by the .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SM-1006) 0 byte files written when message contains invalid content

2007-07-17 Thread Gert Vanthienen (JIRA)

0 byte files written when message contains invalid content
--

 Key: SM-1006
 URL: https://issues.apache.org/activemq/browse/SM-1006
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-file
Affects Versions: 3.1.1
Reporter: Gert Vanthienen


When a message contains invalid content (e.g. incomplete XML message), a 0 byte 
file is created by the .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SM-997) Basic example fails to build: InvalidProjectModelException

2007-07-17 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SM-997:
---

Priority: Critical  (was: Major)

> Basic example fails to build: InvalidProjectModelException
> --
>
> Key: SM-997
> URL: https://issues.apache.org/activemq/browse/SM-997
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-assembly
>Affects Versions: 3.1.1
> Environment: Servicemix 3.1.1-incubating, Windows XP, Java 1.5.0_12, 
> Maven 2.0.6
>Reporter: Evan Deaubl
>Priority: Critical
>
> When I attempt to run either mvn install, or mvn jbi:embeddedServicemix on 
> the project in examples/basic, I receive the following error.  I have 
> completely removed my Maven repository and had it redownload everything from 
> scratch, and still received this error.  I manually checked the file it had 
> downloaded, and the XML file was indeed invalid, and downloading the file 
> directly from the source 
> (http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom)
>  using Firefox yields an XML Parsing Error.
> [INFO] Scanning for projects...
> Downloading: 
> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/samples/3.1.1-incubating/samples-3.1.1-incubating.pom
> 2K downloaded
> Downloading: 
> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
> 69K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 
> '507906935d130cfa9b44696270f62e006367533d'; remote = 
> 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - RETRYING
> Downloading: 
> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
> 69K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 
> '507906935d130cfa9b44696270f62e006367533d'; remote = 
> 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - IGNORING
> [INFO] 
> 
> [ERROR] FATAL ERROR
> [INFO] 
> 
> [INFO] Error building POM (may not be this project's POM).
> Project ID: org.apache.servicemix:samples:pom:null
> Reason: Cannot find parent: org.apache.servicemix:servicemix for project: 
> org.apache.servicemix:samples:pom:null
> [INFO] 
> 
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent: 
> org.apache.servicemix:servicemix for project: 
> org.apache.servicemix:samples:pom:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
> parent: org.apache.servicemix:servicemix for project: 
> org.apache.servicemix:samples:pom:null
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1264)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1281)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:749)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBui

[jira] Resolved: (SM-937) Poller polls subdirectory even though recursive is set to false

2007-07-16 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-937.


   Resolution: Fixed
Fix Version/s: 3.2
   3.1.2

Thanks to Rabi Mishra for providing this patch!

http://svn.apache.org/viewvc?view=rev&revision=556821
http://svn.apache.org/viewvc?view=rev&revision=556822

> Poller polls subdirectory even  though recursive is set to false
> 
>
> Key: SM-937
> URL: https://issues.apache.org/activemq/browse/SM-937
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-ftp
>Affects Versions: 3.1
>Reporter: Markus Rado
>Priority: Minor
> Fix For: 3.1.2, 3.2
>
> Attachments: patch-ftppoller.txt
>
>
> Poller polls subdirectory even  though recursive is set to false because in 
> the first call to pollFileOrDirectory processDir is set to true. Either the 
> first call should use the value of property recursive or the processDir flag 
> should be checked before starting to process the files in the directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-1004) File poller deletes files, even if errors occur while processing

2007-07-16 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-1004.
-

   Resolution: Fixed
Fix Version/s: 3.2
   3.1.2

Thanks to Rabi Mishra for the initial patch and help in resolving this issue!

http://svn.apache.org/viewvc?view=rev&revision=556580
http://svn.apache.org/viewvc?view=rev&revision=556595

> File poller deletes files, even if errors occur while processing
> 
>
> Key: SM-1004
> URL: https://issues.apache.org/activemq/browse/SM-1004
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-file
>Affects Versions: 3.1.1
>Reporter: Gert Vanthienen
> Fix For: 3.1.2, 3.2
>
>
> Other poller components (e.g. FTP poller) leave the message where it is in 
> case of error/fault, so it can be retried afterwards (e.g. services 
> unavailable, XML message content not yet complete, ...).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Created: (SM-1004) File poller deletes files, even iferrorsoccur while processing

2007-07-16 Thread Gert Vanthienen


Rabi,


Shouldn't we add something like
if (exchange.getStatus() == ExchangeStatus.ERROR) {
Exception e = exchange.getError();
if (e == null) {
e = new JBIException("Unkown error");
}
throw e;
}
in the processFile() method as well, to make sure that an exception is 
thrown for every MessageExchange that ends in error?



Gert

[EMAIL PROTECTED] wrote:

Yes,

It is the lock handling... 


1. Every polling therad creates lock with the file uri and then
processes the file..
2. Lock is released once the file is processed and deleted. (Managed by
unlock flag)
3. If there is any exception in processing the file the lock is not
released.

I have just changed it in similar lines with FtpPoller.



Regards,
Rabi Mishra, 
http://rabisblog.blogspot.com/
c++; /* this makes c bigger but returns the old value */ 
-Original Message-----
From: Gert Vanthienen [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 16, 2007 2:05 PM

To: servicemix-dev@geronimo.apache.org
Subject: Re: [jira] Created: (SM-1004) File poller deletes files, even
iferrors occur while processing

Rabi,


Thank you for helping out with this!  A lot of this patch seems to be
formatting changes, but it already saves me the time/effort to figure
things out.  You mainly changed the lock handling, right?

Can you explain what you have changed?  Just curious to know how things
work...


Gert

[EMAIL PROTECTED] wrote:

Gret,

Are you working on this patch? I had fixed it sometime back and
attaching the patch..

-Original Message-----
From: Gert Vanthienen (JIRA) [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 16, 2007 1:17 PM

To: servicemix-dev@geronimo.apache.org
Subject: [jira] Created: (SM-1004) File poller deletes files, even if
errors occur while processing

File poller deletes files, even if errors occur while processing


 Key: SM-1004
 URL:

https://issues.apache.org/activemq/browse/SM-1004

 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-file
Affects Versions: 3.1.1
    Reporter: Gert Vanthienen


Other poller components (e.g. FTP poller) leave the message where it

is

in case of error/fault, so it can be retried afterwards (e.g. services
unavailable, XML message content not yet complete, ...).

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.




The information contained in this electronic message and any

attachments to this message are intended for the exclusive use of the
addressee(s) and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient

should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email.
 
www.wipro.com







Index:

E:/Rabi/work/workspace/servicemix/deployables/bindingcomponents/servicem
ix-file/src/main/java/org/apache/servicemix/file/FilePollerEndpoint.java

===
---

E:/Rabi/work/workspace/servicemix/deployables/bindingcomponents/servicem
ix-file/src/main/java/org/apache/servicemix/file/FilePollerEndpoint.java
(revision 555678)

+++

E:/Rabi/work/workspace/servicemix/deployables/bindingcomponents/servicem
ix-file/src/main/java/org/apache/servicemix/file/FilePollerEndpoint.java
(working copy)

@@ -41,217 +41,229 @@
 import java.util.concurrent.locks.Lock;
 
 /**

- * A polling endpoint which looks for a file or files in a directory
- * and sends the files into the JBI bus as messages, deleting the

files

- * by default when they are processed.
- *
+ * A polling endpoint which looks for a file or files in a directory

and sends

+ * the files into the JBI bus as messages, deleting the files by

default when

+ * they are processed.
+ * 
  * @org.apache.xbean.XBean element="poller"

- *
+ * 
  * @version $Revision$

  */
-public class FilePollerEndpoint extends PollingEndpoint implements

FileEndpointType {

+public class FilePollerEndpoint extends PollingEndpoint implements
+   FileEndpointType {
 
-private File file;

-private FileFilter filter;
-private boolean deleteFile = true;
-private boolean recursive = true;
-private boolean autoCreateDirectory = true;
-private FileMarshaler marshaler = new DefaultFileMarshaler();
-private LockManager lockManager;
+   private File file;
 
-public FilePollerEndpoint() {

-}
+   private FileFil

Re: [jira] Created: (SM-1004) File poller deletes files, even iferrors occur while processing

2007-07-16 Thread Gert Vanthienen


Rabi,


Thank you for helping out with this!  A lot of this patch seems to be 
formatting changes, but it already saves me the time/effort to figure 
things out.  You mainly changed the lock handling, right?


Can you explain what you have changed?  Just curious to know how things 
work...



Gert

[EMAIL PROTECTED] wrote:

Gret,

Are you working on this patch? I had fixed it sometime back and
attaching the patch..

-Original Message-
From: Gert Vanthienen (JIRA) [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 16, 2007 1:17 PM

To: servicemix-dev@geronimo.apache.org
Subject: [jira] Created: (SM-1004) File poller deletes files, even if
errors occur while processing

File poller deletes files, even if errors occur while processing


 Key: SM-1004
 URL: https://issues.apache.org/activemq/browse/SM-1004
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-file
Affects Versions: 3.1.1
Reporter: Gert Vanthienen


Other poller components (e.g. FTP poller) leave the message where it is
in case of error/fault, so it can be retried afterwards (e.g. services
unavailable, XML message content not yet complete, ...).

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.




The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 


WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.
 
www.wipro.com





Index: 
E:/Rabi/work/workspace/servicemix/deployables/bindingcomponents/servicemix-file/src/main/java/org/apache/servicemix/file/FilePollerEndpoint.java
===
--- 
E:/Rabi/work/workspace/servicemix/deployables/bindingcomponents/servicemix-file/src/main/java/org/apache/servicemix/file/FilePollerEndpoint.java
(revision 555678)
+++ 
E:/Rabi/work/workspace/servicemix/deployables/bindingcomponents/servicemix-file/src/main/java/org/apache/servicemix/file/FilePollerEndpoint.java
(working copy)
@@ -41,217 +41,229 @@
 import java.util.concurrent.locks.Lock;
 
 /**

- * A polling endpoint which looks for a file or files in a directory
- * and sends the files into the JBI bus as messages, deleting the files
- * by default when they are processed.
- *
+ * A polling endpoint which looks for a file or files in a directory and sends
+ * the files into the JBI bus as messages, deleting the files by default when
+ * they are processed.
+ * 
  * @org.apache.xbean.XBean element="poller"

- *
+ * 
  * @version $Revision$

  */
-public class FilePollerEndpoint extends PollingEndpoint implements 
FileEndpointType {
+public class FilePollerEndpoint extends PollingEndpoint implements
+   FileEndpointType {
 
-private File file;

-private FileFilter filter;
-private boolean deleteFile = true;
-private boolean recursive = true;
-private boolean autoCreateDirectory = true;
-private FileMarshaler marshaler = new DefaultFileMarshaler();
-private LockManager lockManager;
+   private File file;
 
-public FilePollerEndpoint() {

-}
+   private FileFilter filter;
 
-public FilePollerEndpoint(ServiceUnit serviceUnit, QName service, String endpoint) {

-super(serviceUnit, service, endpoint);
-}
+   private boolean deleteFile = true;
 
-public FilePollerEndpoint(DefaultComponent component, ServiceEndpoint endpoint) {

-super(component, endpoint);
-}
+   private boolean recursive = true;
 
-public void poll() throws Exception {

-pollFileOrDirectory(file);
-}
+   private boolean autoCreateDirectory = true;
 
-public void validate() throws DeploymentException {

-super.validate();
-if (file == null) {
-throw new DeploymentException("You must specify a file property");
-}
-if (isAutoCreateDirectory() && !file.exists()) {
-file.mkdirs();
-}
-if (lockManager == null) {
-lockManager = createLockManager();
-}
-}
-
-protected LockManager createLockManager() {

-return new SimpleLockManager();
-}
+   private FileMarshaler marshaler = new DefaultFileMarshaler();
 
+	private LockManager lockM

[jira] Created: (SM-1004) File poller deletes files, even if errors occur while processing

2007-07-16 Thread Gert Vanthienen (JIRA)

File poller deletes files, even if errors occur while processing


 Key: SM-1004
 URL: https://issues.apache.org/activemq/browse/SM-1004
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-file
Affects Versions: 3.1.1
Reporter: Gert Vanthienen


Other poller components (e.g. FTP poller) leave the message where it is in case 
of error/fault, so it can be retried afterwards (e.g. services unavailable, XML 
message content not yet complete, ...).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SM-1000) ServiceMix :: Maven2 JBI Plugin checkstyle issues

2007-07-12 Thread Gert Vanthienen (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39661
 ] 

Gert Vanthienen commented on SM-1000:
-

Rabi,

My checkout has a CheckStyle suppresion for this particular check in the 
GraphArtifactCollector class registered in 
{{build/src/main/resources/smx-checkstyle-suppressions.xml}}.  Can you check if 
you have that too?  Perhaps your build/ directory needs another update...

Gert

> ServiceMix :: Maven2 JBI Plugin checkstyle issues 
> --
>
> Key: SM-1000
> URL: https://issues.apache.org/activemq/browse/SM-1000
> Project: ServiceMix
>  Issue Type: Bug
>  Components: tooling
>Affects Versions: 3.2
> Environment: Windows
>Reporter: Rabi
>
> [INFO] Building ServiceMix :: Maven2 JBI Plugin
> [INFO]task-segment: [install]
> [INFO] 
> -
> ---
> [INFO] Ignoring available plugin update: 2.3 as it requires Maven version 
> 2.0.5
> [INFO] [checkstyle:checkstyle {execution: validate}]
> [INFO] Starting audit...
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:58:37: More than 
> 7 p
> arameters.
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:96:18: More than 
> 7 p
> arameters.
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37: method 
> def
>  modifier at indentation level 2 not at correct indentation, 4
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37:15: More 
> th
> an 7 parameters.
> Audit done.
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] An error has occurred in Checkstyle report generation.
> Embedded error: There are 4 checkstyle errors.
> [INFO] 
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO] 
> 
> [INFO] Total time: 28 seconds
> [INFO] Finished at: Wed Jul 11 16:34:15 IST 2007
> [INFO] Final Memory: 13M/24M
> [INFO] 
> 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SM-935) Allow to specify additional JNDI properties

2007-07-12 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SM-935:
---

Attachment: SM-935.patch

Phiroze,

The attached patch should enable you to specify jndiProperties="..." on the 
.  Can you help me try it out before I commit it?

Gert

> Allow to specify additional JNDI properties
> ---
>
> Key: SM-935
> URL: https://issues.apache.org/activemq/browse/SM-935
> Project: ServiceMix
>  Issue Type: New Feature
>  Components: servicemix-jms
>Affects Versions: 3.1
>Reporter: Gert Vanthienen
>Priority: Minor
> Attachments: SM-935.patch
>
>
> In addition to using initialContext and jndiProviderUrl to configure a JMS 
> endpoint, it should be possible to specify additional JNDI properties (e.g 
> {{java.naming.security.principal}}, {{java.naming.security.credentials}})

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SM-990) FilePoller with Archiving

2007-07-12 Thread Gert Vanthienen (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39651
 ] 

Gert Vanthienen commented on SM-990:


Perhaps we can create a more generic solution for this:  with SM-751 we have a 
correlation id that allows us to do flow tracing, so it should be possible to 
build an auditor that is triggered whenever a new message arrives (at any kind 
of endpoint: FTP, File, HTTP, ...) and sends a copy of the message to an 
archiving endpoint.

> FilePoller with Archiving
> -
>
> Key: SM-990
> URL: https://issues.apache.org/activemq/browse/SM-990
> Project: ServiceMix
>  Issue Type: Improvement
>  Components: servicemix-components, servicemix-file
>Affects Versions: 3.1
>Reporter: Juergen Mayrbaeurl
>Priority: Minor
>
> The various FilePoller implementations should archive the files before 
> deleting them (e.g. by copying them to another directory)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-996) ServiceMix doesn't start correctly due to javax.management.MalformedObjectNameException: Invalid ObjectName value type [javax.xml.namespace.QName]: only ObjectName and String

2007-07-11 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-996.


   Resolution: Fixed
Fix Version/s: 3.2

Piotr:
Apparently, we were working on the same thing.  I created setter methods for 
the two supported types (String and ObjectName) to trick Spring into skipping 
the conversion to QName.

Anyway, the problem is resolved now: 
http://svn.apache.org/viewvc?view=rev&revision=555219



> ServiceMix doesn't start correctly due to 
> javax.management.MalformedObjectNameException: Invalid ObjectName value type 
> [javax.xml.namespace.QName]: only ObjectName and String supported
> 
>
> Key: SM-996
> URL: https://issues.apache.org/activemq/browse/SM-996
> Project: ServiceMix
>  Issue Type: Bug
>Affects Versions: 3.2
> Environment: ServiceMix trunk rev. 553445
>Reporter: Piotr Bzdyl
>Priority: Blocker
> Fix For: 3.2
>
> Attachments: SM-996.patch.diff
>
>
> After I rebuild SMix from trunk with revision 553445 I got following error 
> upon startup:
> Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
> Caught: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 
> 'org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean' defined in class 
> path resource [jmx.xml]: Invocation of init method failed; nested exception 
> is javax.management.MalformedObjectNameException: Invalid ObjectName value 
> type [javax.xml.namespace.QName]: only ObjectName and String supported.
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean' defined 
> in class path resource [jmx.xml]: Invocation of init method failed; nested 
> exception is javax.management.MalformedObjectNameException: Invalid 
> ObjectName value type [
> javax.xml.namespace.QName]: only ObjectName and String supported.
> Caused by: javax.management.MalformedObjectNameException: Invalid ObjectName 
> value type [javax.xml.namespace.QName]: only ObjectName and String supported.
> at 
> org.springframework.jmx.support.ObjectNameManager.getInstance(ObjectNameManager.java:58)
> at 
> org.springframework.jmx.support.ConnectorServerFactoryBean.setObjectName(ConnectorServerFactoryBean.java:104)
> at 
> org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:186)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1201)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1171)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:284)
> at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
> at 
> org.apache.xbean.spring.context.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:161)
> at 
> org.apache.xbean.spring.context.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:51)
> at org.apache.servicemix.Main.main(Main.java:51)
> 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:585)
> at org.codehaus.classworlds.Launcher.launchStandard(Launcher.java:410)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:344)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:461)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Error formatting macro: snippet

2007-07-10 Thread Gert Vanthienen


Daniel,

Thank you for clarifying this.  Some of our pages have the entire url 
specified in the snippet macro, that's why it doesn't work.  Now we know 
how to solve it...


Gert

Daniel Kulp wrote:
I just checked the confluence snippet macro config and it looks ok.   It 
has a mapping of:


prefix: servicemix/ 
to url: http://svn.apache.org/repos/asf/incubator/servicemix/   


Thus, on your page, it should just be:

{snippet:id=expression|lang=xml|
url=servicemix/trunk/common/servicemix-components/src/test/resources/org/apache/servicemix/components/net/ftp.xml}


Dan

On Tuesday 10 July 2007 10:25, Gert Vanthienen wrote:
  

L.S.,


Some of our documentation pages use Confluence's snippet macro to
include code sample (e.g.
http://incubator.apache.org/servicemix/ftp.html).  Currently, this
macro doesn't seem to work any more:
Error formatting macro: snippet:
java.lang.IllegalArgumentException: Invalid url: must begin with a
configured prefix.

We're not alone, apparently the Struts team has the same problem (e.g.
http://struts.apache.org/2.0.5/docs/conversion-validator.html).  A
quick search on the web seems to indicate that this is some kind of
confguration problem with the snippet macro.  Who can administer the
Confluence instance that hosts our website to resolve this issue?


Gert

[jira] Closed: (SM-977) wsdl-first example fails: XFireFault (could not unmarshal type)

2007-06-29 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen closed SM-977.
--

   Resolution: Fixed
Fix Version/s: 3.2
   3.1.2

http://svn.apache.org/viewvc?view=rev&revision=552098
http://svn.apache.org/viewvc?view=rev&revision=552099


> wsdl-first example fails: XFireFault (could not unmarshal type)
> ---
>
> Key: SM-977
> URL: https://issues.apache.org/activemq/browse/SM-977
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-jsr181
>Affects Versions: 3.1.2
>Reporter: Gert Vanthienen
> Fix For: 3.1.2, 3.2
>
>
> After 'resolving' SM-960, the wsdl-first example no longer works.  It throws 
> this exception, caused by differences in namespace.  The original wsdl file 
> has it's GetPerson element in another namespace than the one that is being 
> shown when browsing for the wsdl after deployment.
> {noformat}
> org.codehaus.xfire.fault.XFireFault: Could not unmarshall type : unexpected 
> element (uri:"http://servicemix.apache.org/samples/wsdl-first";, 
> local:"GetPerson"). Expected elements are 
> <{http://servicemix.apache.org/samples/wsdl-first/types}GetPerson>,<{http://servicemix.apache.org/samples/wsdl-first/types}GetPersonResponse>,<{http://servicemix.apache.org/samples/wsdl-first/types}UnknownPersonFault>
>   at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:216)
>   at 
> org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
>   at 
> org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
>   at 
> org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
>   at 
> org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
>   at 
> org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
>   at 
> org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
>   at 
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
>   at 
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
>   at 
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>   at 
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
>   at 
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
>   at 
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
>   at 
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
>   at java.lang.Thread.run(Thread.java:619)
> {noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: servicemix-sca: updating tuscany dependency

2007-06-28 Thread Gert Vanthienen

L.S.,

Just trying to grasp what the problem/question is...

So, if I understand correctly, the servicemix-sca component will be 
somewhat different from any other JBI component.  We won't be building 
an SCA container as a service engine (like you would do for e.g. EJBs), 
but rather build some kind of support for deploying SCA artifacts 
directly on ServiceMix.  In order to do this, the 'metadata' that is 
available in the SCA artifact (sorry for not using the correct 
terminology, definitely need to read up on SCA) needs to be translated 
into JBI lingo, e.g. if an SCA component with implementation.bpel is 
being deployed, it needs to be translated into a service unit, targeted 
at the Ode JBI SE?

We are looking at the design some kind of SCADeploymentService, with 
translation plugins to enable translation from e.g. an SCA 
(implementation.bpel) -> ODE JBI SU... right?

Gert

Brian O'Neill wrote:

OK, per Guillaume's suggestion perhaps we start anew basing everything
on 0.90 sca.

So, what are peoples thoughts towards the design of the translation 
layer?

Should we leverage Tuscany's parsing capabilities to read in the SCA
contribution?
Then, from the parsed structure generate the service-unit JBI artifacts?
Each type of implementation(e.g. implementation.bpel) will generate
different artifacts.  So, this will need to be pluggable / extensible.

Perhaps we start with Jean-Sebastien's example, then implement the
translation layer first? (independent of both tuscany and servicemix)

What do people think?

-brian

On 6/27/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:

[snip]
Guillaume Nodet wrote:
> Jean-Sebastien said that the apis are quite stable now, so I guess
> the best way would be upgrade to the latest released version.
> Maybe Jean-Sebastien can provide more inforamtions here.
>
> Imo, the tuscany code has changed so much so that it may be
> better to try uinderstanding how the SE works and maybe start
> a new one (at least for the tuscany binding classes).
>
> As for the sources, I guess we should be able to find
> a svn revision that would match the date somehow:
> March the 17th 2006.
>

I'd recommend to use the Tuscany SCA 0.90 release and SDO 1.0 beta 1
levels... March 17th 2006 is more than a year ago :)

--
Jean-Sebastien

Re: [VOTE] Release ServiceMix 3.1.1 (2nd try)

2007-06-25 Thread Gert Vanthienen

Guillaume,

Looks fine to me! We should definitely be able to create something to
automate this kind of administrative tasks in the future...

Gert

Guillaume Nodet wrote:

I have fixed the LICENSE with the missing informations
and redeployed a release to the same staging area.
Hopefully we will find a better way to handle the license informations
(I've seen some generated informations using maven) for the next major
release and fix the generated license files somehow.

Could everyone quickly review the changes ?
I won't start a new vote as only the LICENSE file has
changed, but I can if someone objects.

robert burrell donkin wrote:

On 5/29/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

robert burrell donkin wrote:

On 5/28/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

Just a friendly reminder. We're missing anoter IPMC vote ...

issues
---

i think that apache-servicemix-3.1.1-incubating.tar.gz has some
libraries in lib that are missing their LICENSE/NOTICE entries (eg
howl, jencks)

There are licensed under ASL 2.0 and don't have any NOTICE file afaik.

cool

Should all the jars be listed in the LICENSE / NOTICE file ? My
assumption
was that only those who had some attributions somehow or with a
different license
need to be, but correct me if I'm wrong.

it is safe to release without listing them (and if this were the only
issue then i would probably have voted affirmatively)

but the aim should be to allow people to understand the licensing of
releases without need to ask questions or do research. if i don't
understand the licensing then i will ask. so, it's a good idea to note
the licenses for all jars since it avoids the need to answer questions
like this...

otherwise generally ok but i have a few questions

source in

http://people.apache.org/~gnodet/servicemix-3.1.1-incubating/org/apache/servicemix/samples/wsdl-first/wsdl-first-jsr181-su/3.1.1-incubating/

lacks headers. is this going to be released? if so, are these
generated?

are the jars under
http://people.apache.org/~gnodet/servicemix-3.1.1-incubating/ going to
be released?

servicemix-wsn2005-3.1.1-incubating-sources.jar contains lots of java
sources without headers (mostly under
org.apache.servicemix.wsn.jaxws). is this going to be released? if so,
are these generated?

Yeah, lots of these files are generated. Files generated are not in svn
so we usually check the headers on the svn tree rather than the source
jars generated by maven. These jars are not meant to be built for only
contain all the java sources for debugging purposes. If you want to
build these jars, you need to use the source distribution or use the svn
tag.

fine

i hope to be a bit more prompt with the review next time

- robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Components OdeBpelEngine are not installed yet:

2007-06-24 Thread Gert Vanthienen


Jbi Joe,


If you downloaded the JBI distribution of ODE, your download will 
contain a file named ode-jbi-1.0-incubating.zip.  This is actually a JBI 
SE, so you can deploy it as any other JBI component, e.g. by copying it 
to the install directory in the standalone ServiceMix.



Gert

jbi joe wrote:


Is there a howto to get it installed?  I pulled the apache ODE install
and loaded the jars to the servicemix/lib/optional dir, not luck still get
error message when I try to deploy the EXAMPLE loanbroker-bpel...

[jira] Commented: (SM-977) wsdl-first example fails: XFireFault (could not unmarshal type)


[ 
https://issues.apache.org/activemq/browse/SM-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39494
 ] 

Gert Vanthienen commented on SM-977:


Apparently, you can avoid this exception by omitting the 
*{{org.codehaus.xfire.jaxws.gen.JAXWSProfile}}* from the 
wsgen generator configuration in pom.xml

> wsdl-first example fails: XFireFault (could not unmarshal type)
> ---
>
> Key: SM-977
> URL: https://issues.apache.org/activemq/browse/SM-977
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-jsr181
>Affects Versions: 3.1.2
>    Reporter: Gert Vanthienen
>
> After 'resolving' SM-960, the wsdl-first example no longer works.  It throws 
> this exception, caused by differences in namespace.  The original wsdl file 
> has it's GetPerson element in another namespace than the one that is being 
> shown when browsing for the wsdl after deployment.
> {noformat}
> org.codehaus.xfire.fault.XFireFault: Could not unmarshall type : unexpected 
> element (uri:"http://servicemix.apache.org/samples/wsdl-first";, 
> local:"GetPerson"). Expected elements are 
> <{http://servicemix.apache.org/samples/wsdl-first/types}GetPerson>,<{http://servicemix.apache.org/samples/wsdl-first/types}GetPersonResponse>,<{http://servicemix.apache.org/samples/wsdl-first/types}UnknownPersonFault>
>   at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:216)
>   at 
> org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
>   at 
> org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
>   at 
> org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
>   at 
> org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
>   at 
> org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
>   at 
> org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
>   at 
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
>   at 
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
>   at 
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>   at 
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
>   at 
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
>   at 
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
>   at 
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
>   at java.lang.Thread.run(Thread.java:619)
> {noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SM-977) wsdl-first example fails: XFireFault (could not unmarshal type)

wsdl-first example fails: XFireFault (could not unmarshal type)
---

 Key: SM-977
 URL: https://issues.apache.org/activemq/browse/SM-977
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-jsr181
Affects Versions: 3.1.2
Reporter: Gert Vanthienen


After 'resolving' SM-960, the wsdl-first example no longer works.  It throws 
this exception, caused by differences in namespace.  The original wsdl file has 
it's GetPerson element in another namespace than the one that is being shown 
when browsing for the wsdl after deployment.

{noformat}
org.codehaus.xfire.fault.XFireFault: Could not unmarshall type : unexpected 
element (uri:"http://servicemix.apache.org/samples/wsdl-first";, 
local:"GetPerson"). Expected elements are 
<{http://servicemix.apache.org/samples/wsdl-first/types}GetPerson>,<{http://servicemix.apache.org/samples/wsdl-first/types}GetPersonResponse>,<{http://servicemix.apache.org/samples/wsdl-first/types}UnknownPersonFault>
at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:216)
at 
org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
at 
org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at 
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at 
org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
at 
org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
at 
org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
at 
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at 
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at 
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at 
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at 
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
{noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-973) servmicemix-sca: 2 PMD violations fix.


 [ 
https://issues.apache.org/activemq/browse/SM-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-973.


Resolution: Fixed

Fixed together with SM-976
http://svn.apache.org/viewvc?view=rev&revision=550026

> servmicemix-sca: 2 PMD violations fix.
> --
>
> Key: SM-973
> URL: https://issues.apache.org/activemq/browse/SM-973
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-sca
> Environment: all
>Reporter: Brian O'Neill
>Assignee: Bruce Snyder
>Priority: Minor
> Attachments: sca_pmd_patch.txt
>
>
> Fix for PMD violations causing 2 compilation errors for servicemix-sca

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-976) servicemix-sca is out of touch with the CheckStyle and PMD guides.


 [ 
https://issues.apache.org/activemq/browse/SM-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-976.


Resolution: Fixed

Thank you for this patch, Kit!
Building servicemix-sca now succeeds with PMD/CheckStyle enabled...

> servicemix-sca is out of touch with the CheckStyle and PMD guides. 
> ---
>
> Key: SM-976
> URL: https://issues.apache.org/activemq/browse/SM-976
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-sca
>Reporter: Kit Plummer
> Attachments: checkstyle_fixes_servicemix-sca.diff
>
>
> The current state of the servicemix-sca codebase requires turning off the 
> CheckStyle plugin in SMX/parent/pom.xml and installing it into the Maven repo.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-960) JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE )

2007-06-22 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-960.


   Resolution: Fixed
Fix Version/s: 3.1.2

Modified FragmentStreamReader to get it working:
http://svn.apache.org/viewvc?view=rev&revision=549818

Just a side question: Is there any need for a second FragmentStreamReader in 
servicemix-soap2, otherwise I would delete it there and reuse the 
servicemix-core one...

> JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT, 
> END_ELEMENT or ENTITY_REFERENCE )
> 
>
> Key: SM-960
> URL: https://issues.apache.org/activemq/browse/SM-960
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-jsr181
>Reporter: Sangwoo Han
>Priority: Minor
> Fix For: 3.1.2
>
> Attachments: citytime-sa-1.0-SNAPSHOT.jar
>
>
> The jsr181 orchestration sample doesn't work.
> In the sample of jsr181 orchestration's  CityTimeImpl.java class file
> [...] 
>   public GetCityTimeResponse getCityTime(GetCityTimeRequest 
> GetCityTimeRequest) { 
> 
> GetInfoByCity GetInfoByCity = new GetInfoByCity(); 
> GetInfoByCity.setUSCity(GetCityTimeRequest.getCity()); 
> 
> GetInfoByCityResponse r = usZip.getInfoByCity(GetInfoByCity); 
> Element e = (Element) 
> r.getGetInfoByCityResult().getContent().get(0); 
> e = (Element) e.getElementsByTagName("Table").item(0); 
> e = (Element) e.getElementsByTagName("ZIP").item(0); 
> String ZipCode = e.getTextContent(); 
> 
> //String lt = localTime.localTimeByZipCode(ZipCode); // at this 
> part it errored  
> GetCityTimeResponse rep = new GetCityTimeResponse(); 
> rep.getString().add("23:23"); 
> //rep.setTime(lt);  // wsgen didn't generate "setTime" function 
> return rep; 
> } 
> [...] 
> and the error output is below:
> 
> [...]
> DEBUG - header - << "Content-Length: 426[\r][\n]" 
> DEBUG - content- << " encoding="utf-8"?>http://schemas.xmlso 
> ap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";> dy> xmlns="http://ripedev.com/xsd/ZipCodeResults.xsd";>5/30/2007
>  8:51:44 PM ocalTimeByZipCodeResult>"
>  
> DEBUG - Client - Received message to 
> urn:xfire:transport:jbi:11805763005154-996237611 
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to 
> phase pre-dispatch 
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to 
> phase dispatch 
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to 
> phase dispatch 
> DEBUG - HandlerPipeline- Invoking phase transport 
> DEBUG - HandlerPipeline- Invoking phase parse 
> DEBUG - HandlerPipeline- Invoking phase pre-dispatch 
> DEBUG - HandlerPipeline- Invoking handler 
> org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch 
> DEBUG - Client - Correlating context with ID 
> 118057630051551778993400 
> DEBUG - Client - Found correlated context with ID 
> 118057630051551778993400 
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to 
> phase service 
> DEBUG - HandlerPipeline- Invoking phase dispatch 
> DEBUG - HandlerPipeline- Invoking handler 
> org.codehaus.xfire.handler.LocateBindingHandler in phase dispatch 
> DEBUG - HandlerPipeline- Invoking handler 
> org.codehaus.xfire.soap.handler.SoapBodyHandler in phase dispatch 
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to 
> phase user 
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to 
> phase pre-dispatch 
> DEBUG - HandlerPipeline- Invoking phase transport 
> DEBUG - HandlerPipeline- Invoking phase parse 
> DEBUG - HandlerPipeline- Invoking phase pre-dispatch 
> DEBUG - HandlerPipeline- Invoking handler 
> org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch 
> DEBUG - Client

[jira] Commented: (SM-970) Add support for wildcards in the element in servicemix.xml

2007-06-20 Thread Gert Vanthienen (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39454
 ] 

Gert Vanthienen commented on SM-970:


Isn't this already covered in ServiceMix 3.1 (cfr. "New in ServiceMix 3.1" on 
http://incubator.apache.org/servicemix/classloaders.html) or am I 
misunderstanding your question?

> Add support for wildcards in the  element in 
> servicemix.xml
> 
>
> Key: SM-970
> URL: https://issues.apache.org/activemq/browse/SM-970
> Project: ServiceMix
>  Issue Type: Improvement
>  Components: servicemix-lwcontainer
>Affects Versions: 3.1
>Reporter: Michal Palicka
>
> Hello, 
> we are using service units based on servicemix-lwcontainer.
> In many cases the service units depend on many dependencies (direct or 
> transitive), that also change during the development.
> It would be very helpful, if we could specify the classpath using a wildcard 
> instead of a list of individual dependencies.
> Current status:
> 
> .
> ./lib/lib1.jar
> ./lib/lib2.jar
> ...
>  ./lib/libn.jar
> 
> Desired status:
> 
> .
> ./lib/*.jar
> 
> Thank you.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: servicemix Drool engine Issue

2007-06-19 Thread Gert Vanthienen


Prasanta,


At this moment, there is no servicemix-drools SU archetype.  Please file a
JIRA to have it created...

For now, you can just use the plain SU archetype and go from there.  Have a
look at
http://incubator.apache.org/servicemix/what-is-a-jbi-su-and-how-do-i-create-one.html,
but use -DarchetypeArtifactId=servicemix-service-unit instead.

After that is done, you add a dependency to servicemix-drools to the pom.xml
that has been generated:

org.apache.servicemix
servicemix-http
${servicemix-version}


Now all you have to do is modify your xbean.xml to configure the Drools
service endpoints.  Maven will take care of packaging it a SU targeted at
servicemix-drools.


Gert



pksahoo wrote:
> 
> How can I create a service unit to use the drools rules engine? Please
> share the maven archetype and, if possible, an example
> 
> My JMS client is cnfigured with servicemix drool SU. I am getting
> following error.
> 
> Please advise.
> 
> Here is the details of error: 
> 10:13:49,928 | WARN | pool-component.servicemix-jms-thread-2 |
> DefaultBroker | rvicemix.jbi.nmr.DefaultBroker 341 | ServiceName
> ({urn:logicblaze:soa:loanbroker}myDroolsService) specified for routing,
> but can't find it registered
> 10:13:49,928 | WARN | pool-component.servicemix-jms-thread-2 |
> DefaultBroker | rvicemix.jbi.nmr.DefaultBroker 341 | ServiceName
> ({urn:logicblaze:soa:loanbroker}myDroolsService) specified for routing,
> but can't find it registered
> 10:13:49,928 | ERROR | pool-component.servicemix-jms-thread-2 |
> plexingConsumerProcessor | ultiplexingConsumerProcessor$1 100 | Error
> while handling jms message
> javax.jbi.messaging.MessagingException: Could not find route for exchange:
> InOut[
> id: ID:169.254.185.179-1133f6208c3-5:0
> status: Active
> role: provider
> service: {urn:logicblaze:soa:loanbroker}myDroolsService
> operation: Hello
> in:  xmlns="urn:/HelloWorld2.wsdl"
> xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>
> Hello from Vishal - 
> 
> ] for service: {urn:logicblaze:soa:loanbroker}myDroolsService and
> interface: null
> at
> org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(DefaultBroker.java:295)
> at
> org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket(SecuredBroker.java:81)
> at
> org.apache.servicemix.jbi.container.JBIContainer.sendExchange(JBIContainer.java:793)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:381)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:417)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.sendConsumerExchange(AsyncBaseLifeCycle.java:572)
> at
> org.apache.servicemix.jms.multiplexing.MultiplexingConsumerProcessor$1.run(MultiplexingConsumerProcessor.java:98)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
> 
> [ Show » ] Jawed Khan [18/Jun/07 08:27 AM] Here is the details of error:
> 10:13:49,928 | WARN | pool-component.servicemix-jms-thread-2 |
> DefaultBroker | rvicemix.jbi.nmr.DefaultBroker 341 | ServiceName
> ({urn:logicblaze:soa:loanbroker}myDroolsService) specified for routing,
> but can't find it registered 10:13:49,928 | WARN |
> pool-component.servicemix-jms-thread-2 | DefaultBroker |
> rvicemix.jbi.nmr.DefaultBroker 341 | ServiceName
> ({urn:logicblaze:soa:loanbroker}myDroolsService) specified for routing,
> but can't find it registered 10:13:49,928 | ERROR |
> pool-component.servicemix-jms-thread-2 | plexingConsumerProcessor |
> ultiplexingConsumerProcessor$1 100 | Error while handling jms message
> javax.jbi.messaging.MessagingException: Could not find route for exchange:
> InOut[ id: ID:169.254.185.179-1133f6208c3-5:0 status: Active role:
> provider service: {urn:logicblaze:soa:loanbroker}myDroolsService
> operation: Hello in:  xmlns="urn:/HelloWorld2.wsdl"
> xmlns:soap="http://www.w3.org/2003/05/soap-envelope";> Hello from
> Vishal -   ] for service:
> {urn:logicblaze:soa:loanbroker}myDroolsService and interface: null at
> org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(DefaultBroker.java:295)
> at
> org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket(SecuredBroker.java:81)
> at
> org.apache.servicemix.jbi.container.JBIContainer.sendExchange(JBIContainer.java:793)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:381)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:417)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.sendConsumerExchange(AsyncBaseLifeCycle.java:572)
> at
> org.apache.servicemix.jms.multiplexing.MultiplexingConsumerProcessor$1.run(MultiplexingConsumerProcessor.java:98)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> at
> java.util.concurrent.ThreadPoolExecu

[jira] Commented: (SM-787) IllegalStateException when reading XML message

2007-06-18 Thread Gert Vanthienen (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39442
 ] 

Gert Vanthienen commented on SM-787:


After checking with the XFire mailing list and trying out some things, it 
appears that the exception only occurs if the body of the content is a 
StAXSource.  When a DomSource enters Jsr181ExchangeProcessor's process() 
method, everything works fine.  That explains why the error doesn't occur when 
setting the logging to DEBUG (conversion of body content to a re-readable XML 
source type).  Could there be something wrong with our implementations for 
StaxSource, FragmentStreamReader, ...?  I've already tried replacing our 
StaxSource with JDK 1.6 StAXSource implementation (for testing), but that 
doesn't help either

> IllegalStateException when reading XML message
> --
>
> Key: SM-787
> URL: https://issues.apache.org/activemq/browse/SM-787
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-jsr181
>Affects Versions: 3.1
>Reporter: Horst Studer
>
> When sending a message to a JSR-181 service unit, I get an 
> IllegalStateException
> thown by the Woodstox XML Processor (see stack trace).
> It is important to note that this exception does NOT occur if the log-level 
> for org.apache.servicemix
> is set to DEBUG. But it occurs if the log-level is INFO. This means that 
> writing the message to
> the log seams to prevent the IllegalStateException from happening.
> Here is the stack trace:
> 17:09:14,806 | ERROR | pool-flow.seda.servicemix-jsr181-thread-1 | 
> DefaultFaultHandler  | re.handler.DefaultFaultHandler   35 | Fault 
> occurred!
> java.lang.IllegalStateException: Current state not START_ELEMENT, END_ELEMENT 
> or ENTITY_REFERENCE
>   at 
> com.ctc.wstx.sr.BasicStreamReader.getLocalName(BasicStreamReader.java:708)
>   at 
> org.codehaus.xfire.util.stax.DepthXMLStreamReader.getLocalName(DepthXMLStreamReader.java:100)
>   at 
> org.codehaus.xfire.aegis.stax.ElementReader.(ElementReader.java:58)
>   at 
> org.codehaus.xfire.aegis.stax.ElementReader.(ElementReader.java:69)
>   at 
> org.apache.servicemix.jsr181.xfire.ServiceFactoryHelper$FixedJAXWSOperationBinding.readMessage(ServiceFactoryHelper.java:403)
>   at 
> org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
>   at 
> org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
>   at 
> org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
>   at 
> org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
>   at 
> org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:110)
>   at 
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
>   at 
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
>   at 
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>   at 
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
>   at 
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
>   at 
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
>   at 
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>   at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>   at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
>   at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-965) Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy

2007-06-14 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-965.


   Resolution: Fixed
Fix Version/s: 3.2
   3.1.2

Added the necessary expression=${...} 

http://svn.apache.org/viewvc?view=rev&revision=547183

> Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy
> ---
>
> Key: SM-965
> URL: https://issues.apache.org/activemq/browse/SM-965
> Project: ServiceMix
>  Issue Type: Improvement
>  Components: tooling
>Affects Versions: 3.1
>Reporter: Steve Carmichael
> Fix For: 3.1.2, 3.2
>
>
> when I run the following command: 
> >mvn jbi:projectDeploy -Dhost=XXX.X.X.XXX -Dusername=XXX -Dpassword=XXX 
> (where XXX = real values) 
> to deploy to a remote server running ServiceMix standalone, I get the 
> following error: 
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub: 
> javax.naming.ServiceUnavailableException [Root e 
> xception is java.rmi.ConnectException: Connection refused to host: localhost; 
> nested exception is: 
> java.net.ConnectException: Connection refused: connect] 
> at 
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317) 
> at 
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>  
> at 
> org.apache.servicemix.jbi.management.task.JbiTask.getJMXConnector(JbiTask.java:77)
>  
> at 
> org.apache.servicemix.jbi.management.task.JbiTask.connect(JbiTask.java:85) 
> at 
> org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.java:252) 
> ... 21 more 
> Caused by: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refuse 
> Notice that localhost is being invoked (not the hostname I indicated in the 
> -D option) 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SM-965) Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy

2007-06-14 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SM-965:
---

Issue Type: Improvement  (was: Bug)
   Summary: Allow use of -Dhost, -Dport, -Dusername and -Dpassword on 
jbi:projectDeploy  (was: jbi:projectDeploy with -Dhost=xxx.xxx.xxx.xxx option 
ignores host name and uses localhost)

> Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy
> ---
>
> Key: SM-965
> URL: https://issues.apache.org/activemq/browse/SM-965
> Project: ServiceMix
>  Issue Type: Improvement
>  Components: tooling
>Affects Versions: 3.1
>Reporter: Steve Carmichael
>
> when I run the following command: 
> >mvn jbi:projectDeploy -Dhost=XXX.X.X.XXX -Dusername=XXX -Dpassword=XXX 
> (where XXX = real values) 
> to deploy to a remote server running ServiceMix standalone, I get the 
> following error: 
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub: 
> javax.naming.ServiceUnavailableException [Root e 
> xception is java.rmi.ConnectException: Connection refused to host: localhost; 
> nested exception is: 
> java.net.ConnectException: Connection refused: connect] 
> at 
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317) 
> at 
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>  
> at 
> org.apache.servicemix.jbi.management.task.JbiTask.getJMXConnector(JbiTask.java:77)
>  
> at 
> org.apache.servicemix.jbi.management.task.JbiTask.connect(JbiTask.java:85) 
> at 
> org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.java:252) 
> ... 21 more 
> Caused by: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refuse 
> Notice that localhost is being invoked (not the hostname I indicated in the 
> -D option) 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: ServiceMix 3.1.1 release - when?

2007-06-14 Thread Gert Vanthienen


Guillaume,

I was unaware of things that needed fixing.  What are they?  Can I help 
out with them?


Gert

Guillaume Nodet wrote:

There are a few things that need to be fixed before officially releasing
this version.
Hopefully this should be done soon.

On 6/7/07, Rossmanith, Philipp <[EMAIL PROTECTED]> wrote:



Dear all,

I've been following the vote about releasing 3.1.1. Did you reach a
decision yet? When will it be released?

Ciao,
Philipp


This e-mail may contain confidential or privileged information. Any
unauthorised
copying, use or distribution of this information is strictly prohibited.

[jira] Commented: (SM-787) IllegalStateException when reading XML message

2007-06-14 Thread Gert Vanthienen (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39387
 ] 

Gert Vanthienen commented on SM-787:


I would like to look into this one. This message (or a similar one) is 
mentioned in two other issues (SM-960, SM-964) but I have no idea where to 
look.  The exception is being thrown by Woodstox/XFire, but I do not find a 
mention of a similar bug in any of their mailing lists, so I figured it should 
be something in ServiceMix itself.  Where should I start looking?  

> IllegalStateException when reading XML message
> --
>
> Key: SM-787
> URL: https://issues.apache.org/activemq/browse/SM-787
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-jsr181
>Affects Versions: 3.1
>Reporter: Horst Studer
>
> When sending a message to a JSR-181 service unit, I get an 
> IllegalStateException
> thown by the Woodstox XML Processor (see stack trace).
> It is important to note that this exception does NOT occur if the log-level 
> for org.apache.servicemix
> is set to DEBUG. But it occurs if the log-level is INFO. This means that 
> writing the message to
> the log seams to prevent the IllegalStateException from happening.
> Here is the stack trace:
> 17:09:14,806 | ERROR | pool-flow.seda.servicemix-jsr181-thread-1 | 
> DefaultFaultHandler  | re.handler.DefaultFaultHandler   35 | Fault 
> occurred!
> java.lang.IllegalStateException: Current state not START_ELEMENT, END_ELEMENT 
> or ENTITY_REFERENCE
>   at 
> com.ctc.wstx.sr.BasicStreamReader.getLocalName(BasicStreamReader.java:708)
>   at 
> org.codehaus.xfire.util.stax.DepthXMLStreamReader.getLocalName(DepthXMLStreamReader.java:100)
>   at 
> org.codehaus.xfire.aegis.stax.ElementReader.(ElementReader.java:58)
>   at 
> org.codehaus.xfire.aegis.stax.ElementReader.(ElementReader.java:69)
>   at 
> org.apache.servicemix.jsr181.xfire.ServiceFactoryHelper$FixedJAXWSOperationBinding.readMessage(ServiceFactoryHelper.java:403)
>   at 
> org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
>   at 
> org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
>   at 
> org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
>   at 
> org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
>   at 
> org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:110)
>   at 
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
>   at 
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
>   at 
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>   at 
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
>   at 
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
>   at 
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
>   at 
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>   at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>   at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
>   at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: in-out to in-only adapting - solution

2007-06-13 Thread Gert Vanthienen


L.S.,


Seems like a good addition for servicemix-eip at first glance.  If you 
want to contribute it to ServiceMix, the easiest way to ensure follow-up 
on this would be by raising a JIRA issue.



Thank you,

Gert

ale wrote:

i finally managed to find a solution to the synchronizing issue i requested
help for 1 days ago.
I built a component implementing a pattern which could be thought as the
opposite of a pipeline.
It accepts an in-out mep and holds it associated to a correlation key and
then sends the in message
asynchronously to a target service.
When an in-only mep comes in it tries to correlate the message with one of
the stored exchanges and 
eventually answers back with the corresponding in-out mep.


That's what it does : 

  
  / ->IN-ONLY
/
   <-- IN-OUT --> 
\

  \<--IN-ONLY


Its ina very early version but if anybody finds it interesting i could
provide the full sources on
this forum or as a jira issue.

Let me know, bye.

[jira] Commented: (SM-965) jbi:projectDeploy with -Dhost=xxx.xxx.xxx.xxx option ignores host name and uses localhost

2007-06-12 Thread Gert Vanthienen (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39367
 ] 

Gert Vanthienen commented on SM-965:


It's not a bug apparently, but a feature that hasn't been implemented yet.  
There are no expression annotations on any of the properties in 
AbstractDeployableMojo.

An example:
{code}
/**
 * @parameter default-value="localhost" expression="${jbi.host}"
 */
private String host;
{code}

After the change, I'm able to use this command succesfully:
{{mvn jbi:projectDeploy -Djbi.host=kiwi}} 

> jbi:projectDeploy with -Dhost=xxx.xxx.xxx.xxx option ignores host name and 
> uses localhost
> -
>
> Key: SM-965
> URL: https://issues.apache.org/activemq/browse/SM-965
> Project: ServiceMix
>  Issue Type: Bug
>  Components: tooling
>Affects Versions: 3.1
>Reporter: Steve Carmichael
>
> when I run the following command: 
> >mvn jbi:projectDeploy -Dhost=XXX.X.X.XXX -Dusername=XXX -Dpassword=XXX 
> (where XXX = real values) 
> to deploy to a remote server running ServiceMix standalone, I get the 
> following error: 
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub: 
> javax.naming.ServiceUnavailableException [Root e 
> xception is java.rmi.ConnectException: Connection refused to host: localhost; 
> nested exception is: 
> java.net.ConnectException: Connection refused: connect] 
> at 
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317) 
> at 
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>  
> at 
> org.apache.servicemix.jbi.management.task.JbiTask.getJMXConnector(JbiTask.java:77)
>  
> at 
> org.apache.servicemix.jbi.management.task.JbiTask.connect(JbiTask.java:85) 
> at 
> org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.java:252) 
> ... 21 more 
> Caused by: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refuse 
> Notice that localhost is being invoked (not the hostname I indicated in the 
> -D option) 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Getting started guide

2007-06-11 Thread Gert Vanthienen


L.S.,


I have made some changes to this tutorial:
- added a section on Installing ServiceMix
- added some information about SUs
- tried to clarify why the client.html is being used
- added header/footer {scrollbar}s
- tried to elaborate on the dependency between a SU and a JBI component.

On the exercise page, we already installed a SA without the right 
components being available, so people should be aware of the fact that 
ServiceMix tells you about this from there.  Perhaps I haven't made it 
clear enough...?


I also tried to work out the structure you were describing on 
http://cwiki.apache.org/confluence/x/ON4, with different levels of 
tutorial complexity.


Any additional comment?


Gert



Bruce Snyder wrote:

On 6/7/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote:


Bruce,

I've created a first tutorial, a guided tour of starting, installing,
deploying and testing a first application and, more importantly, a quick
introduction some JBI concepts (service assembly, service unit, ...).  It
isn't completely done yet, but it already shows the intention.  Is 
this what

you had in mind?

For the second tutorial, I would like to focus on the Maven tooling and
archetypes.  Any suggestions on that topic?


This is a great start, Gert! Overall this is a wonderful start. I hope
to be able to create a whole series of these guides to help users get
started easier. Below are my comments:

- Provide a headding to the section about installing ServiceMix to
properly identity it. Right now it's under a heading named Content
which isn't very descriptive.

- Make sure to describe both SAs and SUs. Right now SUs are not
described at all. This is easy to do because there are already FAQ
entries about SAs and SUs that can be referenced for this.

- We should break up the whole guide into sections like Beginner,
Intermediate and Advanced. This will allow us to address more complex
topics without confusing beginners. E.g., In the beginner JMX
tutorial, we only address connecting to a local instance of SMX
whereas an intermediate version would describe how to connect to
multiple remote instances of SMX and an advanced version might go into
code level use of JMX, all of which are cross-linked.

- Be very clear about the component dependencies for deploying the
example. It might be a good idea to demonstrate that SMX will tell you
when a component is missing.

- Provide a better description about what the client.html file is
actually doing to invoke the service (i.e., it is sending an XML
message to the URL where the service is exposed). Upon first using
SMX, many people assume that when configuring the locationURI for
servicemix-http that you can simply visit that URL in a browser to use
it and this is not true. We need to explain that an XML message must
be sent to this URL.

- The header and footer with the arrows for navigation are missing
from most of the pages. Please make sure to add them.

Again, very nice work, Gert. My comments are only meant to be constructive.

Bruce

[jira] Issue Comment Edited: (SM-964) Upgrade to XFire 1.2.6


[ 
https://issues.apache.org/activemq/browse/SM-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39238
 ] 

Gert Vanthienen edited comment on SM-964 at 6/8/07 1:37 PM:


I attempted to do this upgrade by simply changing the xfire-version to 1.2.6.  
However, after the build was done the wsdl-first example no longer works 
correctly.  Is there anything else that I need to change?

{noformat}
The stacktrace is 
java.lang.IllegalStateException: The current event is not START_ELEMENT but 7
at 
com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:124)
at 
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:337)
at 
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:309)
at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:203)
at 
org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
at 
org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at 
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at 
org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
at 
org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
at 
org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
at 
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at 
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at 
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at 
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at 
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
{noformat}


 was:
I attempted to do this upgrade by simply changing the xfire-version to 1.2.6.  
However, after the build was done the wsdl-first example no longer works 
correctly.  Is there anything else that I need to change?

The stacktrace is 
java.lang.IllegalStateException: The current event is not START_ELEMENT
 but 7
at 
com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:124)
at 
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:337)
at 
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:309)
at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:203)
at 
org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
at 
org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at 
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at 
org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
at 
org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
at 
org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
at 
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at 
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at 
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at 
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at 
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)

> Upgrade to XFire 1.2.6
> --
>
> Key: SM-964
> URL: https://issues.apache.org/activemq/browse/SM-964
> Project: ServiceMix
>  Issue Type: Improvement
>  Components: servicemix-jsr181
&g

[jira] Commented: (SM-964) Upgrade to XFire 1.2.6


[ 
https://issues.apache.org/activemq/browse/SM-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39239
 ] 

Gert Vanthienen commented on SM-964:


I noticed that this is the same exception as is mentioned in SM-960, so I tried 
to rerun that as well.  This is the resulting error stack trace:

{noformat}
org.codehaus.xfire.fault.XFireFault: Could not invoke service.. Nested 
exception is org.codehaus.xfire.fault.XFireFault: Could not write to outgoing 
stream.
at 
org.codehaus.xfire.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:83)
at 
org.codehaus.xfire.service.binding.ServiceInvocationHandler.sendMessage(ServiceInvocationHandler.java:320)
at 
org.codehaus.xfire.service.binding.ServiceInvocationHandler$1.run(ServiceInvocationHandler.java:86)
at 
org.codehaus.xfire.service.binding.ServiceInvocationHandler.execute(ServiceInvocationHandler.java:134)
at 
org.codehaus.xfire.service.binding.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:109)
at 
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at 
org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
at 
org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
at 
org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
at 
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at 
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at 
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at 
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at 
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. 
Nested exception is org.codehaus.xfire.fault.XFireFault: Could not write to 
outgoing stream.
at 
org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:92)
at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
at 
org.apache.servicemix.jsr181.xfire.JbiProxyFactoryBean$1.invoke(JbiProxyFactoryBean.java:73)
at $Proxy0.getInfoByCity(Unknown Source)
at 
org.apache.servicemix.samples.citytime.CityTimeImpl.getCityTime(CityTimeImpl.java:34)
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.codehaus.xfire.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:59)
... 18 more
Caused by: org.codehaus.xfire.fault.XFireFault: Could not write to outgoing 
stream.
at 
org.codehaus.xfire.service.binding.DocumentBinding.writeMessage(DocumentBinding.java:67)
at 
org.apache.servicemix.jsr181.xfire.JbiChannel.getContent(JbiChannel.java:173)
at 
org.apache.servicemix.jsr181.xfire.JbiChannel.send(JbiChannel.java:122)
at 
org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
at 
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
at org.codehaus.xfire.client.Client.invoke(Client.java:336)
at 
org.apache.servicemix.jsr181.xfire.JbiProxy$JAXWSJBIClient.invoke(JbiProxy.java:232)
at 
org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)
... 27 more
Caused by: javax.xml.stream.XMLStreamException: Trying to write a namespace 
declaration when there is no open start element.
at 
com.ctc.wstx.sw.BaseStreamWriter.throwOutputError(BaseStreamWriter.java:1473)
at 
com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:128)
at 
org.codehaus.xfire.util.NamespaceHelper.getUniquePrefix(NamespaceHelper.java:139)
at 
org.codehaus.xfire.service.binding.DocumentBinding.writeMessage(DocumentBinding.java:65)
... 36 more
{noformat}

> Upgrade to XFire 1.2.6
> --
>
>

[jira] Commented: (SM-964) Upgrade to XFire 1.2.6


[ 
https://issues.apache.org/activemq/browse/SM-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39238
 ] 

Gert Vanthienen commented on SM-964:


I attempted to do this upgrade by simply changing the xfire-version to 1.2.6.  
However, after the build was done the wsdl-first example no longer works 
correctly.  Is there anything else that I need to change?

The stacktrace is 
java.lang.IllegalStateException: The current event is not START_ELEMENT
 but 7
at 
com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:124)
at 
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:337)
at 
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:309)
at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:203)
at 
org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
at 
org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at 
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at 
org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
at 
org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
at 
org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
at 
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at 
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at 
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at 
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at 
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)

> Upgrade to XFire 1.2.6
> --
>
> Key: SM-964
> URL: https://issues.apache.org/activemq/browse/SM-964
> Project: ServiceMix
>  Issue Type: Improvement
>  Components: servicemix-jsr181
>Affects Versions: 3.1
>    Reporter: Gert Vanthienen
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SM-964) Upgrade to XFire 1.2.6

Upgrade to XFire 1.2.6
--

 Key: SM-964
 URL: https://issues.apache.org/activemq/browse/SM-964
 Project: ServiceMix
  Issue Type: Improvement
  Components: servicemix-jsr181
Affects Versions: 3.1
Reporter: Gert Vanthienen




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Getting started guide

2007-06-07 Thread Gert Vanthienen


Bruce,

I've created a first tutorial, a guided tour of starting, installing,
deploying and testing a first application and, more importantly, a quick
introduction some JBI concepts (service assembly, service unit, ...).  It
isn't completely done yet, but it already shows the intention.  Is this what
you had in mind?

For the second tutorial, I would like to focus on the Maven tooling and
archetypes.  Any suggestions on that topic?

Regards,

Gert


bsnyder wrote:
> 
> On 5/29/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote:
>> L.S.,
>>
>>
>> After having followed the user mailing list for a while, it seems that
>> it's quite a steep learning curve to get started with ServiceMix.
>> I would like to add a tutorial or getting started guide to the website,
>> just guiding a new user through the existing documentation and trying to
>> explain some key concepts on the way.  Something like...
>> # starting the container and connect to it using JMX
>> # installing some components and deploying e.g. the wsdl-first example
>> [to explain e.g. components, service assembly, service unit]
>> # building a simple SA, e.g. re-using the 'File binding' page [to
>> explain about the maven archetypes]
>> # building e.g. the protocol bridge example to explain about message
>> exchange patterns, routing, ...
>>
>> Would this be a worthwhile addition or are there other areas in the
>> documentation that need work more urgently?  Are there any other topics
>> to include in this guided tour?
> 
> Very nice work Gert! I'm excited that someone else is interested to
> help develop more docs - yay!
> 
> There are certainly a lot of concepts with which you must be familiar
> in order to dive in. I had to explain this to a friend recently and he
> was quite overwhelmed at first.
> 
> I have had this task in mind for some time and I just haven't had the
> time to spend on it yet. I wrote the hello world tutorials on building
> components and those are still not 100% complete :-( - if only there
> were 30 hours in a day! So, yes, yes - let's create some simple
> tutorials to help folks get started!
> 
> What I've had in mind is a Getting Started Guide - a set of exercises
> to help users become familiar with ServiceMix, including ActiveMQ, in
> the most expedient manner possible. I'd like to provide a five minute
> version and then much more detailed version, keeping in mind that they
> must be from a user's perspective, not a developer of ServiceMix.
> 
> The most basic tutorials are the most in demand right now such as,
> starting ServiceMix, deploying and testing some of the examples, how
> to send test messages using SoapUI and otherwise, walking users
> through a step-by-step tutorial of building their own flow using
> components that come with ServiceMix.
> 
> Before diving right in without a plan, let's at least outline the
> exercises we would like to create. That way work on different
> exercises can take place concurrently and nobody is hindered by
> another exercises level of completion. Below is a suggested list:
> 
> 1) Starting SMX
> 2) Explain components (e.g., explain and demo both types from a *user*
> perspective)
> 3) Using JMX with SMX via Jconsole (e.g., poke around a bit)
> 4) Explain and run SMX examples (e.g., explain how to deploy and how
> the flow through SUs works)
> 5) Developing and testing your own SUs (e.g., this should be broken up
> into multiple exercises that build upon one another so that we take
> users through a progression that becomes more complex as they go)
> 
> This is just a five minute brain dump - let's work on this together
> via the wiki.
> 
> Bruce
> -- 
> perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E );'
> 
> Apache Geronimo - http://geronimo.apache.org/
> Apache ActiveMQ - http://activemq.org/
> Apache ServiceMix - http://servicemix.org/
> Castor - http://castor.org/
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Getting-started-guide-tf3836548s12049.html#a11015781
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Re: Getting started guide

2007-05-30 Thread Gert Vanthienen


Eduardo,

I have started working on it today, feel free to help out 
whenever/wherever you can...  I have added it as Tutorial (in progress) 
on http://cwiki.apache.org/confluence/display/SM/Sandbox


A lot of the information is already in the wiki, I just want to create a 
step-by-step tutorial to get people started off the right way.  Instead 
of doing copy-paste, I would suggest to 'refactor' the pages and use 
{include} where appropriate (e.g. starting ServiceMix)


Gert

Eduardo de Vera wrote:

Bravo! I was waiting for something like this to happen sooner or later. I
would love to contribute on my spare time.

2007/5/29, Gert Vanthienen <[EMAIL PROTECTED]>:


L.S.,


After having followed the user mailing list for a while, it seems that
it's quite a steep learning curve to get started with ServiceMix.
I would like to add a tutorial or getting started guide to the website,
just guiding a new user through the existing documentation and trying to
explain some key concepts on the way.  Something like...
# starting the container and connect to it using JMX
# installing some components and deploying e.g. the wsdl-first example
[to explain e.g. components, service assembly, service unit]
# building a simple SA, e.g. re-using the 'File binding' page [to
explain about the maven archetypes]
# building e.g. the protocol bridge example to explain about message
exchange patterns, routing, ...

Would this be a worthwhile addition or are there other areas in the
documentation that need work more urgently?  Are there any other topics
to include in this guided tour?


Regards,

Gert

[jira] Updated: (SM-958) Dynamically determine basic authentication credentials for provider endpoint

2007-05-28 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SM-958:
---

Summary: Dynamically determine basic authentication credentials for 
provider endpoint  (was: Dynamically determine basis authentication credentials 
for provider endpoint)

> Dynamically determine basic authentication credentials for provider endpoint
> 
>
> Key: SM-958
> URL: https://issues.apache.org/activemq/browse/SM-958
> Project: ServiceMix
>  Issue Type: New Feature
>  Components: servicemix-http
>Affects Versions: 3.1
>    Reporter: Gert Vanthienen
>Assignee: Gert Vanthienen
>Priority: Minor
> Fix For: 3.1.2
>
>
> It should be possible to just change the type for the username/password 
> properties in the  BasicAuthCredentials into Expression, with a 
> PropertyEditor to ensure correct translation from String to 
> ConstantExpression on existing configuration files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-958) Dynamically determine basis authentication credentials for provider endpoint

2007-05-28 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen resolved SM-958.


Resolution: Fixed

http://svn.apache.org/viewvc?view=rev&revision=542291
http://svn.apache.org/viewvc?view=rev&revision=542294


> Dynamically determine basis authentication credentials for provider endpoint
> 
>
> Key: SM-958
> URL: https://issues.apache.org/activemq/browse/SM-958
> Project: ServiceMix
>  Issue Type: New Feature
>  Components: servicemix-http
>Affects Versions: 3.1
>Reporter: Gert Vanthienen
>Assignee: Gert Vanthienen
>Priority: Minor
> Fix For: 3.1.2
>
>
> It should be possible to just change the type for the username/password 
> properties in the  BasicAuthCredentials into Expression, with a 
> PropertyEditor to ensure correct translation from String to 
> ConstantExpression on existing configuration files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SM-958) Dynamically determine basis authentication credentials for provider endpoint

2007-05-24 Thread Gert Vanthienen (JIRA)

Dynamically determine basis authentication credentials for provider endpoint


 Key: SM-958
 URL: https://issues.apache.org/activemq/browse/SM-958
 Project: ServiceMix
  Issue Type: New Feature
  Components: servicemix-http
Affects Versions: 3.1
Reporter: Gert Vanthienen
 Assigned To: Gert Vanthienen
Priority: Minor
 Fix For: 3.1.2


It should be possible to just change the type for the username/password 
properties in the  BasicAuthCredentials into Expression, with a PropertyEditor 
to ensure correct translation from String to ConstantExpression on existing 
configuration files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release ServiceMix 3.1.1 (2nd try)

2007-05-22 Thread Gert Vanthienen


And here's my +1 too

Guillaume Nodet wrote:

I have uploaded a version of ServiceMix 3.1.1 in the standard repo
for you to review. See
http://incubator.apache.org/servicemix/servicemix-311.html
for the future download page and release notes (these are also 
included in

the
distribution).  The distribution have been uploaded to

http://people.apache.org/~gnodet/servicemix-3.1.1-incubating/org/apache/servicemix/apache-servicemix/3.1.1-incubating/ 



I send this mail both to the dev list and [EMAIL PROTECTED], as a first 
vote has

been
conducted on the ServiceMix dev list and some issues have been fixed 
since

that, so hopefully this one will be fine.

[ ] +1 Release ServiceMix 3.1.1
[ ] +/- 0
[ ] -1 Do not release ServiceMix 3.1.1

The rat log is available at
http://people.apache.org/~gnodet/rat-servicemix-3.1.1-incubating.txt 



Here's my +1

Re: [VOTE] Release ServiceMix 3.1.1

2007-05-17 Thread Gert Vanthienen


Guillaume,

I've just retried a few of the samples as well as some of my own SAs. 
Everything seems to work fine, so here's my +1 now...

Gert


gnodet wrote:
> 
> It should be fixed now.  I have updated the tag and uploaded a new distro.
> Thanks for reporting that !
> 
> On 5/16/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote:
>>
>>
>> L.S.,
>>
>> The WSDL-first example doesn't seem to work.  It gives a
>> javax.jbi.messaging.MessagingException: Do not understand pattern: null
>> when
>> testing it with the client.html on this machine.  The xbean.xml file no
>> longer contains the defaultMep attribute (has been removed while solving
>> SM-901: Upgrade to xfire 1.2.5).
>>
>> Regards,
>>
>> Gert
>>
>>
>> gnodet wrote:
>> >
>> > I have uploaded a version of ServiceMix 3.1.1 in the standard repo
>> > for you to review. See
>> > http://incubator.apache.org/servicemix/servicemix-311.html
>> > for all the links and release notes.
>> >
>> > [ ] +1 Release ServiceMix 3.1.1
>> > [ ] +/- 0
>> > [ ] -1 Do not release ServiceMix 3.1.1
>> >
>> > I will upload a rat report asap.
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> > 
>> > Principal Engineer, IONA
>> > Blog: http://gnodet.blogspot.com/
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/-VOTE--Release-ServiceMix-3.1.1-tf3758807s12049.html#a10639960
>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> Cheers,
> Guillaume Nodet
> 
> Principal Engineer, IONA
> Blog: http://gnodet.blogspot.com/
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-VOTE--Release-ServiceMix-3.1.1-tf3758807s12049.html#a10671058
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Re: [VOTE] Release ServiceMix 3.1.1

2007-05-16 Thread Gert Vanthienen

L.S.,

The WSDL-first example doesn't seem to work.  It gives a
javax.jbi.messaging.MessagingException: Do not understand pattern: null when
testing it with the client.html on this machine.  The xbean.xml file no
longer contains the defaultMep attribute (has been removed while solving
SM-901: Upgrade to xfire 1.2.5).

Regards,

Gert

gnodet wrote:
> 
> I have uploaded a version of ServiceMix 3.1.1 in the standard repo
> for you to review. See
> http://incubator.apache.org/servicemix/servicemix-311.html
> for all the links and release notes.
> 
> [ ] +1 Release ServiceMix 3.1.1
> [ ] +/- 0
> [ ] -1 Do not release ServiceMix 3.1.1
> 
> I will upload a rat report asap.
> 
> -- 
> Cheers,
> Guillaume Nodet
> 
> Principal Engineer, IONA
> Blog: http://gnodet.blogspot.com/
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-VOTE--Release-ServiceMix-3.1.1-tf3758807s12049.html#a10639960
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Re: [Fwd: WARNING - 2 days to deadline for May reports]

2007-05-09 Thread Gert Vanthienen


L.S.,

I have written a summary about what's been going on with ServiceMix in the
last few months on the wiki page that was mentioned in the original mail.  I
hope that is OK...

Can someone take a look to ensure that I've added the correct information in
the report?

Regards,

Gert


Gert Vanthienen wrote:
> 
> Guillaume,
> 
> What exactly is it that needs to be done?  Can I help out with it?
> 
> Gert
> 
> Guillaume Nodet wrote:
>> Anybody want to take a look at this ?
>>   
>>
>> 
>>
>> Subject:
>> WARNING - 2 days to deadline for May reports
>> From:
>> "William A. Rowe, Jr." <[EMAIL PROTECTED]>
>> Date:
>> Mon, 07 May 2007 22:02:00 -0500
>> To:
>> [EMAIL PROTECTED]
>>
>> To:
>> [EMAIL PROTECTED]
>>
>>
>> Well this sort of sucks - with everyone so busy at ApacheCon EU, we've
>> neglected to remind you of the deadline on the 9th (posted months ago)
>> for
>>
>>   http://wiki.apache.org/incubator/May2007
>>
>> Abdera
>> Lokahi
>> NMaven
>> RCF
>> ServiceMix
>> stdcxx
>> Tika
>> TSIK
>> Tuscany
>> Woden
>> WSRP4J
>> XAP
>> Yoko
>>
>> must report.  PLEASE rush to get this done, so we have time to review
>> the reports and get them to the board.
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>   
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-Fwd%3A-WARNING---2-days-to-deadline-for-May-reports--tf3716285s12049.html#a10401473
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Re: [Fwd: WARNING - 2 days to deadline for May reports]

2007-05-09 Thread Gert Vanthienen


Guillaume,

What exactly is it that needs to be done?  Can I help out with it?

Gert

Guillaume Nodet wrote:

Anybody want to take a look at this ?
  




Subject:
WARNING - 2 days to deadline for May reports
From:
"William A. Rowe, Jr." <[EMAIL PROTECTED]>
Date:
Mon, 07 May 2007 22:02:00 -0500
To:
[EMAIL PROTECTED]

To:
[EMAIL PROTECTED]


Well this sort of sucks - with everyone so busy at ApacheCon EU, we've
neglected to remind you of the deadline on the 9th (posted months ago) for

  http://wiki.apache.org/incubator/May2007

Abdera
Lokahi
NMaven
RCF
ServiceMix
stdcxx
Tika
TSIK
Tuscany
Woden
WSRP4J
XAP
Yoko

must report.  PLEASE rush to get this done, so we have time to review
the reports and get them to the board.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

jms:endpoint role="consumer" versus jms:consumer

2007-05-07 Thread Gert Vanthienen


L.S.,

While I was trying to get automatic reconnect to a JMS broker (WebSphere 
MQ which is restarted at least once per week) up and running with 
, I noticed the possibility of using 
 to specify JMS message receiving into the ESB.  The 
 uses Spring's DefaultMessageListenerContainer class, 
which provides the auto-reconnect behavior I was looking for. 

My question: why isn't this syntax specified in any of the docs or used 
in any of the archetypes?  Is the  deprecated or is the 
documentation incomplete?


Regards,

Gert

ActiveMQ configuration

2007-05-07 Thread Gert Vanthienen


L.S.,

After having attended Bruce's talk on ActiveMQ (which was very 
interesting, btw) at ApacheCon last Friday, I took a quick look at how 
ActiveMQ is configured within ServiceMix.  I had understood from this 
talk that it wouldn't be a good idea to use a multicast configuration 
when running in production, but this seems to be the default 
configuration for ActiveMQ in ServiceMix.  Shouldn't we change this into 
something more production-ready or at least have some kind of caveat in 
the documentation somewhere?


Gert

Just a quick patch

2007-05-06 Thread Gert Vanthienen


Just a quick patch for a typo in one of the pom.xml files...


Index: samples/loan-broker/pom.xml
===
--- samples/loan-broker/pom.xml	(revision 535642)
+++ samples/loan-broker/pom.xml	(working copy)
@@ -84,7 +84,7 @@
 
 
   loan-broker-lw-su
-  loan-broker-ope-su
+  loan-broker-ode-su
   loan-broker-jms-su
   loan-broker-sa

[jira] Updated: (SM-902) File Binding example error with JaxenStringXPathExpression

2007-04-30 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SM-902:
---

Attachment: SM-902-with-flag.patch

Is this the kind of patch you're looking for?

The useMessageContent="false" attribute can be used to signal that an 
Expression doesn't access the message content, so no conversion will be done.

>  File Binding example error with JaxenStringXPathExpression 
> 
>
> Key: SM-902
> URL: https://issues.apache.org/activemq/browse/SM-902
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-components
>Affects Versions: 3.1
> Environment: window xp, java1.5, 
>Reporter: Sangwoo Han
>Priority: Minor
> Attachments: SM-902-with-flag.patch, SM-902.patch
>
>
> I have tried example-file binding with servicemix3.1 (latest version) 
> and the file generated in outbox was empty !! size zero ! 
> So I commented out the rename part (filename property with 
> JaxenStringXPathExpression) 
> and it generated file with original file content. It worked !! 
> Guillaume Nodet(gnodet) suspects a problem with the input stream which is not 
> converted before evaluating 
> the expression.
> ==
>   
>  
>
>
>class="org.apache.servicemix.components.util.DefaultFileMarshaler"> 
>  
>   
>
> 
>   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SM-902) File Binding example error with JaxenStringXPathExpression

2007-04-27 Thread Gert Vanthienen (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39050
 ] 

Gert Vanthienen commented on SM-902:


I have run into the same issue once again, now while building an Auditor which 
wants to save all messages being handled by ServiceMix to the disk.  From the 
moment I read the message content, the stream becomes unusable, so it's 
impossible to read it for auditing purposes and again within the service that 
actually needs the contents.

Wouldn't it be better to change our NormalizedMessageImpl to that it 
automatically transforms any (not-rereadable) StreamSource being set into e.g. 
a StringSource to solve all these types of problems in one move?  Or would that 
be too much of a performance overhead?

>  File Binding example error with JaxenStringXPathExpression 
> 
>
> Key: SM-902
> URL: https://issues.apache.org/activemq/browse/SM-902
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-components
>Affects Versions: 3.1
> Environment: window xp, java1.5, 
>Reporter: Sangwoo Han
>Priority: Minor
> Attachments: SM-902.patch
>
>
> I have tried example-file binding with servicemix3.1 (latest version) 
> and the file generated in outbox was empty !! size zero ! 
> So I commented out the rename part (filename property with 
> JaxenStringXPathExpression) 
> and it generated file with original file content. It worked !! 
> Guillaume Nodet(gnodet) suspects a problem with the input stream which is not 
> converted before evaluating 
> the expression.
> ==
>   
>  
>
>
>class="org.apache.servicemix.components.util.DefaultFileMarshaler"> 
>  
>   
>
> 
>   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SM-932) Enable PMD/CheckStyle for binding components

2007-04-26 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SM-932:
---

Attachment: SM-932-http-part2.patch

Additional http patch file to provide the missing AbstractProcessor file

> Enable PMD/CheckStyle for binding components
> 
>
> Key: SM-932
> URL: https://issues.apache.org/activemq/browse/SM-932
> Project: ServiceMix
>  Issue Type: Task
>  Components: servicemix-file, servicemix-ftp, servicemix-http, 
> servicemix-jms, servicemix-truezip
>    Reporter: Gert Vanthienen
>Priority: Minor
> Attachments: SM-932-file.patch, SM-932-ftp.patch, 
> SM-932-http-part2.patch, SM-932-http.patch, SM-932-jms.patch, 
> SM-932-truezip.patch, SM-932-xmpp.patch
>
>
> PMD/CheckStyle should be enabled for binding components

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SM-935) Allow to specify additional JNDI properties

2007-04-16 Thread Gert Vanthienen (JIRA)

Allow to specify additional JNDI properties
---

 Key: SM-935
 URL: https://issues.apache.org/activemq/browse/SM-935
 Project: ServiceMix
  Issue Type: New Feature
  Components: servicemix-jms
Affects Versions: 3.1
Reporter: Gert Vanthienen
Priority: Minor


In addition to using initialContext and jndiProviderUrl to configure a JMS 
endpoint, it should be possible to specify additional JNDI properties (e.g 
{{java.naming.security.principal}}, {{java.naming.security.credentials}})



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SM-915) FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()

2007-04-13 Thread Gert Vanthienen (JIRA)


[ 
https://issues.apache.org/activemq/browse/SM-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39005
 ] 

Gert Vanthienen commented on SM-915:


On the commons mailing list, Rory Winston suggested to upgrade to 
commons-net-2.0 RC, because it contains fixes for various threading issues.  It 
is available at 
http://people.apache.org/~rwinston/commons-net-2.0/commons-net-ftp-2.0.0-SNAPSHOT.jar

However, it requires JDK5/6 and it is not a simple replacement for the current 
commons-net-1.4.x.jar (API changes).

> FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
> 
>
> Key: SM-915
> URL: https://issues.apache.org/activemq/browse/SM-915
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-ftp
>Affects Versions: 3.1
>    Reporter: Gert Vanthienen
> Attachments: SM-915.patch
>
>
> FTP poller threads stop working with the stack trace below, causing the FTP 
> client pool to run out of connections
> {code}
> Name: pool-component.servicemix-ftp-thread-2
> State: RUNNABLE
> Total blocked: 78,430  Total waited: 4,771
> Stack trace: 
> java.net.PlainSocketImpl.socketAccept(Native Method)
> java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
> java.net.ServerSocket.implAccept(ServerSocket.java:450)
> java.net.ServerSocket.accept(ServerSocket.java:421)
> 
> org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:502)
> 
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
> 
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
> 
> org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:211)
> 
> org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:203)
> 
> org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:78)
> 
> org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
> 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> java.lang.Thread.run(Thread.java:595)
> {code}
> See http://www.nabble.com/FTP-poller-stalls...-tf3490690s12049.html for more 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SM-932) Enable PMD/CheckStyle for binding components

2007-04-13 Thread Gert Vanthienen (JIRA)


 [ 
https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SM-932:
---

Attachment: SM-932-http.patch

The last patch file (*-http) contains all necessary modifications for 
servicemix-http.  It also contains the updated pom.xml for the binding 
components.

Just a few remarks:
* I have used some J2SE 5.0 constructs (varargs, generics, ...) during the 
cleanup (e.g. to reduce the amount of code per method).  If you still want to 
be 1.4-compliant, these have to be modified
* SslParameters contains a call to hash(String... strings).  If I don't enclose 
the parameters to this call in a new String[] { }, PMD (incorrectly) complains 
about an unused private method

> Enable PMD/CheckStyle for binding components
> 
>
> Key: SM-932
> URL: https://issues.apache.org/activemq/browse/SM-932
> Project: ServiceMix
>  Issue Type: Task
>  Components: servicemix-file, servicemix-ftp, servicemix-http, 
> servicemix-jms, servicemix-truezip
>    Reporter: Gert Vanthienen
>Priority: Minor
> Attachments: SM-932-file.patch, SM-932-ftp.patch, SM-932-http.patch, 
> SM-932-jms.patch, SM-932-truezip.patch, SM-932-xmpp.patch
>
>
> PMD/CheckStyle should be enabled for binding components

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: virtualised Linux or AIX LPAR provided by IBM

2007-04-12 Thread Gert Vanthienen


L.S.,


I have never worked with AIX before, but ServiceMix does work fine on an 
IBM System i (aka AS/400 -- very similar in hardware), both under OS/400 
and Linux (LPAR). It also works on AIX (recently fixed some problems 
with the startup script), so I don't expect any problems with your setup.



Regards,

Gert Vanthienen


bradburyn wrote:

has anyone used or know of any problems with servicemix in a virtualised
linux enviroment. we will be using websphere community version.

thanks

[jira] Updated: (SM-932) Enable PMD/CheckStyle for binding components


 [ 
https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SM-932:
---

Attachment: SM-932-file.patch

SM-932-file.patch fixes PDM/CheckStyle errors for servicemix-ftp

> Enable PMD/CheckStyle for binding components
> 
>
> Key: SM-932
> URL: https://issues.apache.org/activemq/browse/SM-932
> Project: ServiceMix
>  Issue Type: Task
>  Components: servicemix-file, servicemix-ftp, servicemix-http, 
> servicemix-jms, servicemix-truezip
>    Reporter: Gert Vanthienen
>Priority: Minor
> Attachments: SM-932-file.patch
>
>
> PMD/CheckStyle should be enabled for binding components

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SM-932) Enable PMD/CheckStyle for binding components

Enable PMD/CheckStyle for binding components


 Key: SM-932
 URL: https://issues.apache.org/activemq/browse/SM-932
 Project: ServiceMix
  Issue Type: Task
  Components: servicemix-file, servicemix-ftp, servicemix-http, 
servicemix-jms, servicemix-truezip
Reporter: Gert Vanthienen
Priority: Minor


PMD/CheckStyle should be enabled for binding components

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Commented: (SM-931) PMD/CheckStyle errors for servicemix-eip

2007-04-11 Thread Gert Vanthienen


Thomas,

Perhaps we should create JIRA issues for all modules that still need to 
be corrected and use 'In progress' to avoid doing every component twice...


Gert

Thomas Termin (JIRA) wrote:
[ https://issues.apache.org/activemq/browse/SM-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38988 ] 


Thomas Termin commented on SM-931:
--

Gert,

I'm currently working on this but you were faster. :-)

  

PMD/CheckStyle errors for servicemix-eip


Key: SM-931
URL: https://issues.apache.org/activemq/browse/SM-931
Project: ServiceMix
 Issue Type: Bug
 Components: servicemix-eip
   Reporter: Gert Vanthienen
   Priority: Minor
Attachments: SM-931.patch


Build fails with PMD/CheckStyle enabled for servicemix-eip

[jira] Created: (SM-931) PMD/CheckStyle errors for servicemix-eip

PMD/CheckStyle errors for servicemix-eip


 Key: SM-931
 URL: https://issues.apache.org/activemq/browse/SM-931
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-eip
Reporter: Gert Vanthienen
Priority: Minor
 Attachments: SM-931.patch

Build fails with PMD/CheckStyle enabled for servicemix-eip

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SM-931) PMD/CheckStyle errors for servicemix-eip


 [ 
https://issues.apache.org/activemq/browse/SM-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SM-931:
---

Attachment: SM-931.patch

On my machine, this patch fixes the build

> PMD/CheckStyle errors for servicemix-eip
> 
>
> Key: SM-931
> URL: https://issues.apache.org/activemq/browse/SM-931
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-eip
>    Reporter: Gert Vanthienen
>Priority: Minor
> Attachments: SM-931.patch
>
>
> Build fails with PMD/CheckStyle enabled for servicemix-eip

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SM-902) File Binding example error with JaxenStringXPathExpression