[jira] [Resolved] (BSF-44) Un-thrown exception

[Rony G. Flatscher (JIRA)]

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

Rony G. Flatscher resolved BSF-44.
--
Resolution: Invalid

Working as designed.

> Un-thrown exception
> ---
>
> Key: BSF-44
> URL: https://issues.apache.org/jira/browse/BSF-44
> Project: Commons BSF
>  Issue Type: Bug
>Reporter: Jaechang Nam
>Assignee: Rony G. Flatscher
>Priority: Trivial
>
> There is an un-thrown exception (BadArgumentException) in 
> src/main/java/org/apache/bsf/engines/netrexx/NetRexxEngine.java (found from 
> the current snapshot, f8eeaf2f8dd69e49b094b16b5c4d660c40f6be74). I have no 
> idea if it is intended to do so. But thought it could be worth to report in 
> case.
> {code}
> 128 public NetRexxEngine ()
> 129 {
> 130 // handle logger
> 131 logger = BSF_LogFactory.getLog(this.getClass().getName());
> 132 /*
> 133   The following line is intended to cause the constructor to
> 134   throw a NoClassDefFoundError if the NetRexxC.zip dependency
> 135   is not resolved.
> 136 
> 137   If this line was not here, the problem would not surface until
> 138   the actual processing of a script. We want to know all is well
> 139   at the time the engine is instantiated, not when we attempt to
> 140   process a script.
> 141   */
> 142 
> 143 new netrexx.lang.BadArgumentException();
> 144 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (BSF-44) Un-thrown exception

[Rony G. Flatscher (JIRA)]

[ 
https://issues.apache.org/jira/browse/BSF-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15787528#comment-15787528
 ] 

Rony G. Flatscher commented on BSF-44:
--

Thank you for your observation. However, looking at the code and its remarks it 
becomes clear that this was intentionally coded as is. If the netrexx package 
was not available the statement will cause an exception while creating an 
instance of the NetRexx BSF engine, otherwise creating an instance of the 
NetRexx engine would appear to have worked, causing an exception later, when 
the first script gets executed.

If you are (considering, interested in) employing NetRexx scripts you may want 
to consult the NetRexx community which is in the process of moving to 
Sourceforge at: .


> Un-thrown exception
> ---
>
> Key: BSF-44
> URL: https://issues.apache.org/jira/browse/BSF-44
> Project: Commons BSF
>  Issue Type: Bug
>Reporter: Jaechang Nam
>Assignee: Rony G. Flatscher
>Priority: Trivial
>
> There is an un-thrown exception (BadArgumentException) in 
> src/main/java/org/apache/bsf/engines/netrexx/NetRexxEngine.java (found from 
> the current snapshot, f8eeaf2f8dd69e49b094b16b5c4d660c40f6be74). I have no 
> idea if it is intended to do so. But thought it could be worth to report in 
> case.
> {code}
> 128 public NetRexxEngine ()
> 129 {
> 130 // handle logger
> 131 logger = BSF_LogFactory.getLog(this.getClass().getName());
> 132 /*
> 133   The following line is intended to cause the constructor to
> 134   throw a NoClassDefFoundError if the NetRexxC.zip dependency
> 135   is not resolved.
> 136 
> 137   If this line was not here, the problem would not surface until
> 138   the actual processing of a script. We want to know all is well
> 139   at the time the engine is instantiated, not when we attempt to
> 140   process a script.
> 141   */
> 142 
> 143 new netrexx.lang.BadArgumentException();
> 144 }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (BSF-43) Exception while executing the javascript from xslt

[Rony G. Flatscher (JIRA)]

[ 
https://issues.apache.org/jira/browse/BSF-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033552#comment-15033552
 ] 

Rony G. Flatscher commented on BSF-43:
--

The Apache Xalan project together with information, mailing lists etc. can be 
found here: .

> Exception while executing the javascript from xslt
> --
>
> Key: BSF-43
> URL: https://issues.apache.org/jira/browse/BSF-43
> Project: Commons BSF
>  Issue Type: Bug
>Reporter: sravya
>Priority: Critical
>
> I am gettingjavax.xml.transform.TransformerException: Could not initialize 
> BSF Manager exception while executing the javascript from xslt.
> I included bfs 2.4.jar,js 1.7.jar,xalan 2.7.jar



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (BSF-43) Exception while executing the javascript from xslt

[Rony G. Flatscher (JIRA)]

[ 
https://issues.apache.org/jira/browse/BSF-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033493#comment-15033493
 ] 

Rony G. Flatscher commented on BSF-43:
--

Thank you for supplying more information!

Looking at the exception and the stack trace there is no involvement of BSF 
that would be causing it. The exception 
"javax.xml.transform.TransformerConfigurationException" points at a problem 
where the error message hints that the argument to the getdate() function 
should be an object reference, cf.: "20:37:25,465 ERROR [main] 
JAXPSAXProcessorInvoker - The first argument to the non-static Java function 
'getdate' is not a valid object reference.".

Your observation that while debugging you get 

"... below exception:
Caused by: javax.xml.transform.TransformerException: Could not initialize BSF 
Manager
   at 
org.apache.xalan.extensions.ExtensionHandlerGeneral.(ExtensionHandlerGeneral.java:216)
   ... 21 more", 

may be caused by your debugging configuration. 

As the class is defined in the package org.apache.xalan package and not in the 
org.apache.bsf package, I would advise to approach the xalan project for 
documentation and help with this particular issue.



 



> Exception while executing the javascript from xslt
> --
>
> Key: BSF-43
> URL: https://issues.apache.org/jira/browse/BSF-43
> Project: Commons BSF
>  Issue Type: Bug
>Reporter: sravya
>Priority: Critical
>
> I am gettingjavax.xml.transform.TransformerException: Could not initialize 
> BSF Manager exception while executing the javascript from xslt.
> I included bfs 2.4.jar,js 1.7.jar,xalan 2.7.jar



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (BSF-43) Exception while executing the javascript from xslt

[Rony G. Flatscher (JIRA)]

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

Rony G. Flatscher resolved BSF-43.
--
Resolution: Invalid

There is no exception that is thrown by the org.apache.bsf package, hence this 
report with the supplied information makes it invalid in the context of the BSF 
project.

> Exception while executing the javascript from xslt
> --
>
> Key: BSF-43
> URL: https://issues.apache.org/jira/browse/BSF-43
> Project: Commons BSF
>  Issue Type: Bug
>Reporter: sravya
>Priority: Critical
>
> I am gettingjavax.xml.transform.TransformerException: Could not initialize 
> BSF Manager exception while executing the javascript from xslt.
> I included bfs 2.4.jar,js 1.7.jar,xalan 2.7.jar



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (BSF-43) Exception while executing the javascript from xslt

[Rony G. Flatscher (JIRA)]

[ 
https://issues.apache.org/jira/browse/BSF-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032033#comment-15032033
 ] 

Rony G. Flatscher commented on BSF-43:
--

You would need to supply a few more pieces of information, like

- what exception is thrown where (stack trace?),
- supply a script that demonstrates the problem,
- where did you get the jars from.

The more precise your information the more likelier that a cause can be 
identified, and if in BSF 2.4, a fix for it.

---rony

> Exception while executing the javascript from xslt
> --
>
> Key: BSF-43
> URL: https://issues.apache.org/jira/browse/BSF-43
> Project: Commons BSF
>  Issue Type: Bug
>Reporter: sravya
>Priority: Critical
>
> I am gettingjavax.xml.transform.TransformerException: Could not initialize 
> BSF Manager exception while executing the javascript from xslt.
> I included bfs 2.4.jar,js 1.7.jar,xalan 2.7.jar



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (BSF-42) Exception while executing the javascript from xslt

[Rony G. Flatscher (JIRA)]

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

Rony G. Flatscher closed BSF-42.

Resolution: Duplicate

> Exception while executing the javascript from xslt
> --
>
> Key: BSF-42
> URL: https://issues.apache.org/jira/browse/BSF-42
> Project: Commons BSF
>  Issue Type: Bug
>Reporter: sravya
>Priority: Critical
>
> I am gettingjavax.xml.transform.TransformerException: Could not initialize 
> BSF Manager exception while executing the javascript from xslt.
> I included bfs 2.4.jar,js 1.7R3.jar,xalan 2.7.jar



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (BSF-42) Exception while executing the javascript from xslt

[Rony G. Flatscher (JIRA)]

[ 
https://issues.apache.org/jira/browse/BSF-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032027#comment-15032027
 ] 

Rony G. Flatscher commented on BSF-42:
--

This looks exactly like BSF-43, hence closing this issue, please see comment 
with BSF-43.

> Exception while executing the javascript from xslt
> --
>
> Key: BSF-42
> URL: https://issues.apache.org/jira/browse/BSF-42
> Project: Commons BSF
>  Issue Type: Bug
>Reporter: sravya
>Priority: Critical
>
> I am gettingjavax.xml.transform.TransformerException: Could not initialize 
> BSF Manager exception while executing the javascript from xslt.
> I included bfs 2.4.jar,js 1.7R3.jar,xalan 2.7.jar



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (BSF-41) Memory leak when terminating engines in long running programs

[Rony G. Flatscher (JIRA)]

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

Rony G. Flatscher resolved BSF-41.
--
   Resolution: Fixed
Fix Version/s: BSF-2.5

Fixed with revision 1648600 on 20141230.

> Memory leak when terminating engines in long running programs
> -
>
> Key: BSF-41
> URL: https://issues.apache.org/jira/browse/BSF-41
> Project: Commons BSF
>  Issue Type: Bug
>  Components: BSF-2.x
>Reporter: Rony G. Flatscher
>Assignee: Rony G. Flatscher
> Fix For: BSF-2.5
>
>
> When terminating a BSF engine using BSFManager.terminate() the BSF engine is 
> not removed from the PropertyChange listener causing a memory leak in long 
> running programs that create multifold BSF engine instances.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (BSF-41) Memory leak when terminating engines in long running programs

[Rony G. Flatscher (JIRA)]

Rony G. Flatscher created BSF-41:


 Summary: Memory leak when terminating engines in long running 
programs
 Key: BSF-41
 URL: https://issues.apache.org/jira/browse/BSF-41
 Project: Commons BSF
  Issue Type: Bug
  Components: BSF-2.x
Reporter: Rony G. Flatscher


When terminating a BSF engine using BSFManager.terminate() the BSF engine is 
not removed from the PropertyChange listener causing a memory leak in long 
running programs that create multifold BSF engine instances.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)